Same.

 

I tried it in VR Optimized and still does nothing despite the TLOD showing being changed on the app.

 

I am very confident with the app and know all what the various settings do, as I was quite an early user of the original app and helped with testing.

Silly question but with MSFS 24 doing it's own dynamic performance models is this still necessary?  Can't you set a FPS natively in 24 and your LOD/scenery will be automatically lowered if you fall below that FPS?

Wondering the difference... 

 

1 hour ago, psolk said:

Can't you set a FPS natively in 24 and your LOD/scenery will be automatically lowered if you fall below that FPS?

Question is that we don't know what parameters exactly MSFS24 will change to keep the fps target. With MSFS2024_AutoFPS and the expert mode you can. Your choice 😉

In my setup, MSFS2024_AutoFPS v1.0.10 works only when Expert Options is ticked and Auto Method = "VR Optimized" although I'm only 2D.

4 minutes ago, vbazillio said:

Question is that we don't know what parameters exactly MSFS24 will change to keep the fps target. With MSFS2024_AutoFPS and the expert mode you can. Your choice 😉

In my setup, MSFS2024_AutoFPS v1.0.10 works only when Expert Options is ticked and Auto Method = "VR Optimized" although I'm only 2D.

Ah, that makes sense, thank you!! 

1 hour ago, psolk said:

Silly question but with MSFS 24 doing it's own dynamic performance models is this still necessary?  Can't you set a FPS natively in 24 and your LOD/scenery will be automatically lowered if you fall below that FPS?

Wondering the difference... 

 

From what I've seen, the dynamic settings either don't work or react very slowly to maintain a target fps. It also seems to change other settings besides TLOD and LOD. However, there's no way to be sure about any of this, since there's no way to know exactly what the dynamic settings are actually changing in the settings.

AutoFPS shows you exactly what's changing and the value of the setting. It also gives you multiple options to customize these changes. This alone makes it 100 times better than the dynamic settings. I just wish it didn't give me CTD when using it.

@kayjay1c6b, I have raised an issue on your github asking how you are locating the MSFS 2024 setting memory space as I'd like to get my AutoFPS and DynamicLOD app versions working in 2024. If I have this I can also help you out with making sure the settings our apps are reading and changing are robust with potential changes Asobo made to the MSFS 2024 setting memory space to accommodate new settings, regardless of where they have relocated this memory space.

Edited December 4, 20241 yr by Reset XPDR

6 minutes ago, Reset XPDR said:

I have raised an issue on your github asking how you are locating the MSFS 2024 setting memory space as I'd like to get my AutoFPS and DynamicLOD app versions working in 2024. If I have this I can also help you out with making sure the settings our apps are reading and changing are robust with potential changes Asobo made to the MSFS 2024 setting memory space to accommodate new settings, regardless of where they have relocated this memory space

This is brilliant news!

@kayjay1c6b

I set exactly the same settings as you, and this is what I see....

Clearly not TLOD 400

OK, so I have identified issue which was mainly that you should get an error and the app should disable itself. It looks like the memory mapping is more dynamic than in MSFS 2020 so I tried another approach. There is now a special procedure that you have to perform at the first run to hopefully get it to work:

- Uninstall previous version with the installer (you will get an error but don't worry)
- Install version 1.0.1.1
- Start the sim and load yourself in a cockpit of a plane in 2d (doesn't matter which plane)
- go to settings and set tlod (non vr) to 55 and olod (non vr) to 195. 
- Set dynamic settings to off (non vr and vr)
- Close the settings and go back to the cockpit.
- Start the AptoFPS app.
- After a while you should see MSFS SimConnect and Session green but tlod/olod n/a. This means that the app is scanning your emory to get correct addresses (This could take up to 5 minutes, but you do it only once). 
- You should see then tlod and olod values, this means that the app correctly identified and saved (thanks to Reset XPDR's suggestion) the addresses.
- If not yoou should get an error (Let's hope not)
- For next runs you don't have to do anything special, you can manipulate tlod and olod in the sim and in the app. Also there shouldn't be 5-minutes long scanning.
 

The goal is to identify the memory addresses that are specific to you, save them and then app can run like before. I have relased version 1.0.1.1 on my github here: https://github.com/kayjay1c6b/MSFS2024_AutoFPS-by-kayJay_1c6

Good Luck and let me know if it works. 

6 hours ago, kayjay1c6b said:

OK, so I have identified issue which was mainly that you should get an error and the app should disable itself. It looks like the memory mapping is more dynamic than in MSFS 2020 so I tried another approach. There is now a special procedure that you have to perform at the first run to hopefully get it to work:

- Uninstall previous version with the installer (you will get an error but don't worry)
- Install version 1.0.1.1
- Start the sim and load yourself in a cockpit of a plane in 2d (doesn't matter which plane)
- go to settings and set tlod (non vr) to 55 and olod (non vr) to 195. 
- Set dynamic settings to off (non vr and vr)
- Close the settings and go back to the cockpit.
- Start the AptoFPS app.
- After a while you should see MSFS SimConnect and Session green but tlod/olod n/a. This means that the app is scanning your emory to get correct addresses (This could take up to 5 minutes, but you do it only once). 
- You should see then tlod and olod values, this means that the app correctly identified and saved (thanks to Reset XPDR's suggestion) the addresses.
- If not yoou should get an error (Let's hope not)
- For next runs you don't have to do anything special, you can manipulate tlod and olod in the sim and in the app. Also there shouldn't be 5-minutes long scanning.
 

The goal is to identify the memory addresses that are specific to you, save them and then app can run like before. I have relased version 1.0.1.1 on my github here: https://github.com/kayjay1c6b/MSFS2024_AutoFPS-by-kayJay_1c6

Good Luck and let me know if it works. 

I was about to report that the app appears to not be working on my system.  It is showing as connected but no sim values coming up.  Will leave it running for awhile to see if they eventually populate.  

The new version fixed the CTD issues I had. Now it's working fine.

4 hours ago, edu2703 said:

The new version fixed the CTD issues I had. Now it's working fine.

Great to hear that! Can you please confirm that you can see told changes?

It does work for me now. After starting the app in admin mode

Edited December 7, 20241 yr by mobiel

The application works, as the effect of changing the targets can clearly be noticed.

However, there must’ve been changes in MSFS24 compared to 20 how the TLOD values reflect in the terrain silhouette and texture at distance. In 20, the TLOD target of 600 resulted in perfectly resolved and sharply textured mountains all the way to horizon, in cruise, while in the 24 version the silhouette doesn’t change and the terrain soon becomes smothered, especially when zoomed, even at the max target of 990.

Does anyone have a different experience, and would you mind sharing the settings?

Hello every one

I have exactly the same problem as Mobiel followed all the points and finally got in red

set tlod 55 and olod 195 and start a...

whats going on

but still thanks for your hard work !