Problem with realtime move variable

[Keyla Vought]

Hello guys, i´m building a tool to help me in my nano constructions, but i have a problem with Z axis, i build a hud who send commands to a prim and it resize, rotate and move, at minimum, but i have a problem with Z axis to move, it don´t move like the other axis. X and y i move 0.00001+, but z i only can move 0.0001 and it upgragrates in my hover text 0.001+ , i must click 10x ax z axis to upgrade the hover.

 

       llSetPos(llGetPos() + <posx,posy,posz>); <  i have a remote control system who gives a plus to each axis separated but the z axis don´t work like the other stuff, only here
       llSetRot(llGetRot() + <rotx,roty,rotz,0>);
       llSetText("Channel: " + (string)channel +"\nSize: "+(string)llGetScale()+"\nRotation: "+(string)llGetRot()+"\nPosition: " +(string)llGetPos(), <0.0,1.0,0.0>, 1);

https://pasteboard.co/JnfpzwF.png

ty guys

Take Care, be Safe

 

Keyla Vought

 

 

 

[animats]

What altitude are you at? Are you in some high skybox?

Positions in SL are 32-bit floating point numbers. 24 bits of mantissa, 8 bits of exponent. 2^24 is about 16 million. At 1000 meters altitude, there are only enough bits left to divide a meter into 16,000 parts. That's about 0.0001m. So this is expected behavior.

For more theory, search for "floating point precision explained".

Practical answer: Second Life is designed for roughly real-world sizes. Ultra-small objects will not work, and ultra-huge objects will not work. The useful working range is about 0.001m to 64m. Even that is pushing it. Physics needs objects at least 0.1m to work right.

 

[Keyla Vought]

Ty sweet,  i´ll test on the ground tonight,  my creator room is 2000 meters , it´s a pitty, the hud is pretty cool to deal with jewelery, at least x and y axis works fine.

 

Hugs

Take Care

Be safe

Keyla Vought ❤️