46 minutes ago, Reset XPDR said:

eg. Here's my current flight with LS set to 2X, showing 30 FPS in game, same as if I don't run LS, but actually getting 60 FPS visually. AutoFPS doesn't care whether LS is running or not and works the same either way.

Yes, this has been my experience as well. I guess the challenge is to find a way to detect the LS FPS output (x2, x3 or x4). 

Hello all,

I have this app, on version 0.4.2.16 (see the screenshot) and i have a issue:

My problem is when I approach a (big) airport, the OLOD is like 20, which means that the objects with CAVOK is like everything is flat. The airport of EHAM (Amsterdam Schiphol) or a different airport is like a big white square. When I approach the airport under 5000 ft, I see in the distance that everything is loaded in. But it is very slowly done. I have a decent PC.

My rig are:
AMD 7950x3D
RTX 4090 24GB
64 RAM 6000Mhz
MSFS and every addon on .m2 storage.

Is the above issue known by you guys?

 

Not sure if it's helpful, but with LS active, it's possible to activate an FPS overlay. A base FPS (with or without FG) of 30 and LS at x2 will display 30/60 in the left hand corner of the display. 

13 minutes ago, Cpt_Piett said:

Yes, this has been my experience as well. I guess the challenge is to find a way to detect the LS FPS output (x2, x3 or x4). 

My point is that, even if I can detect it, there is not much point in showing 2, 3 or 4X FPS when no other FPS indicator you have on your system shows it multiplied either. It would just cause confusion I would think. eg. questions like: Why is my in game RTSS FPS display showing 30 FPS but your app shows 60 FPS? I'm thinking it is best to just leave it alone.

14 minutes ago, Cpt_Piett said:

Not sure if it's helpful, but with LS active, it's possible to activate an FPS overlay. A base FPS (with or without FG) of 30 and LS at x2 will display 30/60 in the left hand corner of the display. 

