Sorry if this was already answered. I have a 60 Hz Monitor with VSYNC enabled. Should I specifically enable FrameCap (60) within AutoFPS? Right now, I'm running without the Expert Settings enabled. Thanks.

34 minutes ago, eXpress48 said:

Sorry if this was already answered. I have a 60 Hz Monitor with VSYNC enabled. Should I specifically enable FrameCap (60) within AutoFPS? Right now, I'm running without the Expert Settings enabled. Thanks.

It depends on whether the vsync is acting like an actual cap ie. you keep your setting such that it always achieves it, or it is just a limit that your system can reach but normally doesn't. If the former, you can still use non-expert mode as it will first attempt to detect such an FPS cap is in place. ie. if your FPS sits solid at 60 FPS for the last 5 or more seconds before the initial settle timer expires, the app will consider you are using an FPS cap and behave accordingly. You can see whether it has detected it or not by what mode you end up in - if you don't see FPS Cap then it didn't.

2 hours ago, Reset XPDR said:

It depends on whether the vsync is acting like an actual cap ie. you keep your setting such that it always achieves it, or it is just a limit that your system can reach but normally doesn't. If the former, you can still use non-expert mode as it will first attempt to detect such an FPS cap is in place. ie. if your FPS sits solid at 60 FPS for the last 5 or more seconds before the initial settle timer expires, the app will consider you are using an FPS cap and behave accordingly. You can see whether it has detected it or not by what mode you end up in - if you don't see FPS Cap then it didn't.

Perfect, thanks for taking the time to reply

17 hours ago, Reset XPDR said:

Alternatively, I could just limit the amount of TLOD extra on the ground to +100 in IFR mode, regardless of how high it could go.

That wouldn't be a terrible idea. However, can't there be a setting to force it to stick to TLOD base when below the Alt TLOD base? I'm not sure why it needs to push this at all below there if the user doesn't want it to. If it must then can't it run whatever process it needs to run to establish the data it needs before reducing down to the TLOD base number I have set.

The fact is, in my experience the initial setting is just wrong. Whatever it thinks I can run at the beginning is almost always wrong and instead of being at the 60 FPS I have set and capped it drops to 50-55 as soon as I look around. Then I must put up with this until it realises its wrong. It's just an immersion killer and seems totally unnecessary. If it stuck to my TLOD base number of 100 it would always stay at my 60FPS setting with headroom.

Is there a technical reason why this can't be an option?

 

reinstalled and now it doesn't start automatically when fsuipc is started

6 hours ago, Jazz said:

That wouldn't be a terrible idea. However, can't there be a setting to force it to stick to TLOD base when below the Alt TLOD base? I'm not sure why it needs to push this at all below there if the user doesn't want it to. If it must then can't it run whatever process it needs to run to establish the data it needs before reducing down to the TLOD base number I have set.

The fact is, in my experience the initial setting is just wrong. Whatever it thinks I can run at the beginning is almost always wrong and instead of being at the 60 FPS I have set and capped it drops to 50-55 as soon as I look around. Then I must put up with this until it realises its wrong. It's just an immersion killer and seems totally unnecessary. If it stuck to my TLOD base number of 100 it would always stay at my 60FPS setting with headroom.

Is there a technical reason why this can't be an option?

 

There is already this option, per my initial reply to you:

23 hours ago, Reset XPDR said:

If you don't like this tuning process, but otherwise like FPS Cap mode, try switching to Auto TLOD mode and make sure you have TLOD Base + unchecked. You will lose the ability to set a target FPS, but that's because your TLOD Base and Top should be conservative enough that any FPS cap you have set externally should not be breached, so it doesn't really matter.

2 hours ago, motishow said:

reinstalled and now it doesn't start automatically when fsuipc is started

I just tried installing with the fsuipc autostart option and the app started up fine just after fsuipc loaded for both MSFS 2020 and 2024. Are you running at least the latest release version 0.4.4.5 and did you see the successfully added message when you ran the installer like this?

Edited February 14, 20251 yr by Reset XPDR

Reset ive just realised you should be on the flight sim glamour awards thing !

8 minutes ago, sonny147 said:

Reset ive just realised you should be on the flight sim glamour awards thing !

What, like in the black market, naughty but nice, category? 😄

Just now, Reset XPDR said:

What, like in the black market, naughty but nice, category? 😄

no the renegade maverick robinhood category ! lol 

On 2/12/2025 at 11:09 PM, Reset XPDR said:

FPS Cap TLOD automation mode is what you are looking for

Thanks, Reset. This is working really well. 

The only thing I noticed after the new update is that AutoFPS does not detect the enabled FG, only after restarting the SIM it returns to normal.

28 minutes ago, rutrA said:

The only thing I noticed after the new update is that AutoFPS does not detect the enabled FG, only after restarting the SIM it returns to normal.

Nothing has changed lately in recent versions with FG detection, other than MFG selection for 5000 series cards but that is completely separate.

Per the readme:

• Detection of FG is normally only performed upon starting a flight. If FG is enabled or LS is started after this detection is normally performed, press the Reset button for it to be detected.

Did you enable FG in MSFS after the app had been started and was connected to a session but then didn't click the Reset button to re-detect the change? If so, that is why it wasn't detected.

I will try next time to reset button, cause I didnt tried now. Thanks.

33 minutes ago, rutrA said:

I will try next time to reset button, cause I didnt tried now. Thanks.

I changed it to do it this way a while ago when I was trying to minimise the app's interaction with MSFS memory. Previously it used to poll every second, but FG is normally one of those settings you change rarely so I changed it to be only checked when starting a flight session. It can trip you up if you are unaware of it, like you were, but it is covered in the FAQ in the readme.