Aishagain

We are told by the Status Page that "some regions are experiencing longer restart times than usual...so is this new code? Also I just looked at a world map and there are hundreds of regions down far more that show usually during the RC channels roll so, LL, what is going on this week? ETA at 11:15SLT: Restarts are "continuing" about 15 mins after a false notice announcing the end of the RC channels roll. Who'll give me odds on a rollback?

FWIW I have been seeing both the phenomena you mention, Rick; both the odd slight stuttering at around 50FPS and the occasional poor rendering of mesh objects. Like you I found that altering the LOD makes no appreciable difference to the poor rendering, though zooming in and back out "pops" the item in. If I cam away from the object for more than a few seconds it reverts to the under rendered state. The stuttering I had put down to two possible factors, one the current NVidia drivers (though rollbacks and update have made no difference, the other the writing of group chat to a busy (!) group, Firestorn Support English, which has a large log file. I don't think either are the real reason but as to what it is I am unclear. The issue has persisted through the last three FS updates, indeed I think it started even earlier, when the change to EEP was introduced, though this might simply be my dislike of EEP and general factors (don't you DARE call me an old fart who dislikes cheese moving).

This is a "me three" post. I run two accounts, never simultaneously and both accounts have had this message once or twice, never on successive logins to Agni. Both inventories are quite moderate (c.50k elements) and very well managed with folders and subfolders of moderate size. There is some issue with the login servers getting their "ducks in a row" during the preparation phase of an account's login process. Something has made this phase more vulnerable to failed race processes and I suspect that no-one at LL has a clear idea what it is.

