llSetRegionPos question

[Rhiannon Arkin]

hi

Is it possible that llSetRegionPos 'overshoots' it's target before then rubber banding back to the intended position ? 

thanks

R/

 

 

[Rachel1206]

How much overshooting? The precision of llSetRegionPos is 0.1 meters.

 

And else it sounds like a lag/latency related issues.

[Rhiannon Arkin]

no i am working on a teleporter and it just keeps on missing by about 2-3 meters. only for a very brief flash. then it lands correctly. hm... 

[Rolig Loon]

Then the problem isn't llSetRegionPos.  I don;t know what it is, of course, but llSetRegionPos doesn't do that.

[Nova Convair]

The viewer interpolates and so simulates a movement if you change the position of an object.

If it overshoots that far I think that's due to a very high ping.

[Rhiannon Arkin]

ok. good to know it's not that command. thanks. i'll dig in more then. i'm switching animations too so maybe i'm seeing that. ... 

[Innula Zenovka]

Nova is correct, I'm sure.   As far as the simulator is concerned, llSetRegionPos moves the object to the target directly, without passing through intervening space.   That's why it's not affected by restrictions on parcel entry in intervening parcels as was warpPos, the workaround we had to use  back in the old days before we had llSetRegionPos.

However, between them the simulator, your GPU and your CPU try to interpolate the movement, and that's where the problem is coming from.

 

Edited August 20, 2017 by Innula Zenovka

[Ela Talaj]

llSetRegionPosition() is indeed imprecise. In my experience a deviation from input coordinates may be as high as 1 meter along one of the axes even though it happens rarely, not every time. If precision is required, instead of calling llSetRegionPosition() I usually call a 2-line user function:

SetRegionPosition(vector destination)
{
  llSetRegionPos(destination);
  if(llGetPos() != destination) llSetPos(destination);
}          

[Rhiannon Arkin]

Thanks Ela, i did end up using this idea and first tp to a spot just 10 meters before the target then again to the target. 

But for other reasons, the reason for my imprecision was that my sittarget has an offset so the avatar briefly appears away from the target in the moment of arrival, which looks like the setRegionPos misses, but it actually is pretty much where it should be. 

thanks!