<div>With ODE, it depends on the physics situation.</div>
<div> </div>
<div>With Tri-Mesh and the heightfield collider specifically, ODE generates lots of small effect contacts and then the stepper integrates them all into a contact resolution force. With tri-mesh and the heightfield, depending on how an object collides with another, there could be 20 or 30 contacts that all factor into getting the object to react normally. So, to test, you're going to want to use a stack of 'active'(physical in the client) tri-mesh objects. You may also want two or more trimesh LINKSETS to see how they react.</div>
<div> </div>
<div>My guess, is the first thing that you're going to notice is that a tri-mesh object sitting on another object will become more unstable (vibrate more). Each mini-contact represents a part of the force to keep the object from rotating from the other parts of the contact resolution force. As the effect gets worse, you're going to notice 'rotation anomolies' that occur when objects collide.</div>
<div> </div>
<div>Think of it like... you have a cube shaped trimesh... and the cube's corners are touching a flat ground. In theory, that would generate 4 contact points for each of the vertices touching the flat ground. If you cut one off, then only three of the corners are being held above ground. On a larger scale, If you do that enough, then the object will partially fall through the ground and then bounce back up from an excessive contact resolution force creating instability and vibrating.</div>
<div> </div>
<div>Those are the indicators that I would use to determine if it's OK to make that change. Are 8 contacts enough for ODE to react properly in our usage? That remains to be seen :).</div>
<div> </div>
<div>Regards</div>
<div> </div>
<div>Teravus<br><br></div>
<div class="gmail_quote">On Tue, Jan 3, 2012 at 4:58 PM, Adams, Robert <span dir="ltr"><<a href="mailto:robert.adams@intel.com">robert.adams@intel.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">> ...<br>
<div class="im">> According to [2], the maximum reported scripting collision contacts is 8.<br>><br>> Testing with 8 on Wright Plaza today in the Tuesday meeting seemed to greatly reduce physics scene time compared to<br>
> previously without any apparent loss of required fidelity (50ms with 18 avatars, albeit mostly sitting down -<br>> unfortunately I didn't record previous week's numbers but they were higher. Nebadon tested one of his vehicles).<br>
<br></div>Looking at the code, contacts_per_collision is the number of collision points reported by ODE for each collision -- like a prim sitting on rough terrain and touching multiple places on the ground. Reducing the count to 8 means that no more than 8 contact points will be reported by ODE and, if there are more, you can't be sure you get the 'best' ones.<br>
<br>I suspect that most of the time there are only a few contact points so it doesn't make sense that reducing the number from 80 to 8 would significantly reduce the compute time. If it is the number of contact points causing the computation overhead then ODE must be normally returning more than 8 contact points. Is this really the case? Or is something else going on?<br>
<br>-- ra<br>
<div>
<div></div>
<div class="h5">_______________________________________________<br>Opensim-dev mailing list<br><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br>