20 minutes ago, Reset XPDR said:

, which changed everything related to this.

I'm not so sure about this. On my system (fairly old: 8700K, 1080TI) the ever-changing TLOD changes of the AutoFPS tool induce a major stuttering (regardless of the VSync judders I get when the FPS are not fixed). Looking at the signatures of most of the posters in this thread I have a feeling that the AutoFPS tool works best on high end machines that are running at very high FPS anyway, but does not really help if you are already struggling with performance on an older PC.

With your DynamicLOD tool everything is perfectly smooth even on my system.

 

19 minutes ago, RALF9636 said:

I'm not so sure about this. On my system (fairly old: 8700K, 1080TI) the ever-changing TLOD changes of the AutoFPS tool induce a major stuttering (regardless of the VSync judders I get when the FPS are not fixed). Looking at the signatures of most of the posters in this thread I have a feeling that the AutoFPS tool works best on high end machines that are running at very high FPS anyway, but does not really help if you are already struggling with performance on an older PC.

With your DynamicLOD tool everything is perfectly smooth even on my system.

 

I'm getting reports of reasonable smoothness with AutoFPS on older systems, but admittedly not quite as old as yours so you do have a point. As you say, if you can't achieve smoothness with AutoFPS, whose primary focus is FPS, then you're probably better off with DynamicLOD which is more focused on smoothness.

@Reset XPDR I had a little bit of time to run a few further tests, From what I am seeing the OLOD part is definitely interfering with something causing minor stutters. After the last capture I did another 15 minutes and this time left the OLOD on 10 but turned off the auto feature the results in CapFrame X were back to what I was seeing previously. Next I rebooted my PC and fired everything up again and this time left the OLOD set at 200 and the auto feature turned off ran another CapFrameX capture for just over 15 minutes (1016 seconds) and had zero FTV interference

Smooth: 1016s (100%)

Low FPS: 0s (0%)

Stuttering : 0s (0%)

I will try a flight later hopefully where I can set the OLOD on the ground to 200 then 20 past 10,000 ft and see what happens.

Could this inconsistency be caused because with the AutoFPS app I noticed the TLOD gets to my max setting of 300 rather quickly and at the same time the OLOD is being adjusted. Just trying to think of a logical reason as to what is happening. I want to observe what is actually going on with the sim rather than pay close attention to the numbers from CapFrameX

 

1 hour ago, RJC68 said:

After the last capture I did another 15 minutes and this time left the OLOD on 10 but turned off the auto feature the results in CapFrame X were back to what I was seeing previously. Next I rebooted my PC and fired everything up again and this time left the OLOD set at 200 and the auto feature turned off ran another CapFrameX capture for just over 15 minutes (1016 seconds) and had zero FTV interference

Which OLOD value are you referring to? OLOD base, OLOD top, both? Also, when you say you had the auto feature turned off, do you mean you had OLOD base and top both set to 200, Custom Auto OLOD unchecked or Use Expert Options unchecked?

The way it is currently coded only the first (setting OLOD base and top to the same value) actually turns off the auto feature entirely. The other two currently use a preset Auto OLOD that I have chosen (MSFS current OLOD setting for OLOD base @ 2000 ft and 20% of OLOD base for OLOD top at 10000 ft).

Until such time as we can narrow down what is causing these new stutters, I am very much leaning towards not having any auto OLOD working unless the user explicitly choses to do so under expert settings ie. Custom Auto OLOD would be renamed to be Auto OLOD.

BTW, thanks for doing these test flights for me. This sort of feedback is invaluable for shaping new features like Auto OLOD!

Edited February 28, 20242 yr by Reset XPDR

17 hours ago, Reset XPDR said:

In any case, the fix for you should be to go to C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator and rename the UserCfg.opt file there to something like UserCfg.opt.bak and see if that fixes it.

YES!  That's exactly what it was. I renamed it per your guidance and Auto_FPS now shows DX12 as it should. 

