Skip to content
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

Open
1 task
sl-service-account opened this issue Nov 5, 2015 · 3 comments

Comments

@sl-service-account
Copy link

sl-service-account commented Nov 5, 2015

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.

    2015-11-05T23:07:08Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Are you sure you want to teleport to <nolink>MeshTest2 (1, 138, 85)</nolink>?
    2015-11-05T23:07:09Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Teleport failed.
    Could not teleport closer to destination
    2015-11-05T23:07:09Z INFO:#Messaging process_teleport_start: Teleport initiated by remote TeleportStart message with TeleportFlags: 8
  • 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
Field Value
Issue BUG-10625
Summary [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.
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Reporter Whirly Fizzle (whirly.fizzle)
Created at 2015-11-05T22:48:35Z
Updated at 2017-05-08T22:45:27Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2015-11-24T15:16:31.706-0600',
  "Is there anything you'd like to add?": 'Does not reproduce on Second Life 3.8.6 (305981) Oct 13 2015 17:30:25 (Second Life Release)',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Filling in...',
  'What were you doing when it happened?': '...',
  'What were you expecting to happen instead?': '...',
}
@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-11-22T02:37:19Z

On http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/RIDER2_maint-4952-v-t-u/rev/308134/index.html
The stuck teleport screen is fixed but what happens now is the viewer tries to teleport me twice on pretty much all TP attempts (I also hear the TP sound twice) and about 50% of the time instead of the "Could not teleport closer to destination" message (which is the correct message) I instead get this teleport error:
http://i.imgur.com/tuGfgkO.png

When I get the correct "Could not teleport closer to destination" error and the teleport sound plays twice, logs show:

2015-11-22T02:30:02Z INFO:#Teleport LLTeleportRequestViaLocation::LLTeleportRequestViaLocation: LLTeleportRequestViaLocation created
2015-11-22T02:30:02Z INFO:#Teleport LLTeleportRequestViaLocationLookAt::LLTeleportRequestViaLocationLookAt: LLTeleportRequestViaLocationLookAt created
2015-11-22T02:30:02Z INFO:#Telport LLAgent::startTeleportRequest: Agent handling start teleport request.
2015-11-22T02:30:02Z INFO:#Teleport LLTeleportRequestViaLocationLookAt::startTeleport: LLTeleportRequestViaLocationLookAt::startTeleport
2015-11-22T02:30:02Z INFO:#Teleport LLAgent::teleportCore: In teleport core!
2015-11-22T02:30:02Z INFO: LLFloater::closeFloater: Closing floater worldmap
2015-11-22T02:30:02Z INFO:# LLAgent::teleportRequest: TeleportLocationRequest: '1118203325697024':{ 1.341136, 122.333115, 85.388313 }
2015-11-22T02:30:02Z WARNING:#Teleport LLAgent::handleTeleportFailed: Agent handling teleport failure!
2015-11-22T02:30:02Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Teleport failed.
Could not teleport closer to destination
2015-11-22T02:30:02Z WARNING:#Teleport LLAgent::setTeleportState: Attempt to set teleport state to 1 for previously failed teleport.  Ignore!
2015-11-22T02:30:02Z INFO:#Messaging process_teleport_start: Teleport initiated by remote TeleportStart message with TeleportFlags: 131088

When I get the incorrect "Unable to find teleport destination. The destination may be temporarily unavailable or no longer exists. Please try again in a few minutes." error and the viewer only teleports me once, log shows:

2015-11-22T02:33:20Z INFO:#Teleport LLTeleportRequestViaLocation::LLTeleportRequestViaLocation: LLTeleportRequestViaLocation created
2015-11-22T02:33:20Z INFO:#Teleport LLTeleportRequestViaLocationLookAt::LLTeleportRequestViaLocationLookAt: LLTeleportRequestViaLocationLookAt created
2015-11-22T02:33:20Z INFO:#Teleport LLTeleportRequestViaLocationLookAt::~LLTeleportRequestViaLocationLookAt: ~LLTeleportRequestViaLocationLookAt
2015-11-22T02:33:20Z INFO:#Teleport LLTeleportRequestViaLocation::~LLTeleportRequestViaLocation: ~LLTeleportRequestViaLocation
2015-11-22T02:33:20Z INFO:#Telport LLAgent::startTeleportRequest: Agent handling start teleport request.
2015-11-22T02:33:20Z INFO:#Teleport LLTeleportRequestViaLocationLookAt::startTeleport: LLTeleportRequestViaLocationLookAt::startTeleport
2015-11-22T02:33:20Z INFO:#Teleport LLAgent::teleportCore: In teleport core!
2015-11-22T02:33:20Z INFO: LLFloater::closeFloater: Closing floater worldmap
2015-11-22T02:33:20Z INFO:# LLAgent::teleportRequest: TeleportLocationRequest: '1117103814069248':{ 255.148911, 120.693741, 85.388313 }
2015-11-22T02:33:21Z WARNING:#Teleport LLAgent::handleTeleportFailed: Agent handling teleport failure!
2015-11-22T02:33:21Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Teleport failed.
Unable to find teleport destination. The destination may be temporarily unavailable or no longer exists. Please try again in a few minutes.

When the "Unable to find teleport destination. The destination may be temporarily unavailable or no longer exists. Please try again in a few minutes." error reproduces, the teleport screen also flashes up briefly but goes away after a second.
The TP screen should not appear at all when TPing within a parcel with a forced landing point set.

@sl-service-account
Copy link
Author

Dan Linden commented at 2015-11-24T21:16:32Z

@whirly, would you enter a new bug for this new behavior?

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-11-24T22:51:05Z

Done - BUG-10776

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant