Reset XPDR

If your RTX2060 only has 6BG VRAM then your PC is likely just above the minimum spec to run MSFS 2024. As such, you should be running MSFS at medium, and even low settings. A TLOD of 115, which is around what the high preset gives you, is probably too much for your system and your VRAM is overflowing, causing such low performance. You should really be using a TLOD of around 25-50 with your GPU spec. What performance do you get with using the same settings AutoFPS is setting in MSFS without AutoFPS running? If similar then your issue is the settings you have chosen. If significantly different, message me your log file contents and we'll take it from there.

FYI, the latest test version 0.4.4.8-test9, available here, now supports multi-setting reduction in VR, albeit only changeable for VR on the app's UI when you are in VR.

While this could be done, I don't think it will achieve the desired effect as turning down some settings like those you suggested will just allow others to have a greater share of GPU time and hence your GPU will still be running at full load. GPUs are designed to run continuously at full load, so this shouldn't really be an issue unless the temps and/or noise are bothering you, which seems to be the case with temps at least. The first thing I would consider is are you worrying unnecessarily, since the nVidia spec for the 3080 Ti shows a max GPU temp of 93C and yours is a full 10C under that. Why not just let it run at a higher temp, still below the maximum of course? The next thing I'd be looking at is whether your GPU cooling is being obstructed in some way eg. dust build up or inadequate case airflow. You can also try undervolting your GPU in MSI Afterburner, which often yields lower temps/noise/power for the same performance, but only if you are comfortable doing this. There are plenty of youtube guides out there on how to achieve undervolting with MSI afterburner and advice on what is a reasonable undervolt that could be achieved. If GPU cooling and undervolting has been sorted and you still have a higher GPU temp than you want, the simplest and cleanest solution is to set a lower temp limit in MSI Afterburner. By cleanest I mean that this will spread the GPU performance reduction equally across all current GPU-related MSFS settings. This is opposed to the app trying to guess which settings are contributing most to the load and then, as mentioned earlier, after reducing them just having other settings take up the spare GPU capacity and not resolving your issue.

As requested, this functionality is now in 0.4.4.8-test7, available here. Let me know if this is what you wanted.

Yes, since I mastered command line arguments with the installer when I made the auto update feature, that shouldn't be too difficult for the main app. I'll put it in the next test build within the next day or so.

I have automated the switching of power profile with Voice Attack, so I am sure you can do similar with Axis and Ohs. I am not on my FS computer right now but the Voice Attack command runs a command line command to set a specific profile. You can get the list of available profiles by running a command prompt and typing C:\Windows\system32>powercfg /l This will give something like (for my laptop): Existing Power Schemes (* Active) ----------------------------------- Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced) Power Scheme GUID: d2400cc4-f296-4011-9576-4181a66340c5 (Acer) * Then you just run the command powercfg /setactive <scheme_GUID> using the GUID you want to switch to, eg. powercfg /setactive 381b4222-f694-41f0-9685-ff5bb260df2e You then set this command line up as a shortcut and activate it however you are able to with Axis and Ohs. Just a note that if you do use power saver, make sure you go into the profile under windows settings and turn off the screen off, hibernate and sleep timers for that profile otherwise it may shut down on you when in this mode and you don't touch anything for a few minutes.

I coded this up today and there is good and bad news. The good news is that I was successful in being able to determine the sim rate, albeit indirectly. I now have the app show this at the start of the status line where it will show the sim rate anywhere between 0.125X and 16X. This may be useful for some users wanting to know what their current sim rate is set to. The bad news is that using this detected sim rate to calculate an effective ground speed and have the app auto reduce TLOD when it gets above a certain speed yielded a negligible reduction in CPU workload and temperature on my system. eg. with a trigger speed of 500 kts and flying at 500 kts, when I increased to 4X sim rate for an effective ground speed of 2000 kts, the app reduced my TLOD Max down from 400 to 100 and the CPU workload and temperature remained pretty much the same. As such, I don't think this is worth pursuing any further. As I mentioned in my initial reply, the way I have averted such high CPU temps when flying supersonic or subsonic but with time accel is to simply change the Windows power profile to power saver using PowerPlanSwitcher on the taskbar and that cools and quietens everything down for me, then just change it back up to balanced or high power when you slow down. Edit: The testing I did was with MSFS 2020, since you mentioned PMDG so I assumed that was the sim you were interested in having this feature. I just tried it in MSFS 2024 and while I got the same negligible difference in CPU temp and load, my CPU temp was running at nearly 30C lower than it was in MSFS 2020 at 4X sim rate in an airliner! MSFS 2024 seems much better at managing CPU load. If only there were a few decent PMDG offerings working in it (oh and VR too, which is also pretty bad in 2024)!

