Do you have any idea why I am getting an OLOD at 0 constantly?

3 hours ago, spearmint_flyer said:

Do you have any idea why I am getting an OLOD at 0 constantly?

Edit: I found an issue in 0.4.4.8-test where OLOD would set and show as 0 in non-expert mode, which is not good, that is fixed in 0.4.4.8-test27 just released here. Thank you for identifying this issue.

There is also a minor issue in 0.4.4.7 where OLOD may initially show as 0 while loading in to a flight in non-expert mode but it corrects itself as soon as the session commences, so it is really only cosmetic and will be fixed in 0.4.4.8 anyway.

 

 

Edited March 31, 20251 yr by Reset XPDR

This app work with 2024 ?> 

22 minutes ago, fakeflyer737 said:

This app work with 2024 ?> 

Yes. If you are on MSFS SU1 you can use the formal release version 0.4.4.7. 0.4.4.7 also works with SU2 Beta however if you want FG detected correctly you should use the latest test release 0.4.4.8-test.

I normally keep test version announcements on my github discussion page but this recent and somewhat long overdue change - the ability to change target FPS for graphics modes other than the one you are currently in -  has been something many have requested in the past, so there may be new interest in checking it out. It is available in 0.4.4.8-test31 or later, which you can download here.

• Added ability for user to change the target FPS for graphics modes other than what is currently active.
  • Selectable by using the drop down list of target FPS types in the app window.
  • Target FPS type drop down list background will change to orange when the target FPS type is different to the current graphics mode to clearly indicate this difference to the user.
  • Changes to target FPS for a type different to the current graphics mode will be saved to the config file without reloading the UI as it does not affect any other displayed settings.
  • Changes to any other setting on the UI will reload the target FPS type for the current graphics mode.
  • Particularly useful for VR users who have previously had to be in VR and remove their headset to change this setting.

 

@Reset XPDR

Today I took off from Amsterdam to make a short hop to Rotterdam at 5000 ft.

AutoFPS showed 92 FPS ( FG on ) : Auto target enabled like I use in MSFS 2020.

( MSFS 2024 SU beta )

After take off TLOD remained at 50 and did not increase. 

After setting a fixed FPS of 40 ( = 80 with FG on ) within 10 sec TLOD went up to 172.

At approach to Rotterdam below 2000 ft the framerate dropped to 30 and remained at 30 after landing.

When I disabled AutoFPS the framerate jumped to 62.

Restarting AutoFPS and the framerate went up to over 90 again.

Any suggestions ?

Thanks

 

1 hour ago, GSalden said:

@Reset XPDR

Today I took off from Amsterdam to make a short hop to Rotterdam at 5000 ft.

AutoFPS showed 92 FPS ( FG on ) : Auto target enabled like I use in MSFS 2020.

( MSFS 2024 SU beta )

After take off TLOD remained at 50 and did not increase. 

After setting a fixed FPS of 40 ( = 80 with FG on ) within 10 sec TLOD went up to 172.

At approach to Rotterdam below 2000 ft the framerate dropped to 30 and remained at 30 after landing.

When I disabled AutoFPS the framerate jumped to 62.

Restarting AutoFPS and the framerate went up to over 90 again.

Any suggestions ?

Thanks

 

Your screenshot shows you are under your target FPS, which is why the TLOD is not increasing. Also, when you manually set your target FPS when using FG, you set it to your post, not pre, FG desired FPS, which explains why your TLOD shot up when setting it to 40 but you are actually getting > 70 FPS post-FG.

As for your other observations, it is a bit hard to tell what is going on without an accompanying log file. Please either message me your log file here or, preferably, post it up on the 0.4.4.8-test discussion thread over on my github discussion page here, which is dedicated to this test program and where it is a lot easier to attach whole log files and screen shots.

Edited April 5, 20251 yr by Reset XPDR

10 hours ago, Reset XPDR said:

Your screenshot shows you are under your target FPS, which is why the TLOD is not increasing. Also, when you manually set your target FPS when using FG, you set it to your post, not pre, FG desired FPS, which explains why your TLOD shot up when setting it to 40 but you are actually getting > 70 FPS post-FG.

As for your other observations, it is a bit hard to tell what is going on without an accompanying log file. Please either message me your log file here or, preferably, post it up on the 0.4.4.8-test discussion thread over on my github discussion page here, which is dedicated to this test program and where it is a lot easier to attach whole log files and screen shots.

Thank you for explaining.

Going to make the same flight today as I remembered that after using 40 manual not only TLOD went up to 172 but also the framerate to 112.

Will report back at you Github page.

Hello @Reset XPDR 

Do you plan to introduce " 9 key MSFS settings between their default value (unchecked) and lowest quality setting (checked) for testers to help quantify the effect on FPS and VRAM consumption"  in MSFS 2020?

Sincerely

Carlos

2 hours ago, cteixeira said:

Hello @Reset XPDR 

Do you plan to introduce " 9 key MSFS settings between their default value (unchecked) and lowest quality setting (checked) for testers to help quantify the effect on FPS and VRAM consumption"  in MSFS 2020?

Sincerely

Carlos

Not at this stage, because 2020 is primarily CPU-bound in challenging performance scenarios for most users and these key settings are either 2024-specific or alleviate GPU load, hence are either inapplicable or of limited/no benefit in such situations.

For VR use....Is it still recommended to set Target FPS 2-3 under my actual FPS lock?  For instance, I lock at 45 fps.  Should I set my Target FPS to say 42-43?

7 hours ago, FakeWayne said:

For VR use....Is it still recommended to set Target FPS 2-3 under my actual FPS lock?  For instance, I lock at 45 fps.  Should I set my Target FPS to say 42-43?

No. You can use FPS Cap auto mode and set your target FPS to 45 to match your actual FPS lock. I use this mode with my Quest 3 all the time and it works great.

AutoFPS never has a clue that my msfs2024 is up and running. This has true for the many versions of AFPS that I tried. Including 0448

AutoFPS worked fine for me with msfs2020.

 

 

58 minutes ago, Fielder said:

AutoFPS never has a clue that my msfs2024 is up and running. This has true for the many versions of AFPS that I tried. Including 0448

AutoFPS worked fine for me with msfs2020.

 

 

Try this from the readme:

• If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:
  • Try downloading and installing/repairing a Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.
  • Try downloading and installing/repairing the NET desktop runtime from here and here.
  • If still not resolved and the error code in your AutoFPS log file is Exception 31, you most likely have a corrupt MSFS installation so you can choose to either not run this app or to reinstall MSFS completely.
  • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here, which only takes around 15 minutes to complete and all your settings, controller assignments, career progression and your pilot profile are retained.

 

Thank you, sir. I got autofps up and running in msfs2024 for the first time. It works perfectly now! Not any problems, it works now in 2024 like it always did in 2020. Thanks again!

edit: I wanted autofps for VR, since FG and LSFG doesn't work in VR. Now I have it !

Edited April 9, 20251 yr by Fielder