Would a Wright Plaza meeting even have multiple point collisions? Most (all?) of the active physical objects are avatar agents and they use capsule colliders rather than meshes. Also, most are sitting and the few that aren't are standing on or moving across a flat surface, probably far away from any vertex in a collision mesh.<div>
</div><div>I suspect if you are seeing different physics statistics it's probably something else that's contributing to it.<br><br><div class="gmail_quote">On Tue, Jan 3, 2012 at 1:32 PM, Justin Clark-Casey <span dir="ltr"><<a href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 02/01/12 20:56, Melanie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 02/01/2012 21:51, Justin Clark-Casey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm thinking of making two ODE related changes.<br>
<br>
1) Replace the current ODE libraries in OpenSimulator with ones compiled using the older GIMPACT collider instead of<br>
OPCODE. This is to address ODE crashes in simulators with more than one region as detailed in [1] and [2]. These don't<br>
appear to occur with GIMPACT.<br>
</blockquote>
<br>
I'm not happy with that as a general decision. We should, if<br>
anything like that is done, include both versions to give users the<br>
choice. The OPCODE should remain the default in order to not<br>
jeopardize existing setups and the GIMPACT libs can be copied in by<br>
those experiencing the bug.<br>
Many people don't run multiregion at all and would see only<br>
downsides if this were done.<br>
</blockquote>
<br></div>
Multi-region is a non-experimental configuration that is useful to a large number of people. In my view, it's not correct for out-of-the-box OpenSimulator to continue with such crashes in the long term. This hurts adoption and ultimate long-term success/survival.<br>
<br>
However, it just so happens that on scouring the Internet, GIMPACT is actually the newer collider, as per [1]. I don't know why I thought it was the other way around - I may have misinterpreted something that somebody said.<br>
<br>
Indeed, apparently for our common use case (mostly static objects), GIMPACT should perform better, so I was also wrong about the performance issue. However, as I said, in my own testing I haven't yet noticed any significant difference and these questions are complex ones. But it's certainly my experience that using GIMPACT eliminates the ODE crashes in stress-testing, possibly due to something connected with [2] where global object caches are shared between collision spaces. But this is still a wild-assed guess (we can't use TLS as OpenSim crashes immediately upon startup).<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) Reducing contacts_per_collision in [ODEPhysicsSettings] from 80 to something much lower, maybe even 1. In my own<br>
testing, reducing this number can halve scene physics time. Normal avatar operations, such as standing on prims or<br>
walking up ramps appear to be unaffected even at 1. However, more testing is probably needed to arrive at a compromise<br>
number.<br>
</blockquote>
<br>
This would greatly affect scripts using physics. I believe the<br>
optimum would be 16-20, which would ensure that the scripting<br>
maximum (16) collision contacts are always available.<br>
</blockquote>
<br></div>
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 previously without any apparent loss of required fidelity (50ms with 18 avatars, albeit mostly sitting down - unfortunately I didn't record previous week's numbers but they were higher. Nebadon tested one of his vehicles).<br>
<br>
Testing will continue on the osgrid plazas.<br>
<br>
[1] <a href="http://www.ode.org/old_list_archives/2006-October/020664.html" target="_blank">http://www.ode.org/old_list_<u></u>archives/2006-October/020664.<u></u>html</a><br>
[2] <a href="http://groups.google.com/group/ode-users/browse_thread/thread/f38c56584c650536#" target="_blank">http://groups.google.com/<u></u>group/ode-users/browse_thread/<u></u>thread/f38c56584c650536#</a><br>
[3] <a href="http://wiki.secondlife.com/wiki/Collision" target="_blank">http://wiki.secondlife.com/<u></u>wiki/Collision</a><div class="im HOEnZb"><br>
<br>
-- <br>
Justin Clark-Casey (justincc)<br>
<a href="http://justincc.org/blog" target="_blank">http://justincc.org/blog</a><br>
<a href="http://twitter.com/justincc" target="_blank">http://twitter.com/justincc</a><br></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/<u></u>mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br></div>