 |
Note that if you do not run when jumping, then mantling triggers properly. Perhaps some collision request fails when player model is touching the awning (just a guess). |
|
|
In order to start mantling, a trace of very thin vertical cylinder against world is performed (see idPhysics_Player::MantleTargetTrace). Unfortunately, it fails in the current case (no collision is returned), hence mantling is not initiated, hence player flies into the awning. In the considered case this trace must return edge-edge collision: vertical edge of the player's trm cylinder collides into the horizontal edge of the awning. Note that no other type of collision is present here: only edge-edge collision can be found. The reason why the collision is not found is: the edges of the awning are considered "internal" by collision model manager. The edge of collision model is considered internal when it is a reflex angle between two faces (or the two faces are coplanar and the edge goes inside the face). The internal edges are ignored in edge-edge collision detection as an optimization, because if it generates a collision, there must be some other (more relevant) collision present too. There are two ways to prove that erroneous internal edges cause the issue: 1. Set "g_drawCollisionModels 1" and "cm_drawInternal 1". Now edges of collision models are drawn: internal ones are green, others are red. Notice that the awning consists of green edges (see attached screenshot NewJob_AwningMantle_InternalEdges). 2. Comment line 2930 in CollisionModel_load.cpp (FindInternalEdges call in idCollisionModelManagerLocal::FinishModel). Then the issue disappears. |
|
|
As far as I understand, this model is: atdm:ext_timber01_window01_awning And its def points to: "models/darkmod/architecture/modules/exteriors/ext_timber01/ext_timber01_window01_awning.lwo" However, I don't know where collision model comes from... |
|
|
Ok, the problem is caused by double geometry: the problematic part of collision model contains two equal boxes. So this is double geometry, which causes problems in current collision models manager, according to comment in idCollisionModelManagerLocal::FindInternalEdgesOnPolygon: // FIXME: doubled geometry causes problems |
 |
Should be fixed now, at least for that specific model. |
|
|
The model was changed in rev 15062. This issue can be closed. |
- Anonymous
