That's gotta be a lot of fun on a 77". Magical scenery.

22 minutes ago, Cpt_Piett said:

Getting very nice results with latest test build! Just finished a 450nm GA flight in Northern Norway, cruise 11,000ft, landed at several airports along the way. Auto target FPS from start to finish, no tampering with the structure to make it more docile settings, just set-and forget.

Key highlights:

• FPS 60-90
• TLOD 300-1000
• At some airports I even got TLOD 600 on ground

I really do appreciate the higher TLODs latest build gives me. IMHO it does make a difference when doing scenic flights. My country newer looked this good in a sim 😁

100% agree! 💯 

Wow, tLOD 300-1000 ?  
I guess you won’t see the difference between 300 en 1000 but it surely are impressive numbers ..

44 minutes ago, GSalden said:

Wow, tLOD 300-1000 ?  
I guess you won’t see the difference between 300 en 1000 but it surely are impressive numbers ..

I don't have these settings for bragging rights 😉 And I do see a considerable difference between 300 and 600 up at higher altitudes. More of the terrain is visible in the distance. Especially nice in mountaneous regions. Above 600 - not so sure. 

...

Just departed in the Fenix (again, remote Norwegian airport). Note: this is not criticism, just an observation. I know I was one of those who complained about noted that FPS was uneccesarily high in previous build. 

On ENST ground, I got very decent FPS - 89 with TLOD 600 OLOD 1000. Climbing 5600ft towards FL350 I got FPS 53, TLOD 1079, OLOD 692. 

Although I've been preaching high TLODs, FPS 53 is a tad low for frame generation and G-Sync to work properly. G-Sync at 60 or below = screen tearing. FG-FPS below 60 = choppy / FG-induced artifacts. It's only really an issue when panning around the cockpit though. Just looking straight ahead and there's no perceived choppiness. 

EDIT: I could just reduce TLOD to a more reasonable 400 in usercfg.opt 🙂 Forgot about that! It would make sense when flying airliners, which are more "FPS-heavy" than most GA. Hence - higher FPS is more important than higher TLODs. 

Update: At cruise FL350 and status line says "FPS priority". FG-FPS 54, TLOD 733, OLOD 200. 

Edited March 11, 20242 yr by Cpt_Piett

4 hours ago, Cpt_Piett said:

These were the droids values I was aiming for with non-expert mode

😄

4 hours ago, Cpt_Piett said:

I've set TLOD to 600 in usercfg.opt and OLOD 200 (MSFS menu), clouds ultra. Frame generation on, FPS unlocked. 

On the ground on a remote, icy and probably godforsaken airport very close to the Arctic Circle, I got: FG-FPS 71, TLOD 600, OLOD 1000

Cruising at 11,000ft: FG-FPS 62, TLOD 1185, OLOD 200

If you have set OLOD at 200 in MSFS menu as you state here, you should have been getting 200 on the ground in non-expert mode, not 1000. Were you in non-expert mode at this time?

4 hours ago, Cpt_Piett said:

At cruise altitude, I notice that TLOD changes ever so slightly. Also, the status line continously (does Chrome has an auto-correct feature?) switches between TLOD+ 600 Priority and FPS Priority. Is this working as intended? Honest question, no critisicm (spelling, aargh). 

TLOD changing ever so slightly when near your FPS target is new, yes. Was that acceptable or did it cause some issue?

Continuous switching between TLOD priority and FPS priority usually means you are regularly crossing the altitude threshold between them. If you have TLOD + 600 showing, this altitude threshold calculates to be 9000 ft AGL. The reason this is so high is because your default TLOD is so (ridiculously😆) high - it is only 2667 ft with TLOD 100. Is this the AGL you were around when it was happening?

5 hours ago, Cpt_Piett said:

Occasionally status will switch to TLOD+ 300 Priority. Not really sure what this terminology means. I don't need to know everything though, however I tend to me quite inqusitive!

I think you mean TLOD 300, not TLOD+ 300. In any case, this is in the release notes from a few days ago, which I admit is easy to miss in my recent sea of creativity 🤪, which says:

• Made status line items more concise. TLOD Min nomenclature changed to show the actual TLOD Min value being prioritised and + means extra TLOD Min is active.

