54 minutes ago, Reset XPDR said:

A quick teaser of the final addition I will likely make to AutoFPS 0.4.2 that I mentioned a few weeks ago here, to bring true auto FPS to the MSFS world. If this works, it will change the app from "set and forget" to just "start it up" - no setting required! 😄

 

Very interesting! If it's as great a change as your prior version, allowing TLODmin to be higher if there's room, it'll be great. The latest version before the one you are teasing is FANTASTIC (Test Version 08Mar240150Z)! Even the Expert mode seems to run better.

I flew in low circuits around KJFK with tons of traffic (almost 200 planes) getting 45-60 FPS (with FG) most of the time, dipping into the high 30s when I was looking at all the planes at the terminals as I overflew them (TLOD 100 and OLOD 200 by the automation, as my normal OLOD is 200).

I am going to be leaving it on the non-Expert mode for now, and only enable Expert when I feel I am going to have a really easy flight resource-wise.

Here's a scenario for you guys with the most powerful machines and running the sim in 4k to test. Try this scenario and tell me what kind of fps you get while parked at the gate with the fenix a320 in "ready" state.

1. Inibuilds KJFK
2. FSLTL AI Traffic (base and injector)
3. GSX Pro
4. FS2Crew Fenix A320
5. FS2Crew RAAS
6. Samscane New York City
7. REX Accuseason
8. REX Airport Textures
9. We Love VFR by PUF
10. GAIST Ultra v4.0 with north american caribbean routes enabled
11. seafront vessels core
12. seafront vessels ai
13. seafront global shipping

3 hours ago, captain420 said:

Here's a scenario for you guys with the most powerful machines

That collection of addons while most likely bring my 12900K to it's knees. My guess is that most of these are mainthread-dependent. So having a 4090 won't help much as I'll be mainthread-limited. Which I am 90% of the time anyway. Well, FG will help though, except when native fps are too low for FG to generate AI-images in between native images (see below).

But as I happen to have almost all of these addons, I'll give it a shot! I'm interested to see/hear/smell how much my P-cores will suffer 🙃

Ok, so I loaded the sim with the following:

1. Inibuilds KJFK
2. FSLTL AI Traffic (base and injector)
3. AIG models, flight plans and injector (AIGTC)
4. GSX Pro
5. Fenix A320 V2
6. REX Accuseason
7. REX Airport Textures
8. We Love VFR by PUF
9. GAIST Ultra v4.0 with north american caribbean routes enabled
10. seafront vessels core

Fenix parked at gate, panel status ready, drone mode, no panning. 

FSLTL off: 

FSLTL on: 

AIGTC on:

Without FSLTL: avg fps 71.9     smooth 100%   FTV <2ms 99.2%

With FSLTL:       avg fps 70       smooth 100%   FTV <2ms 92.53%

With AIGTC:       avg fps 50.9   smooth 99.8%   FTV <2ms 65.11%

I was surprised that FSLTL didn't hit harder. Although it's night in NY now and FSLTL have "live" flight plans. This explains partly why AIG hit MUCH harder as it's based on offline flight plans (local time where I'm at i.e. my Windows system time is 11AM). Also, I had max activity set in AIGTC. So it's more like an apples and oranges comparison. It does show however how hard AI traffic can hit at max. 

Panning around makes things much worse with 100% AI traffic. There's simply no overhead left as the poor mainthread is working overtime. With a still drone view above the airport, the mainthread is red-glowing at 44ms (!), native fps 22 (!!) and FG-fps 45). This is an excellent example of the appearance of @Noel's dreaded FG-related flickering (which I call artifacts), and it's quite distracting. FG is recommended by Nvidia with native 60 fps and above for best results. In the AIGTC scenario - native FPS was well below 30. 

Conclusion: AutoFPS handles the scenario très excellemment! If, and only if, there's not a huge bottleneck like 100% AI traffic. Avg fps would of course have been even closer to my target fps if I had set TLOD lower. 

Edited March 8, 20242 yr by Cpt_Piett
downsized images from 5461x2880 to 2731x1440 for faster loading

