OK, I will change the OLOD settings panel visibility to what I originally envisaged before I discovered mouse over, which I must admit can be a bit finnicky at times to keep the panel there. This is what it will look like:

Panel always showing:

Panel hidden:

16 minutes ago, Reset XPDR said:

OK, I will change the OLOD settings panel visibility to what I originally envisaged before I discovered mouse over, which I must admit can be a bit finnicky at times to keep the panel there.

Yay! Now that's what I call incredible support! Many thanks! 🙂

2 hours ago, Adamski_NZ said:

Yay! Now that's what I call incredible support! Many thanks! 🙂

 

14 hours ago, vgbaron said:

Hmm - I'm using SU3 Beta 1.5.3 and the last two test builds and the RC1 build fail the MSFS compat test.

I tried changing MSFS settings etc, also did a clean install of the app.

App recognizes SU3 and connects, then the sinconnect  activates but when it gets to the session - error and close.

I removed the MSFS cache, roaming downloads and scenery indexes - no help.

Thanx!

 

FYI, 0.4.4.10-RC2, available here, is now out with the promised AutoOLOD panel show/hide change and a fix for the memory compat test fail issue identified by @vgbaron.

8 hours ago, Reset XPDR said:

The log will tell you whether the change is being accepted or not. Are you sure you are actually accepting the change by hitting enter or tab after you enter the number? Is this on a particular profile only or any of them?

It's not the number value as I ticked "Auto Target FPS" but the Target field which is always on PC instead of FG if I get it right.

37 minutes ago, vbazillio said:

It's not the number value as I ticked "Auto Target FPS" but the Target field which is always on PC instead of FG if I get it right.

What specific FG are you using? Is it the MSFS in-built FG, which can currently only be set to 2X and is NOT MFG? Or is it MFG, specific to 5000 series GPUs, and you have set it to 2X via the drop down on the status line (which it looks like you have done)?

Regardless, if you are using Auto Target FPS, as your screenshot shows, the target FPS is greyed out because AutoFPS is selecting the target FPS, not you, so you will not be able to change target FPS with this setting enabled.

Also, the fact that the target FPS type of FG is showing with an orange background means you manually changed the target FPS type yourself. Why did you do this and what was it showing before you changed it?

Given all this, my suggestion is that if you are using in-built FG, set MFG to off as you are not actually using MFG, otherwise if using MFG leave MFG set to whatever multiplier you have set in the nVidia app. If you want to set Target FPS you must have Auto Target FPS turned off. Finally, don't use the Target FPS type dropdown unless you are wanting to change Target FPS for a graphics mode you are NOT currently in - ie. generally leave this drop down well alone.

Edit: I have just found something in the code that may be the reason you are trying to change the Target FPS type and that is because you are not being presented with an MFG target FPS type because the logic removes it before it has actually run the check to see if you have a 5000 series GPU.

I will fix the code so that it will present it and then you could have another go at trying to do what you were before, noting you still can't have auto target FPS enabled if you ever want to set a target FPS. I will let you know when I have fixed it and have a test version for you to try.

Edited May 25, 20251 yr by Reset XPDR

I'm using the Frame Rate Multiplier from MSFS (2x). Nvidia App is set to "Use the 3D Application setting". I have a 5070ti.

19 minutes ago, Reset XPDR said:

Also, the fact that the target FPS type of FG is showing with an orange background means you manually changed the target FPS type yourself. Why did you do this and what was it showing before you changed it?

I manually changed the Target field "type"(and it was the whole point of my initial question) because it default displays "PC" at each launch. And I though I need to be aligned with my MSFS settings. I also though that MFG set to 2x in MSFS_AutoFPS would be a good idea even if there's confusion with MFG and FG when only 2x is used 😉 Is the mode 2x FG or MFG 2x ?

Regarding target FPS, I set it in MSFS (usercfg.opt and now in SU3 in the Graphics Settings UI) to 30. MSFS_AutoFPS seems to understand that the final fps is 60 fps (30x2) and managed TLOD accordingly.

Edited May 25, 20251 yr by vbazillio

13 minutes ago, vbazillio said:

I'm using the Frame Rate Multiplier from MSFS (2x). Nvidia App is set to "Use the 3D Application setting". I have a 5070ti.

I manually changed the Target field "type"(and it was the whole point of my initial question) because it default displays "PC" at each launch. And I though I need to be aligned with my MSFS settings. I also though that MFG set to 2x in MSFS_AutoFPS would be a good idea even if there's confusion with MFG and FG when only 2x is used 😉 Is the mode 2x FG or MFG ?

 

