Hi, with the latest build 4.4.10 I've noticed that I have to start autofps whilst in VR otherwise although the autofps panel may say tlod of 50 it won't change the tlod setting in the SIM itself, didn't  seem to be the case with previous builds, am I missing something?

 

10 hours ago, magdrop said:

Hi, with the latest build 4.4.10 I've noticed that I have to start autofps whilst in VR otherwise although the autofps panel may say tlod of 50 it won't change the tlod setting in the SIM itself, didn't  seem to be the case with previous builds, am I missing something?

 

I have just double checked this and it is working fine in VR on my end, regardless of whether I start the app before or after entering VR. As long as the app says VR at the start of the app status line, which it will do within 5 seconds of switching to VR, then the app is controlling VR settings. Make sure you are looking at MSFS VR, not General, settings to verify what the app says TLOD should be versus what MSFS says it is currently set to.

After struggling to get the new proposed acronym BASE, replacing PC in the app, working with grammatic consistency with the other graphics mode acronyms in the readme, I have decided to choose another. Since no actual acronym seems to currently exist for not using frame generation, I will need to create a new one and the best one I can come up with is Native Frame Rate (NFR) as that is what it truly is, so I am now planning on using that in future versions of this app.

Being a new acronym, it will be defined at first use in the readme and in the tooltip for the graphics type dropdown. BTW, I have done a quick check to see whether NFR has any undesired connotations and nothing is coming up. The worst is from urban dictionary, defining it as No Fun Ryan and I think I can live with that. 😄 

Please let me know if I am about to step onto something I really shouldn't, otherwise 0.4.4.11 formal release containing this change is planned for a few hours time.

Draft readme change in the Summary section:

• Simultaneous Native Frame Rate (NFR), Frame Generation (FG) - including native nVidia, MFG, FG mod, FSR3 or Lossless Scaling - and VR graphics mode compatibility, including correct FG FPS display, and separate FPS targets for each mode,

Then all PC references changed to NFR for the rest of the readme.

Proposed UI on startup with tooltip showing:

Very good!

I prefer: "Not for Resuscitation" 🙂 🙂 🙂

Unfortunately, another aviation-related one came up: "Network Flight Recorder" ... but maybe that's a little obscure!

Also ... seeeing as I'm in NZ ... how's about "Nuclear Free Region" 😉

6 hours ago, Reset XPDR said:

I have just double checked this and it is working fine in VR on my end, regardless of whether I start the app before or after entering VR. As long as the app says VR at the start of the app status line, which it will do within 5 seconds of switching to VR, then the app is controlling VR settings. Make sure you are looking at MSFS VR, not General, settings to verify what the app says TLOD should be versus what MSFS says it is currently set to.

It's definitely in the vr settings. It must be something unique to my system as it is the same in both Fs24 and fs20. The autofps panel is responding correctly but is not changing the flight SIM tlod unless I start it when already in vr mode. Not a major problem but curious. 

2 minutes ago, magdrop said:

It's definitely in the vr settings. It must be something unique to my system as it is the same in both Fs24 and fs20. The autofps panel is responding correctly but is not changing the flight SIM tlod unless I start it when already in vr mode. Not a major problem but curious. 

Is this the Steam or MS versions of MSFS? Also, does the app show VR on the status line when you switch to VR after starting AutoFPS in 2D mode?

In any case, send me a private message of the initial log file contents of a flight session where you load in in 2D then switch to VR and I will see if that tells me any more.

MSFS_AutoFPS version 0.4.4.11 has just been formally released and is available for download here. It was only a minor update, with most changes internal and not really testable by testers, hence no public test phase was conducted. Nonethless, the internal changes have been thoroughly tested by me and should be solid. If not, I'm sure you'll let me know!

Executive Summary

A minor update, primarily to fix auto update to work with formal releases and future test versions and to replace the outdated PC acronym in the app with a more accurate and new NFR (Native Frame Rate) acronym.

 

 

 

1 hour ago, Reset XPDR said:

Is this the Steam or MS versions of MSFS? Also, does the app show VR on the status line when you switch to VR after starting AutoFPS in 2D mode?

In any case, send me a private message of the initial log file contents of a flight session where you load in in 2D then switch to VR and I will see if that tells me any more.

It's the MS version for both Fs24 fs20, the status bar shows VR and the tlod 50 (on the ground) but SIM tlod stays at 150(VR settings) unless I restart autofps while in vr mode, then it performs correctly.

How do I access log file? It's not a big issue for me as the autofps works fine otherwise.

41 minutes ago, magdrop said:

It's the MS version for both Fs24 fs20, the status bar shows VR and the tlod 50 (on the ground) but SIM tlod stays at 150(VR settings) unless I restart autofps while in vr mode, then it performs correctly.

How do I access log file? It's not a big issue for me as the autofps works fine otherwise.

It's a big issue for me if it's not working as it should for such a core function.

The log files are located in %appdata%\MSFS_AutoFPS\log. I'll message you my email address so you can just attach the file directly.

Thanks

Email with Log attachment sent.

With the paint barely dry on MSFS_AutoFPS version 0.4.4.11, 0.4.4.12 has just been formally released and is available for download here. A minor but important update for VR users to fix a TLOD setting issue on transition from 2D to VR mode and vice versa.

This issue, discovered through@magdrop's keen observation, was inadevertently introduced in 0.4.4.10 by a change for the app to be less intrusive with MSFS by limiting LOD changes to the current graphics mode rather than both 2D and VR as done with all previous app versions. One line of code that assumed this previous dual graphics mode arrangement managed to sneak through all testing defences, due to the obscure conditions require to trigger it, and finally played up with @magdrop's unique settings.

Thankfully it was a very simple fix and I decided to make an immediate update due to impact it could have on some VR users.

Detailed Changes

• Fixed issue where TLOD was not being reset correctly when transitioning between 2D and VR modes if the current TLOD value was the same as the new TLOD value.

 

 

With this latest version, I cannot get it to open, its open on my desktop but i cant even access the program.

Thoughts?

I deleted everything MSFS auto fps to do a fresh reinstall, when I click on the exe it does nothing..........

 

What is going on?

Nevermind, was able to uninstall and reinstall and got to work finally.