 |
Are we going to notice a difference between 10 contacts and 11? 12? 13? Why do you think 10 is "definitely too low"? I can see where there'd be a difference between 2 contacts and 10, but I suspect id set a cutoff at 10 because it was enough to calculate a reasonable estimate for the physics, and counts larger than that wouldn't change much. id categorized their physics as "good enough". Unless there are specific situations that are absolutely wonky, I wouldn't spend any time on a general fix; I'd just focus on the wonkiness. |
 |
Because if the player stacks 11 items on a moveable plate in my map, only 10 items get activated if the plate/blocks moves. If the player stacks (or there are) more than 11 items, even more are left floating. The same would probably be true for elevators in normal TDM FMs. Anywhere a mover has more than 10 contacts and starts to move, some of them will not get activated. |
 |
Has anyone ever reported an actual example of this causing a problem? I'm not aware of any. And we've seen videos of massive stacks of crates all falling properly when the bottom one is removed--I can't recall ever seeing anything just left floating. |
|
|
Okay, I read this report the wrong way. I assumed it had something to do with friction. Now that I'm seeing it for what it really is, I agree that the limit should be removed. |
|
|
@Springheel: It only occurs with movers + their contacts. A crate sitting on a crate is a "moveable touching a moveable", not a "moveable touching a mover". This is a small, but important distinction, as the code handles both cases in different places and differently. The limit of 10 only occurs in the latter case. |
 |
Revision 7136 Increased limit to 128 |
 |
The limit was only increased in idEntity::ActivateContacts. However, there are other calls of gameLocal.clip.Contacts, which still use limit = 10: idPhysics_Base::AddGroundContacts idPhysics_AF::EvaluateContacts idPhysics_RigidBody::EvaluateContacts And this limit is not enough sometimes, leading to unknown consequences.... I have changed it in the following series of commits: r9343. Increased maximum number of contacts in physics from 10 to 32. r9344. Maximum supported number of contacts in idEntity::ActivateContacts reduced back from 128 to 32. r9345. Now size of contacts array in all gameLocal.clip.Contacts calls is set to CONTACTS_MAX_NUMBER = 32. The behavior does not change, it is only minor refactoring. So now the limit is 32 for all calls. My commits also rely on idRaw hack to avoid zeroing these arrays without need: r9341. Added idRaw<T> hack which can be used to avoid idVec3 filling for large local variables. These changes will take effect in TDM 2.10. |
- Anonymous