I think I caused that when I was running another installer (for the Stripr app) and accidently clicked on the Steam option.  I think the installer choked (rightfully so) and I ended up having to kill it with Task Manager.  That's the only thing I can come up with.

Just did another test flight and Auto_FPS is running great.  Thanks again for the awesome app, and the help!

 

1 hour ago, Reset XPDR said:

Which OLOD value are you referring to? OLOD base, OLOD top,

What I did was once the OLOD top has reached its value (10 in my case) I then unchecked the auto olod option then started the CapFrameX capture after I had recorded deviations in the same session prior to doing this  

 

1 hour ago, Reset XPDR said:

Also, when you say you had the auto feature turned off, do you mean you had OLOD base and top both set to 200, Custom Auto OLOD unchecked or Use Expert Options unchecked?

Yes when I did the final test with the latest 4.1 I made sure my OLOD was set to 200 in the sim and unchecked the Auto OLOD option so basically just TLOD was being used. The variations I saw I CapFrameX were pretty minute but it did show something was going on and in certain situations like is saw at FlyTampa CYYZ and the surrounding photogrammetry this morning the effects were worse. 
 

Hope this makes sense 

Edited February 28, 20242 yr by RJC68

7 minutes ago, RJC68 said:

Yes when I did the final test with the latest 4.1 I made sure my OLOD was set to 200 in the sim and unchecked the Auto OLOD option so basically just TLOD was being used.

No, it wasn't just using TLOD like that as it was still in auto OLOD mode, just with default settings I had chosen as described here: 

1 hour ago, Reset XPDR said:

The way it is currently coded only the first (setting OLOD base and top to the same value) actually turns off the auto feature entirely. The other two currently use a preset Auto OLOD that I have chosen (MSFS current OLOD setting for OLOD base @ 2000 ft and 20% of OLOD base for OLOD top at 10000 ft).

In any case, for this next version I have decided to make Auto OLOD only function when you have that Auto OLOD checkbox checked, otherwise it will be off entirely because it even confused you and you know what you're doing! In fact I have just finished coding up this change and will drop a new test version with this change shortly.

Edited February 28, 20242 yr by Reset XPDR

5 minutes ago, Reset XPDR said:

n any case, for this next version I have decided to make Auto OLOD only function when you have that Auto OLOD checkbox checked, otherwise it will be off entirely because it even confused you and you know what you're doing! In fact I have just finished coding up this change and will drop a new test version with this change shortly

Sorry my bad I did completely misunderstand how it worked, it’s been a long day lol

I will gladly give the new version a go but it won’t be until tomorrow afternoon Toronto time. 

Edited February 28, 20242 yr by RJC68

5 minutes ago, RJC68 said:

Sorry my bad I did completely misunderstand how it worked, it’s been a long day lol

I will gladly give the new version a go but it won’t be until tomorrow afternoon Toronto time. 

No, not your bad, I just did something that I thought would be clever but ended up confusing everyone with its cleverness, so not so clever after all. 😆Again, thanks for your input on this. It is much appreciated!

Edited February 28, 20242 yr by Reset XPDR

1 minute ago, Reset XPDR said:

No, not your bad, I just did something that I thought would be clever but ended up confusing everyone with its cleverness, so not so clever after all. 😆Again, thanks for your input on this. It is much appreciated!

You’re very welcome my friend, you’ve done so much for the community and if I can help in any way to make your app even better than it already is I’ll be happy too. 

New AutoFPS test version available here. If you experience any stutters with the new Auto OLOD function enabled, try disabling it completely by unchecking Auto OLOD and let me know the outcome.

New test version 28Feb240210Z:

