No issues with 0.4.4.7 in MSFS2024 just some four hours ago...

13 minutes ago, AnkH said:

No issues with 0.4.4.7 in MSFS2024 just some four hours ago...

After partcicipating in Beta, I re-installed the sim and now the version is Live Build 1.3.2.3 (Beta = None). Perhaps I have missed something?

Edited March 10, 20251 yr by History

3 minutes ago, History said:

After partcicipating in Beta, I re-installed the sim and now the version is Live Build 1.3.2.3 (Beta = None). Perhaps I have missed something?

I stay in the Beta and my MSFS2024 has been updated (should I say downgraded 😉 ) to 1.3.23 without any issue since then... including MSFS_AutoFPS. Have you tried un-installing MSFS_AutoFPS and re-installing it? I think I did once since officiel SU1 release.

13 minutes ago, vbazillio said:

I stay in the Beta and my MSFS2024 has been updated (should I say downgraded 😉 ) to 1.3.23 without any issue since then... including MSFS_AutoFPS. Have you tried un-installing MSFS_AutoFPS and re-installing it? I think I did once since officiel SU1 release.

Thank you sir. It's all well now. And I think my single digit fps drop during take off is gone now after reinstalling (but that's a different story). 

I had a previous version working fine until today, then got a warning message that said it failed to recognise MSFS2024 or something, so I updated to the latest version and it's working fine.  A truly helpful little program as far as I am concerned alongside the FRG generator ffor 3000 series cards.

Following the release of SU1, MSFS 2024 now seems to have somewhat stabilised so I have been looking at whether some of the original features that were implemented, and worked well, for MSFS 2020 may no longer be as applicable for MSFS 2024. 

In particular, the GPU load activation method for cloud quality reduction, which is the only option available in the new FPS Cap mode, is now largely ineffective in MSFS 2024 due to it being much more GPU bound than its predecessor and I notice many recent screenshots of AutoFPS show users have disabled this.  

Additionally, Auto OLOD was a legacy feature from DynamicLOD that IMO had never yielded much in the way of performance improvements as the times when it is set to lower (ie. in the air) are times when you are already getting adequate performance and don't actually need it. While I could just leave this in, it may be better to use this UI real estate for something more useful.

What I am currently thinking is for the app to be able to reduce some other key settings in two specific scenarios where performance gets marginal, ie. when target FPS cannot be achieved at the lowest TLOD available for the current automation method and when VRAM overflow is impending to do more than just lower TLOD until it hits the floor.

The tricky bit is working out which key settings could be reduced. I have researched on the internet, eg. here, here and here, the impact MSFS 2024 settings seem to have on FPS but I am encountering inconsistent results on changing particular settings. Nonetheless, there do seem to be some common themes and what I am finding is that Trees, Terrain Shadows, Ray Traced Shadows (VRAM consumption in particular) and our good old friends TLOD, OLOD and Cloud Quality have the greatest impact. 

The idea would be that these reductions would only become active when performance becomes marginal as mentioned above and that the user could possibly choose which ones get reduced and by how much, with default selections for those that don't really know what they are playing with or, in the name of simplicity and because they are only for marginal conditions, they could just happen without user intervention and set-ability.

This is just a discussion point at this time so please let me know your thoughts on this. I haven't made any changes yet, but if and when I do there will a usual test and feedback program over at the AutoFPS github page.

Edit: I forgot to mention that DLSS quality or TAA render scaling are two other possibilities for recovering performance, however I have already trialed changing these on the fly and unfortunately it either results in a frozen image or a black screen, recoverable by going to the settings menu and changing any setting but certainly not without such user intervention. As such, this option is currently deemed unsuitable.

 

 

Edited March 12, 20251 yr by Reset XPDR

20 minutes ago, Reset XPDR said:

Nonetheless, there do seem to be some common themes and what I am finding is that Trees, Terrain Shadows, Ray Traced Shadows (VRAM consumption in particular) and our good old friends TLOD, OLOD and Cloud Quality have the greatest impact. 

Interesting. Just a few days ago I turned off ray traced shadows which resulted in up to 10 more FPS. I’ve also tuned down trees, buildings and several other settings, but I haven’t tested the performance impact of these.

I think it would be useful if AutoFPS could dynamically change some of these settings.

I agree, these areas are certainly worth exploring. Although my system is reasonably good, I still run with mostly HIGH rather than ULTRA for most settings except cloud quality, which gives me good flying results with your program. I still get some slowdowns and stutters at complex airports in a complex airliner so some of the options you mention could help in these circumstances.

wanted to ask for a feature.

Do you think it is possible to detect simrate increase and setup AutoFPS down to the bare minimum of settings while using an increased simrate?

Because i most of the time use time accellaration in the PMDG aircraft up to x4 and when i do my CPU getting hammered, would be nice if autoFPS could help in decreasing the Tlod settings, dont need to have good graphics when flying at supersonic through Cruise, but the constant freezes because the CPU is getting to hot are a bit concerning, i always think my sim might crashed 😞

