This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
[BUG-10625] [CoreHTTP] Attempting an intra-parcel TP when a forced landing point is set leaves TP screen hanging at "Requesting teleport" instead of showing "Could not teleport closer to destination" error. #933
Labels
Steps To Reproduce.
Login on http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.8.7.306796
Teleport to region MeshTest2.
Observe you land at the forced landing point inside the orange circle at http://maps.secondlife.com/secondlife/MeshTest2/4/128/85
Walk to one edge of the platform and create a new landmark for this location, for example at http://maps.secondlife.com/secondlife/MeshTest2/1/138/85
Go back to the orange circle so you are standing at the forced landing point.
Teleport to the landmark you created earlier.
Observed Behaviour
When attempting to teleport to the landmark, the viewer will get stuck on the "Requesting Teleport" screen - See Fig 1 attached.
It may take a couple of teleport attempts to reproduce getting stuck - usually starts to reproduce on the 2nd attempt and keeps reproducing after that though.
If you watch the session log while the telport screen is stuck, you will see that the "Teleport failed. Could not teleport closer to destination" error is printed to the log, but the viewer does not backup to the world view and display this.
Also note that after the teleport failed warning in the log, there is always a "Teleport initiated by remote TeleportStart message with TeleportFlags: 8" after this.
This extra line never seems to happen on default release.
If you click the Cancel button on the stuck teleport screen, you then see the "Could not teleport closer to destination" error.
If you wait long enough without clicking the cancel button, the stuck teleport screen does eventually go away - takes a couple of minutes though.
I have never yet been disconnected while the teleport screen is stuck, but others are having teleport disconnections on this viewer - ref BUG-10598.
Problem also reproduces when standing at the landing point and double click teleporting.
Expected Behaviour
Expected behaviour is seen on default release - Second Life 3.8.6 (305981) Oct 13 2015 17:30:25 (Second Life Release).
On default release, each time you attempt to teleport to the landmark, you immediately see the "Could not teleport closer to destination" error. The teleport screen does not even appear.
Other Information.
Does not reproduce on Second Life 3.8.6 (305981) Oct 13 2015 17:30:25 (Second Life Release)
I cannot reproduce the disconnect on TP (BUG-10598) that several people seem to be suffering on the Core-HTTP viewer.
This is as close as I can manage :D
Attachments
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: