Monty Linden

That's a part of it.

As others have mentioned, enhancement Jiras are the way to ask. I'm skeptical that scheduled region restarts are a magic cure-all but one thing they can't do is replace rolls and bounces. Rolls (upgrades) and bounces (restarts) have to happen simhost-wide and across the channel. At least under the current design.

All RCs got 571998 today. I'll see about getting more details up...

And @animats work towards a totally new Rust-based viewer. (Yes, early days still...)

You can experience what a direct translation to TCP would be like by using a VPN over TCP. It's a tool people should consider when their UDP connectivity just can't handle SL or other games.

That can happen. In this case, try other connectivity to file the support ticket: mobile, friends. Block will often clear on its own. (Perhaps there's a TPV feature here to probe the login service and report with a nice GUI panel...)

Some things to try: Probably most important, try the browser lookup of the login page. If you get a 'Reference ID' on the page, take that and file a support ticket with the information. However problem may clear on its own after a cool-down period.

I would guess that a manager/orchestration script in the object is manipulating inventory and killed your script. I can see this deletion happen between two external HTTP invocations. Review your other scripts, pay attention to the DEBUG console, look for non-unique names in object inventory.

Script was intentionally deleted (by LSL script) at 12:18:44SLT on the 26th.

For the record, I haven't touched anything. So if you've been basking in the marvelous improvements in SL connectivity in the past few days, it's entirely placebo effect. (I have made a descent into the dark corners of the UDP code and now I'm sad.)

Et voila!

Oh, it's sticking.

I want to meet the Windows Server person.

Keep these updates coming. Enjoy them greatly...

baldER

Hey! That's our internal motto!

Nope. That's just the first time I've ever seen ISP license management as a reason for reduced bandwidth. That's beyond dog-ate-my-homework.

Another possibility is that your cable ISP isn't installing all their licenses correctly:

For some perspective, I checked logs and you personally had 13 network blocking events on that region in a 24 hour period. The region as a whole had 100 and the simhost on which it was running had 2000 (one every 43 seconds on average). Yours correlated well with region entry and rezzing/derezzing operations. None of this is necessarily a problem on either end. But you might see some of this in action by pulling up the Windows monitoring tools and watching the network adapters. The numbers may be adequate to show the correlation between these events and packet activity. (Shift-Ctrl-1 needs better visualizations... )

Usually, that's not useful. There may be 50 hops between your computer and SL servers and very little overlap with a path to google. You can catch a problem with your ISP or modem/router or a firewall/AV being really awful. So it may eliminate those possibilities but doesn't help beyond that.

This is in the UDP system so it's based on slow acknowledgements from the viewer. The problem can lie anywhere in the path. From the socket held by the simulator to the OS scheduling the viewer and everything in between. A bit more data from this one event first: the simulator was very quiet, one avatar (yours), a few on neighboring regions. Scripts using email for communication (grrr). But metrics and logging all very quiet, nothing exceptional happening in the region or on its simhost. In this scenario, the likely cause is elsewhere. I.e. "the Internet did it." I can also look at the viewer log from your session to confirm what happened from its point-of-view. You can email it to monty @ you-know-where or we can arrange other means. We can't make the internet (or cable ISPs or home operating system) behave but I'm interested in a few more events to see if any pattern emerges. If so, we can turn this into a visible Jira. Also inviting events from others here.

From our side I see: 17:43:41 - Attachment removed to be returned to inventory 17:44:00 - Congestion declared while sending updates to your viewer 17:44:05 - Appearance requested and congestion declared cleared So it appears like a stall in the network somewhere. I'm curious just how awful the updates were but I don't have that here. But there is a why to this event.

I'm curious about these events. I'll happily listen to details on particularly awful instances of this problem. Jira or here: where, who, when (to the second, timezone), and what happened. (Have looked at some bad rezzing/attachment events - this is a different problem, I think.)

Bwahaha, wrong tree, dog! The roadmap still stands but things may change. Watch for updates, monitor the user groups...

Oh, dear god, do we. I walked through that recently for the first time ever and despaired. A non-linear function of three terms, one of which uses the result of a loose, converging (maybe) iteration. I suspect that wiki page needs some updates but, yes, that is relevant.