37 minutes ago, deepstar said:

Okay.

Remember what the doctor said ?

Those crazy ideas ! You have to stop ! The time has come to say enough is enough ! I have to put you into a retirement home !

😁🤣

 

 

 

Too late, it is done. 😁 You can always stay with test 14 if you don't want any more updates. Don't go deleting that installer! 😆

Alrighty then, test 16, available here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test, has been created to provide the new VRAM overflow protection when the app is run with the GPU-Z companion app.

I had a hard enough time testing this myself as you need to get your VRAM usage to a point where the feature will trigger, and that takes a bit of trickery with changing VRAM thresholds in the config file then playing with render resolution in TAA mode to get things to trigger. As such, I am not asking anyone to test the trigger mechanism as I have done this extensively myself and it's just a simple state machine.

What I will ask testers to do is to make sure the app is detecting your GPU correctly and that the reported VRAM total is what your GPU actually has. To that end, please message your log file after a test run of the app with GPU-Z running where you go into a flight for at least a minute or so.

If I've done everything right, your GPU should be correctly detected as well as current VRAM use and total VRAM available and all logged to the log file. Otherwise, you should see nothing else different, unless your VRAM really does get to 95%+ usage or you decide to mess around with trigger thresholds and render resolutions yourself!

Feature details:

• Added new TLOD limiter when impending VRAM overflow is detected, particularly useful with DX12 operations and especially with MSFS 2024 which is known to breach VRAM capacity:
  • Requires the GPU-Z companion app to be installed and running to work (see Readme). Feature will be disabled if GPU-Z is not found running.
  • Uses two thresholds for VRAM usage, both changeable in the config file after running the app once after updating:
    • Hold threshold, defaults to > 95% VRAM in use and will cap TLOD to its current value, even if favourable performance conditions exist.
    • Reduce threshold, defaults to > 98% VRAM in use and will progressively reduce TLOD down until the Hold threshold is achieved, but no lower than TLOD Min/Base..
  • When VRAM use drops below the Hold threshold, TLOD will progressively increase up to TLOD Max/Top should favourable performance conditions exist.

Example screenshots when the feature is active, using a VRAM Hold of 80% and a VRAM Reduce of 85% for demonstration purposes:

Above VRAM Reduce threshold:

Above VRAM Hold threshold but below VRAM Reduce threshold:

Recovering from the VRAM limiter being lifted:

Thank you for your hard work on this app!

I've installed it and it seems to be working, but I still experience my biggest issue which is major stutters/rubber banding as the airport I'm approaching loads in.

For example, approaching KLAX (Los Angeles) from the West in the default 737 Max, all is smooth until a mile out or so as the airport loads in then BOOM (major stutter) then again and again like 3 more times as I approach the runway (this is even with the "enhanced" KLAX by Asobo temporarily disabled).

What settings on the app should I target to prevent this?

Specs are 10900K, 3070 card 8GB, 32GB Ram

Thanks!

Steve

15 minutes ago, Republic DC9 said:

For example, approaching KLAX (Los Angeles) from the West in the default 737 Max, all is smooth until a mile out or so as the airport loads in then BOOM (major stutter) then again and again like 3 more times as I approach the runway (this is even with the "enhanced" KLAX by Asobo temporarily disabled).

What settings on the app should I target to prevent this?

Based on my experience, approaches to KLAX (especially from the east), is probably the most demanding situation in the whole sim. We're flying in very complex airliners over probably the largest photogrammetry area in the sim, into one of the largest airports in the sim. I'm honestly not sure if current hardware can deal with everything without stutters - especially not when an ATC addon and AI traffic are added into the mix. 

What I've done, which somewhat works is to use expert settings, IFR mode, FPS sensitivity 5 and TLOD min to 50 (with no TLOD min extra enabled). FPS target depends on hardware. I'd recommend setting it to something that you're likely to achieve most of the time, even on final approach to KLAX. I.e. this requires some testing and trial and error. 

My FPS target is 65 with DLSS frame generation enabled. I think a good rule of thumb is to aim for at least 30 FPS without any sort of frame gen. Below 30 FPS it's hard to get a nice and smooth simming experience. In my very honest opinion!

Edit:

Or - forget what I just said and follow the developer's suggestions below instead 😅

Edited December 30, 20241 yr by Cpt_Piett

1 minute ago, Republic DC9 said:

Thank you for your hard work on this app!

I've installed it and it seems to be working, but I still experience my biggest issue which is major stutters/rubber banding as the airport I'm approaching loads in.

For example, approaching KLAX (Los Angeles) from the West in the default 737 Max, all is smooth until a mile out or so as the airport loads in then BOOM (major stutter) then again and again like 3 more times as I approach the runway (this is even with the "enhanced" KLAX by Asobo temporarily disabled).

What settings on the app should I target to prevent this?

Specs are 10900K, 3070 card 8GB, 32GB Ram

Thanks!

Steve

This is usually because your app settings are too aggressive, particularly if your target FPS is too high for your system's capability. The easiest way to work out what is best is to, before you start this app, set your MSFS TLOD, OLOD and cloud quality settings as you would without using this app and for an average type of flight you do. Then, as covered in the readme FAQ:

• Start the app before you load your flight,
• Leave Use Expert Settings unchecked,
• Pick what type of flight you are doing via the radio buttons ie. either VFR (GA aircraft) or IFR (airliners),
• Enter a realistic target FPS (or click on auto target FPS for the app to pick it for you),
• Click back on MSFS and wait until any FPS settle or TLOD seek events have finished (60 seconds max), then
• Go fly!

 