3 hours ago, Reset XPDR said:

A quick teaser of the final addition I will likely make to AutoFPS 0.4.2 that I mentioned a few weeks ago here, to bring true auto FPS to the MSFS world. If this works, it will change the app from "set and forget" to just "start it up" - no setting required! 😄

 

May I ask you how you determine what the target fps for each setup is ?

One person wants a minimum of 30 and the next person 40 or 50 or 60.

In my case I use FG icw no Vsync. Pc 1 has 2x 4K displays. and Pc 2 has 1x 4K display.

Pc 1 only has a working FG on the main MSFS screen , so the extra view has half of the fps …

Great work !

1 hour ago, GSalden said:

May I ask you how you determine what the target fps for each setup is ?

One person wants a minimum of 30 and the next person 40 or 50 or 60.

In my case I use FG icw no Vsync. Pc 1 has 2x 4K displays. and Pc 2 has 1x 4K display.

Pc 1 only has a working FG on the main MSFS screen , so the extra view has half of the fps …

Great work !

This feature is being created with the non-expert user in mind, particularly those who may not have an idea of what FPS to choose but also, if it works good enough, those who want the app to tune to their current flight scenario using their existing MSFS settings as the starting point. It may not even work for those of you with multi monitor or multi computer setups but it would be worth someone like yourself to try it and let me know how it fares, one way or another. And for anyone that wants total control over their FPS target, simply don't use it.

The basic concept is that in non-expert setting mode and on the ground after just starting the flight, the app takes your existing MSFS settings as the starting point and sets you up with a TLOD Min of 50% of the existing setting. After an appropriate FPS settling time, the app will monitor your FPS over the calibration time and then set your target FPS to somewhere around the average over the calibration time, maybe slightly higher.

The theory is that on the ground with TLOD Min you usually get your lowest FPS. Since your performance usually improves as you climb up and away from complex scenery, the target FPS will be breached and TLOD can automatically increase as it currently does. While the app already does this when you set a suitable target FPS in the first place, having a fixed target FPS it doesn't really cover the variety of flights you may do. One flight you might be doing an IFR flight out of KLAX in heavy weather and the next you hop in your favourite GA aircraft and go buzzing through the mountains, so having the option to auto tune your FPS based on scenario may help you get more out of the experience without having to change anything.

Anyway, it is something that I have wanted to try for a while as I like to change settings as little as possible between flights, but I understand others may not like it and if most don't like it I will just take it out and leave it in my personal test build. Let's see what I can throw together first.

 

 

@Reset XPDR

Thanks for explaining. Up to now I am using your Adaptive LOD and it certainly works. 

However, I will absolutely try the Auto FPS version. 

Auto target fps is only available in VR mode?

Edited March 8, 20242 yr by grandfred29

9 minutes ago, grandfred29 said:

Auto target fps is only available in VR mode?

It's available in all graphics modes. I just happened to be in VR at the time I took the screenshot.

5 hours ago, captain420 said:

Here's a scenario for you guys with the most powerful machines and running the sim in 4k to test. Try this scenario and tell me what kind of fps you get while parked at the gate with the fenix a320 in "ready" state.

1. Inibuilds KJFK
2. FSLTL AI Traffic (base and injector)
3. GSX Pro
4. FS2Crew Fenix A320
5. FS2Crew RAAS
6. Samscane New York City
7. REX Accuseason
8. REX Airport Textures
9. We Love VFR by PUF
10. GAIST Ultra v4.0 with north american caribbean routes enabled
11. seafront vessels core
12. seafront vessels ai
13. seafront global shipping

My machine is overheating just reading this scenario😄

I did do a flight out of JFK a few days ago with the Fenix. I was surprised how poor my performance was at the gate (JetBlue terminal facing west)...only about 17 fps.  I have the same addons you have minus the Seafront packages and FS2C.  I also had my KEWR and KLGA addons disabled. JFK has always been a tough area for me and I generally avoid it. FSLTL (or any AI traffic) is the main culprit I think.  When I turned AI traffic off I was back up to 30fps.  I have not tried using AutoFPS yet at JFK.  My first flight while using AutoFPS was last night and I did in fact fly into KEWR (disabled KJFK).  It seemed to work pretty well even though I could not keep 30 fps but only dipped to about 26-27.  My TLOD was set on 70. This was also with FSLTL (mostly parked traffic @ MAX 40 and 20 IFR).