I see that too but for some reason it doesn't come out in screen shots. IMO that is the indicator users should be looking for that LS is doing it's thing, not AutoFPS because no other app or FPS indicator does either (Well, I haven't found one).

1 hour ago, AMSPilot06 said:

Hello all,

I have this app, on version 0.4.2.16 (see the screenshot) and i have a issue:

My problem is when I approach a (big) airport, the OLOD is like 20, which means that the objects with CAVOK is like everything is flat. The airport of EHAM (Amsterdam Schiphol) or a different airport is like a big white square. When I approach the airport under 5000 ft, I see in the distance that everything is loaded in. But it is very slowly done. I have a decent PC.

My rig are:
AMD 7950x3D
RTX 4090 24GB
64 RAM 6000Mhz
MSFS and every addon on .m2 storage.

Is the above issue known by you guys?

 

If objects are not appearing on the ground in front of you, that's a TLOD not an OLOD issue because, as far as I am aware, TLOD affects draw distance and OLOD affects object quality out to that distance. ie. if objects aren't appearing when you want them to then your TLOD is too low and if you increase TLOD to improve it but can't get the FPS you want then your system is not performing up to your expectations, no matter how powerful it may be.

Edited September 8, 20241 yr by Reset XPDR

19 minutes ago, Reset XPDR said:

I see that too but for some reason it doesn't come out in screen shots. IMO that is the indicator users should be looking for that LS is doing it's thing, not AutoFPS because no other app or FPS indicator does either (Well, I haven't found one).

Same here, LS FPS not detected in screenshots or video captures. 

19 minutes ago, Reset XPDR said:

I'm thinking it is best to just leave it alone.

I'd be interested to hear feedback from other people. There seems to be quite a bit of interest in LS. My own (perhaps controversial opinion), is that it'll be fine to leave it alone. 

Edited September 8, 20241 yr by Cpt_Piett

28 minutes ago, Cpt_Piett said:

Same here, LS FPS not detected in screenshots or video captures. 

I'd be interested to hear feedback from other people. There seems to be quite a bit of interest in LS. My own (perhaps controversial opinion), is that it'll be fine to leave it alone. 

Just to add, with FG it turned out to be useful for the app to detect it properly because the detectable FPS did change when it was active and halved when it was inactive. Also, and perhaps most importantly, when changing from inactive to active, FG did not suddenly double rather it took a few seconds to settle, which is why it was important for the app to detect FG so that it could use the settle timer at the right time so that TLOD wasn't changing based on unstable FPS readings.

In contrast with LS, the detectable FPS stays the same whether LS is active or not, so nothing changes FPS display wise. Also there are no notable FPS fluctuations caused by LS activating and deactivating, even when MSFS gains or loses focus, so there is nothing for AutoFPS to watch out for to prevent inappropriate TLOD changes. All the user simply has to do is set their AutoFPS target FPS to be their LS non-FG target FPS and the app will function just fine.

If anyone has experience otherwise with LS and AutoFPS, please let me know.

10 hours ago, AMSPilot06 said:

Hello all,

I have this app, on version 0.4.2.16 (see the screenshot) and i have a issue:

My problem is when I approach a (big) airport, the OLOD is like 20, which means that the objects with CAVOK is like everything is flat. The airport of EHAM (Amsterdam Schiphol) or a different airport is like a big white square. When I approach the airport under 5000 ft, I see in the distance that everything is loaded in. But it is very slowly done. I have a decent PC.

My rig are:
AMD 7950x3D
RTX 4090 24GB
64 RAM 6000Mhz
MSFS and every addon on .m2 storage.

Is the above issue known by you guys?

 

In the expert drop down menu I chose to use TLOD instead of FPS and the ap works great. My FPS are locked @30.

I have a partial implementation of Lossless Scaling app awareness working. The app can detect if Lossless Scaling app is running and, if so, scale up the FPS reading by the LS FG multiplier so you are seeing your actual LS FG FPS. The LS FG multiplier is currently manually set by the user as I don't have a way to determine what multiplier is in use by LS, well not yet anyway, so as long as you match what multiplier you have set in LS with what is selected in the drop down list in AutoFPS then the FPS display is correct. I will continue to look for a way to automatically detect what multiplier LS is actually using, but at least it works OK this way for now.

12 hours ago, Reset XPDR said:

If objects are not appearing on the ground in front of you, that's a TLOD not an OLOD issue because, as far as I am aware, TLOD affects draw distance and OLOD affects object quality out to that distance. ie. if objects aren't appearing when you want them to then your TLOD is too low and if you increase TLOD to improve it but can't get the FPS you want then your system is not performing up to your expectations, no matter how powerful it may be.

Thank you. I will try again when I am at home and try to replicate the flight.

Another piece of the LSFG puzzle solved! The app can now auto detect what FG scaling you are using in LS, so no need to manually select the FG multiplier to match what is in LS anymore. To minimise app overhead, it will only read the LS config file when loading in at the start of each flight. If you start LS later or change the FG scaling, just hit the new Reset button and it will be correctly detected.

The final piece of the puzzle is to see if the app can detect when scaling is actually toggled on in LS, but I am not very hopeful I'll find this given anti-cheat software can't even detect when it is doing its thing. Nonetheless, I think it is a pretty safe assumption that if you have the LS app running when MSFS and AutoFPS are running too then, unless LSFG is turned off in LS settings, AutoFPS can reasonably assume you are planning on using LSFG and configure itself to do so, so not being able to detect whether LSFG is currently active or not should not a be an issue.

 

14 hours ago, Cpt_Piett said:

Not at all. I'm using 4K DLSS+DLAA with no render scaling. Tested over the Alps at FL130, VOR approach to Bolzano and RNAV to Venice,  and avg GPU use is below 79%. 

I am still using TLAA which would explain why I see such high GPU usage when running unlocked 

I can not find test10 to download.

 

Thanks Frank

A new test version v0.4.2.17-test10 is available here.

There are lots of changes, some of which are a WIP but relatively stable and only a Reset button push away from straightening out should you experience any issues, but the main one I want to get out there for users to try is Lossless Scaling support for those that use that app. TLOD Min Extra in Auto TLOD has been a long-term desire of mine to get working with the capped FPS I use for VR so that I get the most TLOD I can while maintaining that FPS cap, so it may not appeal to many but hey it's my app and I can code what I want! 😄

If your head is spinning a bit from all these test builds (mine is!), a lot of what was trialed earlier failed and has been tossed out, so the TL;DR summary of where we are right now since v0.4.2.16 is:

• Added Lossless Scaling (LS) app and associated FG scaling detection to allow the app to show the actual LSFG FPS being produced in MSFS and allow the user to set an LSFG target frame rate.
• Added Reset button to the General section of the UI that will reset your TLOD, Cloud, LSFG, and FG settings to initial app flight start values and will recalculate TLOD Min Extra if required.
• Completely reworked TLOD Min Extra functionality to allow far higher TLOD Mins than previous versions when performance conditions permit and to also work in Auto TLOD automation mode.
• Completely reworked FPS settle and TLOD Min Extra seek timing be condition based rather than a set time period, resulting in much shorter settle/seek times.
• Added TLOD Max Extra functionality, which is disabled by default, to trigger additional TLOD at higher ground elevations, namely mountain regions, to allow much greater object drawing distance in scenic areas with minimal performance penalty.
• Significantly reduced MSFS memory space interaction by up to 30 times when nothing is being changed by the app, leading to a smoother flight experience.
• Revised status line to show the current allowable TLOD range and simplified app priority and mountains status messages accordingly.
• Updated supporting apps ( MobiFlight Wasm Flight and Dot NET) to their latest versions.
• Added DecCloudQNonExpert config file option setting, which defaults to true, to be able to disable cloud quality reduction in non-expert mode by setting it to false.
• Updated app logging to record events and settings relating to the new TLOD Min Extra and TLOD Max Extra functionality.

Specific changes since v0.4.2.17-test9:

• Added Lossless Scaling (LS) app and associated FG scaling detection.
  • If LS is detected as running at the start of a flight, the FPS reading will be scaled up by the LS FG multiplier so you are seeing your actual LS FG FPS.
  • The app status line and target FPS label will show LSFG and, for the former, what multiplier is currently in use.
  • Due to the technical limitation of the app not being able to detect whether you actually have activated LSFG in LS, this app will reasonably assume that if you are running LS at the same time as this app and MSFS that you are going to activate LSFG.
• Extended TLOD Min Extra functionality to Auto TLOD automation mode.
  • FPS settling and TLOD Min+ seeking logic tuned to account for likely FPS cap in Auto TLOD.
  • When enabled, a target FPS will be required for the logic to work, which you should set to, or slightly lower than, your FPS cap if you use one.
  • FPS settling and TLOD Min+ seeking will take at least 10 seconds, the last 5 of which must be less than 1 non-FG FPS of the target FPS, otherwise up to 20 seconds.
  • TLOD Min+ seeking will iterate until either TLOD @ Top is achieved or the FPS drops more than 1 non-FG FPS below the target FPS.If the latter, TLOD Min+ seeking will backtrack to the last TLOD Min Extra where the FPS target was easily achieved.
  • At any time, if FPS drops more than 1 non-FG FPS below the target FPS then TLOD Min Extra will automatically reduce by 25%, down to zero if necessary.
• Expanded and revised TLOD Max Extra
  • Extended functionality to Auto TLOD Automation Mode
  • Revised status line item for Mtns to show Mtns+ when fully activated and Mtns- when decrementing down towards complete deactivation.
  • Corrected deactivation timer to be 5, not 10, minutes.
• Minor tweaks to TLOD Min Extra and FPS settling functionality.

Hi,

I've downloaded v0.4.2.17-test10 and installed, but it doesn't execute...

Latest version (test9) works without issue.

Regards.