NiranV Dean

First of all, sorry it took me so long to answer, i don't have my eyes everywhere and i had some PC issues the entire day... To answer this for everyone, AVX is a (in theory) faster version, if your CPU supports it, take it, otherwise use the normal version. You should see no difference in the Viewer itself, both are the exact same Viewer, they are just compiled with and without AVX extension. Movement keys have been changed to the default (which SL should have really had from the beginning) AWSD strafing movment scheme rather than the long gone rotation movement. BD however (unlike other Viewers) offers you the option to easily and fully remap all controls which would usually require you to edit files. If you need help doing so you can always ask for help. Camera controls are the same, unless you are speaking of keyboard controls once again, i tried adding all of them but leaving doubles and/or overlapping combinations out, such as CTRL + Alt + D which at the time was used to enable the Advanced menu (this is no longer the case obviously and i might have to look at readding all missing combinations if there are still any). Once again i don't want overlapping controls, AWSD are very special keys which are used for several things (snapshot for instance uses Ctrl + Shift + S which means i cant bind this one either) You don't have to choose between Projectors or Sun shadows, you never had to. I don't know what you mean by that and whoever told you that you had to choose between them has no idea what he's talking about. BD just like any Viewer offers you the option to enable shadows (without projectors) or shadows (with projectors) or disable them all. The only option missing is projectors only (which can be done with windlight editing or by playing with the shadow distance/resolution settings (hacky but works). I even use both in the very video you posted. Also that's just the current video (for halloween) i'm soon going to switch it back to the original:

Das Problem kam mit 3.6.0 im 30. August 2019 in den Black Dragon und wurde kurz darauf bereits am 4. September behoben und released nachdem ein paar User das Problem berichteten. Warum Firestorm das Problem entgegen meiner ausdrücklichen Warnung vor diesem Bug lange bevor die ihr Update gemacht hatten dennoch diesen Bug nicht gefixt haben ist mir schleierhaft. Linden Labs hat ebenfalls ziemlich lange gebraucht obwohl ich das Thema direkt am nächsten Meeting angesprochen hatte und dort bereits einen Fix angeboten habe.

Personal recommendation: Upgrade from your FX to a Ryzen 3600. That's what i did and the performance is much better for relatively little money. I've been running everything ultra and shadows since it was introduced back around 2010/11 all with the same AMD FX 6200 at the time, performance was "Okay" 20-60 FPS that is with basically every avatar over 250k complexity (BD complexity not LL complexity) jellydolled, which was 80% of all avatars. I never had to disabe shadows and if i did it didn't help at all. Though i always thought of an upgrade when the chance arrives, this chance was obviously a Ryzen 3600 (actually i was aiming for a 2600 at the time but then 3000 series was released for the same price) and the difference is quite a big one especially around people i get roughly double the framerate and can disable jellydolls completely (although i really shouldn't render badly optimized avatars anyway) and only use max avatars instead while still having around 40-50 FPS with shadows on but even with a Ryzen there are still places where my framerate drop into sub 20, theres simply nothing you can do about those places, they are simply badly optimized and turning down graphics for these places wont help much because the problem isn't your PC or the rendering its simply the bad content around.

There are several values that need to be 0.0 since focusing and other actions are seperate modes with seperate attention values and the lookAt will still be shown, it just won't go anywhere anymore because all your avatar will focus on is looking straight ahead idly like it does when you are in basic third person mode and nothing else is happening (aka the follow-your-mouse-movement-idle).

It is possible.

It does yes. SL has been notorious in the past for having a lot of issues with AMD cards and if you wade through the Viewer code you'll find quite a lot of weird extra hacks that need to be done for AMD to not do something stupid.

AMD's bad OpenGL support is still pretty recent, probably wont change ever now that OpenGL is being replaced with Vulkan anyway.

This is none of it though. SL has always run better on NVidia cards because ATI/AMD's infamously bad OpenGL support (which SL runs on)

