Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008086opensim[REGION] OpenSim Corepublic2016-12-10 09:312016-12-10 10:05
Reporteraiaustin 
Assigned ToAliciaRaven 
PrioritynormalSeverityminorReproducibilityalways
StatusassignedResolutionopen 
PlatformPCOSWindowsOS Version10
Product Version 
Target VersionFixed in Version 
Summary0008086: osTeleportAgent(avatar, <128.0,128.0,1001.0>, < 0.0,0.0,0.0>) ;
DescriptionA prim containing a simple script near 128,128,22 on a region on OSGrid that when touched should teleport the agent up to 1000m higher. The main function is

osTeleportAgent(avatar, <128.0,128.0,1001.0>, < 0.0,0.0,0.0>) ;

The full script is given below for testing. It used to work when last tested maybe 3 months ago. But now it just jumps the avatar up a few metres.

The following variant in a prim high up for the reverse journey appears to work fine...
osTeleportAgent(avatar, <128.0,128.0,25.0>, < 0.0,0.0,0.0>) ;
Steps To ReproduceCreate a prim on a normal ground level at say Z=25m and put the script below into it. Touch it and see if you are set to 1001m or just moved up a few metres.
Additional Informationdefault
{
    state_entry()
    {
        // Set up the llSitTarget() and sit text first
        llSetSitText(g_SitText);
        llSetText(g_FloatingText, g_TextColor, TRUE);
    }
    
    touch_start(integer id)
    {
        key avatar = llDetectedKey(0);
        osTeleportAgent(avatar, <128.0,128.0,1001.0>, < 0.0,0.0,0.0>) ;
    }
}
TagsNo tags attached.
Git Revision or version numberOSgrid OpenSimulator 0.9.1.dev.f574039 - [zip] [32.0mb] 12-10-2016
Run Mode Grid (Multiple Regions per Sim)
Physics EngineBulletSim
Script Engine
Environment.NET / Windows64
Mono VersionNone
ViewerFirestorm 4.7.10.52132
Attached Files

- Relationships

-  Notes
(0031419)
aiaustin (developer)
2016-12-10 09:36

Also tested in another viewer I happen to have installed that is MUCH older (CtrlAltStudio 1.2.6.43412 based on Firestorm 4.6.9 and I do mean there not the current 4.7.9) and that has same behaviour. So I am not suspecting a viewer issue.
(0031420)
AliciaRaven (manager)
2016-12-10 09:45

Hi aiaustin

This is an unexpected side effect of a new feature i added for creating a default region landing point. The default landing point is used when some one teleports to a region and does not specify any coords. The code assumes a teleport location of precisely 128, 128 as being such as case and tries to use the new region default.

At some point tonight i will commit a fix for this case. Until then you could avoid getting caught by this check by changing the location slightly in the script, setting it to 128.01 would be enough to do this.
(0031421)
aiaustin (developer)
2016-12-10 09:51

Got it. Thanks for the explanation. Its just my "VRLand" test screens and visuals for VR testing on OSGrid and not at all urgent. If you make a change I will watch for that and use the existing VRLand script as a test to see if that little flitch gets fixed.
(0031422)
AliciaRaven (manager)
2016-12-10 10:05

Fixed in master

<cia-opensim>opensim: alicia * rd49a5374c379 OpenSim/Region (2 files in 2 dirs):
<cia-opensim> Make it more unlikely that a script teleport will be caught by default region landing point.
<cia-opensim> http://opensimulator.org/viewgit/?a=commit&p=opensim&h=d49a5374c37967110a8bf11844893f62951878ee [^]

- Issue History
Date Modified Username Field Change
2016-12-10 09:31 aiaustin New Issue
2016-12-10 09:36 aiaustin Note Added: 0031419
2016-12-10 09:45 AliciaRaven Note Added: 0031420
2016-12-10 09:45 AliciaRaven Assigned To => AliciaRaven
2016-12-10 09:45 AliciaRaven Status new => assigned
2016-12-10 09:51 aiaustin Note Added: 0031421
2016-12-10 10:05 AliciaRaven Note Added: 0031422


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker