I’m not going to trawl through the whole thread to see if it has been suggested nor am I going to guarantee it still works but before SU5 those who edited UserCfg.opt did so after they made all their other sim changes, they marked the file ‘read only’ and then made no further settings changes whatsoever as doing so will revert all of them back to those shown in the menus. That probably includes dev mode selection or anything else that means “Apply and Save”.
I suggest putting a shortcut in documents along with a text based copy that includes all of your optimisations that you can simply C&P over replacing the text in the original, save and once again mark ‘read only’ so it sticks if you don’t make further changes. You can also access these files in sim by pressing the windows key and navigating to the docs folder. It’s sure to be laborious but we’ve already been told the higher LODs will be available after the next update so be patient.
It’s already been said the read only trick doesn’t work because whether read only or not, once you toggle settings from any of low-mid-high-ultra, whatever you have set in usercfg.opt is overwritten for that session.
I read your post but you didn’t read the thread. As mentioned numerous times, that won’t work with this bug. The workaround requires a toggle which negates usercfg.opt read only or not.
This bug is internal, so don’t have any direct relation with what you have in the user cfg file. What you have in the file, and also what you see in the settings menu, is not what you get during fly.
Édit: so C&P will not work
If you leave the config file as read only, you won’t get the new off screen cache option included in the config file, and hence you won’t see any difference from this.
OK, maybe at cross purposes. Here is what I understand goes on with the config file.
If it is NOT read only:
When you start the sim, the settings are loaded. If you make changes in the sim, those changes take effect for that session (until you close the sim) and are written to the config file so that they persist to the next session.
If the file IS read only:
When you start the sim, the settings are loaded. If you make changes in the sim, those changes take effect for that session (until you close the sim) BUT are NOT written to the config file and they don’t persist to the next session.
I don’t know what happens if you change the file WHILST the sim is running (which is what I think you did here from your post above).
If you have LODs set as 9 with the file read only, they will be 9 in the sim as long as you don’t make any changes to the graphics settings. Note that if you make any graphics settings changes, the graphics settings shown in the UI will be applied for the remainder of that session. So to keep LOD 9, you must not make any changes to the graphics settings at all [note that there may be some settings that don’t do this, e.g. data settings etc - I;ve not tried them all]
By the way, this is how people are saying they are getting 30+ FPS with LOD 9 - becuase they aren’t actually seeing LOD 9 at all - they’ve checked the graphics settings or made some other change that means the sim resets the LODs to whatever is shown in the UI.
If the file is read only when you start the sim after the update, it cannot add the new off screen cache setting to the config file - but I see it has now done that, so that setting will now take effect.
Because the bug has been around for several weeks and nobody has provided any evidence from any other airport or indeed any other location that is reproducable.
That would be an assumption yet to be proven. I’d like to hear from Asobo directly on this. If you’re right, at a minimum, they should have patched EGNX and stated that this was an EGNX specific issue given the # of people interested in this issue.