In this context you would have more luck teaching a brick to fly! I don't think they are actively ignoring this issue. As a matter of fact I am pretty sure LL would dearly love to fix this bug. The simple fact is that they don't know what is causing it (it's most likely server-side...but which level?). LL have never been good at admitting they have another head-scratcher. They tend to retreat into their shell, as they seem to be doing right now.

Nowt on the Grid Status Page this week for Tuesday and Wednesday so...no restarts at all, this week? Eta: Main Server regions are restarting and I see the notices have finally appeared on the GSP.

Gotta love LL's way of "not quite" closing JIRAs; they tag them "Accepted" even when they are unassigned...it's their way of saying "Yeah, we know and we can't fix it right now". Comments are then closed but you can still "watch" it. I find watching paint dry more soothing

Well apart from some issue that I cannot address since I know next to nothing about any of the Linux distros, one thing I know for sure is that that version of the viewer is hopelessly outdated, version 5.0.9 I believe and the current Windows version is 6.6.8! So even if you could log in it would be unlikely to render SL properly. Linden Lab stopped developing a Linux version of their viewer ages ago. Try the current Linux Firestorm Viewer, that one is current.

Replying to this thread as a totally non-technical ex- ATI (as they were then) user, I am familiar with the description of the graphics failure. The fact that the AMD chip is using on-board graphics, which are routinely regarded as unsuitable for SL and the use of an object LOD factor of 4.00, which is quite inadvisable for even a strong discrete GPU, would most likely cause the saturation and subsequent corruption of the rendering (it did for me), resulting in either viewer crashes, forced logout and/or cache corruption. The adoption of a lower LOD is strongly advised, say 2.50, not as low as 1.125, which I found utterly inadequate and the use of a reduced draw-distance (say no more than 64 or 96m, may prolong the time online before a relog to avoid the artefacts is essential. I must assume the viewer restart clears volatile memory, to be honest I never did find out WHY it worked, just that it DID. My ultimate solution was to replace that system with a low-end desktop and on that I replaced the discrete but still feeble AMD gpu with a low end but still far better Nvidia gpu. AMD support for OpenGL is now much improved but I suspect that that, combined with the barely adequate system RAM of 8GB and Firestorm's need for resource is at the heart of this issue.

While I wish all USA residents a Happy Thanksgiving (Canadians celebrated a short while ago, I believe), I hope the Linden employees responsible for forum posting will return to normal operations soon. The radio silence on this thread is disturbing. And yes, I am deliberately bumping this thread.

Since we have not had an update from either LL or LoganPryor I am assuming that no new code was rolled to the RC Channels today (I have not knowingly visited one myself).

I can confirm what LoganPryor says that Main Server regions are receiving 567542. I am also noticeing that on these rolled and newly restarted regions that while the stats are looking fine, script communication seems poor (slow) and inventory errors are seemingly rather common, judging by FSE chat and the fact that I have had a couple myself, whereas I'd NEVER had one before today. Probably co-oncidence but it is odd. That being said we have several animesh animals out on the region and they seem to be unaffected.

What Nal was referring to was the 6.6.8 Firestorm I think, which is the latest Beta, possibly a release candidate for the next full release Firestorm. It has several significant changes from the current full release, 6.6.3, which may have performance implications. Since you are running both FS and the Linden viewer in pre-release forms, there are likely to be performance differences/issues compared with current releases.

I know it is still only Monday for most of us but I wanted to put a marker down here to ask a simple question: Have official posts from Linden Lab regarding restarts and new code rolls ceased in this forum altogether, or are Linden Lab all so busy gaffer-taping SL back together that they simply don't have time to post in here or publish release notes on the new code versions? I know the notifications are put out on the Grid Status Page, but all that tells is is that something is happening, not what. ETA: Today, the Main Server regions of SL are to be ... just restarted? From my point of view this blanket silence is not merely unwelcome, it makes me feel that we are returning to the bad old days of over ten years ago, when the userbase of SL was given "the mushroom treatment" and by and large disrespected. I can scarcely believe that the current management would repeat the errors of the Mark Kingdon era. FETA: The release notes to 2022-11-11.576542, last week's RC channel code, are at long last available and it would seem that there has been effort put it to improve the dreadful voice issues...maybe it is coming to a Main Server region near you today. It would've been nice to have "official" confirmation.

Ah well there seems little prospect of any timely details of the recent RC Channel or Main Server Deploys being released and I can (to date) find no information or recent SUG minutes. This does not seem like mere oversight now, it has been going on too long: this appears to be a change in Linden Lab policy and I find it disappointing in the extreme.

I'm not 100% sure that this is not entirely normal but if you look at your camera floater you should see options to show or hide the user interface, Linden Dollar balance, and HUDs. Now these are available whether or not the RLVa is in use, so you can argue that it is a "cheat", although it only provides a still picture. I do not know of a way to disable that toggle neither do I know if it is the same in the "true" RLV code by Marine Kelley (also, I believe used by Kokua). I am sure that it has been so for years.

So...RC regions ARE receiving new code despite there being not a word from LL on this forum. Outstanding. So, that is two consecutive weeks without a peep from LL in this forum, last week could be guessed and so could Tuesday this week, by a process of deduction but today is a mystery to users. Was there, I wonder, any hint given at the last SUG?

While thanks to LoganPryor we know what is being rolled to Main Server regions today, and we have some idea of one aspect of the new code, the expected restart post is MIA again, and the release notes for the code are still unreachable. I saw Mazidox post in the FSE chat last UK night so I know he's alive....where's the post in this forum?

Not happening for me on an AMD Ryzen 9 3900X/Nvidia 1660Ti Win 10 outfit. There ARE a few FS-specific bugs, none, as far as I know, directly impacting FPS or texture rezzing. Yes, texture acquisition IS poor but that is mostly due to the revisions LL made to the render-code that gives the higher FPS. It sounds like something in your system is choking, and wiser heads than mine may know what. The default viewer has just as many bugs, is only marginally faster and still has the texture-thashing caused by the enforced tiny texture-buffer size. Add to that the horrible UI and you have all the reasons why I dislike it so. FWIW some of your settings are odd, notably your bandwidth and LOD on the default viewer. I find my system runs more slowly at lower quality (without deferred rendering (ALM) and such low LOD. YMMV. I also note the 0.9% packet loss on the default viewer connection...that is rarely a healthy level of packet-loss.

'tis strange that there has been no word from LL on this thread about the RC channel roll this week, given that there WAS new code. ETA: At 5pm GMT10th November (Thursday) the release notes are still unavaiable!

Wiser heads than mine will quote the relevant JIRAs but this bug is well-known and I understand has both viewer and server-side components, both of which need changes from Linden Lab. I understand that the next update to the Firestorm viewer will have a bug-fix to make the issue less intrusive but all TPVs must wait for LL to introduce a genuine fix both server-side and in the viewer To my knowledge there is nothing we can do as mere users.

The GSP says the RC channel restarts will begin in about an hour, yet there is nothing from LL on this thread. I await an update from LoganPryor 🙂.

I have seen this phenomenon several times on the last two FS releases and wiser heads than mine point to various connection inadequacies, none of which stand up to close scrutiny. I have not seen this on the "official" viewer but then I can't stand to use it much for various RLVa reasons! Also the UI is abhorrent to me. So quite what is going on I have no clue.

This issue has been discussed with LL and they are aware that some unwanted changes have recently introduced to water reflections which manifest at SL sunrise and sunset. The solution is being sought at LL.

A truly typical "dialogue of the deaf". By the end of this thread most readers will have given up in disgust at the blinkered and sectional interests displayed. Second Life will never be directly comparable with "A list" video games - that argument was done to death years ago. Second Life is run by many people who had never otherwise bothered with video games...I am one of them. SL is saddled with trying to be "all things to all folk". As such it is populated with many who are resistant to change in order to appease the gear-head fashionistas. Guilty as charged. Not everyone is keen to transfer heaps of personal bric a brac to a new computer to get the latest shiny, regardless of the cost. We live in a real and rather costly world. Speaking entirely for myself, I am fairly content with how SL looks on my far from potato PC, but I am probably not your typical SL user, being largely immobile and close to my eighth decade. Just my little rant. Please continue your esoteric and utterly pointless "discussion".

The RC roll is happening but there is no post in this forum yet. Can we assume there is nothing new ready?