52 minutes ago, Reset XPDR said:

We hold no grudge against each other and may even collaborate into the future.

pfft!

I select trial by combat. 

😛

Regarding my failure to implement autostart of MSFS as stated in my post above, here is some additional information.
- I messed up by leaving the "<" in front of my user name in the path provided in the ReadME
- Thank you to those who responded

What should be the settings for VR with Motion Reprojection on? 

- Is AutoFPS or DynamicLOD_Reset more appropriate for VR with MR on?

- What should be the FPS target?

In VR, maintaining the target FPS is key, and MR is a must for most users (me included) for smooth experience. But the problem is that it essentially caps framerate at 45 (in case of 90Hz refresh) or 40 (80 Hz) or 36 (72Hz). So how would AutoFPS know that it's time to increase FPS if they would never go above that value? Also, would it be too late correcting the problem when FPS fall below 45 - because when it happens there would already be stutters in VR. This makes it far from clear what target FPS to set.

So what are the recommended settings for this? 

If it matters, I have Quest 3 + Virtual Desktop (god mode, VDXR), RTX 4090, 7950X3D, 64Gb DDR5 RAM.

20 minutes ago, El Diablito said:

There's something really weird going on now. When the sim launches, both versions 0.3.5 and 0.4.1 both launch and I get the error to say it's already running. I can click the "ok" on the error and the sim still loads as normal but what the hell is going on now? lol

I also get a double launch of FSUIPC7, which I have to click off the error for also. I think there comes a point when you have to stop adding things to the sim for quality of life fixes and just go back to basics.

Locate your EXE.xml file and remove the sections you don't want to start. You can find it here: MS Store Version: "C:\Users\YOUR_USERNAME\AppData\Local\Packages\Microsoft. FlightSimulator_8wekyb3d8bbwe\LocalCache\ or Steam Version: "C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator"

 

eg. to remove the 0.3.5 startup, delete this section entirely:

 <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>DynamicLOD</Name>
    <Path>C:\Users\<username>\AppData\Roaming\DynamicLOD\bin\DynamicLOD.exe</Path>
  </Launch.Addon>

 

Edited March 4, 20242 yr by Reset XPDR

9 minutes ago, Reset XPDR said:

Locate your EXE.xml file and remove the sections you don't want to start. You can find it here: MS Store Version: "C:\Users\YOUR_USERNAME\AppData\Local\Packages\Microsoft. FlightSimulator_8wekyb3d8bbwe\LocalCache\ or Steam Version: "C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator"

 

eg. to remove the 0.3.5 startup, delete this section entirely:

 <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>DynamicLOD</Name>
    <Path>C:\Users\<username>\AppData\Roaming\DynamicLOD\bin\DynamicLOD.exe</Path>
  </Launch.Addon>

 

Willco, Reset 👍

4 minutes ago, El Diablito said:

Willco, Reset 👍

If you get stuck, just copy and paste your EXE.xml contents into a message you send me and I will trim out the two offending entries for you.

3 minutes ago, Reset XPDR said:

If you get stuck, just copy and paste your EXE.xml contents into a message you send me and I will trim out the two offending entries for you.

Fair play to you, I've just done the editing there myself including deleting the launch for FSUIPC in there also, that's been happening for a few months now and I couldn't figure out why. Killing 2 birds with one stone hopefully.

I'll let you know how it goes. Thanks again.

31 minutes ago, Roman Design said:

What should be the settings for VR with Motion Reprojection on? 

- Is AutoFPS or DynamicLOD_Reset more appropriate for VR with MR on?

- What should be the FPS target?

In VR, maintaining the target FPS is key, and MR is a must for most users (me included) for smooth experience. But the problem is that it essentially caps framerate at 45 (in case of 90Hz refresh) or 40 (80 Hz) or 36 (72Hz). So how would AutoFPS know that it's time to increase FPS if they would never go above that value? Also, would it be too late correcting the problem when FPS fall below 45 - because when it happens there would already be stutters in VR. This makes it far from clear what target FPS to set.

So what are the recommended settings for this? 

If it matters, I have Quest 3 + Virtual Desktop (god mode, VDXR), RTX 4090, 7950X3D, 64Gb DDR5 RAM.

This is all covered in the readme.

32 minutes ago, Reset XPDR said:

If you get stuck, just copy and paste your EXE.xml contents into a message you send me and I will trim out the two offending entries for you.

Yeah that fixed it, no more double launch of the other app too. Sim loads twice as fast now too. What an odd quirk.