CPU always bottlenecks no matter which CPU you have, that's just SL. I had the same CPU before and i can tell you that its fine and can easily get 40-60 fps with shadows and everything on, with avg 30 fps around crowded places given you don't allow every ***** avatar to render. I highly recommend reducing complexity (although honestly its kinda worthless since 40k already allows the worst of the worst to be rendered while proper optimized avatars are not) to something around 70-80k and reducing max avatars to 5, this alone should give you a massive boost around people. Since you can't tell apart good from bad content with the default complexity i can't recommend manually jellydolling people since you wont have any value to go by (again complexity as it is in FS and LL Viewer is complete trash and useless)

What you see is probably a combination of a lot of small factors coming together. FS uses KDU, BD uses OpenJpeg. OpenJpeg is known to be much slower, which would explain texture loading/decoding times. Meshes and other objects i dont know, i'd assume Firestorm has probably made alterations to how items are downloaded/cached to improve performance and/or reliability. And there's always the "random" aspect of SL. I've never seen a difference in loading times between OpenJpeg and KDU which is why i don't believe in a use for KDU. OpenJpeg is totally fine until it isnt anymore.

My GPU wasn't maxed, just dying because it was shoving textures around in memory which kills performance, if you want to max your GPU turn SSR or Volumetric Lighting resolution up, or go super nuts with Depth of Field blur.

SLURL's to these places would be a good start, other than that i assume its something you've set. With your Intel you should never run into a situation where you are getting only 1 FPS, EVER, it's straight up impossible with normal settings. I went to places, enabled full res textures, disabled impostors and jellydolls, let everyone fully load and even though my GPU was basically burning in hell i was still getting more than just 1 FPS and that was with shadows and everything on. There were like 30 people around so i doubt you can manage to drop that low without *****ing up a setting somewhere.

The taxing part about "Ambient Occlusion" is the the light softening which in combination with SSAO does show a slight performance impact, SSAO in itself however is basically free unless you are using a GPU from equivalent of a GTX 260 or slower but then you'll be running into a whole host of other issues.

What you want is Ambient Occlusion. LL just hasn't cared to use it properly yet, there are a few options you can change to make it stronger (or ... well actually visible) because right now Ambient Occlusion is basically configured to be a waste of resources (although almost none because SSAO is almost free)

I tried that. Needless to say the Viewer acts very allergic to that and crashes really quick when there's no fallback. Under normal circumstances there is no need for it but if you're a developer and you're editing shaders and stuff and you ***** up the shader, it will try to step down until it finds a shader level that works, too bad if the shader you are editing is already level 1 and there is no fallback. Poof Viewer gone. I didn't notice any performance improvements, such improvements would be miniscule and are on the same level of optimization as what i've been doing, replacing setting calls with cached settings so the Viewer doesn't actively do slow setting list lookups. I didn't notice any performance improvement from doing so, if anything it would be in the sub-fps range which you cant see anyway because SL's framerate is unstable as hell anyway.

That's not true. TPV's are a lot more than "just" code grabs and different defaults. Exodus at its time did redefine graphics in a major way, it is the reason we have Materials today. Alchemy, although only privately (and only from hearsay and pictures) offers some extra graphical features including some NVidia Gameworks stuff. Black Dragon is the only Viewer that "sets different default settings" for graphics in addition to offering a variety of extra features, including those from Exodus. Firestorm offers Exodus's post processing stack (Tone Mapping, Color Correction and Vignette) just like BD does but doesn't (anymore) feature additional features. They did have Screen Space Reflections but got rid of it due to customer complains. So if anything Exodus was a major step up and Black Dragon is the closest to a recent "re-definition" of graphics. We are limited of course in how much we can redefine graphics especially as TPV since only those on said TPV would have these graphics and establishing a new default is nigh impossible, even LL doesn't get it done after a decade (so many people still using windlight or legacy rendering even though deferred rendering and shadows have been around for a decade now) and i'm further limited by my lack of skills regarding rendering (and more specifically OpenGL rendering) related coding knowledge. If i had the skills Exodus and Alchemy teams have i'd have "redefined" SL graphics every year anew.

