Aishagain

It is? Goodness me, I must have got my download from an unauthorized source and it is missing stuff...'cos mine works just fine! PS: Just kidding I got it from the firestorm page (I'm not (contrary to popular rumour) stupid).

So, now that we are to be on a new software version, when do we see release notes?

Rolling Restarts for most Second Life RC Channels Jul 7, 13:00-19:00 PDT We will be performing rolling restarts for most regions on the Second Life RC Server channels today (Thursday, July 7th) beginning at approximately 1:00 PM PDT. Please refrain from rezzing no copy objects before and during the restart, and remember to save all builds. Please check this blog for updates. Posted on Jul 7, 12:29 PDT hmm. Methinks thou speakest to soon, or is this rolling the changes made to Bluesteel to the other RC channels? And now Main Server as well what DID you lot break?? (non judgemental semi-ironic wibble).

I wonder if the update rolled to Bluesteel regions (a subset now known only to the Lindens, of course) is the cause of this elevated Region crash rate?

Yes, Ardy. That's most likely the reason this fix happened so quickly! Perhaps folk won't be so quick to dismiss the value of OpenGL subsequently. Perhaps.

Yes I installed the new driver shortly after its release to the UK last night, so far it appears to be good. All reports that I have seen in the FSE group bear this out. This is with a GTX 1660Ti on Windows 10 21H2.

*Sigh* Seems that NVidia only listed Firestorm because that was the name most often mentioned in the myriad complaints that NVidia received. Both Beq Janus yourself and myself mentioned that the issue affected ALL SecondLife viewers, including several TPVs. If they fixed this mess perhaps we should be grateful and accept that their ability to read is no greater than Linden Lab. At this time the new version has not made if to the UK users (at least not to my Experience set-up).

@Jira36 The issue you describe could only be as a result of changes on your computer. Nothing is changed in the Viewer. Do you use WASD for movement or the arrows on the keypad? Check the set up of the keyboard on your computer.

@LykanXEclipse The issue was reported to NVidia on the day of the driver's release and I had confirmation via the NVidia user forum that the issue had been added to the list of open issues. We are perhaps fortunate in one way that this issue does not affect "just" SL but also Minecraft among others, so our chances of a "Hotfix" being issued is substantially greater. The issue has also been reported to NVidia by one of the FS developers, Beq Janus. Frankly the more complaints that are registered the better!

And that is the best advice that can be given. Frankly SL is running without issues for me on a driver which is upwards of 6 months old now (497.09) and I see absolutely no point in updating to a driver that perhaps has a profile for a new fad game and little else. NVidia do not test against such systems as SL, (perhaps they should since SL is a beast of a programme), because it is a vanishingly small minority interest. NVidia have a list of "open isssues" which need addressing and the one afflicting SL (which is only one among several other applications affected, I might add) is on the "to do" list. Sadly several on this list, I suspect, also appear on the "too hard, can't be bothered" list.

@Silent Mistwalker I was in no way critical of your rig, I suspect you have quite missed my point.

