You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
Open the World Map
For your new region input Hippotropolis
Click on Teleport
Actual Behavior
You arrive underground and a moment later are popped up above ground.
Expected Behavior
You arrive above ground.
Other information
I brought this up with Andrew Linden at his User Group meeting this afternoon; this jira should be brought to his attention.
Original Jira Fields
Field
Value
Issue
BUG-1280
Summary
Teleporting using the World Map puts you underground upon arrival
Type
Bug
Priority
Unset
Status
Accepted
Resolution
Released
Reporter
Jonathan Yap (jonathan.yap)
Created at
2013-01-08T20:28:00Z
Updated at
2014-05-22T22:55:53Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2013-01-08T15:03:40.791-0600',
"Is there anything you'd like to add?": 'I brought this up with Andrew Linden at his User Group meeting this afternoon; this jira should be brought to his attention.',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Open the World Map\r\nFor your new region input Hippotropolis\r\nClick on Teleport\r\n\r\nObserved behavior: You arrive underground and a moment later are popped up above ground.\r\n\r\n',
'What were you doing when it happened?': 'Teleport arrival',
'What were you expecting to happen instead?': 'Expected behavior: You arrive above ground.',
}
The text was updated successfully, but these errors were encountered:
I noticed this too on aditi. It is possible this is an interstlist bug. Or it could be that the dark teleport/login curtain that the viewer uses to shield the location transition is being raised too soon.
When I search for Hippotropolis on the world map, and select to TP to the destination, the default TP destination point in the sim is 128,128,0. When I TP to that parcel (which does not have a landing point), I arrive at the specified destination (128,128,0), and then get moved up to ground level by the sim (128,128,30) ~2 seconds later. I can reproduce the effect with other regions as well, though obviously it's more profound in regions with high ground elevation.
Here is my environment:
Second Life 3.4.3 (268262) Dec 17 2012 12:16:07 (Second Life Release)
Release Notes
You are at 260224.0, 252544.0, 87.4 in Ohno located at sim9661.agni.lindenlab.com (216.82.44.118:13000)
Second Life Server 12.12.18.268345
Error fetching server release notes URL.
CPU: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz (2800 MHz)
Memory: 4096 MB
OS Version: Mac OS X 10.6.8 Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce 9600M GT OpenGL Engine
OpenGL Version: 2.1 NVIDIA-1.6.36
libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU v7.0
Audio Driver Version: FMOD version 3.750000
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Vivox 3.2.0002.10426
Built with GCC version 40201
Packets Lost: 434/111210 (0.4%)
Heres a vid one of our Firestorm users made to show what happens when TPing to a Magnum region via worldmap since the last rollout.
He lands underground as reported on this issue but ontop of that his avatar is unable move and no other avatars on the region will render for him (they render normally on non Magnum regions as shown at the start of the video)
Steps to Reproduce
Open the World Map
For your new region input Hippotropolis
Click on Teleport
Actual Behavior
You arrive underground and a moment later are popped up above ground.
Expected Behavior
You arrive above ground.
Other information
I brought this up with Andrew Linden at his User Group meeting this afternoon; this jira should be brought to his attention.
Original Jira Fields
The text was updated successfully, but these errors were encountered: