Difference between revisions of "Talk:What's Changed With Havok4"

From Second Life Wiki
Jump to navigation Jump to search
(New page: == Need LSL method to monitor LOD changes == As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it is completely unacceptable for the LO...)
 
(update to match sldev mail)
Line 1: Line 1:
== Need LSL method to monitor LOD changes ==
== Need LSL method to monitor LOD changes ==


As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it is completely unacceptable for the LOD to degrade from a cylinder to a cube since this will immediately jam the device where the newly formed cube corners are overlapping where the cylinder was curved.
As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it isn't a good idea for the LOD to be able to suddenly degrade from a cylinder to a cube without notifying the scripts. This sudden uinannounced LOD changing will immediately jam the device where the newly formed cube corners overlap where a cylinder or sphere was previously curved.
Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and potentially even worse until the object explodes.  


Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and even worse until the object explodes.
We will need the ability to detect these physics LOD changes on the per-prim or per-link-group level so that the scripts driving the impellers, etc, can know there's a problem and can self-deactivate and go non-physical until the LOD goes back up to normal. It's much better to simply sleep the movers until the engine LOD returns to normal.  


I need the ability to detect these physics LOD changes on the per-prim level so that the scripts driving the impellers, etc, can know there's a problem and can self-deactivate and go non-physical until the LOD goes back up to normal.
Also, some sort of visual indication of LOD degrading would be useful to builders. In the beta sandboxes, how am I to know if the incorrect interactions I see are due to actual bugs, or just the sim silently and invisibly substituting cubes in place of all my cylinders and toruses?
 
This isn't a bug necessarily so it's probably not appropriate to post on the JIRA.


[[User:Scalar Tardis|Scalar Tardis]] 18:58, 28 September 2007 (PDT)
[[User:Scalar Tardis|Scalar Tardis]] 18:58, 28 September 2007 (PDT)

Revision as of 19:27, 28 September 2007

Need LSL method to monitor LOD changes

As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it isn't a good idea for the LOD to be able to suddenly degrade from a cylinder to a cube without notifying the scripts. This sudden uinannounced LOD changing will immediately jam the device where the newly formed cube corners overlap where a cylinder or sphere was previously curved. Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and potentially even worse until the object explodes.

We will need the ability to detect these physics LOD changes on the per-prim or per-link-group level so that the scripts driving the impellers, etc, can know there's a problem and can self-deactivate and go non-physical until the LOD goes back up to normal. It's much better to simply sleep the movers until the engine LOD returns to normal.

Also, some sort of visual indication of LOD degrading would be useful to builders. In the beta sandboxes, how am I to know if the incorrect interactions I see are due to actual bugs, or just the sim silently and invisibly substituting cubes in place of all my cylinders and toruses?

Scalar Tardis 18:58, 28 September 2007 (PDT)