Thinking about the automatic exposure changes leaving the outside world over-exposed when the sim thinks there’s too much cockpit in view (and vice versa), would it make sense to implement a way to tell the sim what it is we’re actually looking at? Maybe I CTRL click outside the cockpit to tell the sim to prioritise correct exposure of the outside world, or CTRL click the panel to tell it to correctly expose the instruments? This would surely let us sit back and enjoy the outside view without having to find the right angle/zoom or switching the cockpit off completely, and switch to being able to read the panel without physically moving my virtual head (just click to adjust exposure).
Taking it further, a slider could define how extreme the exposure shift should be… ie. Blackout to whiteout, to no change, and everything in between.
Does this make sense? I guess my point is just because the camera is pointed at something doesn’t mean that’s what my eyes are looking at.
Edit: Perhaps not a solution for VR, but where I’m sitting at my desk with a relatively fixed view…
There is already a parameter to adjust this in UserCfg.opt called EyeAdaptation
By default it is set to 1, but there is no way in the UI to change that setting.
By editing userCfg.opt before starting MSFS and a bit of messing about with the server syncing), you can force this parameter to be 0 when the sim is running, and this greatly reduces the effect - so much so, that it might even be turned off if it was set to 0.
Interesting, is that with it OFF, the effect is still slightly there, because of what your eye is doing… with a bright outside, the panel does appear to get darker, but if you keep that view with the bright outside, and just cover it the bright area up on the Monitor, the cockpit appears to your eye, to get slightly brighter again.
So, maybe all that is needed is a UI control Eyeadaptation ON / OFF ?
The good news is that there is a possible workaround.
Same applies to Fringe 1 !!! which really messes up certain parts of the hangar windows frames etc etc ( No UI to control this)
No idea why it is even there – it looks like an attempt to make image look 3D, if you wear red/green 3D Glasses ??
Anyway, that can also be over-ridden by editing the UserCfg.opt file, EVERY time before you start the sim. (when you close the sim, it gets written back with original default value of 1)
If these edits are done within a startup script,( bat file) that does these search replaces, before starting the sim, its quite painless.
I read this somewhere and it works. If you copy the Eye Adaptation line and replicate it two more times, it will stick. Next time you look at the usercfg.opt file, it will only appear once, but mine never changes. It looks like this…
EyeAdaptation 0
EyeAdaptation 0
EyeAdaptation 0
IN fact, once Fridge is set to 0 before starting MSFS, and witha bit of sync forcing, it gets saved as 0 on the server, and ten when starting MSFS, there is no ne3ed to pre-edit the opt file !!!
But if you change any of the opts that would be saved in the opt file, then Fridge gets reset back to 1, so you may as well run the search/replace script every time MSFS starts.
This is what the Hangar windows look like with Fringe forced to 0
Not even camera/lens manufacturers want CA, it’s a negative effect that is more pronounced the cheaper the camera gear is (Same for TVs). Maybe MSFS can also add in film grain and cataracts.
This may help to address some of these issues ----
Here is a MSFS Splash Screen startup Batch file I use to start MSFS, which also does any required search/replaces on MSFS configuration files, before starting MSFS.
Makes sense, N6722c. I guess it’s a potential trade off. If you don’t make many changes I guess it’s ok to make it read only. I think your point is well taken If you mess with options often.
Guys, I don’t understand at all, I have the impression that those whose simulator returns values to 1 has some kind of preset in the settings ULTRA or something. I have custom settings, just made an experiment, everything remains with zero after the start. One exception: I have eye adaptation value - 1, because I like the effect, but all another are switched off, and I’ve never seen the simulator try to get them back. Maybe custom setting is a problem solver?
The same reason folks post real life photos in the forum of aerial night scenes and then complain that the sim is unrealistic because it looks nothing like the photos. They’ve never actually seen this for themselves outside of photos and have no point of reference as to what it should actually look like to the naked eye vs through a camera lens.