if needed i can provide a simconnect variable for reading out the current Simrate with Axis and Ohs (don't know if you can detect the same variables)

This app has benefited so many by so much! And it has potential beyond FPS. For example, would it be possible to intercept cloud drawing and dynamically add or multiply the density, to force a more realistic effect of the cloud coverage?

1 hour ago, Bam2000 said:

wanted to ask for a feature.

Do you think it is possible to detect simrate increase and setup AutoFPS down to the bare minimum of settings while using an increased simrate?

Because i most of the time use time accellaration in the PMDG aircraft up to x4 and when i do my CPU getting hammered, would be nice if autoFPS could help in decreasing the Tlod settings, dont need to have good graphics when flying at supersonic through Cruise, but the constant freezes because the CPU is getting to hot are a bit concerning, i always think my sim might crashed 😞

if needed i can provide a simconnect variable for reading out the current Simrate with Axis and Ohs (don't know if you can detect the same variables)

I get this sometimes when flying supersonic over photogrammetry areas in Concorde (yes I know, very naughty! 😆) without any time acceleration, so I know what you mean about your CPU running hard for no great reason.

My solution to date has been to use power profile switcher (free in MS Store) and just switch to power save mode, which disables the CPU's turbo, and temps drop dramatically and interestingly no FPS reduction by doing so.

Nonetheless, what you propose should be possible. I could have it do something like proportionally reduce TLOD if the equivalent ground speed exceeds a threshold like 500 kts ground speed, so if you at 4x and flying 500 kts ground speed thats the equivalent of 2000 kts ie. 4 times the threshold so maybe 1/4 the TLOD. Something like that.

If you could let me know the appropriate simconnect variable, it would save me the trouble. Thanks.

 

1 hour ago, Mark1616 said:

This app has benefited so many by so much! And it has potential beyond FPS. For example, would it be possible to intercept cloud drawing and dynamically add or multiply the density, to force a more realistic effect of the cloud coverage?

Unfortunately, that's way beyond the capability of this app, which is limited to changing a few graphics settings that you could otherwise change yourself. Frankly, given that even this existing innocuous interaction with MSFS has MS's and Asobo's nose out of joint (officially at least, but secretly I think they actually don't mind how the app helps users enjoy their sim more), I am not prepared to venture any further than this with this app.

9 hours ago, Reset XPDR said:

There do seem to be some common themes and what I am finding is that Trees, Terrain Shadows, Ray Traced Shadows (VRAM consumption in particular) and our good old friends TLOD, OLOD and Cloud Quality have the greatest impact.

I have already located all these, and a few extra medium impact, settings for the app to be able to change so I hope to put together a concept test version in the next couple of days. 

This initial version will be set up to see if reducing some or all of these settings either progressively or in one go is both visually acceptable and smooth. It will likely be triggered manually rather than automatically initially so that observation of the changes is predictable for test purposes, so it will come with some UI controls for this purpose that likely won't appear on the final version.

If any of this tickles your sense of adventure, stay tuned for announcement of the test program!

First off, I haven’t had the chance to keep up with the latest beta on GitHub, but I did get to test the latest release a bit, and the results, along with the newest version of Lossless Scale, are absolutely amazing. With a base framerate of 30 and a Gsync-compatible monitor, I’m hitting 120 frames with barely any glitches and no annoying stutters. Thanks to your tips, I’m keeping the VRAM in check during the trickiest scenarios using DLSS Quality. The app hardly needs to adjust the TLOD due to excess VRAM. In my 40 years of simming, I’ve never had such a smooth experience with a simulator. I totally get it, but it really bums me out that your efforts aren’t getting recognized on the official forum; it feels really unfair.

As for the settings that impact VRAM usage the most, as I mentioned before, I think one of the key ones is the offscreen terrain pre-cache. I’m sure that in extreme situations, reducing it would free up resources right away, especially VRAM. The other parameter is texture size, but unfortunately, we know we can’t change that on the fly without restarting the simulator. I agree that OLOD has almost no impact on performance. Another one that comes to mind is the number of AI flights, but I imagine it must be pretty complicated to modify that in real-time.

I still don’t get why there isn’t a setting to adjust the resolution of the AI liveries like there is for reflections or shadows. We’re forced to rescale them manually. And it’s crazy how much memory those 4K textures and the new 8K ones are demanding (are they really necessary?)

27 minutes ago, Maddormo said:

First off, I haven’t had the chance to keep up with the latest beta on GitHub, but I did get to test the latest release a bit, and the results, along with the newest version of Lossless Scale, are absolutely amazing. With a base framerate of 30 and a Gsync-compatible monitor, I’m hitting 120 frames with barely any glitches and no annoying stutters. Thanks to your tips, I’m keeping the VRAM in check during the trickiest scenarios using DLSS Quality. The app hardly needs to adjust the TLOD due to excess VRAM. In my 40 years of simming, I’ve never had such a smooth experience with a simulator. I totally get it, but it really bums me out that your efforts aren’t getting recognized on the official forum; it feels really unfair.

I'm pleased that users like you appreciate my efforts and are getting a better flight simming experience as a result of it.  While it would be nice to be able to talk about this app over on the official forum, I think it gets plenty of exposure here and on youtube. I am just pleased I haven't been shut down, but as I said before I think my actions are silently tolerated because what the app does is actually harmless and improves the experience for many sim users, not to mention I don't actually profit from it at all. It is what it is and I am OK with that.

27 minutes ago, Maddormo said:

As for the settings that impact VRAM usage the most, as I mentioned before, I think one of the key ones is the offscreen terrain pre-cache. I’m sure that in extreme situations, reducing it would free up resources right away, especially VRAM. The other parameter is texture size, but unfortunately, we know we can’t change that on the fly without restarting the simulator. I agree that OLOD has almost no impact on performance. Another one that comes to mind is the number of AI flights, but I imagine it must be pretty complicated to modify that in real-time.

Offscreen terrain pre-cache is one of the additional settings I have already earmarked for testing for the very reasons you state, so it is good to see we are on the same page with this. I'm not at my MSFS computer right now but IIRC the others I have earmarked are: displacement mapping, buildings, plants and grass. As you say, texture size is not applicable because of the restart requirement. AI density is a possibility but potentially complicated if driven by external programs and data (eg. live traffic schedules), so I'll see how I go with these others first.

Edited March 13, 20251 yr by Reset XPDR