I am looking at this now. This one doesn't show up in the list of simvars that AutoFPS can access, but I can get aircraft latitude and longitude and from that can calculate sim rate dependent ground speed. ie. at sim rate 2x, you move twice as far in a second compared to normal, so I should be able to calculate what increased speed your aircraft is traveling over the ground. That's the theory anyway, let me see if it actually works! Edit: yes, it works!

Yes it is available to download here, however the reduction setting feature is currently limited to 2D and does not work in VR, mainly due to the impracticality of manually changing multiple app settings with a VR headset on. When the final settings have been chosen and it becomes automated in 2D, it will also be automated for VR. If you want to try it out in 2D in the interim you are more than welcome and can contribute your feedback here. The app otherwise functions as with 0.4.4.7 in VR.

Now I see what you mean. In 0.4.4.7, the app already does the TLOD hold and reduction part of this when you use the GPU-Z companion app in the background, but instead of setting a specific VRAM threshold amount it uses a VRAM usage percentage, which is similar but does not require the user to know how much VRAM their system has. 0.4.4.8 is looking to expand what is reduced to other key settings when the reduction threshold is breached, such as OSTPreCaching, RTShadows, DispMap, TerrainShadows, Buildings, Trees, Plants and Grass. It is early days, but so far reducing all these settings only has a mild reduction in VRAM use (around 1.5GB on my system with 24GB VRAM) and DispMap is proving to exhibit unacceptable graphics corruption when toggled back on (regardless of whether you do it yourself in MSFS settings or via the app) so it will probably have to go. The SU2 beta program, which is rumoured to contain VRAM reduction improvements itself, is due to start this week, so I'll be holding off assessing the efficacy of these new changes until I can try them with it and see where we go from there..

I'm not quite sure what you mean by this. Can you please rephrase. Thanks.

Everything is now ready for the start of the 0.4.4.8 test program. If you wish to participate, head on over to my github discussion thead here. This release will initially aim to quantify whether 9 specific key MSFS settings have a notable improvement in FPS and/or VRAM reduction when reduced. If any or all of these prove useful for this purpose, the next phase will be to automate them when performance conditions are marginal. As usual, this new test release will also bring some bug fixes and optimisations, the most notable in the first release being the updating of the app from .NET 7 to 8 as the former is no longer being supported by MS and as a result will potentially become vulnerable to future security issues.

I'm nearly there. I am still wresting with the inconsistent way some of the settings denote an off condition, but should have it nutted out shortly. FYI, these new test check boxes will only change the 2D, not VR, values for now as it is just a concept demonstrator and it is difficult to change such settings when in VR with a headset on anyway.

The test check boxes will only be visible and active in expert mode and only in the test version. If some/all of these settings appear worthwhile to deal with marginal performance conditions, I intend to have them activate automatically in both expert and non-expert modes, with possibly some configurability in the former mode. This is consistent with the design philosophy I've used for non-expert mode since the app was developed ie. a feature is enabled automatically if deemed beneficial to non-expert users.

If a digital setting like is configured off by default, it will not change with toggling it's respective checkbox because the choices are: checked - off, unchecked - original setting, which in your case is off. ie. always off. As previously mentioned, this is just a test configuration for easy triggering of an effect to low/off and back to default again. The final implementation will be automatic, activated only in the most dire of performance conditions, and will likely reduce any of these settings when required, to off if necessary, then restore them to what they were on restoration of performance or exiting the program.