Phantom Menace
One of my jira issues got a very, very speedy fix, so I was poking about on the jira after I closed it and found this remark by Falcon (Havok 7 person) from 18 March, regarding the desire for individual-prim-set-to-phantom-in-linkset which we only have now in a kind of sideways workaround through floopy prims or by child-phantom scripts. He said:
"Hi Folks,
Denis Tristan pinged me on this inworld, and it aligns with what I'm working on right now, so I thought I'd drop a note to all of you. First, believe it or not, providing this feature is not as simple as it sounds. That's the bad news. The good news is that the need for the feature will soon be obviated. I'm presently working on a system that will allow you to specify individual prims in a linkset as having no physics shape. This is not quite the same as having individual prims be phantom in that phantom prims bounce off the ground whereas a prim having no physics shape will have no physical interaction at all. Accordingly, to keep objects from getting lost, you will not be able to have a linkset without at least one of the prims having a physics shape. But in general, this new feature should allow content creators to build all the things they could have built with per-prim phantomness. I'm marking this feature request as Resolved (Won't Fix), but rest assured that a better solution is in the works. The new system will also be more extensible, allowing us to provide you with entirely new options for physics shapes down the road. (E.g., we might allow you to specify that a shape should behave like llVolumeDetect and provide callbacks into LSL when it's penetrated, or allow you to request information about overlaps synchronously in an LSL script. Note that neither of these are in the works at present, but they are real options down the road with this new implementation.)
Cheers,
Falcon"
- 
Post a Comment
PLZ LEEVE A MEZZAGE KTHNXBAI