Anyway, I'm off to bed. See if anyone can break my latest test 16 while I am asleep!😂

Mhmm not seeing vram usage 😞

Maybe I missed something. 

7 minutes ago, iFlySimX said:

Mhmm not seeing vram usage 😞

Install GPU-Z and make sure it is running https://www.techpowerup.com/download/techpowerup-gpu-z/

4 minutes ago, Cpt_Piett said:

Install GPU-Z and make sure it is running https://www.techpowerup.com/download/techpowerup-gpu-z/

Ok now its working, ty. 

Edited December 30, 20241 yr by iFlySimX

Hello everyone,

I’d like to inform you that the GPU is properly recognized, and VRAM usage is as well. I’m locking my FPS via NVidia because I use pop-ups, and with RTSS, it reduces the FPS by 4/5...

Here is the log as requested, along with the screenshots confirming that it works. I hope this helps.

Happy holidays!

LOG File: https://www.swisstransfer.com/d/308dd18c-c752-461c-90c8-b7ffc674943b

Edited December 30, 20241 yr by TVOpium

Allright, so like @TVOpium says, the app successfully detects VRAM use. 

I'm trying to torture test the app by making the sim insanely GPU-limited. So far I'm somewhat successful by setting resolution to 6K with TAA and a render scaling of 150. VRAM use then exceeds what's available, and I get this: 

I need to do more tests to fully understand the VRAM overflow logic, and how I can break it! 😅 Should have enough time before he wakes up!

Log file: https://drive.google.com/file/d/1ZU-5b2u3I18WDrux9JA4_WpnKhlR70FK/view?usp=sharing

Quote

GPU-Z companion app running 
GPU-Z GPU Load sensor found 
GPU-Z GPU Memory Used sensor found 
GPU-Z Initial Memory Used: 24253 MB 
System Reported Total GPU Memory: 24142 MB 
GPU Initial Memory Usage: 100% 

 

Edited December 30, 20241 yr by Cpt_Piett

1 minute ago, Cpt_Piett said:

Très bien, comme @TVOpium dit, l'application détecte avec succès l'utilisation de VRAM. 

J'essaie de tester l'application en rendant la simulation incroyablement limitée par GPU. Jusqu'à présent, je suis un peu réussi en définissant la résolution à 6K avec TAA et une échelle de rendu de 150. L'utilisation de VRAM dépasse alors ce qui est disponible, et j'obtiens ceci: 

J'ai besoin de faire plus de tests pour bien comprendre la logique de débordement VRAM, et comment je peux le casser! 😅 Il devrait avoir assez de temps avant de se réveiller!

Go to OMDB Airport with FSLTL and FBW A380X. 

7 hours ago, iFlySimX said:

Ok now its working, ty. 

Your initial test was not in vain as it shows me the app still works normally without gpu-z running, so thanks for that.

6 hours ago, Cpt_Piett said:

Allright, so like @TVOpium says, the app successfully detects VRAM use. 

I'm trying to torture test the app by making the sim insanely GPU-limited. So far I'm somewhat successful by setting resolution to 6K with TAA and a render scaling of 150. VRAM use then exceeds what's available, and I get this: 

I need to do more tests to fully understand the VRAM overflow logic, and how I can break it! 😅 Should have enough time before he wakes up!

Log file: https://drive.google.com/file/d/1ZU-5b2u3I18WDrux9JA4_WpnKhlR70FK/view?usp=sharing

 

Nice try at breaking it @Cpt_Piett😄! It looks like it did what it was supposed to, although TLOD was already at TLOD Min so it had nowhere to go anyway. Maybe I need to allow TLOD to go lower than TLOD Min in such cases, but that could have undesired side effects on other calculations that use TLOD Min and this was a pretty extreme case where you couldn't even hit your target FPS at TLOD Min because it was so hobbled at the start, which is a bit beyond what this feature is supposed to protect you from, but I did ask you to try and break it! 😆

If you really want to see it function as intended, set yourself up in the air where you are in FPS priority mode with your normal desktop resolution and slowly increase TAA render resolution until VRAM gets above the default VRAM Hold threshold of 95%. Actually, for testing it is easier if you edit the config file and change the two VRAM thresholds to be lower so that it triggers without pushing your system into memory overload because, as you likely experienced, things get ugly at 100% VRAM usage eg.

  <add key="VRAMOverflowHoldTLOD" value="80" />
  <add key="VRAMOverflowReduceTLOD" value="85" />

On my system, starting at 4K over YSSY in the 737 Max and Ultra settings and TLOD Max at 1000, I could get it to hit the test VRAM hold threshold of 80% at around 130 render resolution, then the test VRAM Reduce threshold at around 150. Putting it back to 100 or lower allowed me to see the recovery. For others, only try this if you are very comfortable with changing the settings I mentioned and know how to put things back to what they were, especially the VRAM thresholds as it will otherwise trigger too early for normal use.

 

Edited December 30, 20241 yr by Reset XPDR

6 hours ago, TVOpium said:

Hello everyone,

I’d like to inform you that the GPU is properly recognized, and VRAM usage is as well. I’m locking my FPS via NVidia because I use pop-ups, and with RTSS, it reduces the FPS by 4/5...

Here is the log as requested, along with the screenshots confirming that it works. I hope this helps.

Happy holidays!

LOG File: https://www.swisstransfer.com/d/308dd18c-c752-461c-90c8-b7ffc674943b

This is great thanks as it shows it is detecting GPU and VRAM total correctly and that MSFS should not be getting near your VRAM limit most of the time.