I was just wondering: Even though I have the headroom, is the TLOD lower here (screenshot) due to the AGL? I notice that the status line says "TLOD+ Pri" - does that mean I'm below the "transition altitude"? After landing I got 120+ FPS with a TLOD of 240 (it's a remote area). Then after a seeking process, I got "TLOD+ Pri 400" with FPS around 100. 

Just trying to understand a bit more in-depth how things work. 

Readme:

Quote

On descent through the calculated TLOD priority mode transition altitude, TLOD Min + will lock until landed to give the app time to reduce TLOD to Min at a moderate rate

Again from the readme:

Quote

Avoid rapidly changing views or panning your external view too quickly, especially initially as un-cached scenery loads in, as you will induce temporary FPS drops that may trigger an unnecessary TLOD Min + reduction

Should I avoid quick panning in general? I'm not using VR or head tracking, so I use custom views to look around the cockpit or look right/left. Changing between views is pretty sudden. 

 

Edited September 22, 20241 yr by Cpt_Piett

Hi, I´m relatively new to AutoFPS and I have what might be a dumb question. When setting the target FPS, and if I´m using FrameGen, does the set FPS have to be with or without FG. For example: 30fps, would be 30 fps natively or 30fps with FG on??? For now I´ve let the program set the target fps and worked fine, but it doesn´t entirelly remove the stutters on final/landing , but I that´s, I think, more on my side due to limited 6gb of VRAM (that´s why I have to have rolling cache on, land on the airport first, save the data on the RC and then fly the next day without rellying on streaming services so much)

1 minute ago, litos_97 said:

When setting the target FPS, and if I´m using FrameGen, does the set FPS have to be with or without FG.

With FG.When FG is active, you will see “Target FG Active FPS” (like in the screenshot I posted above).

55 minutes ago, Cpt_Piett said:

With FG.When FG is active, you will see “Target FG Active FPS” (like in the screenshot I posted above).

Thank you very much, but I think I´ll stick to "Auto Target FPS" for now. I don´t think my pc is good enought to set it to something like 50fps, so I´ll just let AutoFPS be the judge.

1 hour ago, Cpt_Piett said:

I was just wondering: Even though I have the headroom, is the TLOD lower here (screenshot) due to the AGL? I notice that the status line says "TLOD+ Pri" - does that mean I'm below the "transition altitude"? After landing I got 120+ FPS with a TLOD of 240 (it's a remote area). Then after a seeking process, I got "TLOD+ Pri 400" with FPS around 100. 

Just trying to understand a bit more in-depth how things work. 

Yes you have descended below the priority "transition altitude" and TLOD Min has locked in as described in the readme:

• While in FPS priority mode, TLOD Min + will calculate to be 50% of the lower of either whatever TLOD you are currently getting or TLOD Max without TLOD Mtn Amt, but no lower than TLOD Min.

Since your TLOD Max is 400, 50% of that is 200 and you are getting an extra 40 because your FPS is much higher than the target (which I probably need to describe in the readme), so a TLOD Min + of 240 sounds about right.

The reason it is lower than what it recalibrated to on the ground is that the app assume you are descending in to a worst case scenery complexity increase, ie. a busy airport, which is why the TLOD Min + is so conservative. Thinking a bit more about this now, I could leave the IFR profile being this aggressive a reduction, because a busy airport could be reasonably expected, but I could make the reduction a little less, say 25% for the VFR profile as a busy airport being encountered is unlikely. This would have given you a landing TLOD for your scenario of around 320. What do you think?

BTW, I will probably be rolling out a .1 update to fix two other minor issues that have come up since release, any anything else that comes up, so including this change won't be a big deal.

 

2 hours ago, Cpt_Piett said:

Should I avoid quick panning in general? I'm not using VR or head tracking, so I use custom views to look around the cockpit or look right/left. Changing between views is pretty sudden. 

Snap view changes don't seem to be as bad with FPS dips, so they're probably OK as long as you aren't doing many in quick succession. If you watch your FPS counter as you are view changing, you'll get an idea of what makes it hiccup the most. By all means change view how and when you like, I just want the user to be aware that there are consequences to TLOD Min + if you doing so causes FPS to dip for a while.

6 minutes ago, Reset XPDR said:

Thinking a bit more about this now, I could leave the IFR profile being this aggressive a reduction, because a busy airport could be reasonably expected, but I could make the reduction a little less, say 25% for the VFR profile as a busy airport being encountered is unlikely. This would have given you a landing TLOD for your scenario of around 320. What do you think?

