13 minutes ago, Rocky_53 said:

Hey guys, I'm a little late to the party with this one  I have been using the Adaptive LOD app since it's release and have been very happy with it, so I've not used the Auto FPS app. I have a question, I fly with clouds on high, don't experience any gain from the slider being any lower and see little visual benefit, although very slightly, from having it on ultra. Correct me if I'm wrong, my understanding is that this app changes both the clouds and the terrain LOD to maintain a predetermined FPS. My question is, if I don't use the cloud part of the app, what would be the benefit of me in using this app? Is there some benefit that I have overlooked? 

There's a section in my DynamicLOD_ResetEdition readme that covers the difference between the two apps as follows:

Which app should I use? DynamicLOD_ResetEdition or MSFS_AutoFPS?:

• Essentially both apps are intended to give you better overall performance but with different priorities to achieve it that result in a slightly different experience. They both allow a lower TLOD down low and on the ground, when your viewing distance reduced anyway so the visual impact is minimal, and a higher TLOD when at higher altitude and not in close proximity to complex scenery or traffic. They also adjust OLOD and Cloud Quality but TLOD is usually the most important determiner of performance at these two extremes.
• Where they differ is that DynamicLOD provides user set tables for LOD changes at specific altitudes, giving the user precise control over when and where these changes take place such that they can optimise them to their particular flight activity they normally do, and can set a specific profile for each one. The price of such precise control is that the user must be intimately familiar with LODs to be able to tune a variety of settings in the app for the best outcome and this can be a bit daunting for more casual and non-technical users.
• Alternatively, AutoFPS seeks to automate these changes as much as possible based on a target FPS and a minimum and maximum LOD range within which to automatically adjust. This results in a much simpler and generally similarly acceptable user experience compared to DynamicLOD. Nonetheless, the automation algorithm does require FPS headroom to function correctly, so can conflict in cases where an FPS cap is being used, such as with Vsync or motion reprojection in VR. Additionally, AutoFPS tends to make constant small changes to TLOD, much more than DynamicLOD does, and this can induce stuttering on older hardware as it struggles to manage even small scenery changes. In these cases, the user would be better off using DynamicLOD in a more manually tuned approach.

1 hour ago, Reset XPDR said:

Sorry about that. This one got through what I though was a pretty robust security net. While I can't guarantee this sort of thing will never happen again, I will do my best to make it much less likely.

No worries!

37 minutes ago, Reset XPDR said:

There's a section in my DynamicLOD_ResetEdition readme that covers the difference between the two apps as follows:

Which app should I use? DynamicLOD_ResetEdition or MSFS_AutoFPS?:

• Essentially both apps are intended to give you better overall performance but with different priorities to achieve it that result in a slightly different experience. They both allow a lower TLOD down low and on the ground, when your viewing distance reduced anyway so the visual impact is minimal, and a higher TLOD when at higher altitude and not in close proximity to complex scenery or traffic. They also adjust OLOD and Cloud Quality but TLOD is usually the most important determiner of performance at these two extremes.
• Where they differ is that DynamicLOD provides user set tables for LOD changes at specific altitudes, giving the user precise control over when and where these changes take place such that they can optimise them to their particular flight activity they normally do, and can set a specific profile for each one. The price of such precise control is that the user must be intimately familiar with LODs to be able to tune a variety of settings in the app for the best outcome and this can be a bit daunting for more casual and non-technical users.
• Alternatively, AutoFPS seeks to automate these changes as much as possible based on a target FPS and a minimum and maximum LOD range within which to automatically adjust. This results in a much simpler and generally similarly acceptable user experience compared to DynamicLOD. Nonetheless, the automation algorithm does require FPS headroom to function correctly, so can conflict in cases where an FPS cap is being used, such as with Vsync or motion reprojection in VR. Additionally, AutoFPS tends to make constant small changes to TLOD, much more than DynamicLOD does, and this can induce stuttering on older hardware as it struggles to manage even small scenery changes. In these cases, the user would be better off using DynamicLOD in a more manually tuned approach.

Ah ha, thanks for the detailed reply, appreciated.

It seems that adding the DecCloudQNonExpert parameter doesn't prevent the cloud quality from changing on non-Expert settings - I added this to my 2024 config file, but I still see it drop from Ultra to High:

<?xml version="1.0" encoding="utf-8"?>
<appSettings>
  <add key="mfLvarPerFrame" value="15" />
  <add key="ConfigVersion" value="1" />
  <add key="logFilePath" value="MSFS2024_AutoFPS.log" />
  <add key="logLevel" value="Debug" />
  <add key="waitForConnect" value="true" />
  <add key="DecCloudQNonExpert" value="false" />
</appSettings>

 

 

13 minutes ago, LukeFF said:

It seems that adding the DecCloudQNonExpert parameter doesn't prevent the cloud quality from changing on non-Expert settings - I added this to my 2024 config file, but I still see it drop from Ultra to High:

<?xml version="1.0" encoding="utf-8"?>
<appSettings>
  <add key="mfLvarPerFrame" value="15" />
  <add key="ConfigVersion" value="1" />
  <add key="logFilePath" value="MSFS2024_AutoFPS.log" />
  <add key="logLevel" value="Debug" />
  <add key="waitForConnect" value="true" />
  <add key="DecCloudQNonExpert" value="false" />
