I must admit that I am getting overwhelmed by all the configuration.

I too am also starting to use 40 Locked FPS + LSFG x3 for a solid 120 fps, which I can achieve everywhere now.  But I still use "Fps sensitivity" as someway in "FPS Caps" something the TLOD  on the ground goes up to 300. I don't really understand the behavior. So I guess I would be a candidate for "FPS Caps" but still using "FPS sensitivity"

When using LSFG the app does not always show the correct mode, e.g. currently I am in 3X mode but the app is showing 2X. Also, the app seems to show the base FPS multiplied by the mode x, i.e. in 2X mode two times the base FPS, 3X mode three times etc. The app does not show the actual achieved FPS, e.g. for my setup I have the FPS capped at 117 (GSYNC 120hz monitor) and when the cap of 117 is reached the app often shows a higher figure based on the 2 or 3 times multiple. I hope this makes sense 🤔

36 minutes ago, vincentrouleau said:

I must admit that I am getting overwhelmed by all the configuration.

I too am also starting to use 40 Locked FPS + LSFG x3 for a solid 120 fps, which I can achieve everywhere now.  But I still use "Fps sensitivity" as someway in "FPS Caps" something the TLOD  on the ground goes up to 300. I don't really understand the behavior. So I guess I would be a candidate for "FPS Caps" but still using "FPS sensitivity"

Same here.

It should be able to stop the TLOD on the ground also with the CAPs method.

3 hours ago, Cpt_Piett said:

I'll do more test flights today, both in GA and airliners, and hopefully I'll understand more over time 🙂

Cardiff to Heathrow in the turbine Duke, default TLOD 100, non-expert mode, IFR. Cruise FL100. Good performance mostly, except over London PG, despite a TLOD of 50 (server related?). AutoFPS set TLOD to 20 on the ILS, then 10 on the ground at EGLL. FPS locked to 72. FPS unlocked at EGLL with a TLOD of 10: approximately 100. 

I guess that in IFR mode TLOD on the ground is set like this (changelog):

Quote

TLODMin will be 25% of the default TLOD for IFR and 50% for VFR

I.e. for this particular flight I probably should have set default TLOD higher - perhaps 200. 

Edited January 14, 20251 yr by Cpt_Piett

29 minutes ago, Cpt_Piett said:

Still confused re: what settings to use.

Me too. I am not capping my FPS for smoothness, just a high 117 to keep within the GSYNC range. My issue is as my post above, the app is not reporting the LSFG mode correctly and is not reporting the actual FPS being achieved in LSFG just a multiple of the base FPS rate.

I've also stopped testing today after 2 CTDs in the cruise 🙄

Edited January 14, 20251 yr by Harrier77

I don't want to confuse everyone with my posts, just trying to understand FPS Cap. Still at default TLOD 100, FL110 en route from Heathrow to Cardiff now. 

I reset AutoFPS on the ground at Heathrow, so not sure why AutoFPS sets TLOD to 20 at FL110. 

Quote

TLODMax will be 100% of the default TLOD for IFR and 150% for VFR

Hang on... did default TLOD somehow get reset to 10? It actually appears so, according to usercfg.opt. I definitely did not touch it after I set it to 100 in the graphics menu. 

Edited January 14, 20251 yr by Cpt_Piett

