Gamestudio Links
Zorro Links
Newest Posts
Change chart colours
by 7th_zorro. 05/11/24 09:25
Data from CSV not parsed correctly
by dr_panther. 05/06/24 18:50
AUM Magazine
Latest Screens
The Bible Game
A psychological thriller game
SHADOW (2014)
DEAD TASTE
Who's Online Now
1 registered members (AndrewAMD), 1,310 guests, and 1 spider.
Key: Admin, Global Mod, Mod
Newest Members
Hanky27, firatv, wandaluciaia, Mega_Rod, EternallyCurious
19051 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Page 4 of 4 1 2 3 4
Re: Please submit bugs and omissions here [Re: Rocko75] #24630
05/06/04 07:59
05/06/04 07:59
Joined: Sep 2003
Posts: 3,236
San Diego, CA
M
Marco_Grubert Offline OP
Expert
Marco_Grubert  Offline OP
Expert
M

Joined: Sep 2003
Posts: 3,236
San Diego, CA
Okay, that explains the problem. What happens is that the hood partially enters the level block and then creates lots of contact points (polygon-polygon) depending on how far inside the block it is these contacts may be impossible to satisfy at the same time. Workarounds: don't use PH_POLY but rather PH_BOX for your car. This greatly reduces the number of contacts created. Decrease the CFM and increase the ERP values to make the car less squishy so it does not penetrate the level block as much. Check for EVENT_FRICTION and reduce forward motion while the car collides with the block.


Here's a quick overview of how penetration tests are done in A6:
There are two kinds of collision tests. One test is done at the beginning of each frame and when objects are slightly (!) intersecting the physics system limits the movement in that direction by a certain amount, (depends on setcorrections and constraint properties). If they are deeply intertwined or have a high polycount (with PH_POLY set) this creates lots of contact points that can become impossible to satisfy. E.g. two boxes at the same spot perfectly aligned would yield contacts in +X,-X,+Y,-Y,+Z, and -Z directions - where to go from there? Usually it's not as bad, yet bad enough to cause an explosion.

When no collision is detected at the beginning of the frame (e.g. they are 0.1 quants apart) the object is free to move in that direction. This would allow fast moving objects to be at position x before and at position x+wall_thickness after the physics update. To prevent object penetration I use c_trace to check whether the object's center has intersected a wall and if so move the object back a few quants so that it's bounding sphere touches the wall. This can fail because the object's center may not penetrate an object but the object's perimeter does penetrate it to a great degree (remember that small penetration is good, large penetration is bad).

Re: Please submit bugs and omissions here [Re: Marco_Grubert] #24631
05/06/04 18:37
05/06/04 18:37
Joined: Feb 2004
Posts: 39
Stuttgart, Germany
Rocko75 Offline
Newbie
Rocko75  Offline
Newbie

Joined: Feb 2004
Posts: 39
Stuttgart, Germany
Quote:

Check for EVENT_FRICTION and reduce forward motion while the car collides with the block.




I checked EVENT_FRICTION but this only works with collisions between Models, so a collision with the level is not detected at all!

Re: Please submit bugs and omissions here [Re: Rocko75] #24632
05/07/04 00:44
05/07/04 00:44
Joined: Mar 2003
Posts: 5,377
USofA
fastlane69 Offline
Senior Expert
fastlane69  Offline
Senior Expert

Joined: Mar 2003
Posts: 5,377
USofA
Quote:

(remember that small penetration is good, large penetration is bad).






Not according to my girlfriends.

Page 4 of 4 1 2 3 4

Moderated by  HeelX, Spirit 

Gamestudio download | chip programmers | Zorro platform | shop | Data Protection Policy

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) opgroup.de

Powered by UBB.threads™ PHP Forum Software 7.7.1