As of just now, llRezAtRoot() still works erroneously.
I've just confirmed Beatfox Xevious' observation in the 1.5 grid
Here in the 1.6 preview grid it IS rezzing as if the Second from the Root was the Root prim. Or is that the 1st prim being used when it should be the 0th?
Welcome to the Second Life Forums Archive
These forums are CLOSED. Please visit the new forums HERE
llRezAtRoot still rezes second prim's position |
|
|
Konigmann Lippmann
Registered User
Join date: 15 Jun 2004
Posts: 40
|
03-06-2005 11:58
|
|
Jeffrey Gomez
Cubed™
Join date: 11 Jun 2004
Posts: 3,522
|
03-06-2005 12:26
llRezObject, and I believe llRezObjectAtRoot, utilize the center of a rezzed object's bounding box for the position it rezzes in. You can negate this effect by compensating for the position with the average of the values given by llGetBoundingBox at present, but it would be nice if that was already done for us at the backend in some form.
Perhaps llRezAtChildPos()? _____________________
---
|
|
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
|
03-06-2005 12:38
Jeffery, llRezAtRoot is supposed to rez the specified object's root at the position passed to it. llRezObject, on the other hand, is supposed to do what you said. The very reason LL implemented two rezzing functions is to allow older rezzors (that used llRezObject) to still work properly while "fixing" the behavior of the position parameter.
The Original Poster describes a bug that still needs fixing (assuming the OP's information is correct). ==Chris |
|
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
|
03-06-2005 12:40
Here in the 1.6 preview grid it IS rezzing as if the Second from the Root was the Root prim. Or is that the 1st prim being used when it should be the 0th? Link number 1 is the root prim, 2 is the first child prim, and so on. Its kind of odd why LL chose this numbering scheme versus a 0-based index one, like lists use. ==Chris |
|
blaze Spinnaker
1/2 Serious
Join date: 12 Aug 2004
Posts: 5,898
|
03-06-2005 14:14
The problem is that if they do fix this, it'll probably bust all sorts of stuff.
I just gave up finally (though I think Jeff figured it out) and move the object towards the position I want it to be at after it rezzes. Lots of extra work, but I had little choice otherwise. _____________________
Taken from The last paragraph on pg. 16 of Cory Ondrejka's paper "Changing Realities: User Creation, Communication, and Innovation in Digital Worlds :
"User-created content takes the idea of leveraging player opinions a step further by allowing them to effectively prototype new ideas and features. Developers can then measure which new concepts most improve the products and incorporate them into the game in future patches." |
|
Konigmann Lippmann
Registered User
Join date: 15 Jun 2004
Posts: 40
|
03-08-2005 00:52
The fact that this function has been broken for 4 months certainly means that's not all that unlikely that people are dependant on the current behavior.
After making the original post, it finally hit me, that I could duplicate my first prim, so that I had an IDENTICAL second prim, and that should work around the problem too, and it should work right when/if the error ever gets corrected. |