Viewer Bug Reports

While trying to understand why Featurettes compared to current releases felt like a more "smoother" experience, even after all the "improvements", I found the following: - Performance goes down by a lot after the viewer comes back into focus, while switching between applications , even after waiting a minute or so until the textures are "resized/rendered", not only in FPS count, but stutters... really noticeable comparing to a after login experience, I never noticed that with older builds... and keeps getting worst overtime in long sessions... its not memory, since this machine has a 64gb DDR4 @3200 and videocard with 16gb VRAM. This only happens on a PBR scene (several PBR objects + PBR EEP + reflection probes ). Steps to reproduce: Login with DeltaFPS, wait about a minute or so, cam around a bit... take a reading. Switch to another application (Youtube, Substance, etc), use it for a few minutes, while SL still logged in, in the background. Switch back to the viewer, wait for a minute or so until all textures are "full rez" again, or until FPS stabilizes. Cam around, take a reading, which should show a much decreased performance, also compare how it feels rotating the avatar, stutter, etc... This simply does not happen if you are on a "legacy" only scene (Legacy materials, Legacy EEP with Reflection Probe Ambiance set to zero )... performance is pretty much the same after switching and using different applications. I'm attaching a few screenshots with such readings which I can reproduce easily, it gets worse overtime with longer sessions, with the lowest I've experienced going down to about 50fps, really "stuttery" rendering, those are just examples, while writing/editing this, and switching back to the viewer, ExtraFPS is at 60 fps... On another note: ExtraFPS is probably right there as one of the worst RC releases when it comes to its state, is more like a "preview" released for a specific small group to test: EEP controls (Editor, Personal Lighting), simply does not work correctly, its broken, no "realtime" effects to see results, does not position the sun (also visible on the snapshots below), etc, there is no way to know if something was saved or not. Due to the current implementation of a "new" tonemapper, colors are completely off, oversaturated in PBR scenes. Probably forgot to "tonemap" the EEP too. Full bright textures are now completely overblow, its really hard on the eyes to play for a while looking at that rendering. Is the "fix" for too dark, to be oversaturated? Seems like you are trying to fix bad EEP settings with a different tonemapper, mistake over another mistake. Colors on the color picker simply don't match, they are different (maybe forgot to "tonemap" the color picker too?). Why the default documentation and tutorials for authoring tools with recommend settings that dont match the new "default" tonemapper. What is the solution for whoever already created several PBR items to make it display as intended with this new "default tonemapper"? Change all over again? Tell customers, "switch your tonemapper"? Usually that kind of "stuff" is really implemented in third party viewers, which is great, specially if they serve a specific purpose (Black Dragon as an example for photographers, etc... ), not the "official viewer"... one of the great benefits was conformity between authoring objects and publish in-world (From Substance as an example, to display/sale in-world), easily reproducible steps, what you see there, is what you get here using default/recommended settings. Is that gone? Are we going back to mess?

Extreme locked lag avatar is not able to move easy at all no more, upon newest viewer update. Laptop #1. No issue like this on older with Intel Tiger Lake 4 cores CPU with Nvidia MX450. High FPS no lag or locked lag. No viewer freeze up on graphics settings change.. Old laptop truly is running SL way better than ever before. Upon Newest SL viewer. Laptop #2. Recent Issues are new on this latest update. Dropped the FPS is above 15 at 1st. Then reduces lower. 2 - 3 FPS. Then extreme lag & stopped locked AV. Extreme long freeze up to a minute on graphics change. This has latest CPU Intel(R) Core(TM) Ultra 7 155H has 16 cores along with ARC GPU with even higher specs than older laptop #1 with MX450. was not like this a few months ago after got this new laptop. New laptop should run SL far faster & better than old laptop #1 from 4 years older with lesser CPU & lower spec GPU.

graphic preset select

