durp Posted August 26, 2024 Posted August 26, 2024 This issue has been around for quiet a while, fun fact, since the introduction of MultiThreading. It never got fixed so far. There were some posts here and there about the broken auto brightness adjustment (also not addressed yet, other than turning on global illumination) On daytime the effect is an overbrightness when switching from the F10 map to the cockpit, at night, the total opposite. at night, this is how it is supposed to look: this is what it looks like when switching from F10 to cockpit without moving a lot: workarounds are to hammer F2 to get to another plane and then switch back... the same issue in reverse: this is how it is supposed to look like: this is what it looks like after switching from F10 to cockpit Running, as recommended, in MT mode, Gamma is set to 1.6 to balance the nuclear look after swapping from F10 back to cockpit. And if the adaptive brightness is not already bad, this is really annoying, particularly when at night everything gets so dark, you can't even see the NVG overlay anymore. Other Link(s): and maybe more... 2
Maddaawg Posted October 2, 2024 Posted October 2, 2024 Happens to me too in VR 1 Meta Quest 3, AMD 9800x3D, EVGA 3080Ti FTW3, Corsair 2x32GB DDR5 6000, ASUS ROG Strix X870E-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive
YoYo Posted October 2, 2024 Posted October 2, 2024 Yes, its not solved, long time issue: 1 Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Recommended Posts