ISSUE DESCRIPTION
Description of the issue:
The human eye does not generate lens flairs. It already adjusts to lighting.
Can we please fully disable these gamification “features” and let the Mark 1 eyeball do what it already does?
Playing in VR, I turn my head to look at the dashboard, and outside goes super bright, I look outside, the dashboard dims. The eye adaption is looking at where center of screen is, not where my eyes are, so lets us turn this all off.
In real flight, sometimes you are just scanning over the dash and do not have to turn your head much. Right now as I pass the window support on my helicopter, the entire screen flashes as it tries to auto adjust the brightness.
Simulate the proper colors and lighting, and our own eyes will adjust.
Please keep all the effects on the external, drone and camera views, as those would be cameras you would be using for that purpose.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
3 Likes
I find that if I add back this section from the MSFS Usercfg.opt file into the MSFS 2024 Usercfg.opt file, it gives me those options back.
Like you, I am no fan of the sudden overexposure.
This is the whole section:
{PostProcess
Enabled 1
EyeAdaptation 0
ColorGrading 0
Sharpen 1
Fringe 0
LensDistortion 0
Dirt 1
LensFlare 0
FilmGrain 0
Vignette 0
LensBlurMultiplier 1.000000
FringeMultiplier 1.000000
}
and I added it just above the last section before the VR part, where is is in the MSFS version.
Please note that changing a setting will delete this addition and put it back to enabled with no means of disabling it.
I guess that marking the file as read only might stop that, but it will also stop the changing of any other settings.
YMMV.
Unfortunately, this trick with the Usercfg.opt file in MSFS2024 does not work.
When MSFS2024 launches, during the package activation phase, it modifies the Usercfg.opt file before it fully loads, deleting the PostProcess section.
I didn’t try making the file read-only, as it needs to be written (at least for me), since I’m running MSFS2024 in windowed mode and repositioning it.
This is why I typed YMMV.
Here is it, “not working”
https://www.dropbox.com/scl/fi/ocivbfeiat2df18v1584m/bandicam-2025-02-05-10-27-18-578.mp4?rlkey=orp40xhet95rtbhcm6sv3zvtt&st=11siujgh&dl=0
The Usercfg.opt file is what its name implies, a configuration file, so it has no effect on what you do with MSFS 2024 in Windowed mode or otherwise, except as it first appears when you load it.
If you are using VR, I have no idea if it would work, but I will guess that you would need to add the same section to the VR part of the Usercfg.opt file.
It just a suggestion, that works here to solve the issue, see the video.
If you know better, or it doesn’t work for you, that’s all good.
Add the propeller and rotor effects to the list too.
2 Likes
The problem is also with the current simulation tarmac does not behave or look like as you would see it with your eyes. The further you move away from the apron the brighter it get, which makes dirt literally disappear. That’s not even how a camera works. That’s just not how it works whatsoever:
this is the same apron just from different distances. It looks like 2 completely different aprons, or the same apron with dirt removed.
Sadly, that is less eye simulation and more level of detail being too aggressive, and lower LODs not having the dirt detail on it.
Have to have LODs or we lose FPS, the trick is finding the sweet spot where you dont notice the blending between the two at their change over distance(s).
I’m voting for this because it’s one of those simulated things that just doesn’t need simulating. I would love to turn it off so I’m able to view everything correctly no matter where I’m looking and not having to wait for the screen to “adapt.”
4 Likes
What I dont like is that the sim tries displays the dynamic range different between bright sky and dim instrument panel on non-hdr displays, which usually results in too dark panels.
In reality, this is not an issue as the eye has a high dynamic range, so you can see both fine at the same time, but in the sim the artificial darkening makes it hard to read especially analogue instruments!
2 Likes
Was any of this addressed with SU4? I’m so tired of having lens flair while simulating a pilot, not a GoPro. The other thing with the brightness outside making the panels darker fails to recognize an important thing.. pilots can hold their hand up to block the light outside when looking at the panel. We don’t have that ability in the sim, so this isn’t realistic.
2 Likes
Cleary nice looking screenshots and showcase videos are higher priority for Asobo than realism and usability.
1 Like
Are coded LOD curves the same for Xbox, PS5, and high-end PC’s?