Edited March 8, 20242 yr by Flic1

5 hours ago, Cpt_Piett said:

Fenix parked at gate, panel status ready, drone mode, no panning. 

You should seriously consider undervolting your 4090... Up to 390 watts? Seriously? I bet you could go down to 300W max with nothing more than some percent performance penalty... https://www.techpowerup.com/301649/nvidia-geforce-rtx-4090-with-nearly-half-its-power-limit-and-undervolting-loses-just-8-performance

5 hours ago, captain420 said:

Here's a scenario for you guys with the most powerful machines and running the sim in 4k to test. Try this scenario and tell me what kind of fps you get while parked at the gate with the fenix a320 in "ready" state.

1. Inibuilds KJFK
2. FSLTL AI Traffic (base and injector)
3. GSX Pro
4. FS2Crew Fenix A320
5. FS2Crew RAAS
6. Samscane New York City
7. REX Accuseason
8. REX Airport Textures
9. We Love VFR by PUF
10. GAIST Ultra v4.0 with north american caribbean routes enabled
11. seafront vessels core
12. seafront vessels ai
13. seafront global shipping

My example right above yours was with this scenario, largely. I time shifted to midday so that I got lots of realtime traffic through PSXT/RT (nearly 200 planes, as mentioned).

I was also flying the BKSQ Bonanza so that I could loiter at low altitude in tight circles around the terminals (ie - a worst case scenario). I have almost every addon you mention active, but I do believe this: as bad as it could get, Auto FPS will do a great job delivery the best smoothness I could get.

1 minute ago, AnkH said:

You should seriously consider undervolting your 4090... Up to 390 watts? Seriously? I bet you could go down to 300W max with nothing more than some percent performance penalty... https://www.techpowerup.com/301649/nvidia-geforce-rtx-4090-with-nearly-half-its-power-limit-and-undervolting-loses-just-8-performance

I have done this exactly as well. My card is much happier. 

3 minutes ago, AnkH said:

You should seriously consider undervolting your 4090... Up to 390 watts? Seriously? I bet you could go down to 300W max with nothing more than some percent performance penalty... https://www.techpowerup.com/301649/nvidia-geforce-rtx-4090-with-nearly-half-its-power-limit-and-undervolting-loses-just-8-performance

It is a tad power/hungry, yes. I’m feeding it with a 850W PSU (the 12900KF “only” gets 750W). To be honest I’ve never tried undervolting, although I’ve heard it mention a number of times. I’ll look into the article, although I’m much more likely to mess with the registry editor, disabling SysMain and NDU, as well as disabling “Ring to Core offset (Down bin)”

54 minutes ago, Flic1 said:

It seemed to work pretty well even though I could not keep 30 fps but only dipped to about 26-27.  My TLOD was set on 70. This was also with FSLTL (mostly parked traffic @ MAX 40 and 20 IFR).

And this is with a very decent GPU&CPU.

9 hours ago, Reset XPDR said:

A quick teaser of the final addition I will likely make to AutoFPS 0.4.2 that I mentioned a few weeks ago here, to bring true auto FPS to the MSFS world. If this works, it will change the app from "set and forget" to just "start it up" - no setting required! 😄

 

This one is turning out to be a bit harder than I thought to implement, with many tentacles between code modules. I've got a working prototype but it is not even polished enough to put out for testing, so I'll leave that for tomorrow after a good night's sleep and a group flight to see how it goes outside a test environment. It's looking reasonably promising and worst case if it does go flippy it can be easily disabled by unchecking Auto Target FPS and everything goes back to normal.

Oh and extra test logging for the test versions has been taken off the UI because it was taking up valuable real estate and most users seem to have it on anyway, so in future test versions it will be hard coded on. G'night everyone.