Aishagain

What you describe appears to be the action of the V-Sync function as the viewer's FPS falls below the refresh rate of your monitor. To avoid "tearing" of the video (a phenomenon I barely understand since I have never knowingly seen it) by rendering an incomplete frame, V-Sync reduces the frame rendering rate to a fraction of your monitor's refresh rate, usually 1/2 though on occasions it might be less. That is an undesirably slow frame-rate for most folk which is why I so forcibly condemn it. The stutter seen at other times can be closely correalated with VRAM and system RAM use by the viewer and I assume reflects the lag difference between accessing on-board VRAM on the GPU and accessing system RAM. Whether that is correct or not it is a real phenomenon and may or maybe not a result of some arcane video memory function. That I don't see the stutter when Dynamic Texture Memory management is disabled my be a complete red herring since with it off, the texture thrashing that results is considerably less desirable than the stuttering (for me, YMMV).

I am a tad surprised that this topic has attracted so little apparent interest. This has been repeated on other threads on this issue. Does no-one care or is it just a very few of us that experience it? If the latter, why?

This is an issue that I've been looking into a lot lately. I beleve that it is caused (partly at least) by the swapping between your GPU's VRAM and system RAM. Like you I have 32GB DDR4 RAM with an AMD Ryzen 9 3900X CPU, but once the texture loading exceeds the value set (somewhat arbitrarily) for your GPU in Dynamic Texture Management (look in Preferences>Graphics>Hardware settings) which I assume you have activated. I also assume you are using Firestorm (if not you will grossly underuse the VRAM available on your 3060). I found disabling DTM and running at the arbitary 2048MB limit imposed for my GPU (GTX1660Ti 6GB) resulted in a smoother run but quite unacceptable levels of texture thrashing. I have, as yet, not found a "sweet spot" between texture thrashing and stuttering and I am thinking that the balance between the two is something you may well need to establish by trial and error yourself. Given free reign, Firestorm is a real resource-hog when it comes to VRAM use, and I doubt if it is unique in that regard. There may well be more accomplished minds able to offer you more effective solutions. All I can say is that V-Sync is a poor function and results in very poor FPS on occasions. Avoid it like the plague! I have tried various frame-rate limiters, both the NVidia one in the GPU's own control Panel and the Firestorm one and while neither are brilliant, the Firestorm one is better. ETA : I might add that I was sufficiently irritated by this phenomenon that I raised a support request in the Firestorm JIRA, but to date I have had no useful response.

The perennial question. Whether to be looking "dead and likeless like a store mannaquin" or a sufferer from tourettes?

Seems that the RC channels (not sure if one or all of them) are getting 2023-06-09.580543. Looking at the software's release date it must've been QA'd by the night shift!

Just so that anyone waiting for their region to restart knows, today Main "SecondLife" server rolled to 2023-05-25.580357 today. My region was late back up and was down for an hour so don't sweat it if you have been made temporarily homeless!

I wonder if some benign Linden or moderator might consider closing this thread to further posts. Otherwise this pointless bickering might go on for ages.

Oy vey, enough, Gavin!

Good grief. If I expected that, I'd be expecting a lot more! No, I just expected better service, a thing I am just not going to get any more, I realise.

Nope. Didn't get either this week. And yet the SLS channel is being restarted. In what universe does not communicating constitute communication?

And, as if by magic, the SLS channel restart is in progress, the notification accompanied by the "scheduled" notice. Did anyone see the "scheduled" notice before the roll started, 'cos I looked less than an hour before and I didn't see it.

Intriguing. The Grid Status Page announced that the issues surrounding 2023-05-25.580357 "should be" resolved now. I wonder if that means another rollback? With the absence of anything new in the release notes and no mention of a restart schedule for either SLS or RC channels on the Status Page, what will happen this week? All will be revelaed in due course, no doubt. Or not.

Well you live and learn! I did NOT know that to rez Linden plants required a special ability! Or about the sandbox angle either. The coalesced vs linked aspect had not occurred to me.