• Changed Auto OLOD to only be enabled if the (renamed) Auto OLOD checkbox is selected, otherwise MSFS will be set to use the fixed OLOD value that MSFS was originally set to. This is due to confusion over whether Auto OLOD was being used or not and because some test users are experiencing stutters with this new feature so it is now best to make it completely optional and disabled by default at this time.
• Changed TLOD Min on Ground/Landing logic to have locking primed at 1000 ft above the locking altitude, which has increased from 1000 ft to 2000 ft to further stabilise TLOD for the final approach phase, and to then lock below 2000 ft to only allow TLOD reductions towards TLOD Min from then on until crossing 500 ft when the lock will be lifted.
• Added OLOD parameters to the list of parameters reported with the test Log Sim Values option enabled.

Edited February 28, 20242 yr by Reset XPDR

Hi again,

While trying to get Autostart setup (MS Store version), I see that I do not have an EXE.xml file at: 
C:\Users\Michael\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\
I guess I never had an add-on that needed to create one.

I'd like to create one and see if that will clear the way for the Autostart feature to work.  I have Notepad++ (encoding set to ANSI with the Character Set "Windows-1252".  I just need the text to copy and paste.  If you would post it here I'd surely appreciate it.  

Thank you!

2 hours ago, Mike7777 said:

Hi again,

While trying to get Autostart setup (MS Store version), I see that I do not have an EXE.xml file at: 
C:\Users\Michael\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\
I guess I never had an add-on that needed to create one.

I'd like to create one and see if that will clear the way for the Autostart feature to work.  I have Notepad++ (encoding set to ANSI with the Character Set "Windows-1252".  I just need the text to copy and paste.  If you would post it here I'd surely appreciate it.  

Thank you!

Here's a template of the content of mine, where you should just have to put in <username>:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>EXE.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Name>MSFS2020_AutoFPS</Name>

    <Path>C:\Users\<username>\AppData\Roaming\MSFS2020_AutoFPS\bin\MSFS2020_AutoFPS.exe</Path>

  </Launch.Addon>

</SimBase.Document>

FYI everyone, I've updated the AutoFPS readme for the umpteenth time which you can view here, but this time it contains a "Which app should I use? DynamicLOD_ResetEdition or AutoFPS"  section near the top. I'd post the content here for quick reference but the Avsim forum's autobots don't like it for some reason.

Also, I've managed to get "app window on top" functionality working on my latest test version and will be in the next release version. It is more handy than I thought it would be, especially for those using FG as they can overlay the app over MSFS and see their real FG for once, yay!

Edited February 28, 20242 yr by Reset XPDR

8 hours ago, Reset XPDR said:

New AutoFPS test version available here.

I tested it on an A300 flight from EDDM to LIML. Heavy clouds and I used AI traffic (FSLTL). Everything was silky-smooth all the way! 

8 hours ago, Reset XPDR said:

Changed TLOD Min on Ground/Landing logic to have locking primed at 1000 ft above the locking altitude, which has increased from 1000 ft to 2000 ft to further stabilise TLOD for the final approach phase, and to then lock below 2000 ft to only allow TLOD reductions towards TLOD Min from then on until crossing 500 ft when the lock will be lifted.

Not sure if I understand this 100%. But what I experienced on final was that TLOD was still above minimum below 1000ft AGL. In previous versions TLOD would reach minimum at 1000ft AGL (IIRC). I had set TLOD min to 100 and max 600. I didn't have time to take a screenshot of the app (too busy flying the plane!), but I'm pretty sure TLOD was 162 below 1000ft. At the gate now, and TLOD is 100...

Based on your description above, it seems that it worked as intended if I understand correctly. Does the TLOD decrease until 500ft now and then lock?

This is a screenshot from descent (AGL 5475):

2 hours ago, Reset XPDR said:

Also, I've managed to get "app window on top" functionality working on my latest test version and will be in the next release version. It is more handy than I thought it would be, especially for those using FG as they can overlay the app over MSFS and see their real FG for once, yay!

Excellent work! 😄 

Edited February 28, 20242 yr by Cpt_Piett