You may have missed my edit above as I have identified a chicken and egg situation with 5000 series card detection in that the detection is currently done after you connect to a session, but the window creation code blows away the MFG option because it is run before this.

Please understand that I don't have a 5000 series card myself and in the nearly 4 months since 5000 series cards came out you are the first to actually provide me any feedback at all on the MFG option that I had to code blind without actually being able to test it properly. I will do my best to resolve this given this limitation.

 

11 minutes ago, vbazillio said:

I also though that MFG set to 2x in MSFS_AutoFPS would be a good idea even if there's confusion with MFG and FG when only 2x is used 😉 Is the mode 2x FG or MFG ?

Again, this is the first time anyone has shown me a screenshot of how MFG is actually set in the nVidia app and to be honest I am not really sure whether there is a difference or not. Let me ponder it some more.

Edited May 25, 20251 yr by Reset XPDR

It's absolutely not a top priority. Considering it actually works. 

I'm putting in the shoes of someone wanted to test MSFS_AutoFPS for the first time and explore the Expert mode 😉

Let me know if I can help as I didn't expect to be the first given feedback with a 5000 série.

10 minutes ago, vbazillio said:

It's absolutely not a top priority. Considering it actually works. 

I'm putting in the shoes of someone wanted to test MSFS_AutoFPS for the first time and explore the Expert mode 😉

Let me know if I can help as I didn't expect to be the first given feedback with a 5000 série.

I think I've fixed it here in 0.4.4.10-RC3. 

MFG should now be initially presented as a Target FPS Type and autodetect and stay that way once you are in a flight session as long as you have MFG multiplier set to anything other than Off. Regarding whether to use MFG as 2X or set it to Off and have the app auto detect that you have enabled it in MSFS graphics settings, either should work (I think 😄). 

I'm sure you'll let me know one way or another!

51 minutes ago, Reset XPDR said:

I'm sure you'll let me know one way or another!

0.4.4.10-RC3 seems to behave as expected. Without setting anything manually (here on ground, screenshot process limit to 30fps but when focused on MSFS, it's a steady 60fps as expected):

Thank you!

Edited May 25, 20251 yr by vbazillio

9 hours ago, Reset XPDR said:

FYI, 0.4.4.10-RC2, available here, is now out with the promised AutoOLOD panel show/hide change and a fix for the memory compat test fail issue identified by @vgbaron.

Works perfectly!  Thanx!

 

Vic

MSFS_AutoFPS version 0.4.4.10 has just been formally released and is available for download here. As usual, my heartfelt thanks go out to everyone who provided feedback, especially to the regular testers over on Github who contributed the most. Enjoy!

Executive Summary

This update introduces Line of Sight correction, installer and auto-update improvements, UI refinements, optimized VRAM+ and TLOD logic, enhanced LOD verification, removed redundant functionality, and expanded logging.

Summary of Changes

• Line of Sight Correction: Added an option for more realistic TLOD automation behaviour.
• Installer: Updated to .NET 8.0 and improved VC++ installer with a /norestart option.
• Auto Update: Introduced -quickupdate for simplified updates and improved test version detection.
• UI: Improved OLOD panel visibility, fixed MFG selection, refined version display, and added new symbols for TLOD/OLOD limits.
• VRAM+: Enhanced logic for TLOD adjustments based on VRAM usage to optimise performance.
• TLOD Base +: Fixed and refined TLOD seek behavior for improved altitude-dependent adjustments.
• LOD Changes: Optimized TLOD/OLOD verification, added lockout logic for resets, and improved profile bounding.
• General: Removed redundant functionality and fixed a rare VR settings restoration issue.
• Logging: Enhanced logging to include VRAM+ details, Line of Sight setting changes, and profile updates.

Works brillantly with MSFS 2024 SU2. Flying the 777F, in 4K with FSR3/TAA I'm getting 70+ FPS with TLOD at 400, most settings on high/ultra.

"It just works".

Though it's already a 204pp topic, I still think there's enough space to voice some appreciation for an addon that we may have once thought to be destined for the boneyard - but has become as indispensible as Addons Linker. It's been an interesting journey, watching it get tweaked and improved.

Kiwis are fond of their Pavlovas, so here's a Kiwi Oscar for you!

I am very Happy with autofps.

Now that i have a 5080 how would i set it up with using frame gen?

60hz tv here.4k

Do i just select mfsg x 2?in autofps?

Vsync off? Or on?

Will it help with vram as it has only 16gb? And dx12

 

Thanks

Mike