Hello!

I'm working on a little game that has a girl on a swing. I'm using the physics engine to handle the swing's motion. At the moment, the girl is a separate entity than the swing. I only have the Commercial version of GameStudio, so I only have one physics object available.

My question is, what's the best way to have the girl stay on the swing? At the moment, the swing entity (with physice) keeps colliding with the girl entity. Is there any way to tell the physics engine that the girl should NOT be considered when doing collision detection? I've tried the .push attribute, but it doesn't seem to help.

One solution is to make the girl and swing "one". (How Zen!) I'd like to hear other solutions before I resort to doing that.

Thanks!
- Bret

Hmmmm....

My impression is that that registering an object as a physics object nullifies the possibility of doing this by setting .passable flags and such.

How about having the girl have a constant ent_move update routine that places her maybe 5 quants above and 5 quants forward of the swing.

This way, as the swing swings, the girl will always be moved to be relative to the swing.

maybe this will work??

why don't you make the girl passable?

I think that setting passable will make the girl passable to ent_moves, but not the PE based moves.

Worth a check though...

Oh, talk about embarrassed. Making the girl passable worked great. I don't know why I didn't try that before posting. My apologies.

Thank you Ventilator and fastlane69 for your responses.
- Bret

I am so confused as to which flags work with PE and which don't.

I wish the manual was a bit clearer as to what effect the flags have and don't have under ent_move and the PE.

Tack ".passable" onto the PE usable list