Realistic Rope Physics(example), works in LITE with modification Options

[ditdingiscool]

• Title: advanced rope physics
• Description: realistic(ish) ropes
• GM Version: gm7
• Registered: no, see aditional information
• File Type: gmk
• File Size: 20kb
• File Link: http://www.box.net/shared/3l42rtc6bg

Additional Info
for lite users:this wont work unles you replace all the ds-lists with arrays...

EDIT: READ THIS>>> uploaded my old version... new version at the link above, waaay better than the old one sorry if this caused any inconvenience to you guys, all my replies are made with the new version in mind, so sorry for any incorrect information...

EDIT2:you can read how this works on my blog(click the banner in mys sig)

This post has been edited by ditdingiscool: Mar 11 2009, 02:35 PM

[Dark Mario]

How does the plugs work?

[toopz]

This is just plain cool man. I think I'm gonna use this. Only few questions I have is if there's a way to adjust the resolution of the ropes. It wasn't very noticeable, but I did nonetheless noticed some clear segments in the ropes when I moved them quickly. Though I think it's at a good balance of detail vs speed, it would still be a good thing to know I suppose.

Good work

[Newly Discovered]

Agreed. this is pretty awesome. I love wire engines. you could bring this pretty far.
maybe come up with more devices, and some explanation on what's in here.

anyway, I love it.

[gloinus]

Nope, doesn't work in lite.

[ditdingiscool]

@gloinus in the screens2 object in the step event, remove the "scr2.image_angle=point_direction(obj1.x,obj1.
y,obj2.x,obj2.y)" line, this should be the only pro thing in there...

@toopz there is a way to change resolution, when you look at the 'create_rope' script, there is a short explanation of the function:
create_rope(x1,y1,x2,y2,nodes,maxlen)
where the 'nodes' argument changes the amount off segments, so when an instance creates a rope it calls that function, for example the screens object calls it two times in the create event, so you can change the resolution there...

@Dark Mario you mean the points where the rope is fixed to something?, a rope consists of one 'rope' object, and multiple 'dot' objects, when you create a rope, the create_rope() functions returns the id off the rope object, which contains a ds-list with all dot objects in it, you use this to find the correct dot, and then set the 'fixed' variable to true for that dot, this prevents it from falling, and you can just set the x/y coordinates off that dot,

@gloinus, @toopz and Dark mario, these comments are for the wrong version, please re-download for the new version, sorry for that...

if someone still has questions/suggestions, please comment...

This post has been edited by ditdingiscool: Feb 17 2009, 05:26 PM

[Dark Mario]

@ ditdingiscool

What I meant is how does the demo (sending information) works.
Example: If I connect 3 then + then 5 the graph.
Thats what i meant.

[ditdingiscool]

@ ditdingiscool

What I meant is how does the demo (sending information) works.
Example: If I connect 3 then + then 5 the graph.
Thats what i meant.

yeah i realized that i posted the wrong version, the new one has smaller example but the same type off deal could be made with the new one,
and now for the answer:
the plug that is created keeps track off the currect value, and makes sure the other plug also has this value, then the other objects set/get the values for the plugs, it's realy simple actualy. you just have to make sure that when the value off the first plug changes the second plug should change with it...

[chocoblock]

wow nice engine i wish i could make something like that.

[ditdingiscool]

wow nice engine i wish i could make something like that.

it's not that hard to make, and this can actualy do more than only ropes, if you can get the dot object to collision with a wall object you could make softbody physics with this...
i can't even make a working platform engine, so this is easier to make than al those mario/sonic/whatever clones

This post has been edited by ditdingiscool: Feb 21 2009, 10:31 AM

[2d_games]

wow nice engine i wish i could make something like that.

it's not that hard to make, and this can actualy do more than only ropes, if you can get the dot object to collision with a wall object you could make softbody physics with this...
i can't even make a working platform engine, so this is easier to make than al those mario/sonic/whatever clones

I can't make physics like this but I can platform engines with ease.

I'm not sure this could work in lite though. It uses the ds_list functions...

[ditdingiscool]

wow nice engine i wish i could make something like that.

it's not that hard to make, and this can actualy do more than only ropes, if you can get the dot object to collision with a wall object you could make softbody physics with this...
i can't even make a working platform engine, so this is easier to make than al those mario/sonic/whatever clones

I can't make physics like this but I can platform engines with ease.

I'm not sure this could work in lite though. It uses the ds_list functions...

those work in lite right?
*searches manual*
shoot, you're right, man thats stupid, never knew
but you can use this in lite, but then you would need to hard-code the ropes/connections,
or you could re-code it with arrays

[benja]

Please release a lite version.

[ditdingiscool]

Please release a lite version.

that would be hard, this uses ds-lists, i can give you a piece off core code with which you can achieve the same effects:

CODE

//join(from,to,length)
f=argument0
t=argument1
l=argument2
dis=point_distance(f.x,f.y,t.x,t.y);
dir=point_direction(f.x,f.y,t.x,t.y);
dif=dis-l
if(f.fixed=true or t.fixed=true)
dif=dif*2

if!(f.fixed)
{
f.x+=lengthdir_x(dif/2,dir);
f.y+=lengthdir_y(dif/2,dir);
f.hspeed+=lengthdir_x(dif/2,dir);
f.vspeed+=lengthdir_y(dif/2,dir);
}
if!(t.fixed)
{
t.x+=lengthdir_x(dif/2,dir+180);
t.y+=lengthdir_y(dif/2,dir+180);
t.hspeed+=lengthdir_x(dif/2,dir+180);
t.vspeed+=lengthdir_y(dif/2,dir+180);
}

place that in a script called 'join'with this you can make sure two objects stay at the same distance, note that both the from and the to instance need to have the fixed variable set, just do something like this:

CODE

//dummy object create event
gravity=1
fixed=false

CODE

//control object create event
n1=instance_create(x,y,dummy)
n2=instance_create(x+32,y,dummy)
n1.fixed=true

CODE

//control object step event
join(n1,n2,32)

CODE

//draw event control object
draw_line(n1.x,n1.y,n2.x,n2.y)

that will create a line thats anchored at one end and acts like a pendulum at the other end. the real engine works like that with only one difference:it loops through a set off ds-lists so you don't have to call the join function for each rope section, but since this is not available in light you need to do it manualy or use arrays...

[benja]

Cheers nigga, I'll tell you how it goes