Ugh. I hate when people bake effects into textures, it clashes hard with the in-rendering features, doubling down on it is a surefire way to break these. Double shadows... double Ambient Occlusion.... Ambient Occlusion should only ever be baked on very special occasions with absolutely static items and static places (so basically never) and if anything should only ever be used to suplement the already existing in-engine SSAO, not replace it. Whenever i see baked Ambient Occlusion it combines with the rendering SSAO and gets way too dark. Here two comparisons of acceptable ambient occlusion baking (although the roof and wall in the background do have quite strong ambient occlusion baked in) https://cdn.knightlab.com/libs/juxtapose/latest/embed/index.html?uid=037c4aa8-2bc1-11ea-b9b8-0edaf8f81e27 https://cdn.knightlab.com/libs/juxtapose/latest/embed/index.html?uid=28ddc4fc-2bc1-11ea-b9b8-0edaf8f81e27

Du "crashst" nicht beim Teleport und das hat auch nichts mit den Viewern zu tun, weshalb es unabhängig vom Viewer passiert. Wie einige bereits vorher erwähnt haben ist das momentan ein Allgemeines Problem von welchem ich bisher verschont geblieben bin (ich kenne auch niemanden der dieses Problem hat, würde mich aber nicht wundern wenn es im entfernten mit dem ganzen Attachment-Verlust ding zusammenhängt). Was hier passiert ist das du ledeglich nicht rechtzeitig eine Verbindung zur neuen SIM bekommst, was an vielem liegen kann, dein Router, deine Firewall, Third Party Internet Überwachungsprogramme oder anderweitige Einstellungen (das beinhaltet auch die vom Viewer, was aber hier auszuschließen ist da du sonst nicht in SL kommen würdest), sollte das ganze nochmal in größerem Maße auftreten kannst du davon ausgehen das es mal wieder ein Serverproblem ist, bis dahin alles was du machen kannst ist abwarten und Tee trinken bis die das Problem behoben haben. Du kannst aber mal einen TP wagen mit leerem Avatar (test Avatar oder generell vollkommen ohne Attachments) und sehen ob das hilft, wäre durchaus interessant zu wissen.

I've added an "Object List" to Black Dragon as well but i haven't yet found out how to resolve names of objects so they are all just the UUIDs of the prims/objects. I assume that resolving the name actually needs a request to the server, which if doing to the entire list of objects around sounds like a mini DDoS for each and every user using it which is why i've so far held off from doing something like that (that and the fact that area search is commonly used to cheat in games and events)

The "About Land" window actually has an object list if you are the owner of the parcel/region, where you can see all objects of yourself and others, although its grouped and you can only select them all at once.

Thats not an area search, that's the pathfinding linksets window.

That makes it just as much real as any other Viewer. Anyone can use it, anyone can do it just like anyone can open preferences and enable/disable graphics features but just because not everyone enables them doesn't mean they are not there. Third Party Viewers are alternatives BECAUSE LL doesn't offer these, if i was in charge these things would be baseline. The unwillingness of everyone (including LL) is the reason this hasnt happen yet.

I think you got the whole "reality" thing a bit wrong, i mean that these shown graphics are not some faked eyecandy some company is showing to boost a product, these graphics are actually archievable, they exist for anyone to use who spend the time to do so and similar graphical fidelity could become the new standard if SL just moved forward. I'm basically showing "tech demos" of what could be if SL wanted to.

The point of my pictures is that they are just as much "real" as they can get. Anyone can similarly awesome looks if SL would finally get its butt up. Right now i have to fix issues FOR content creators to make it look like that, and i have to change settings (because obviously a region cannot change these outside of windlights) but all of these issues could be fixed if SL gave us these tools (experiences are a tiny step into that direction, windlights another, something like RLVa is another step). Obviously nothing will look good with the same settings you use for a certain scene because your settings were made for a totally different scene with a totally different "goal" but my point is that the overall fancy graphics can be achieved by anyone if there was a general accepted "standard" of graphic settings everyone builds for (not even those we have right now, some build for deferred rendering, some for windlight and some not even for that and still for 2007 graphics). Most of this is up to the content creators, the rest is just LL giving us (or the content creators) more tools to change certain aspects of the viewer to make users have a certain experience they want on their region.

Pet peeve #4: Problem explanations that are not informative enough for me to make a call on what the issue is forcing me to reply with: So what exactly isn't working? Does the Viewer not start up? If so does it give you an error message?