At Black Sea, In front of me in the mini map, sea disappered but it does exist in the map of the viewer. If i go there with my boat, it will be returned and i will be down on the botton. Then the viewer gets stuck and i need to force it to close and relog

It’s been impossible for me to fly in most water sims like Blake and Second Norway etc. I used to fly for hours before with no or very little problem. This happened about 3-4 weeks ago approximately and still to this day no improvement.

I'll have to compile this information. However, In the meantime, I have noticed that when you cross and the vehicle stops responding, if you have the mini map open (and your distance is set far enough) the next sims do not show up either. I've right clicked and selected EDIT on my vehicle, boat, plane to stop it in its tracks. If you wait 10 to 30secs, you'll see a flicker (its the only way I can describe it) and then all of a sudden the mini map fills in the sims ahead. If you then stop editing, you're able to recover and keep going...most of th time. Sometimes it doesn't matter and your flung into limbo or spinning around your vehicle as it continues off into limbo. For me, its rarely caused a viewer crash, just frustration and not wanting to log in. As far as precise data, I don't have that yet, but it doesn't seem to happen in specific places, its everywhere. Blake, Tulagi Seaport, etc. etc.

## When an Event Occurs

* Note the time. Down to seconds, if possible, and timezone of choice

* Capture any warning or error display from the viewer

* Gather viewer logs covering the event

## Put Together the Report Package

### Describe the Problem Context

Write a description of the event. Details should include:

* Who. What agents were involved. Include yours, we don't want to make assumptions.

* Where. What regions were involved in the problem. Both source and destination when the problem involves teleports and region crossings.

* What. Describe what went wrong. Not "Teleport was borked." What was expected, what visually happened.

* When. Accurate and precise times when events occurred. Include timezone. UTC or SLT preferred.

### The Package

You now have a useful report package:

* The viewer logs (huge)

* Any screen captures taken (mid-sized to huge)

* Problem context above (small, concise, to-the-point)

Where to ship it?

## Choose Your Delivery Mechanism

* You can file a support ticket. They'll accept the entire report package and safely handle your logs. But it can take awhile to get that into Engineering or open a discussion.

* Report via feedback/Canny. You can't (and probably shouldn't) send viewer logs to Canny. You can create a new bug report and just supply the problem context and maybe the screen captures. For sensitive items, compress and send to: bug-attachments@lindenlab.com (This is gmail - it may filter on size, encryption, container, other things.)

* Just send it all to bug-attachments@lindenlab.com. If this is part of a larger bug investigation, you can dump it here with some pointers so that we know what to do with it when we find it. This is a viable option for this Canny.

Monty Brandenberg Maestro Linden I have sent the log via email. If you look for "ichelus" you can find where one of the extreme crossing delays occurred.

There is a huge number of :

newview/llaudiosourcevo.cpp(167) LLAudioSourceVO::updateMute : roots identical

which may indicate a time when I am in crossing "limbo". I do not know this for sure.

Monty Brandenberg I am in the process of getting a log file ready for emailing. It would be helpful if you posted the process for doing that in this thread.

How can we get on LL's toes so they finally do something?

We're certainly paying attention to this and Blake Sea is an important early warning system for problems. But for all the above, we still haven't received viewer logs and accurate and precise who/what/when/where/how info about particular events. ('Last week' is not a time.) Certain actions only happen in viewers and they are not reported back to us.

I don't know about seconds, numbers, and measurements—but the FLOW and the feeling... and that really isn't working yet; I've tried it with different vehicles. And yeah, for those who just sit around chatting, everything's fine anyway, but the exciting thing about a virtual parallel world is the Hvok engine and script.

5 days of complaint, and the general consensus is that the Blake Sea is no longer navigable, and my own experience is that other regions are having similar problems, if not as consistently.

Yet there is nothing on the second life status page https://status.secondlifegrid.net/ . Everything is operational, green.

It was reported that a Linden suggested a griefer might be responsible. Colour me extremely sceptical.

I'd like to see signs that the Lindens have heard us and acknowledge and OWN the problem, and intend to keep the residents informed.