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?
