Aishagain

@Felicia Nova I suspect what you would need to do is to contact LL via the help facility on the Main site and have them synchronise your inventory with Aditi. This often takes 24 hours (at the weekend it may be longer). If you are a Premium member you could use Live chat.

If this were a motorway opening, say around 1960, I can just imagine the incident insurance lawyers rubbing their hands with glee and waiting for the bangs and screams.

Thankyou Signal

It is now 22nd August and the SLS regions are being restarted (bounced I assume). Would it be unreasonable to expect some clarification of all the foregoing mess?

...Pardon? I must assume that I am just too thick to follow all the above, but right now I am confused as heck! I didn't used to worry and I innocently assumed this was a minor matter and LL really had this sorted. No longer.

On the topic of viewer Texture RAM use, I have observed that the latest version of Firestorm for Windows, 6.6.14 seems to have a greater appetite for RAM than its predecessors, most recently 6.6.8. At a specific location, a fairly busy club, 6.6.8 would top out at about 6.5GB, but 6.6.14 stabilzed at 10.5 GB.

Not seeing this either on 6.6.14 (GTX1660TI GPU driver 536.23 and AMD Ryzen CPU), Windows 10 current build. Been hearing that there are some issues with Nvidia's 536.99 driver.

@Silver Selenium: Is this the one?

@Rebecca Crisp referred to 100% processing memory so yes, I guess I misinterpreted her text, my error.

Two things to check. First is to ensure that all the elements of FS are "whitelisted" in you AV programme. See https://wiki.firestormviewer.org/antivirus_whitelisting?s[]=fs&s[]=whitelist Secondly I notice that your texture memory is pegged at 512MB in your settings. By enabling Texture Memory Management in your viewer graphics>rendering preferences you ought to be able to access at least 2048MB of VRAM. above that FS will slowly encroach on your system RAM which since you have 16GB should not cause a crash. I note your session packet looss is 0.6% which is a tad high but since the session length was short that may be a red herring. This ridiculous CPU use phenomenon is not unknown but rare. @Beq Janus?

Yes. Not great but adequate.

Maybe I wasn't clear. You "can" run Blender and photoshop on your machine. What you will NOT be able to do is run those programmes AND SL. SL is very memory hungry and it will slow your machine to a crawl if any of the other programmes run alongside SL. So, if you will run SL on a seperate machine, sure go ahead. If not, sorry to be blunt but forget it.

In a word No.

@Garretmsl you need to set your viewer as the default handler for SLurls. ETA dammit! Rowan beat me to the link again!!

Some time ago I had a similar baffling issue with a DJ stream that simply would not run in my viewer, yet ran perfectly in all other audio applications. I never did find out WHY but when I was running the viewer it triggered my AV to block the url. I only found out what was occurring when I discussed it in detail with my AV support and they told me that the domain had been blanket-blocked due to a single rogue instance with one url! They checked the domain and a couple of days later the stream ran as normal in the viewer. I never got an explanation of how a single rogue instance had caused the issue. In this case I'd be inclined to see if the security settings of the two computers were identical.

Look in the "worn" tab of your inventory. You should be wearing a minimum of four items: Shape, skin, eyes and brow shape/bald cap (it has verious names). If ANY of those are not worn you will not rez and you may need to take action. One way, if your inventory is fully loaded is to create a very basic outfit containing the four basic elements, Shape, skin, eyes, and brow shape/bald cap. all wearables not appliers of anything. Log in, select the outfit and click "replace outfit" ETA; as I was typing this Rowan Amore gave you a useful link which you should read.

@AkiraKagami as all the above contributors note; you do not need 400fps for a perfectly smooth SL experience. It is frequently claimed that the eye cannot detect anything above 30FPS. Of course it can, but anything above say 70FPS is just wasting energy and in your case superheating your GPU and proably the rest of your PC in the process, leading to thermal shutdowns. If You use Firestorm use the viewer's own framerate limiter (in Prefs>Graphics>rendering) or if not use the Framerate Limiter on the NVidia Control Panel...the former is much preferable.

@Naiman Broome One common problem with downloading from the FS website is the firewall or AV blocking the d/l due to a certificate issue. Usually the OS will tell you that the d/l is not reccomended but if you then click on the "other action" or "other options" button it should present you with a "download anyway" option. The precise message varies depending on your OS (Operatiing System...Windows 10/11 or equivlent Apple version) and your security level set in you browser. Once the download is complete (as it should then be) proceed as normal. It is imperative to only download the viewer (whichever you choose) from that viewer's official website. Accept no substitutes.

Y'know, this all still leaves me pondering...yes, the render process uses (or CAN use) multiple threads and in my case does, but that still leaves me unconvinced thatthese other referred threads are on other cores. I have carefully, nay, obsessively, watched Task Manager on my 12 core CPU and I'm damned if I see any activity outside of almost transient spikes of activity in any other than the first core, which is running at or near 100% all the time I am using the viewer. What am I missing? ETA: I am a Firestorm user...I detest the UI and functionality of the Default viewer. I only use it when I need to convince LL of a bug.

Well dammit, I didn't know some of that Kathrine! I stand thus informed. I have been indoctrinated with the "SL only uses a single core" mantra for years!

Multi-thread maybe but still single core only.

Yes, as a Thick Brit I forgot it's the fourth today..mea culpa.

The Absence of any info regarding restarts to Main Server regions today is puzzling. I have understood the new system whereby we should expect Main Server restarts on Tuesday and RC Channel restarts on Wednesday, new information being disseminated via the Tools and Technology Blog, new Server versions being outlined on the release notes. All well and good...but.... I noticed the absence of a "heads up" for Main Server regions on the Status Page over the weekend (the potential of some limited deploy on selected RC Channel regions is reported), so I assumed the Main Server Regions were just getting their weekly "bounce" restarts. Today, nothing! Now maybe I'm just too picky but doesn't the absence of a restart of ANY kind class as an unusual circumstance and isn't THAT worthy of some/any comment?

@heartfullady Those libraries should be downloaded and installed BEFORE intalling your Firestorm. Try ensuring the libraries are in place before attempting another download/instal sequence.

I don't think it is broken as such, I suspect that it just operates in a very clunky and unhelpful way in SecondLife. In games where the complexity of scene to be rendered does not change as much it may well work as intended but others more technically minded can explain its operation better than I. @Beq Janus?