7 minutes ago, Reset XPDR said:

Do you have the latest test version 2 installed? It is available here.

If so, what specifically is the issue?

Yes latest one. For example when i first start a session the TLOD of the in game and the app doesn’t match.

Just now, roi1862 said:

Yes latest one. For example when i first start a session the TLOD of the in game and the app doesn’t match.

Can you message me your log file please, located in %appdata%\DynamicLOD_ResetEdition\log. Thanks.

7 minutes ago, Reset XPDR said:

Can you message me your log file please, located in %appdata%\DynamicLOD_ResetEdition\log. Thanks.

I cant seem to find this folder 

11 minutes ago, roi1862 said:

I cant seem to find this folder 

Can you at least find %appdata%\DynamicLOD_ResetEdition because that's where the app gets installed? Are you sure you have test 2 installed? Just run the installer again from here to be sure.

Edited January 30, 20251 yr by Reset XPDR

11 minutes ago, Reset XPDR said:

Can you at least find %appdata%\DynamicLOD_ResetEdition because that's where the app gets installed? Are you sure you have test 2 installed? Just run the installer again from here to be sure.

Got it. Sent you.

Thanks to @roi1862, who has uncovered a major bug with the initialisation of TLOD and OLOD with DynamicLOD_ResetEdition at the start of a session that has been present for many version now, please find a new test version 3 here (or here if the link has been superceded - just navigate to the latest test version).

Due to the severity of this bug, I will likely release a mandatory formal version update to the app once I have confirmation from other users that it is now resolved.

If anyone wants to know how to reproduce the issue, start DynamicLOD_ResetEdition before you start your flight from the MSFS main menu, once your flight has started and the session is green and the settle timer has finished go into the MSFS settings and check that your TLOD and OLOD values match what the app says they are currently set to. In all versions prior to test 3 these values would still be your default MSFS TLOD and OLOD values and in test 3 they should now match what is shown in the app.

Did uninstall AutoFPS and installed this and everything rocks again. I can manually force tlod values i want, so there will be no spikes with TLOD. In VR, there is no need for TLOD of +250, because you wont notice the diffrence drawed far away... Even with latest DLSS transformer model. Thank you for updating this app same as AutoFPS. There is users for this also!

 

Following confirmation that the major TLOD/OLOD initialisation bug was fixed in 0.4.4-test3, I have now formally released DynamicLOD_ResetEdition version 04.4 here. My thanks go out to @roi1862for persisting with identifying this major bug, which would otherwise have gone unnoticed for a very long time.

I was going to release 0.4.4 as a mandatory update due to the severity of this bug, however the mandatory update code needed revising to account for users on much older versions of this app hence it was not used in this case.

Nonetheless, it is strongly recommended that ALL DynamicLOD_ResetEdition users (MSFS 2020 and/or MSFS 2024) update to this version as all versions since Oct 24 will not correctly initialise your TLOD and OLOD when starting a flight session with the app already running, which is the usual way to use this app.

Summary of Changes:

• Fixed major bug that causes TLOD and OLOD not to be initialised correctly when starting a session with the app loaded before the session starts.
• Added MSFS 2024 SU1 Beta (1.3.10.0) Compatibility to the app.
• Various minor bug fixes and improvements.

 

 

Edited February 3, 20251 yr by Reset XPDR

https://youtu.be/t7RRQDE7MIA?si=t2jDvB2LLgDbkfw-

Video about dynamiclod.

16 minutes ago, Corsten said:

https://youtu.be/t7RRQDE7MIA?si=t2jDvB2LLgDbkfw-

Video about dynamiclod.

I am glad that it is working well for you!

@CorstenAre you the same Corsten over on the MSFS official forum with the 5090? If so, have you tried the new MFG with DynamicLOD_ResetEdition and seen what the app detects?  I expect that it will only show 2X when FG is enabled, as that is hard coded in for FG because that's all there was before the 5000 series arrived.

As such, I am trying to work out how to have the app detect what MFG multiplier is in use, but I suspect that the setting is buried somewhere within the nVidia driver settings that are not accessible to external apps without admin privilege, like how nVidia inspector has to run, which pretty much rules out this app being able to detect it without user intervention.

As such, until such time a Asobo puts out an MSFS update where the user can set the MFG multiplier in the MSFS settings menu, I may have to resort to having the user set the MFG multiplier manually, either in the config file (simple for me, messy for the user) or as a drop down list override (messy for me, simple for the user). Either that or the user just needs to be aware that only 2X will show and to factor that in with whatever MFG multiplier they are actually using, ie. pretty much what they'd have to do now anyway, which is ugly but does the job.

Your, or anyone else's, thoughts on this?

1 hour ago, Reset XPDR said:

@CorstenAre you the same Corsten over on the MSFS official forum with the 5090? If so, have you tried the new MFG with DynamicLOD_ResetEdition and seen what the app detects?  I expect that it will only show 2X when FG is enabled, as that is hard coded in for FG because that's all there was before the 5000 series arrived.

As such, I am trying to work out how to have the app detect what MFG multiplier is in use, but I suspect that the setting is buried somewhere within the nVidia driver settings that are not accessible to external apps without admin privilege, like how nVidia inspector has to run, which pretty much rules out this app being able to detect it without user intervention.

As such, until such time a Asobo puts out an MSFS update where the user can set the MFG multiplier in the MSFS settings menu, I may have to resort to having the user set the MFG multiplier manually, either in the config file (simple for me, messy for the user) or as a drop down list override (messy for me, simple for the user). Either that or the user just needs to be aware that only 2X will show and to factor that in with whatever MFG multiplier they are actually using, ie. pretty much what they'd have to do now anyway, which is ugly but does the job.

Your, or anyone else's, thoughts on this?

yes im the same corsten with 5090. I dont know is mfg even working with MSFS, havent tried with nvidia profile inspector settings. Dont actually care, because i fly only in VR atm.

20 minutes ago, Corsten said:

yes im the same corsten with 5090. I dont know is mfg even working with MSFS, havent tried with nvidia profile inspector settings. Dont actually care, because i fly only in VR atm.

If MFG isn't working in MSFS yet, that's probably why I haven't been asked to look into it by anyone yet. I'll just cool my heels until it becomes operational then.

Edit: I just found this video here, which shows MFG operational in MSFS 2020, so there must be some way to do it. I'll start looking at a manual override dropdown selection in the status line, as that is the most user friendly and achievable option at this time.

 

Edited February 13, 20251 yr by Reset XPDR

33 minutes ago, Reset XPDR said:

If MFG isn't working in MSFS yet, that's probably why I haven't been asked to look into it by anyone yet. I'll just cool my heels until it becomes operational then.

Edit: I just found this video here, which shows MFG operational in MSFS 2020, so there must be some way to do it. I'll start looking at a manual override dropdown selection in the status line, as that is the most user friendly and achievable option at this time.

 

 

I can test today with 5090 with msfs2024. So i need to activate it in profile inspector and select x4 in there and in game with frame generation enabled? Would it work that way?

Edited February 13, 20251 yr by Corsten

2 minutes ago, Corsten said:

 

I can test today with 5090 with msfs2024. So i need to activate it in profile inspector and select x4 in there and in game with frame generation enabled? Would it work that way?

I believe so. No one has been able to tell me exactly how to do it, and I can't do it myself as I am slumming it with a 4090 😆, so give it a go and let me know!