10 hours ago, Corsten said:

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

Video about dynamiclod.

Nice music track, did you create that yourself?

4 hours ago, kevinfirth said:

Nice music track, did you create that yourself?

Yes, all the music in my videos are my own.

4 hours ago, Reset XPDR said:

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!

So DynamicLod is showing native fps, but it doesent matter to me because DynamicLOD dont need FPS info with this conficuration. But with FPS adaption things are diffrent.

1 hour ago, Corsten said:

Yes, all the music in my videos are my own.

Where can I get more please?

39 minutes ago, kevinfirth said:

Where can I get more please?

did message you DM.

7 hours ago, Corsten said:

So DynamicLod is showing native fps, but it doesent matter to me because DynamicLOD dont need FPS info with this conficuration. But with FPS adaption things are diffrent.

Thanks for doing this. I gather you didn't need to enable frame generation in the MSFS settings for MFG to work? If you did have to, the app would have detected FG and would have given you the 2X FG FPS reading ie 70 in this case.

As it looks like you don't have to enable in-game FG and it is not possible for the app to detect what nVidia Inspector or App settings are in play, it looks like the only way to get the app to show MFG properly at this time is by the user manually setting it somewhere, either on the UI or in the config file. I'll have more of a think about how to deal with it.

Re FPS adaption, you can still use it as the app currently stands but you have to set it to your non MFG trigger FPS. eg. with what looks like 4x MFG in use and FPS adaption set to 30 as you currently have, and subsequently enabled, it would trigger at 120 FPS actual FPS.

As I have AutoFPS open for development ATM, I have coded up what could be an interim, albeit manual, solution to displaying MFG correctly for 5000 series cards that I could also put in DynamicLOD_ResetEdition.

The app will detect whether you have a 5000 series graphics card automatically from reading the Video Adapter information in your UserCfg.opt file and, if so, will present you with an MFG drop down list, that will default to MFG off, at the left side of the app status line like so:

If you leave it at MFG off, it will behave as it normally would in PC mode with no FG enabled.

If you select one of the MFG multipliers to be consistent with what MFG multiplier you have set in the nVidia app or inspector, your FPS will be multiplied and displayed correctly and an MFG-specific target FPS will come to play (under FPS Adaption for DynamicLOD_ResetEdition).

With MFG 4X it will look something like this:

If a 5000 series card is not detected, the app will function and display the same as it always has, with no MFG drop down box being shown at all. In VR mode, this drop down list will also disappear as it is not relevant to VR.

When Asobo adds the ability to select MFG mode and multiplier within MSFS settings, I will update these apps to automatically detect it and do away with this interim MFG drop down list.

Would this be acceptable to everyone as an interim solution?

I had a bit of spare time today so I rolled the MFG change mentioned above into a DynamicLOD_ResetEdition test version 0.4.5-test1 available here.

While I was in there, I also rolled the new Auto Update feature I currently have being trialed in an AutoFPS test build, with good success so far. Basically, this will allow users a relatively hands off approach in keeping their app updated. It will also allow optional participation in test phases with automatic updates available there too.

The middle ground option is essentially what the app currently does ie. shows if an update is available and presents a link to update to it should the user so desire. This now works for test build updates as well, if the user is already running a test version.

For those that don't like change, there is a mandatory only update choice where users will not even be notified of other updates except mandatory ones, of which there have been none yet but there will be the next time an MSFS update breaks compatibility or a critical bug is found and fixed.

Anyway, if someone with a 5000 series card (@Corsten?) could take a look at the new MFG functionality and report back I would greatly appreciate it.

Edited February 15, 20251 yr by Reset XPDR

On 2/15/2025 at 1:31 PM, Reset XPDR said:

I had a bit of spare time today so I rolled the MFG change mentioned above into a DynamicLOD_ResetEdition test version 0.4.5-test1 available here.

While I was in there, I also rolled the new Auto Update feature I currently have being trialed in an AutoFPS test build, with good success so far. Basically, this will allow users a relatively hands off approach in keeping their app updated. It will also allow optional participation in test phases with automatic updates available there too.

The middle ground option is essentially what the app currently does ie. shows if an update is available and presents a link to update to it should the user so desire. This now works for test build updates as well, if the user is already running a test version.

For those that don't like change, there is a mandatory only update choice where users will not even be notified of other updates except mandatory ones, of which there have been none yet but there will be the next time an MSFS update breaks compatibility or a critical bug is found and fixed.

Anyway, if someone with a 5000 series card (@Corsten?) could take a look at the new MFG functionality and report back I would greatly appreciate it.