Allright, I think I understand better how to use FPS Cap now (I guess I'm a slow learner, lol). I've experimented with non-expert mode all day, flying back and forth Cardiff-Heathrow too many times, piston Duke and Fenix A319. Before that, I flew around remote areas in Arizona and Utah in the DA42. This is what I've found so far:

• Both the Duke and the A319 over London: I set default TLOD to 100 and IFR mode, which works with my hardware
• GA over less dense areas: I guess I could get away with default TLOD of 200 and VFR mode
• FPS lock / target FPS: My goal is to stay well above 30 non-FG FPS.

Still, my hardware cannot handle London CBD with the Fenix. BUT - it's much better when I turn PG off. Not really a huge revelation - but the difference in performance is quite large. 

So, PG off and I finally had a (relatively) smooth ILS 27L approach into Heathrow. Not sure why it's not in FS Cap mode (it was for most of the flight), but here's a screenshot:

Edited January 14, 20251 yr by Cpt_Piett

3 hours ago, Harrier77 said:

When using LSFG the app does not always show the correct mode, e.g. currently I am in 3X mode but the app is showing 2X. Also, the app seems to show the base FPS multiplied by the mode x, i.e. in 2X mode two times the base FPS, 3X mode three times etc. The app does not show the actual achieved FPS, e.g. for my setup I have the FPS capped at 117 (GSYNC 120hz monitor) and when the cap of 117 is reached the app often shows a higher figure based on the 2 or 3 times multiple. I hope this makes sense 🤔

0.4.4.3 test 2 fixed this issue with LSFG.  I haven't installed test 5 yet, but I can confirm the issue was resolved in 0.4.4.3 test 2 through test 4.

7 hours ago, Cpt_Piett said:

Some questions:

• in non-expert mode, if I fly from a sparsely to a densely populated area, what default TLOD should I aim for to ensure I get a smooth approach?

 

If you are using non-expert mode and are flying in to densely populated area, you should use the IFR profile which sets TLOD Base and Top to 25% and 100% of your default TLOD. As such, if your default TLOD is 200, then those numbers are 50 and 200 respectively. If your system can always handle TLOD 50 on approach then this should be fine.

 

7 hours ago, Cpt_Piett said:

is it unwise to change settings whilst airborne (e.g. I started in VFR mode but want to change to IFR)?

No that's fine to do.

7 hours ago, Cpt_Piett said:

@Reset XPDR, do you have some general advice on how to use FPS Cap mode, apart from what's written in the changelog?

What I wrote here

 

6 hours ago, vincentrouleau said:

I must admit that I am getting overwhelmed by all the configuration.

I too am also starting to use 40 Locked FPS + LSFG x3 for a solid 120 fps, which I can achieve everywhere now.  But I still use "Fps sensitivity" as someway in "FPS Caps" something the TLOD  on the ground goes up to 300. I don't really understand the behavior. So I guess I would be a candidate for "FPS Caps" but still using "FPS sensitivity"

FPS Cap is just a specific configuration of Auto TLOD, which has been around since Apr 24, but otherwise the app interface is the same as it always has been.

The behaviour of FPS Cap is described below. In short, your TLOD is going up to 300 on the ground because your system has sufficient performance overhead to be able to do so, so why wouldn't you want it to be doing that?  It can do exactly the same thing in FPS Sensitivity mode if you enable TLOD Min +, but FPS Cap works better with an FPS cap as it always tries to work up to the cap whereas TLOD Min + works around your FPS target and can go above it.

 

Edited January 14, 20251 yr by Reset XPDR

5 hours ago, Harrier77 said:

When using LSFG the app does not always show the correct mode, e.g. currently I am in 3X mode but the app is showing 2X. Also, the app seems to show the base FPS multiplied by the mode x, i.e. in 2X mode two times the base FPS, 3X mode three times etc. The app does not show the actual achieved FPS, e.g. for my setup I have the FPS capped at 117 (GSYNC 120hz monitor) and when the cap of 117 is reached the app often shows a higher figure based on the 2 or 3 times multiple. I hope this makes sense 🤔

Do you have the latest LSFG version installed, because that's the format of LSFG configuration file that the app is trying to read and will not work with older versions? If you do have the latest LSFG version, with 3.0 support, and it is still not detecting correctly, please message me the contents of your LSFG settings.xml file, located in %localappdata%/Lossless Scaling and I'll see what the issue is.

Re not showing the actual FPS if you are using a non-standard FPS cap and it is reaching it, that is a limitation of LSFG detection because there is no way that I have found to read the actual FPS other than estimating it based on what in-game FPS you are achieving and multiplying it by the detected LSFG multiplier. If your G sync monitor goes up to 120Hz, why not just set an FPS cap in game to say 40 FPS (1/3 vsync or manually set with RTSS) then use LSFG at 3X to always give you 120 FPS?

5 hours ago, mobiel said:

Same here.

It should be able to stop the TLOD on the ground also with the CAPs method.

If your system has the available headroom to have a higher TLOD on the ground, which it must do if it is getting there, why would you want to stop it achieving the highest TLOD it can?

As mentioned previously, if you really want a fixed TLOD/altitude schedule then use Auto TLOD, a mode that has been available in earlier versions of this app since Apr 24, without TLOD Base + checked. If you do however, you are potentially missing out on higher TLOD than your system can actually handle. It's up to you of course.

As an example of how good I find using FPS Cap mode, every day I do a 2000-3500nm flight in the Concorde in VR from different departure and arrival airports with my VA. I have TLOD Base set to 50 and TLOD Top set to 200 and an FPS cap of 40 for my VR motion projection to work. If I am at a busy/complex airport eg. Heathrow, then there is no performance headroom and I get the base TLOD 50 on the ground and 200 in the air, which is fine. If I am starting from somewhere more isolated, eg Quito, Equador, the app detects the spare performance capacity and bumps my ground TLOD up as high as 200 and I get 350 in the air. If at any time this performance overhead disappears, it drops automatically to maintain the FPS Cap. How is this not a great outcome for FPS cap users?

4 hours ago, Cpt_Piett said:

I don't want to confuse everyone with my posts, just trying to understand FPS Cap. Still at default TLOD 100, FL110 en route from Heathrow to Cardiff now. 

I reset AutoFPS on the ground at Heathrow, so not sure why AutoFPS sets TLOD to 20 at FL110. 

Hang on... did default TLOD somehow get reset to 10? It actually appears so, according to usercfg.opt. I definitely did not touch it after I set it to 100 in the graphics menu. 

As you discovered, your default TLOD changed somehow. The app does it's best to save your default TLOD going in to a flight then restoring it coming out of it, even if you experience an MSFS CTD, but somethings things can go awry with the value it restores and I'm yet to put my finger on what causes that.  Can you message me the log file around when this happened so I can see if I can find what it is.

As you have done, resetting your TLOD in the MSFS settings with the app not running is the way to fix it. If you use expert mode, then you avoid this issue because it doesn't matter what your default TLOD and OLOD are (default clouds are used however). I know you have been trying non-expert mode to help me out with testing, which I much appreciate, I suggest you go back to non-expert mode when testing is finished so that this is no longer an issue.

59 minutes ago, Reset XPDR said:

As you have done, resetting your TLOD in the MSFS settings with the app not running is the way to fix it. If you use expert mode, then you avoid this issue because it doesn't matter what your default TLOD and OLOD are (default clouds are used however). I know you have been trying non-expert mode to help me out with testing, which I much appreciate, I suggest you go back to non-expert mode when testing is finished so that this is no longer an issue.

Affirmative. Just one more flight in non-expert mode (not just for testing, I like it). This time with BATC + AIG models, ENGM-EGLL. Excellent performance so far with default TLOD at 200, IFR. Night mode is active though, so the current TLOD is 189 at FL330, range 100-200. 

4 hours ago, Cpt_Piett said:

Allright, I think I understand better how to use FPS Cap now (I guess I'm a slow learner, lol). I've experimented with non-expert mode all day, flying back and forth Cardiff-Heathrow too many times, piston Duke and Fenix A319. Before that, I flew around remote areas in Arizona and Utah in the DA42. This is what I've found so far:

• Both the Duke and the A319 over London: I set default TLOD to 100 and IFR mode, which works with my hardware
• GA over less dense areas: I guess I could get away with default TLOD of 200 and VFR mode
• FPS lock / target FPS: My goal is to stay well above 30 non-FG FPS.

Still, my hardware cannot handle London CBD with the Fenix. BUT - it's much better when I turn PG off. Not really a huge revelation - but the difference in performance is quite large. 

So, PG off and I finally had a (relatively) smooth ILS 27L approach into Heathrow. Not sure why it's not in FS Cap mode (it was for most of the flight), but here's a screenshot:

What are using for a monitor ? 

No disrespect to you but you have a 4090 and sim looks terrible - boy they have some work to do 

I never saw this coming I thought we would be a bit better than 2020 and move on from there - boy I was wrong - sim looks very milky / washed out also especially in the cockpit depending what aircraft you are flying -  be nice if they will acknowledge it and address it - prob never happen 😞 Fenix isint to bad 

 

Edited January 14, 20251 yr by Richard Sennett