Bug in Physical Response on Tiled Actors ?

Non-platform specific questions.

Bug in Physical Response on Tiled Actors ?

Postby fauldran » Sat Mar 18, 2006 9:02 am

It seems that if you try to use Physical Response in a collision event on a tiled actor strange things happen.

http://www.darkspiregames.com/physResp_demo.zip

The sample .ged demonstrates four scenarios for using Physical Response.
To interact with demo simply click somewhere to make player_base move to that location.

There are two ways to use physical response: on the actor you want to bounce or on the actor you want to bounce off of.

:D scenario 1: (on the actor you want to bounce)
wall_A is setup so that a collision event on player_base executes a physical response causing the player_base bounce off of wall_A. This works great.

:D scenario 2: (on the actor you want to bounce off of)
wall_B is setup so that a collision event on wall_B executes a physical response and causes the player to bounce off wall_B. This works great.

In the next two scenarios we introduce tiled actors. wall_C and wall_D are both tiled.

:!: scenario 3: (on the actor you want to bounce off of)
wall_C is setup so that a collision event on wall_C executes a physical response and attempts to cause the player to bounce off wall_C. This however rarely happens. Instead player_base gets pulled inside wall_C and then trapped. bogus. The only difference between this and scenario 2 is that wall_C is tiled and wall_B is not.

:D scenario 4: (on the actor you want to bounce)
wall_D is setup so that a collision event on player_base executes a physical response and causes the player to bounce off wall_D. This works great.

The Point:
for my particular project the setup in scenario three is the most code/time effective. Unfortunately it does not seem to behave as expected. The above tests establish the method by which physical response is employed should work. (as indicated by scenario 2) My game contains many wall objects and it will be a pain to setup a physical response on player_base for each one of them especially when I should only have to do it once on a source_wall actor. Then all other walls could just inherit events from source_wall.

So...

:?: Is the behavior in scenario 3 a bug?

P.S.
Sorry if this is a rambling question, answered elsewhere, or doesn’t make sense. Its like 3:00AM and I doubt I am thinking clearly.
:?
Thanks.
Fauldran
Image
fauldran
 
Posts: 43
Joined: Tue Dec 20, 2005 10:52 am
Score: 0 Give a positive score

Postby makslane » Mon Mar 20, 2006 2:16 pm

I can't see the problem here, but you can try change the mass values.
makslane
Site Admin
 
Posts: 3947
Joined: Sat Apr 05, 2003 6:47 pm
Score: 182 Give a positive score

Postby fauldran » Mon Mar 20, 2006 8:56 pm

If you run the red dot into wall_C over and over eventually it till slip inside of the wall and get stuck. I have tried Event Actor mass as 1, 10, 100, and 1000 and it still happens. The opposite setup on wall_D works fine though. I willl just use the wall_D setup.
Fauldran
Image
fauldran
 
Posts: 43
Joined: Tue Dec 20, 2005 10:52 am
Score: 0 Give a positive score

Postby DilloDude » Sat Apr 15, 2006 8:23 am

I had noticed this problem too. I will try the scenario 4 method and see if it works better.
Image
User avatar
DilloDude
 
Posts: 866
Joined: Tue Jan 24, 2006 9:51 am
Location: Nyerellion
Score: 58 Give a positive score


Return to General

Who is online

Users browsing this forum: No registered users and 1 guest