5 hours ago, DAD said:

I get an error message when installing the test build: Exception 'System.IO.FileNotFoundException' during AutoStart.exe. Anybody else? Happy start it manually though (which works and is the most important thing)

This is covered in the readme:

• If you get an exception 'System.IO.DirectoryNotFoundException' during AutoStartExe when trying to install with the autostart option for MSFS, it usually means that your MSFS installation is missing the required EXE.xml file in which to place the autostart entry. To resolve, you need to go to your MSFS root user directory (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") and manually create an EXE.xml file and save it there. You can use the following EXE.xml template, inserting your Windows username where shown:

<?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>

1 hour ago, Andy2640 said:

Hi Guys and gals,

I'm on a 78003xd + 4090 + quest 3 +32gb.

I have been following this thread with deep interest.

As a user of a quest 3 VR HMD, I have been wondering how i can get the auto fps app to work.

Well, with a locked 36fps, with ASW on adaptive, and ultra and high settings in sim, and 1.4 oculus super-sampling, I seem to have had some real decent success so far.  I dont know how it was working exactly, because my fps never budges from an alternating 36 or 37 fps. The 37fps may be an inaccurate number been shown from "rivatuner", but not fully sure. My logic is that if that fps number is true, and 36 and 37 are being cycled intermittently, then perhaps the auto fps logic is using this "tiny" variation and providing some benefit.  Bit baffled at this point, but i havnt been able to get enough time dedicated to it thus far.

Two days ago, is when I began simming with auto-fps, and at first it seemed to work a charm. Rising from base 75 TLOD from 1000ft, and gently rising up to a max of 350 in the DC.  Amazing. Upon landing it was as smooth as peanut butter. 

- That was with 34 fps target and at 5% deviency.  Looking back, i still dont fully understand how it was working.

 

Then I seen someone mention a 10% target. This didn't seem to work as well, so i reverted back to 5%.

 

Got to try again tonight, but I hope this continues to provide good results,  because my first few flights with auto-fps were mind blowing.  At one stage i was taxi'ing around Heathrow with full live traffic, and it was stunning, truly stunning. To do this before, I would really have to lower settings and also lower resolution, which never made it worth it.

 

Like other posters, I cant seem to understand how the TLOD lowers itself. After all, the fps never breaks lock of 36. If it ever does, its goodnight Vienna. 

 

Also, if it doesn't work well again like the first few flights, my thinking is, i can at least make use of the "on ground/below 1000ft" TLOD minimums. Then, just keep my max TLOD at my usual in-sim values. That way, i get great airport experiences and a normal flying experience in the air. My thinking is that, because of the 36  fps lock (half of 72hz) , and the auto-fps logic not been able to take advantage of a decreasing fps, at least it will detect my high fps overall, and increase from the tarmac upwards, essentially taking me to my max TLOD in the air.  Then, upon landing, it reduces automatically when i hit the tarmac again. So for me, even if it doesn't fully work with fps locks (VR headsets), i can at least have a much better experience then with no auto-fps app at all.

 

Does this make sense to anyone else?

To be honest, I'm impressed this app is working at all if you are setting your target FPS close to your ASW, as doing so usually causes conflict with the app's automation engine, unless you are using the latest test version in which I have actually bypassed the FPS tolerance band and the app is continuously adjusting. If that's the case, it may be serendipity (a fortunate discovery) that this now works with frame rate caps. Thanks for the feedback.

2 minutes ago, Reset XPDR said:

If you have set OLOD at 200 in MSFS menu as you state here, you should have been getting 200 on the ground in non-expert mode, not 1000. Were you in non-expert mode at this time?

100% sure I wasn't. Been flying in full auto-mode the whole day, on latest build. Could I have set OLOD 1000 in usercfg.opt? Just checking now and it's ObjectsLoD LoDFactor 2.000000. I did notice something else though: Terrain LoDFactor 7.330000. 

5 minutes ago, Reset XPDR said:

TLOD changing ever so slightly when near your FPS target is new, yes. Was that acceptable or did it cause some issue?

Absolutely no issue at all. Just an observation 🙂

5 minutes ago, Reset XPDR said:

Continuous switching between TLOD priority and FPS priority usually means you are regularly crossing the altitude threshold between them. If you have TLOD + 600 showing, this altitude threshold calculates to be 9000 ft AGL. The reason this is so high is because your default TLOD is so (ridiculously😆) high - it is only 2667 ft with TLOD 100. Is this the AGL you were around when it was happening?

Thanks, that makes sense. Yeah, crazy TLOD in usercfg.opt, I know. It just reflects my habitual state of being a tad loopy 😉 

Log file from first departure: 

Quote

FPS: 40 TLOD: 553 OLOD: 928 AGL: 2748 FPM: 1804 Clouds: Ultra 

Around cruise 11,000ft it get's a bit interesting: 

Quote

FPS: 35 TLOD: 957 OLOD: 200 AGL: 10531 FPM: 1275 Clouds: Ultra 

Expert: False Mode: FG AutoTarget: False Target: 76 Tol: 5 TMin: 100 TMax: 600 CloudQ: False CRecovT: 120 Pause: True TMinGL: True TLODBAlt: 1000 MaxDescRate 1500 CustomOLOD: True OLODB: 200 OLODT: 20 OLODBAlt: 2000 OLODTAlt: 10000 
FPS: 30 TLOD: 882 OLOD: 200 AGL: 10699 FPM: 1006 Clouds: Ultra 
FPS: 30 TLOD: 792 OLOD: 200 AGL: 10819 FPM: 662 Clouds: Ultra 
Expert: False Mode: FG AutoTarget: False Target: 76 Tol: 5 TMin: 100 TMax: 600 CloudQ: False CRecovT: 120 Pause: True TMinGL: True TLODBAlt: 1000 MaxDescRate 1500 CustomOLOD: True OLODB: 200 OLODT: 20 OLODBAlt: 2000 OLODTAlt: 10000 
FPS: 82 TLOD: 712 OLOD: 200 AGL: 10895 FPM: 430 Clouds: Ultra 
FPS: 77 TLOD: 792 OLOD: 200 AGL: 10946 FPM: 282 Clouds: Ultra 
FPS: 72 TLOD: 772 OLOD: 200 AGL: 10979 FPM: 184 Clouds: Ultra 
FPS: 71 TLOD: 727 OLOD: 200 AGL: 11000 FPM: 113 Clouds: Ultra 
FPS: 65 TLOD: 672 OLOD: 200 AGL: 11012 FPM: 65 Clouds: Ultra 
FPS: 68 TLOD: 582 OLOD: 200 AGL: 11018 FPM: 30 Clouds: Ultra 
FPS: 83 TLOD: 577 OLOD: 200 AGL: 11021 FPM: 10 Clouds: Ultra 

...

11 minutes ago, Reset XPDR said:

I think you mean TLOD 300, not TLOD+ 300. In any case, this is in the release notes from a few days ago

To quote a fellow Fenix enthusiast 2 hrs ago: 

Quote

You know how it is. People are faster to ask questions on forums instead of reading manuals or changelogs...

 

17 minutes ago, Reset XPDR said:

This is covered in the readme

well, cough, thanks. better RTFM next time 😉

1 hour ago, El Diablito said:

That's gotta be a lot of fun on a 77". Magical scenery.

Finally another believer! THANK YOU! I've got nothing but scepticism re: my TLOD settings. I was even called stupid earlier today, which I didn't appreciate that much. 

I don't think that many people have been able to appreciate that I like tinkering and experimenting with settings. I'm inquisitive by nature. I'm on an eternal quest to figure out what's possible in this sim. TLOD 1800 is possible but not necessary. Likewise, FPS 180 (when OLED max refresh rate is 120Hz....). 

I hope that clears things up a bit for fellow enthusiasts reading this thread 🙂

4 minutes ago, Cpt_Piett said:

100% sure I wasn't. Been flying in full auto-mode the whole day, on latest build. Could I have set OLOD 1000 in usercfg.opt? Just checking now and it's ObjectsLoD LoDFactor 2.000000. I did notice something else though: Terrain LoDFactor 7.330000. 

Just to be clear, I define full auto mode as Use Expert Settings unchecked and Auto Target FPS checked.

Those numbers you are showing in your usercfg.opt file get multiplied by 100, so it is showing TLOD 733 and OLOD 200. You can still change your OLOD and TLOD in the MSFS settings menu when the app is running, as long as you are not in a flight - you have to be at the main menu.

33 minutes ago, Reset XPDR said:

Just to be clear, I define full auto mode as Use Expert Settings unchecked and Auto Target FPS checked.

Those numbers you are showing in your usercfg.opt file get multiplied by 100, so it is showing TLOD 733 and OLOD 200. 

Well, that's been my definition as well. To be perfectly clear: ever since updating to latest build, I've been in non-expert mode with auto target FPS enabled. Not once today have I disabled auto-TFPS or entered expert mode. Like you recommended us to do 🙂

I'll probably set TLOD 400 before doing my next Fenix flight. 

Not sure if it's interesting, but here's an edited log from 11,000ft descent to ground at ENRA (AGL 230). 

Quote

FPS: 25 TLOD: 1565 OLOD: 200 AGL: 10998 FPM: -2 Clouds: Ultra 
FPS: 50 TLOD: 1565 OLOD: 200 AGL: 10059 FPM: -2021 Clouds: Ultra 
FPS: 49 TLOD: 1565 OLOD: 222 AGL: 9756 FPM: -2018 Clouds: Ultra 
FPS: 49 TLOD: 1545 OLOD: 253 AGL: 9454 FPM: -2014 Clouds: Ultra 
FPS: 50 TLOD: 1526 OLOD: 283 AGL: 9154 FPM: -2011 Clouds: Ultra 
FPS: 24 TLOD: 1340 OLOD: 373 AGL: 8250 FPM: -2006 Clouds: Ultra 
FPS: 26 TLOD: 1209 OLOD: 494 AGL: 7045 FPM: -2004 Clouds: Ultra 
FPS: 71 TLOD: 1073 OLOD: 585 AGL: 6146 FPM: -2000 Clouds: Ultra 
FPS: 72 TLOD: 937 OLOD: 675 AGL: 5242 FPM: -2011 Clouds: Ultra 
FPS: 69 TLOD: 752 OLOD: 798 AGL: 4012 FPM: -114 Clouds: Ultra 
FPS: 54 TLOD: 623 OLOD: 885 AGL: 3131 FPM: -1465 Clouds: Ultra 
FPS: 50 TLOD: 463 OLOD: 991 AGL: 2069 FPM: -1435 Clouds: Ultra 
FPS: 53 TLOD: 420 OLOD: 1000 AGL: 1802 FPM: 10 Clouds: Ultra 
FPS: 50 TLOD: 405 OLOD: 1000 AGL: 1697 FPM: -729 Clouds: Ultra 
FPS: 50 TLOD: 387 OLOD: 1000 AGL: 1574 FPM: -868 Clouds: Ultra 
FPS: 50 TLOD: 366 OLOD: 1000 AGL: 1433 FPM: -970 Clouds: Ultra 
FPS: 50 TLOD: 341 OLOD: 1000 AGL: 1268 FPM: -1174 Clouds: Ultra 
FPS: 55 TLOD: 313 OLOD: 1000 AGL: 1083 FPM: -1253 Clouds: Ultra 
FPS: 51 TLOD: 300 OLOD: 1000 AGL: 908 FPM: -988 Clouds: Ultra 
FPS: 53 TLOD: 300 OLOD: 1000 AGL: 758 FPM: -836 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 654 FPM: -822 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 546 FPM: -610 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 449 FPM: -739 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 326 FPM: -838 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 196 FPM: -904 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 63 FPM: -784 Clouds: Ultra 
FPS: 50 TLOD: 300 OLOD: 1000 AGL: 4 FPM: 2 Clouds: Ultra 

...

33 minutes ago, Reset XPDR said:

You can still change your OLOD and TLOD in the MSFS settings menu when the app is running, as long as you are not in a flight - you have to be at the main menu.

You know, I'll do that just now. Well, I have to land first of course, so I'll just make a diversion. However - if I still have TLOD 600 set in usercfg.opt, I'm not sure I can change it to 400 in main menu. Please stand by. 

Edited March 11, 20242 yr by Cpt_Piett

There must be something wrong with my settings, as I am not achieving the desired results with the Auto FPS mode. If I select only that mode (full auto mode as you say) in a busy environment, I get my TLOD / 2 showing up, but it creates a situation where buzzing the terminals at the iniBuilds KJFK with >150 planes of PSXT traffic creates stuttering and FPS in the 45-55 range. My settings are TLOT/OLOD of 200/200 in the sim settings, and I seem to struggle a bit.

When I select Expert mode (and it seems to work with both Auto FPS selected as well as not selected - I will have to drill down deeper and see if there is an effective difference to that option being enable or not with Expert Mode also selected), I get much more fluid performance as well as the desired graphical performance. My expert settings are TLOD 50@50 with TLOD Min on ground handling checked, 2000 fpm descent and 600 TLOD Max. My OLOD settings are  600@1000 and 100@5000.

One question I had is that when I select Auto Target FPS, the Target PC FPS grays out, says "auto" and then changes to a grayed out number that seems to be within a FPS or two of the frame rate I had when I first selected auto. It does not seem to use the target FPS that was previously in that input box - which I guess is fine, since it's supposed to be fully automatic. However, I don't know if it's trying to maintain the number that it puts in there?

6 minutes ago, Cpt_Piett said:

Well, that's been my definition as well. To be perfectly clear: ever since updating to latest build, I've been in non-expert mode with auto target FPS enabled. Not once today have I disabled auto-TFPS or entered expert mode. Like you recommended us to do 🙂

I'll probably set TLOD 400 before doing my next Fenix flight. 

Not sure if it's interesting, but here's an edited log from 11,000ft descent to ground at ENRA (AGL 230). 

 

There's some weird FPS drops in that table. Was that noticeably happening in your descent?

9 minutes ago, Reset XPDR said:

There's some weird FPS drops in that table. Was that noticeably happening in your descent?

Nope, performance was good for the whole flight. Didn't notice any stuttering. Perhaps G-Sync took care of it. 

16 minutes ago, mmcmah said:

There must be something wrong with my settings, as I am not achieving the desired results with the Auto FPS mode. If I select only that mode (full auto mode as you say) in a busy environment, I get my TLOD / 2 showing up, but it creates a situation where buzzing the terminals at the iniBuilds KJFK with >150 planes of PSXT traffic creates stuttering and FPS in the 45-55 range. My settings are TLOT/OLOD of 200/200 in the sim settings, and I seem to struggle a bit.

When I select Expert mode (and it seems to work with both Auto FPS selected as well as not selected - I will have to drill down deeper and see if there is an effective difference to that option being enable or not with Expert Mode also selected), I get much more fluid performance as well as the desired graphical performance. My expert settings are TLOD 50@50 with TLOD Min on ground handling checked, 2000 fpm descent and 600 TLOD Max. My OLOD settings are  600@1000 and 100@5000.

I'd say it is your MSFS default TLOD of 200 causing the issue because in non-expert mode it will choose half of that as the lowest TLOD Min ie. 100 and that is double what you are manually setting in expert mode. I suggest you try setting TLOD 100 in the MSFS settings menu and not in a flight (otherwise the setting won't stick) and give non-expert mode another try.

16 minutes ago, mmcmah said:

One question I had is that when I select Auto Target FPS, the Target PC FPS grays out, says "auto" and then changes to a grayed out number that seems to be within a FPS or two of the frame rate I had when I first selected auto. It does not seem to use the target FPS that was previously in that input box - which I guess is fine, since it's supposed to be fully automatic. However, I don't know if it's trying to maintain the number that it puts in there?

That's correct. Once you enable Auto Target FPS it ignores any previously set target FPS and on the ground uses 95% of your current FPS as the target (down to 85% above 3000 ft). It is greyed out because you are no longer in control of it, although you can reset it at any time by toggling Auto Targer FPS off then back on again if you want a quick re-calibration.

16 minutes ago, mmcmah said:

it creates a situation where buzzing the terminals at the iniBuilds KJFK with >150 planes of PSXT traffic creates stuttering and FPS in the 45-55 range.

BTW,  I hope you realise that doing things like this you are asking for stuttering issues. 😄

Edited March 11, 20242 yr by Reset XPDR