I think that's a good idea. For some reason I'm still on IFR even though I've mainly been flying GA in remote areas lately. It doesn't make any sense, it's probably just habit. 

But yeah, IFR would probably imply some sort of airliner flying, and usually the arrival airport will be a bit more complex than a GA airfield. And I guess it'll be in an urban area as well. 

Edited September 22, 20241 yr by Cpt_Piett

Saw this today talking about VR optimisations in MSFS 2024:

VR users are also bound to have a better experience in MSFS 2024. While this topic was barely touched, we learned that one of the biggest things VR people will enjoy is an automatically adjusting detail system. You can set a target FPS, and the system will automatically adjust the detail to maintain that frame rate. This should help provide a very smooth VR experience. It’s quite similar to existing mods for MSFS such as Auto FPS.

Looks like I can go into retirement soon! 😄

Oh that's good, about time they took VR seriously with related features.

Although don't retire just yet, who knows you might still do a better job than what they've achieved 😉

5 hours ago, MarcG said:

Although don't retire just yet, who knows you might still do a better job than what they've achieved 😉

I agree! So many great features in AutoFPS that I doubt will be available in the new sim.

But it’s good that VR users get some tools to enhance the experience. I’m guessing this might be available for non-VR users as well.

12 hours ago, Reset XPDR said:

Saw this today talking about VR optimisations in MSFS 2024:

VR users are also bound to have a better experience in MSFS 2024. While this topic was barely touched, we learned that one of the biggest things VR people will enjoy is an automatically adjusting detail system. You can set a target FPS, and the system will automatically adjust the detail to maintain that frame rate. This should help provide a very smooth VR experience. It’s quite similar to existing mods for MSFS such as Auto FPS.

Looks like I can go into retirement soon! 😄

Finally they seems to have learned from the most clever Guy 😆

17 hours ago, Reset XPDR said:

Looks like I can go into retirement soon! 😄

Your efforts are highly acclaimed and appreciated in the flight sim community, and it is my firm belief that if MSFS 2024 does embody such a change that is your vision and efforts that created their awareness of the need.

At FlyTampa's Amsterdam Schiphol with FSHud v2 + AIG. Clearly my hardware is not up to the task, even at TLOD 25. So I decided to give lossless scaling a go. 

The problem is that although LSFG 2X is detected, FPS is reported as non-LSFG. So I'm still getting TLOD 25. 

LSFG FPS counter shows approximately 60/120. 

EDIT: I was using native frame generation. Without it, the FPS readout takes into account LSFG. My base FPS is only around 25, so I used x3. I guess I don't need a TLOD of 325, but that's because LSFG gave me headroom for it, and I've got TLOD Min Extra enabled. 

I'm getting severe frame gen induced artifacts though... But I guess it might be worth it at those major hubs with AI traffic to be able to get decent performance. It's a choice between stutters and artifacts...

Edited September 24, 20241 yr by Cpt_Piett

6 hours ago, Cpt_Piett said:

At FlyTampa's Amsterdam Schiphol with FSHud v2 + AIG. Clearly my hardware is not up to the task, even at TLOD 25. So I decided to give lossless scaling a go. 

The problem is that although LSFG 2X is detected, FPS is reported as non-LSFG. So I'm still getting TLOD 25. 

LSFG FPS counter shows approximately 60/120. 

EDIT: I was using native frame generation. Without it, the FPS readout takes into account LSFG. My base FPS is only around 25, so I used x3. I guess I don't need a TLOD of 325, but that's because LSFG gave me headroom for it, and I've got TLOD Min Extra enabled. 

I'm getting severe frame gen induced artifacts though... But I guess it might be worth it at those major hubs with AI traffic to be able to get decent performance. It's a choice between stutters and artifacts...

As you have discovered, AutoFPS doesn't account for someone using native FG AND LSFG because not only does it complicate FPS calculations but using both at the same time is something a user should not really be doing anyway. The reason being that if you really want 4X FG, then simply just use LSFG set to 4X rather than native FG 2X and LSFG 2X. Also, as you later discovered, you can't have anything less than 4X using both whereas with LSFG you can have 3X if you really want, so again just use LSFG.

Multiple times now with this latest version, the sim has frozen literally at touchdown point on landing for a good 20 seconds....