Go to a sandbox region (find in search). Rez the item. Find the parts you want. Go to edit on it. Unlink it in edit. "Take" that item back into your inventory. Keep doing that for each item until you have them all. You will have to rename each item in edit BEFORE you "take" it. Call each part something you can remember.

And it looks as though the viewers' code really does NOT like LL's new thumbnail code. 2023-05-25.580357 is not working as intended but at least it isn't a crasher this week. See the Grid Status reports.

This week Main Server was just bounced (restarted on the same software version). That's 2023-05-05.579955 Some or all the RC Channels should get: 2023-05-25.580357 tomorrow. I'm guessing that's a debugged version of what was rolled to Bluesteel last Wednesday.

Once again I totally fail to see your point, Love. Whatever Signal Linden's post says does not explain the absence of ANY communication from LL since his post. Never mind, we will not agree, so it goes.

So, in the absence of any meaningful communication we must employ educated guesswork as to what will happen this week (commencing 29.05.2023). The silence from LL following the rollback last Wednesday is deafening.

Interesting. I heard coincidentally about another user caught out by an unannounced restart/rollback yesterday. No announcements officially though! Anywhere.

Bump

Secondlife Server (Main Server) Channel was rolled to 2023-05-05.579955 today. I can find no information as yet on the plans for tomorrow's RC Channel roll. I imagine LL have been a bit busy sorting out the issue with Secondlife.com today. ETA: RC channel will get a new server version: 2023-05-19.580235 It is my hope that someone wiser than I can explain those changes listed! It is unclear if this will be deployed to all RC channel regions. Thanks to Pantera and Lucia I see that it was only rolled to Bluesteel regions. I must assume the others were just "bounced".

@axxya Bandalora..yes, the frieds list issue has dragged on a long time but it was a complex issue and LL are testing their final fix on a couple of ex-sandbox regions at the moment. The Linden purchase issue was due to some serious probems with Secondlife.com and its related pages and was fixed about 15 minutes ago. I know because I could not purchase Linden dollars myself or access my account and both are now functioning normally.

@Anthony Marques..Nal's advice is good as regards the viewers and there is nothing to add. However What is still unclear is the perennial issue of boy/skin/shape. You say you had to buy a seperate body and skin, yes, but only if it was a mesh body. The default body is not visible since you must at all times wear a skin and that skin cannot be taken off, only replaced ( a skin will only offer you one option, to "wear" not "add"). The issue you appear to be having is most likely that your computer is not rezzing (resolving) the mesh body of your friend. Does anyone else have the same issue when looking at your friend? If not I would surmise that the issue is with your computer. WARNING (the next paragraph may cause your brain to boil) Once we get onto the topic of mesh bodies it all gets a liitle more complex. Mesh Bodies are are in fact not bodies in any real sense; they are simply mesh objects (that happen to be body-shaped!). I do not want to boggle your mind with more complications like Bakes on Mesh (BoM), whereby scripts in the mesh body show the base skin that your Linden body is wearing. If at THAT point you wear an alpha (most mesh bodies come with their own full body alpha) it all goes red! (See what I mean about complications). Just for completeness your base default body has four components that MUST be worn in order to rez, one skin, one shape, one brow/bald cap/hair and one lot of default eyes. If any of those are not worn you will not resolve and will remain a cloud, or if particles are off, a white egg, in the Linden viewer.

Fairy Nuff. I was repeating something I'd heard. Your version makes more sense, though I still wonder what is causing the issue with avatars wearing evoX heads.

Reading the heading post saddens me. For several reasons: So Lindens regard this communication with their users as "pushing paper around"? All this indicates to me is their misunderstanding of the value of communication. Yes frequent blog posts will be good but bear in mind that replies are not allowed on the Linden blog posts. Love, YOU may know who to ask but I'm willing to bet the majority do not. My takeaway from this is that the staff of Linden Lab that remain simply do not have the time to genuinely engage with their customers (there's that awkward word again) in any meaningful way.