Yes, some games apparently do play without issues, but that is NOT the point. Just because it is "far harder on graphics" does not mean that it uses the parts of the graphics system that are affected by this bug. When you log into SL and use either ambient occlusion of any of the advanced lighting model, ie deferred rendering, ie shadows etc, be assured you WILL see artefacts. (As a test I tried the driver on my system which uses a GTX1660Ti, and sure enough I got striations etc as soon as I turned on shadows in SL. I rolled back to an earlier (MUCH earlier) driver and they went away. I will not be doing that again. ETA: Oh, and by the way the GTX 1660 series are not particularly powerful GPUs by today's standards. I found that out to my dismay some time ago.

Pipe-dream. NVidia has shown scant regard for some of the minor videogames in the virtual firmament, and most of them have a much larger userbase than Second Life. I share your sentiment that it would indeed be a good case-study for NVidia but my limited interractions with them (most recently over this currect debacle) suggest to me that most of their technical staff neither know nor care about SL. For us in SL we are fortunate that this issue affects a far wider userbase than SL, I understand Minecraft is impacted as well, and THAT ought to set alarm bells ringing at NVidia. For now we must stick with the known workarounds, namely a rollback to a driver previously known to be good for SL or try using a Studio driver from NVidia, about which I know nothing.

Just a quick "heads up". NVidia are now aware of this issue and it is on the list of "Open Issues". I am assured that they are "working on it" (sic).

Just a quick "heads up". NVidia are now aware of this issue and are apparently "working on it". I just hope they work quickly.

It is beginning to look as though NVidia have made a complete hash of their most recent GPU drivers for most Linux and Windows. see:https://jira.firestormviewer.org/browse/FIRE-31747 & https://jira.firestormviewer.org/browse/FIRE-31746

Alisha, please see https://wiki.firestormviewer.org/fs_bake_fail and read the whole article. You can try replacing all worn items by a full outfit replace from your outfits folder, always assuming that you have any saved outfits. Also you might try using the default Linden second Life Viewer: https://secondlife.com/support/downloads/ and see if you rez on that viewer.

The issue of being disconnected when SL cannot resolve the start and end location of a requested TP is something we all suffer now and then, though in recent months it seems far more common than it was for years. At these disconnects SL loses all record of the account's configuration and reverts to the state at the last "good" shutdown, including any scripted functions. Strangely (to me) any worn mesh changes are retained but any worn layers, be they alpha or applied (I suppose these are scripted), are not retained. In these times of BoM that can be a real pain in the shoes... I mean ***e. I have never experienced (touch wood) any of the more extreme inventory or photographic effects mentioned above.

@Prokofy NevaI was quoting Mazidox Linden's words, quite what he meant I would not like to say but I would imagine that the technical folk were watching the boot-up process for each sim-server closely to see if they could identify any rell-tale signs of incomplete loading of their software.

This puzzles me. When Second Life was hosted on Linden Lab's own servers inside a terrestrial data centre, I can recall that a rolling restart instance where new software was being rolled out would take upwards of 20 minutes, sometimes an hour. Over the years that time did reduce somewhat but I did not start to worry unless my home region was down for more than 45 minutes. Following our elevation (cough) to the cloud such restarts could take over 90 minutes since the new server hardware appeared less happy to accept new software and Oz Linden and others noted that the process was "not as smooth as we would wish" Recently Mazidox Linden told us that rolls were being done more slowly out of "an abundance of caution", and some servers appeared reluctant to restart promptly. Perhaps I have been fortunate but my home has only once in recent months showed a reluctance to restart, and even so the downtime was less than two hours. As Love Zhaoying notes above: There could be a new, more thorough verification process in place, which occurs before the simulator servers are "brought back up". This is, as I understand it, so. Perhaps we should be glad that LL are proceding with "an abundance of caution" now, since the alternative would likely entail a good deal of data (asset) loss. I have an analogy. You build a tower of cards: now, as you add new and better cards to this tower, you need to remove some of the older redundant cards from lower in the stack. If this is not done carefully, the entire pile comes crashing to the ground. Not a good scenario. Therefore all additions are done with great care. SecondLife is a very high, somewhat unstable tower of cards. I think we would all prefer that it did not come crashing down.

I am fascinated by this phrase. What on earth do you mean by it?

@iceing BraveheartLaudable though you request is, this is not the place to make it. Put your request/ideas into a JIRA submission under "feature request" and someone from Linden Lab will see it. Posting here, in a residents' forum, is unlikely to reach their eyes. While some members of the Linden operation do vist these pages from time to time, your chances of them seeing your post are minimal and the likelihood of any action on their part resulting is tending to zero. jira.secondlife.com is your point of entry using your SL login.

Has anyone else noticed that their region traffic is oddly low since this last set of rolls? I am looking at 2 different regions, both on Main Server so on 571998. Both are less than 50% of their normal value. It's only a small sample so far so I don't know if it's an issue or not, yet.

Still no Deploy information. This is disappointing and quite honestly a little worrying. LL must have a reason for not giving out the information post-roll about this week's deploys, if it is just arbitrary laziness that's bad, if it is because they are concerned about potential exploits, that's worse.

@Linn Darkwatchdid I say that it was either/or? No; some of the work done recently has NOT been of a high standard and I, like many others have complained. There is much that they "could do better". Linden Lab's user facing approach still is FAR from satisfactory, the repeated litany of "attend Server User Group meetings" is frequently trotted out. I cannot, for very good RL reasons. One thing that I fervently wish LL would address is the frequent silence on the Server Thread regarding the upcoming rolls. Some weeks it is more important than others but it is still necessary, in my opinion. In that case it is my opinion that you have been VERY fortunate.