Accepting Teleport After Teleporting Disconnects Viewer
tracked
Pazako Karu
If you are offered a teleport, teleport elsewhere - and then accept the teleport, the viewer hangs on "Requesting Teleport..." for 90 seconds. Most times this causes a disconnect.
With some testing:
After this... if you try to tp to the destination region again you time out.
If you tp elsewhere first, you might recover.
Log In
AlettaMondragon Resident
I have been experiencing this for some time now too. Not entirely consistent and not too frequent but it happens often enough to be annoying. If I accept a TP offer within the same region that I had just teleported to, it seems to be a very solid way to reproduce this. As far as I can remember whenever I've done that (mostly accidentally, first teleporting to the target parcel from the SLURL in the TP offer instead of the button, and then hitting the button when I landed on a landing point instead of the destination), it resulted in the requesting teleport state getting stuck, timing out and disconnecting, irreversibly (no cancel or quit button). This is on several Firestorm V7 builds in the past 3 months.
Maestro Linden
tracked
Maestro Linden
Hi Pazako Karu, I've tried this a few times, and I'm not able to reproduce the viewer disconnection event when using Second Life Release 7.1.15.15596336374 on Second Life Server 2025-04-24.14648572313.
With this viewer, I see that accepting a teleport offer after moving to a new region causes the offered teleport to fail after a 27 second timeout, which looks like this in the viewer's SecondLife.log:
```
2025-07-09T17:28:16Z WARNING #Teleport# newview/llviewerdisplay.cpp(284) update_tp_display : Giving up on teleport. elapsed time 27.0207 exceeds max time 27
```
Looking at the server logs, it seems that the issue is that the TP-lured user's 2nd region has no record of the lure, and rejects the teleport outright.
Following the TP offer should ideally succeed. If that's not possible due to missing data, the failure should appear immediately in the viewer, rather than causing it to display a ~30 second loading screen before ultimately timing out and failing.
Pazako Karu
Maestro Linden My log showed the same line but with 90 seconds, is this different per simulator version? I didn't see anything indicative in the log so I didn't provide it, just the failure line.
Maestro Linden
Pazako Karu: I think the timeout shown in the viewer log is determined by the viewer. It's not clear to me what sets the timeout though - when I tested on Firestorm 7.1.13, it was instead using a 30 second timeout instead of the 27 second timeout that I posted here.
The server is actually failing the teleport attempt immediately, as it has no record of the TP offer.