9 hours ago9 hr @Reset XPDR Would it be possible to edit the Auto Reduce Settings so that one can choose wich parts go 1 level down and which parts can go 2 levels down in detail ? For me Building Textures can go from High to Medium, while Trees, Plants Grass and Shadows can go from High to Low. Just my 2 cents... 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv.13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degreesMy flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
8 hours ago8 hr Author 1 hour ago, GSalden said:@Reset XPDRWould it be possible to edit the Auto Reduce Settings so that one can choose wich parts go 1 level down and which parts can go 2 levels down in detail ?For me Building Textures can go from High to Medium, while Trees, Plants Grass and Shadows can go from High to Low. Just my 2 cents...Thanks for the suggestion, and I can see the logic behind why you would want that. Unfortunately, it is not something I will be able to implement. The reduction and restoration system is built around a single, synchronised step counter and floor where everything that is enabled steps down and recovers together in lockstep. Decoupling individual settings so some drop one level while others drop two would completely break that logic and require a massive rewrite of the state tracking for both reducing and restoring graphics settings.Beyond the code rework, storing custom depth limits for every setting across each profile, plus PC and VR modes, would significantly bloat the configuration file. It would also either require a messy UI overhaul or force users to manually edit config files, which very few people would ever want to do.It is just too much complexity and development effort for a niche requirement, so keeping the simple on or off toggles with a shared floor is the best balance for keeping the app lightweight and reliable. I appreciate you taking the time to share your thoughts though. 9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit MSFS @ 4K Ultra DLSS Performance FG 80 FPS | VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11 Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11
8 hours ago8 hr 8 hours ago, Reset XPDR said:If you mean what do you set specifically for your VR flying using OFXR, then set Fixed OFXR Target FPS at 72 in the app before you go into VR and it should auto detect OFXR 2X when you switch to VR.Re locking your FPS, I believe that the OFXR dev says to not use an FPS lock, but I have used one with it with no harm. If you do set one, I'd set it in MSFS under the Max Frame setting rather than in nVidia CP, but either way should work.Thank you for the clarification and many thanks for your incredible work!
5 hours ago5 hr 6 hours ago, Reset XPDR said:Thanks for reporting it, you saved me from a massive post-release headache!Happy to help! Thanks for all of your efforts!
Create an account or sign in to comment