</appSettings>

 

 

It is late where I am so I'll take a look at it tomorrow.

Hello all, I’ve used the app for FS 2020 without issues. I’ve gone solely to FS2024 and when I try to use Auto FPS, I get an error in red saying

“set TLOD 55 olod 195 in the sim (non-vr) be on a runway and start the app”

I launch the program before I run FS and everything seems fine until about 20 seconds into a flight when it gives me the error. I did set the TLOD and OLOD to the setting the app is telling me but I get the same result. I’ve also tried uninstalling the app and reinstalling.

Everything is working fine for me now....Frame gen FPS is showing now and the cloud settings work as before the MSFS2024 update.

I reinstalled a fresh version of the newest v0.4.4.1  and everything is working great.

It might have been some sort of corruption in the MSFS 2024 settings but everything magically start working as it should.

Once again a huge thanks for all your efforts....this program really is a game changer for MSFS2020 and 2024.

Chris

1 hour ago, mmjaxstang said:

Hello all, I’ve used the app for FS 2020 without issues. I’ve gone solely to FS2024 and when I try to use Auto FPS, I get an error in red saying

“set TLOD 55 olod 195 in the sim (non-vr) be on a runway and start the app”

I launch the program before I run FS and everything seems fine until about 20 seconds into a flight when it gives me the error. I did set the TLOD and OLOD to the setting the app is telling me but I get the same result. I’ve also tried uninstalling the app and reinstalling.

You are using kayjay's app, not mine, so you should ask your question on his app's thread here

 

I have been playing with this app today and I must say its a game changer. Had no need for it with 2020 but with my rig 2024 has been disappointing with the performance. I have only flown in 2024 with the A2A comanche and the performance when on or near the ground has been borderline. Enough to convince me that airliners were not going to be an option for me and my rig in 2024. Anything less than 60 FPS is not acceptable to me, especially with track IR. However, after spending a few hours with this today, I have managed to massively increase my graphics and maintain that 60 fps at all times. It's no understatment to say that it's a game changer.

Why Asobo have not implemented this into the sim is mindblowing to me. It's so obvious and effective as to be an open goal. The fact that a hobbyist has done this work by himself makes me raise an eyebrow as well as to force me to doth my cap to the man.

Thank you, Reset XPDR. MS2024 is looking much more enjoyable thanks to your efforts. It really is appreciated.

58 minutes ago, Jazz said:

I have been playing with this app today and I must say its a game changer. Had no need for it with 2020 but with my rig 2024 has been disappointing with the performance. I have only flown in 2024 with the A2A comanche and the performance when on or near the ground has been borderline. Enough to convince me that airliners were not going to be an option for me and my rig in 2024. Anything less than 60 FPS is not acceptable to me, especially with track IR. However, after spending a few hours with this today, I have managed to massively increase my graphics and maintain that 60 fps at all times. It's no understatment to say that it's a game changer.

Why Asobo have not implemented this into the sim is mindblowing to me. It's so obvious and effective as to be an open goal. The fact that a hobbyist has done this work by himself makes me raise an eyebrow as well as to force me to doth my cap to the man.

Thank you, Reset XPDR. MS2024 is looking much more enjoyable thanks to your efforts. It really is appreciated.

Legend !

29 minutes ago, sonny147 said:

Legend !

A little gushing, perhaps. Appreciated, none-the-less. The praise isn't for me, though. It's for the author.

The author deserves all the praise. So true!

20 minutes ago, Jazz said:

A little gushing, perhaps. Appreciated, none-the-less. The praise isn't for me, though. It's for the author.

Really !

1 minute ago, sonny147 said:

Really !

Sure, although, I'm not sure where this is going......how about a game of snooker? Do you play snooker on Shoooters Pool? It's like the flight sim version of snooker.

13 hours ago, LukeFF said:

It seems that adding the DecCloudQNonExpert parameter doesn't prevent the cloud quality from changing on non-Expert settings - I added this to my 2024 config file, but I still see it drop from Ultra to High:

<?xml version="1.0" encoding="utf-8"?>
<appSettings>
  <add key="mfLvarPerFrame" value="15" />
  <add key="ConfigVersion" value="1" />
  <add key="logFilePath" value="MSFS2024_AutoFPS.log" />
  <add key="logLevel" value="Debug" />
  <add key="waitForConnect" value="true" />
  <add key="DecCloudQNonExpert" value="false" />
</appSettings>

 

 

I just tested this and it is working correctly.

I think I know the problem. It looks like you have changed the <add key="DecCloudQNonExpert" value="false" /> line in the MSFS2024_AutoFPS.config file in the app's bin subdirectory, which is a template config file not the real one. You need to make the change in the MSFS2024_AutoFPS.config file in the app's root directory ie. one directory up.

Try that and let me know if that fixes it. Either way, I have updated the readme to make it clearer which MSFS2024_AutoFPS.config file should be modified as I can see how it could be confusing.

 

Edited December 22, 20241 yr by Reset XPDR