Aishagain

<key>RenderGLContextCoreProfile</key> is what I see, I assume you meant that, Gavin? (I should add that I do not have this hang-up issue)

True, the UDP bandwidth setting matters far less now than it did, since most server data, certainly all texture and object data is sent by http, not UDP. The operative word though, is "most". The servers still cap their sending capacity at about 2mbps, and from my experience, setting the bandwidth value much above 1500kbps or 1.5mbps merely increases my packet loss. My connection to SL is about 50mbps up, from the UK to the AWS system, and my modem can handle much more, so that part of the system has no influence (to the best of my limited knowledge). Wiser heads than mine will give you chapter and verse on this but that is my experience, as they say, YMMV.

These various slownesses and glitchiness are phenomena we have probably all encountered over our time in SL. I've been here since 2008 so I have seen a lot of weird goings on, most of which I can put down to operating system or PC glitches. The last Firestorm (6.6.5) was very slow to load and I never found out why...it always did so I didn't worry. The present one (6.6.8) is much quicker for me but loads of folk have a variety of issues, some of which are related to the C++ redidtributables that most folk have lurking in their software (not everyone though) or other maladies that suggest their antivirus programmes are being more aggressive than they used to be. If weird things did not happen, it wouldn't be SL, would it?

Possibly because it's not their problem to fix! The previous post gives you the solution; whitelisting the utility in your antivirus programme is the fix.

I don't imagine this is relevant to the OPs issues but the bandwidth listed in the Help specs at 30Mbps - 30,000kbps looks way outside any value I've even set mine to! One factor I did notice was that you (the OP) are running Windows 11 and I see more issues with folk running this OS than any other version.

With all due respect, what d'you want? Praise for "being outstandingly different"? You won't get it from me. I used Firestorm because someone else did the hard work of finding many of the debug settings and providing more understandable ways to access them. Yes, some folk play blindly with them and end up with a bloody mess of settings. That's their problem! With the default Linden viewer they would probably lose interest in SL long before they figured out how to make it work well for them. I've used Kokua and find it OK, Alchemy is underdeveloped and Black Dragon is just not for me any more than Kisten's was years ago. But I simply think "so what, each to their own". Going way back to the OP, they were simply going the wrong way about a good idea (in their view) and were advised how best to go about proposing it.

In order to give any useful help you need to publish your system specs in a post here, we may be able to assist then. Without any clue as to your hard and software, and your chosen settings, no one could offer any useful help. By system specs I mean Operating system specs and the info on the Help >about>...whichever viewer you use, so cpu, gpu/driver, RAM etc, edit out anything you think is sensitive.

It been an issue in SL for as long as I can remember. The simple fact is that Group chat, as envisaged by LL at the start of SL , was never intended as a general "conversation" application, say like discord and many other communication apps and as such it has neither the capacity nor the scalability to handle the various expansions of both the number and size of SL groups nor the use that it now gets. LL say they are working on a remedy but they have said that many many times over the years with no significant and lasting change.

2 Questions need answering first. 1) do you have the various .exe files "whitelisted" on your computer, even if they were for previous version of FS or any viewer, renew the whitelisting. 2) Which operating system does your computer use...Winows 10 or 11, iOS or Linux? Actually a third occurs...which Anti-Virus app do you use (if none you are using Windows' own Defender)? The whitelisting advice is the same. For whitelisting advice: https://wiki.firestormviewer.org/antivirus_whitelisting

Thanks @Monty Linden. It would be good if the "failure of execution" stopped sooner rather than later. Your reply was reassuring...almost.

The above comments are interesting and informative but in my opinion completely miss the point of the OP's concern. We have become used to various members of Linden Lab staff posting the broad details of the weekly rolling restarts to Maim Server or Release Candidate regions on Tuesday or Wednesday respectively. When there is no Release Candidate update, we are used to seeing no posting from LL on the following week. This is no real issue, but recently the posting of genuine updates also ceased without any explanation from LL. Those weekly posts were started by LL themselves to inform and warn their userbase(customers) of upcoming changes/interruptions to the SL service additional to the basic information posted on the Grid Status Page. Whether this withdrawal of information is actual policy or simply a manifestation of internal disorganisation is not clear but it IS undesirable. It would be reassuring if someone from LL were to explain this unwelcome development.

I'm sticking my neck out here about this. Yes,I have experienced it, but like Susie above anything missed has always appeared following a relog. I wonder if this is another manifestation of the issue with "avatar presence" (ie the object cannot locate the destination account) that as I understand things, is behind these friends list probems and the non-appearance pf the online friends (apart from one) at log in; both of which are server side issues, I believe. Maybe I am conflating several unrealated issues so it is just supposition on my part.

This advice may only be of use if your are a Firestorm Viewer user, but the defaults are likely to be the same in the Linden Viewer, providing you can locate your Debug settings floater. https://wiki.firestormviewer.org/fs_missing_windows

The matter of avatars first appearing as clouds is largely, in your case, down to the viewer not resolving the avatar until ALL its components are registered as downloaded, the slowest to appear tend to be (in my experience alpha layers which are commonly worn with much mesh clothing especially in Bakes on Mesh (BoM) mode. Currently LL are said to be looking at ways to speed up avatar rezzing, but as I see it, it is a function of the way that the rezzing process goes in all viewers. As an aside, I would not recommend having object LOD set as high as 4.00. The default value in the Linden viewer is far too low, so I compromise with LOD of between 2.5 and 3.00. Also the 50 series graphics cards, while being perfectly adequate for SL are a little on the weak side, 70 series cards substantially outperform them in crowded areas. An i5 CPU is fine so long as you do not co-run SL with other applications. Wireless connection is adequate but a hard-wired ethernet connection is far superior.

Other than the suggestion above I can only think of one other possibility and that is the saddle may not be compatible with Aurum. Does the Vae Victis saddle state categorically that it CAN be used with Aurum? What is suitable for other virtual flesh and blood Teeglepets is not necessarily compatible with the mech and skeleton horses.

I read the above posts with some interest. Some may remember the period while SL was headed up by Mark Kingdon. I forget which major player he came to Linden Lab from but I do remember the effect his "visionary approach" and "no nonsense" attitude had on SL. I am not alone In shivering at my memory of that period in SL. I sincerely hope the same error will not be made again. The advent of an individual with clear intentions but zero understanding fills me with foreboding.

Oh boy LL have really screwed the pooch (pardon my use of this term, it is not in my default lexicon) this time. I see reports of sound producing rezzed items now producing their sounds abnormally despite the server rollback and it goes further...my robot sounds HUD, which only produced a "beep" as I typed now beeps at every movement or teleport, and all I did was to TP into an RC Channel region after the first roll but before the rollback (I was investigating some apparently isolated issues with sounds). The HUD is worn, not rezzed and has not been available for some time, the creator having left SL last year. The change is not important for me but I'd say it represents a significant issue within SL unless it's an isolated incident.

All well and good @Signal Linden but the release notes for the recent and troublesome releases ARE NOT there! A laudable aspiration which is simply not borne out in fact.

And it would seem that this new server version is bugged in that sounds that rely on a trigger script (ie a day/night sound or a light which is only on at certain light conditions) play once (and apparently ONLY once) when an avatar TPs or logs in to a region.

The radio silence from LL continues on this thread. I simply ask if posting here by LL has been abandoned? If so, why? ETA: So it seems we must now rely on the information passed to us from Inara Pey's Blog or someother entity attending the Server User Group relevant to the release, via @Logan Elf . Release Notes anyone?

Thankyou @Monty Linden

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.