This: Release v0.4.5-RC Auto Update and MFG Support Version · ResetXPDR/DynamicLOD_ResetEdition · GitHub    DynamicLOD_ResetEdition-Installer-v0.4.5-RC1.exe ?

1 minute ago, Corsten said:

This: Release v0.4.5-RC Auto Update and MFG Support Version · ResetXPDR/DynamicLOD_ResetEdition · GitHub    DynamicLOD_ResetEdition-Installer-v0.4.5-RC1.exe ?

Yes that one thanks.

DynamicLOD_ResetEdition version 0.4.5-RC2 has just been released and is available for download here.

Of particular notes is that I have finally worked out how to make an editable combo box, so I have introduced the following new feature that was requested by users a long time ago:

- Added user edit-ability of the profile list names.
  - Double clicking on the profile combo box toggles edit-ability, with non-editable being the initial state on startup.
  - Press Enter, press Tab or click on another control on the app UI for the changed text to be accepted.

If someone can have a try of this new feature and let me know how it goes, I will much appreciate it.

On the expectation that this change will be acceptable, I plan to formally release 0.4.5 shortly after MSFS 2024 SU1 is formally release, probably in the next week or so.

 

So glad you are keeping this mod going for those of us who  dont want to use AutoFPS.  Makes a huge difference.  Such smooth flights on my laptop with custom airports.  

DynamicLOD_ResetEdition version 0.4.5 has just been released and is available for download here. Thanks go out to everyone who participated in and provided feedback during the relatively short test phase.

Summary of Changes:

• Fully compatible with MSFS 2024 SU1 (1.3.23.0).
• Added user edit-ability of the profile list names.
• Added support for Adaptive Frame Generation with the Lossless Scaling app.
• Expanded app update checking to add auto update installation and optional test version participation capability.
• Added interim manual MFG support for 5000 series nVidia GPUs.
• General improvements, optimisations and minor bug fixes.

Finally, although the detailed list of changes is quite long, the vast majority of these changes were developed and thoroughly tested beforehand with AutoFPS. They have been included because they are equally applicable to DynamicLOD_ResetEdition and keep a common baseline of equivalent functionality for maintainability purposes.

 

With the recent release of MSFS 2024 SU2 beta, DynamicLOD_ResetEdition will be updated to properly detect the changes made in SU2 to frame generation settings. To that end, if you are on the SU2 beta and want this to work again please update to the latest v0.4.6 test version here. 

As other SU2 new "features" affecting DynamicLOD_ResetEdition are discovered, new test versions will be released addressing them.

Release notes for v0.4.6-test:

Test1:

• Updated FG detection to work with the MSFS 2024 SU2 Beta.
  • FSR3 FG is now detected, however a base target FPS must be used as the FG multiplier is variable for this type of FG.
  • MFG for 5000 series GPUs now looks to be settable in the MSFS 2024 SU2 Beta. The app will be updated in a future test version to support auto-detection of this FG type.

 

Edited March 26, 20251 yr by Reset XPDR

FYI, there is a new DynamicLOD_ResetEdition 0.4.6-test2 version out available here.

I wasn't intending to announce each test release anymore, but this one fixes FG detection on the latest MSFS 2024 SU2 Beta 1.4.9.0, so if you are on this version it is worth updating to it.

There are a few other applicable improvements rolled in from the AutoFPS 0.4.4.8 test program which has been running for a few weeks now, so these should be pretty solid to use.

As usual with new DynamicLOD_ResetEdition releases, functionality and the UI remains essentially the same!

Specific changes in Test2 are:

• Changed FG (DLSS or FSR3) detection to read directly from the UsferCfg.opt file in lieu of MSFS memory as a more reliable and less intrusive detection method. A postive side effect of this change is that FG is now checked every second in a flight session will automatically switch to whatever the user changes the MSFS setting to while in that session.
• Modified the MSFS 2024 memory offset search to begin from the last known working offset.
  • Expands incrementally above and below this starting point, accounting for the tendency of the offset to shift slightly following updates to MSFS 2024.
  • Should result in quicker offset searches that are more likely to find the new offset for future MSFS 2024 updates.
• Changed MSFS connection status to be orange when the memory offset search is running.
• Added sim rate detection with a range of 0.125X to 16X, which will display on the app status line for any value except 1X.
• Added two new allowable FSUIPC7 registry keys for MSFS2020-only and MSFS2024-only FSUIPC7 installations to the installer for the FSUIPC autostart option.
• Updated app to .NET 8.0.14.