Interesting to me is that there are undocumented in the release notes updates in each of these SU betas.
Here’s one example. The default enhanced LFPG got an update today (v6.0.0→v6.22.0) when I updated to SU4 beta 1.6.22.0. I see these because I have some larger airports as well as some default aircraft downloaded locally. On the previous SU4 beta 1.6.21.0 I had an undocumented update for the default 737 Max. So there are things getting updated beyond the release notes, that you would likely never notice if you stream everything.
Also of note is I no longer get a yellow notification ‘lamp’ / circle over ‘Installed’ menu button alerting me that there is an update waiting. I have to manually go check under ‘Installed’ tab in CM and only then I see there is an update available. Several SU4 betas ago I used to see a yellow notification circle over ‘installed’ tab when there was an update available, but it would appear to be no longer working/functional.
Exactly. You can be sure that there is a lot more going on under the hood and it is really not necessary to inform about every bit changed. Especially not about little changes regarding performance because then there will be users complaining that they don‘t notice anything at all.
Would be nice if got told. There are several bugs on the default 737 max for example. They didn’t get addressed in that update I mentioned, but it would have been good to know what did. Maybe we see them in the final SU4 release notes.
Yep they are still in the process of optimizing all airports/airfields manually. They started doing that months ago and pretty much don’t specifically report about it in the changelogs.
I’m guessing it’s performance but perhaps AI traffic flow too. When people report AI traffic meeting head to head for example that’s sometimes airport related right, AFCAD data? I think BATC (which I use for AI traffic injection) gets around this by generating it’s own data for airport taxi patterns. Presumably Gaya is improving this type of stuff manually.
I have never had any beta update changing my graphics settings. Is it maybe caused by the nvidia app resetting them from time to time in case you let the app deciding to use optimized values or did so in the past?
Valid point. I once chose optimized settnigs in NVidia app but haven’t been using NVidia App to optimize again. There was a NVidia driver update yesterday so maybe you are on to something, I’ll check when I see another driver update.
The strange part is the random graphics settings that get changed, it’s not consistent.
Game developers often don’t list every single bug they’ve fixed in the changelog - the list would be so long you’d stop reading halfway through. Usually, only the most important fixes make it into the changelog.
EDIT
I’m not installing NVIDIA app because I simply don’t need it. I already have the latest driver (581.80) so there’s no point in adding more background software. I’ll check in a moment if my MSFS SU4 beta graphics settings got reset after beta update.
EDIT 2
After launching MSFS and checking graphics settings, I found that they didn’t reset.
I‘m using it only to access the latest version of DLSS. Sure, we have dlss injector but it looks like it‘s not always a very reliable tool. It‘s also very easy to set a custom dlss scale factor in the nvidia app. The default one that comes with the quality preset is at 67%. I have mine set to 77% in order to further improve a quite sharp cockpit view.
No, I did not miss it, voted myself and that’s why I wrote they just fixed what they screwed up before. And you are right, this is a step in the right direction, for example, they completely ignored the VR cockpit LOD bug reported by many for the last SU3 beta, causing a lot of frustration when SU3 came out.
Unfortunately, Asobo didn’t do anything about it, they admitted that it was a mistake and that’s it, people from su2 are waiting for this moment to be fixed, do you think this is normal? As far as I’m concerned, no, it shouldn’t be like that, it should be fixed in the first patch.
Would you fly with black squares around the edges of textures at night? I don’t think
If it’s any consolation. I had no ability to use FS2024 on my system when SU2 was released. The performance drop at airports introduced by SU2 completely killed the sim for me. Others with new/powerful hardware didn’t notice so much. SU3 still had the same performance issues much to my dismay, but now SU4 has finally addressed most of them, so waiting for ‘game breaking’ fixes can take a few updates. Just be happy if you’ve still be able to use it in the meantime. I had 4-5 months of downtime with FS2024.
Something I do as a matter of course, to avoid situations like parms being changed, is when there is an update the first thing i do is take a copy of the usercfg.opt file, yesterdays became UserCfg - 251105 SU4 beta 22.opt .
After the update is done I do a compare between the old file and the new file to see if there is any difference and if so investigate the new parms. It also enables you fallback if there is a problem.
I know that I will be teaching some people to suck eggs, but to some others it might be a useful safety tip.
