Region Crossings continued
tracked
RodericMurgatroyd Resident
A year later and it is getting worse. It happens nearly every trip in my boat. I have identified three ways this happens on a region change. I suspect that they are different manifestations of the same underlying cause.
- Unsit, where the boat does rez in the new sim and continues on its way while I am thrown overboard and end up on the bottom. My boat (Machichaco by Isard) detects this and sends me a message with it's current SLURL, allowing me to TP to it, resit, and take control. This used to be the most common form of failure.
- Loss of control. I remain sitting on the boat but it is no longer responsive to my inputs. The boat (and I) continue in the new sim, moving along the previous velocity vector in a phantom state, passing through buildings and land. If the velocity had a vertical component we may end up flying up at an angle, or submerging. I think this is the viewer extrapolating on its own.
- Catapult. The boat does NOT complete rezzing in the new sim but I do. Since the boat no longer exists, it does not send me a SLURL message and it does not end up on somebody's land where it would eventually get returned. As in case #2, my avatar continues along the previous velocity vector, often up into the sky (sometimes hundreds of meters up). I can follow my progress on the Map but I notice that the viewpoint and the avatar location are not together. I can see myself off in the distance as we fly away. Eventually, either a timeout or reaching the far side of the new sim, I am suddenly jerked back to two sims back, standing on the sea bottom. I can walk forward and backward but unable to turn. At this point I can TP back home but on arrival, the inability to turn continues. This case is happening a lot now.
Examination of the log for case #3 (collected at 2026-06-03T02:16:14Z) finds many suspicious WARNING messages which may provide clues. I was proceeding West along an open corridor in the Blake Sea area: Norwegian, Japan, Irish, China. Caribbean. Speed was about 11 knots. (Entry to Caribbean is where case #3 happened.) Each of these warnings appear multiple times. I was using a non-mesh avatar with no scripts other than a Navigation HUD that was logging sim crossings (88 kB), and the boat control HUD (64 kB).
- There is, in at least case #3, no logging of actually entering the new sim.
- requestExperiences : Capability query method not set
- getCapability called before caps received for GetExperienceInfo
- stageAfterCompletion : HTTP request 0x7f6205a56c10 failed after 0 retries. Reason: Forbidden (Http_403)
- onCompleted : Possible failure [Http_404] cannot POST url 'https://simhost-0353d13a62153db1f.agni.secondlife.io:12043/cap/defd51df-3e5d-1671-81f7-5d5f44b87a5e' because Not Found
- onAssetLoadComplete : Error getting material asset data: Asset request: failed (-1)
- process_agent_movement_complete : agent_movement_complete() with NULL avatarp.
- parserWarning : Failed to parse parameter "sd[order]"
The "Statistics" window shows that UDP traffic continues as before with a sim ping time of 134ms.
This looks like a combination of race conditions and the new sim simply not responding. I note that setting Draw distance to just 32m increases reliability considerably but it is very boring because the whole point of these trips is to look at the scenery pass by.
Log In
Maestro Linden
updated the status to
tracked
Maestro Linden
updated the status to
under review
Thanks for the email with all the requested information, including log files.
As Monty Linden mentioned in his reply, it looks like this particular crossing failure can be explained by 'Blake Sea - China' crashing just around the time you were passing through. We are investigating that crash.
Maestro Linden
updated the status to
needs info
Maestro Linden
Hi RodericMurgatroyd Resident, we can investigate your particular region crossing failure to see if it's one of the known types of crossing failures, but in order to do so we need details of specific failure events. The details we need are:
1) A description of the symptoms of a particular failed region crossing incident. The level of detail you went into in your initial post is probably enough information for this purpose, though if you have other details (such as the name of the vehicle), that could be helpful as well.
2) The details of the crossing incident, including:
* Precise timestamp of the crossing failure
* The name or agent_id of the avatar involved (if not yourself)
* The names of the source and destination regions involved in the crossing
* Log from your viewer during the session that hit the crossing incident.
To send this a viewer log file, the instructions are:
1. Log out
2. Zip up your viewer logs folder. This page tells you where to find the logs folder: https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/ Note that for Firestorm sessions, the directory and log filename pattern is the same but with "Firestorm" substituted for "SecondLife".
3. Email the zip file to bug-attachments@lindenlab.com and reference the issue name in the email subject line.
4. Leave a comment on this canny issue once that's done so we can take a look at the logs.
With this information, we can compare the server logs to the viewer log and hopefully see what triggered the failure.
RodericMurgatroyd Resident
Maestro Linden, log file and additional details emailed as requested.