I present the same model (a small avatar accessory) with 2 different sets of LOD models. In each case the lowest LOD model has been 'zeroed out' to 18 tris as is typical in this use case. Triangle counts are as follows. * Model 1 - High 63040 (36k virts), Med 15760, Low 3940 * Model 2 - High 15760 (10k virts), Med 3940, Low 3940 Both of these models are visually indistinguishable in use. The DAE files prior to upload are sized as follows. * 63040 tris - 9.2mb * 15760 tris - 2.2mb * 3940 tris - 500kb Working on the dae sizes alone ... * Model 1 - 11.9mb * Model 2 - 4.9mb However .... * Model 1 - Download weight 0.7 * Model 2 - Download weight 3.1 When worn ARC is equally broken (as reported in firestorm) * Model 1 - ARC 319 * Model 2 - ARC 672 Objectively Model 2 is better for performance. Duplicating the mesh for 2 detail levels is punished to the point that using a sub division surface modifier to generate an insane 63k tris high model results in 'better consumer numbers' at intended object scale (it's also cheaper to upload). In addition to model duplication being unnecessarily punished, the scale component of Li accounting is fundamentally flawed and pushes creators into a situation where large items need to be low poly and tiny (often worn) items are best high poly! No wonder everyone's avatar is solid in wire-frame. This model is a small avatar accessory. Obviously the example mesh is over detailed, 'unoptimized' and created using techniques best suited to slow rendered content rather than real time. The point is why should anyone bother with 'low poly' when this gets the-job-done and is predictably rewarded.

My FPS are super low with the new update of the offcial SL viewer and also FS viewer update. They used to be 64 FPS and now is 8 FPS and with low graphics!

In an area with no mirrors, note the framerate. Create a mirror probe. Note the framerate. Delete the mirror probe. Note the framerate. Observed: The framerate after deleting the mirror probe is the same as when a mirror probe is present. Expected: The framerate after deleting the last mirror probe in a scene should be the same as before creating a mirror probe.

Made the switch yesterday to the Firestorm PBR . The water, eesh. Everything I have under the water is visible whereas before it just blended under. Like one of those teal colors to make the water look tropical, it just is so prominent from above. I can turn off translucent water but then I dont see them at all. Is there a setting im missing that can blend the stuff underwater like the older versions? Its blotchy and in your face and from a distance the water looks very glitchy. The loading screen is PBR (I know it says to download the latest version, but this was after I re-installed the older version, with the PBR still in the cache. The other screen is prior to the PBR install.

Bug copied from https://jira.secondlife.com/browse/BUG-234859 ---- What just happened? Using Second Life on Bellisseria as sun set. I had the Statistics bar up for PBR viewer testing. As the sun finally went down there was a visual change and a big drop in FPS, which did not recover afterwards. FPS while sun was still up was approx 85fps, with a frame of around 11ms. Immediately the sun finally set the FPS dropped to around 40FPs and the frame time jumped up to around 25ms. It stayed like that for some minutes. Looking at the statistics bar about 5 minutes later the FPS was round 70 FS and frame time around 15ms. What were you doing when it happened? Watching the sun set on Bellisseria with Statistics bar open. Using Release candidate 7.1.2.7215179142. What were you expecting to happen instead? Frame rate to stay similar in all sun/moon conditions. Other information A relog after 5 minutes or so appears to allow the FPS to go back to around 85fps (frame time 11ms or so) rather than the limited FPS it had settled on ahead of the relog. I had noticed during previous testing related to the NVidia GPU/8 core CPU systems on Firestorm and LL viewers that there could be a big an sudden change in FPS at times when sun was out and not. But the report as shown above was my clearest indication the frame rate drop was exactly as the sun finally left the sky and the sky turned a sudden deeper blue with no sun colour in it.

I noticed the low graphics preset makes the viewer slower than anything higher. To reproduce it : 1° Show fps using the improve graphics window for instance 2° Go graphics preferences, set the slider to Low -> 80 fps 3° Set the slider to Low-Mid -> 240 fps 4° Set the slider to High -> 130fps In a completely empty sim, i actually got better fps with the slider set to Ultra vs Low It happens on a macbook pro M2 Pro It doesn't happen on a windows pc with nvidia graphics (where the low preset logically shows better fps).