Rolling Restart to deploy 1.27.1

/me was thinking that only non-american people have trouble with the US time notation

Thank you, Dante.
It is really normal to get lost on it. In fact there are not 12h AM or 12 PM. We can say 12:01 AM or PM (heheh). or just use 00h (Midnight) and 12h (Mid-day)...
Sorry for this off-topic and thanks for fix that.

Good luck all team!
We love SL

This error still seems to be an issue with some accounts, after the bug fix deploy.

I guess it's asking too much for code to be "tested" and "finalized" before being slated to be "rolled"? I note that this is the third time in as almost as many weeks that the grid is being restarted to implement 1.27 server.. eeew!..

Haha, I knew there was a 1.27.1 coming, and a 1.27.2 soon to come.

I did notice (Or atleast it was a client side glitch) that the 'Double Upload Fee' bug returned in 1.27, and for some reason I'll get completely null HTTP responses in some scripts. (That or its a bug in my own script and I have yet to find the cause.)

On 1.27.1 regions on aditi?

Could not have been spoken better.

1.27.0 absolutely sux. I have never seen so many Sim nearly killed from this. There are Class 5 Sims, with 1-4 FPS and empty Sims at 10-20 FPS slower than 1.26 server edition. I think they were in too big of a hurry to release the 1.27.0.xxx

Agreed, You would not believe how many do not know what Zulu time is.

It will be tested and finalized before we deploy, but that doesn't mean we can't make an educated guess about when that finalization will happen and try to schedule accordingly. If, in the end, we don't have something tested by the time we're supposed to deploy it, we would presumably delay the release or remove the untested code. Announcing our intended schedule is an effort to give advanced notice to residents so they can plan around our work as best as possible.

I don't have the JIRA link on hand but there is an issue where teleporting in and out of a region can bring a region to it's knees because it lags or even stops all scripts and physics from working. This is exacerbated when many avatars are doing this repeatedly thus the throttle.

The problem was that the way LL implemented it counted failed TP's against the limit so that people were hitting the limit when they had repeated teleport failures so the change in this patch as far as I can tell from what I've read and what Dante said raises the limit to something nobody will accidentally hit until LL can fix the system to stop failed tp's from counting at which point they can lower the limit again to stop abuse.

correct me if i got this wrong:

there is a bug in the server code that makes sims laggy if people teleport to them, so LL "fixes" that by limiting teleports?

... what exactly is wrong in this picture?

Any complicated rezzing is going to be a hit on the sim, and an avatar teleporting in is really a fancy case of rezzing. The throttle is to make it less useful as a denial of service attack.

right now the throttle is making teleporting less useful FULL STOP.



and i still think that this approach of fixing the issue is like shooting yourself in the belly to cure diarrhea.


fix it so that "complicated rezzing" is not such a big impact, and you fix the broken sim borders rigth along with it., not only the incoming teleports lagging the sim.

border crossing is almost identical to teleporting so once the teleport/complicated rezzing is fixed so will sim border crossing.

this question and statement, and never can have three days that you can not teleport from anywhere at least for me personally I think it is also ridiculous and not very many serious updates for many things and I spend that money on que IESC not to move also worry about these things.

I have a problem by three days ...i cannot teleportp anywhere I go

ok, now take a deep breath, relax, have a coffee, then formulate your thoughts again, but readable.
kthxbye.

Do you wear objects that have many prims or many scripts in them, cobra?

Try detaching some objects before teleporting - that may help.

Yes same problem for me ...I have troubles teleporting in any region.It doesn't work also detaching objects or cleaning up cache files.Works very slow and sometime i keep crash in it.

With slow and frequent failing teleports it is worth to check if you still got good speed to websites or maybe someone on your network is doing some heavy downloading/filesharing.
In case you are on older cable internet it might even be someone in the street using up all the bandwith.

teleports and bordercrossing have always been very sensative to network problems and the current teleport sim freezing only makes it worse.

According to the release notes 1.27.0 should have a teleport throttle of 3 per 15 seconds, but my experience is much different. After a failed teleport i have to wait a full minute before i can try the next TP. This makes teleporting even more troublesome. Is this part of the TP-throttle and will it be more relaxed in 1.27.1 or is it some kind of bug?

Fun. been logged out twice in an hour. what's the problem???

there's not one bit of info on the status update page.

That's not what the throttle is for; it's meant to limit bots. The fact that failed teleports count toward the threshold is a bug, and we'll be relaxing the threshold in 1.27.1. We'll revisit the threshold when we've deployed code to address that bug.

Thank you for clarifying Dante.

(sometimes people need to remember, that a lot of times, the residents are guessing at what a fix it for, and unless they have been told specifically or can quote the official source, it is best to leave speculations unsaid (or clarify that it is indeed a speculation))

(well, that is what I think, others may feel differently)

On another note, I also had the failed to upload errors, but it was well after logging in, they happened when changing clothes, skins, stuff like that. Not sure what server the sim I was on, was running on, but I can check and update or send you a msg if needed Dante.

from my experience it seems that failed teleports count even higher towards the treshold than successful ones...


... are all variables involved in the threshold of the same signedness?
if you add -1 to a signed int but then do an unsigned comparison the int suddenly is bigger than 32000... which would be over ANY threshold.