Hey,
thanks for this. In fact the collision detection is prohibitive; the
woodpecker effect is the result of detecting more than one collision -
ie, in both directions with a line, so it bounces back and forward not
knowing which way to apply the radius 'buffer'.
All of our code is using tempx and tempy, deciding whether to move, and
then moving if the way is free - but it's managing the multiple
directions and collisions with multiple objects that's causing us headaches.
Cheers,
J
Andreas Rønning wrote:
Again:
Get input
Calculate where the input will place the character
React to calculation - Either move character or don't. No woodpecker! :D
not
Get input
move character
react post collision
- Andreas
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