6 hours ago, Reset XPDR said:

This is all covered in the readme.

I actually read both readme files for both apps before posting. It's generalized for all FPS caps (FPS about 10% less than cap) and basically says "if it breaks motion reprojection for you - this app is not for you". But I was wondering about people's actual experience with it. In theory, going anywhere below 45 FPS (with 90Hz) will break motion reprojection (I had G2 prior to Quest 3) and create some judder or tearing. But people seem happy with VR and this app, including you I assume. I suspect that the actual setting for the FPS, and chosing the right app from the two can be very important, and a couple of FPS can make or brake the whole thing. So I was wondering what people are using with Quest 3 and VDXR, how close they get (someone mentioned 5% and not 10%) to the cap etc. If would be nice to know what works for VR users, because most seem to use pancake mode.

2 hours ago, Roman Design said:

I actually read both readme files for both apps before posting. It's generalized for all FPS caps (FPS about 10% less than cap) and basically says "if it breaks motion reprojection for you - this app is not for you". But I was wondering about people's actual experience with it. In theory, going anywhere below 45 FPS (with 90Hz) will break motion reprojection (I had G2 prior to Quest 3) and create some judder or tearing. But people seem happy with VR and this app, including you I assume. I suspect that the actual setting for the FPS, and chosing the right app from the two can be very important, and a couple of FPS can make or brake the whole thing. So I was wondering what people are using with Quest 3 and VDXR, how close they get (someone mentioned 5% and not 10%) to the cap etc. If would be nice to know what works for VR users, because most seem to use pancake mode.

I don't use MR so I can't offer you my personal experience with this. If you don't get any takers to help you with settings, perhaps you could experiment and find out what does work, then let me know and I will update the readme accordingly.

Proposed new app icon. Guess which one it is: 😄

Following up on the conflict between TweakUI and MSFS2020_AutoFPS, I decided to test whether the new nVidia app's statistics overlay causes the same failure. I am pleased to report that it does not. If the nVidia app is loaded after MSFS2020_AutoFPS, it will show NA for FPS. If nVidia is loaded first and MSFS2020_AutoFPS second, both apps will report FPS. But, so far, neither app has caused the other to crash. 

As for Roman Designs question, I use MSFS2020_AutoFPS in VR. I am still experimenting with settings. I have motion reprojection in the sim set to DEPTH. Using Varjo Aero and RTX4090 on an i9-13900K system. I set  the desired fps to 90 in MSFS2020_AutoFPS and the Varjo base software to 45 fps. It seemed to struggle a bit. So, tonight I set the desired fps to 90 in MSFS2020_AutoFPS and the Varjo base to 30 fps. That gives me a solid 30-31 fps in VR with motion reprojection. However, the TLOD and OLOD drop to minimum and the clouds drop from ultra to high.  I will continue to play with it but so far, in MSFS2020_AutoFPS has not broken motion reprojection on this system.

 

Edited March 5, 20242 yr by SkylanePilot
typo

Wow! I've just come across this app and absolutely love it! Flying complex aircraft into add-on scenery has never been  easier. Used to have frame fade and freezes like mad but now can do an approach and do finals really smoothly and concentrate on the hands-on flying like I should. Thank you!

I have started working on the next AutoFPS version.

After using the app for a week doing normal, not test, flights, one thing I have found is that even though I generally only change one expert setting depending on the type of flight I am doing, namely TLOD Min, this also requires that I rejig Cloud Recover TLOD as it is currently an absolute value that often conflicts with my new TLOD Min. DynamicLOD_ResetEdition uses a relative rather than absolute recovery value. While I could just switch to this in the next version, this may cause confusion for users used to the existing arrangement. As such, I thought of giving a simple option for the user to choose which one they want, like this:

 

In this example Cloud Recovery TLOD is relative + 50, so if I leave my TLOD Min as it currently is here the Cloud Recovery TLOD works out to be 50 + 50 = 100 and if I change TLOD Min to be 100, Cloud Recovery TLOD works out to be 100 + 50 = 150. There will be boundary checks of course so for example if you unchecked the + option right here, you can't have an absolute Cloud Recover TLOD the same value as your TLOD Min so it would calculate a new one within bounds but that you could change again within those bounds if you wanted. I suspect this is the sort of option that people would either check or uncheck and leave it, but the boundary protection is there in any case.

FWIW, I will be using the + (relative) option with my flying.

BTW, I have recently discovered tooltips, so they will be coming to the next version too.