8 hours ago, Reset XPDR said:

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:

I'd appreciate it if someone with an AMD GPU could try this test version and confirm that VRAM use shows correctly on the app status line.

As @Cpt_Pietthas already stated:

8 hours ago, Cpt_Piett said:

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

I use the following settings so that it starts up minimised to the system tray when I start Windows, so I never have to worry about firing it up. It uses very few resources when running in the background like this.

1 hour ago, Reset XPDR said:

I'd appreciate it if someone with an AMD GPU could try this test version and confirm that VRAM use shows correctly on the app status line.

AMD RX7900XT, running triples, working fine.

https://ibb.co/hffxG1S

Edited December 30, 20241 yr by ConairMSFS

Hello, 

I fly with last version test 16 into DTTJ-EGGC.

I tinkered a bit between TAA and DLSS DLA with the latest DLLs during the flight. Wow, FS2024 is very demanding on VRAM! ^^

It took a while to drop to TLOD 100 as I was approaching 2000ft; I stayed at 270 TLOD otherwise. The application works very well, though.

For reference, here’s my setup: I9-13900K (B760 Plus WIFI) - 64GB RAM DDR5 5600MHz - RTX 4080 566.45 Driver
Fenix A320 - ActiveSky - SimBox - MSFS Pop-Up Manager 2024 - Navigraph Unlimited - FSRealistic - AutoFPS V16 - WinWing FCU+EFIS L - HoneyComb T+Y

I'm off for another long haul (LH)!

Good Night

Log file : https://www.swisstransfer.com/d/f78c7b14-d99c-42d2-96ba-f560fc2e53c1

 

New test version 17 here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test, with a few minor tweaks to VRAM overflow protection, the most significant of which is TLOD can now be reduced all the way down to 10, the sim minimum, should the overflow be severe enough (I'm looking at you @Cpt_Piett!😄).

4 minutes ago, ConairMSFS said:

AMD RX7900XT, running triples, working fine.

https://ibb.co/hffxG1S

It looks like your GPU wasn't correctly detected, otherwise you should have been seeing VRAM usage % after GPU load.

Actually I think I know why because your gpu-z screenshot shows Memory Used (dedicated) as the sensor whereas with all nVidia results so far that sensor is called just Memory Used and that is what the app has been looking for. If so, it should be a simple fix.

Can you message me your log file and I'll see what's going on for sure. Thanks.

8 minutes ago, Reset XPDR said:

Can you message me your log file and I'll see what's going on for sure. Thanks.

Sure, here it is:

https://jumpshare.com/s/8jjkkxpY2ihsBHoLkauN

And thanks again for excellent job!

21 minutes ago, ConairMSFS said:

Sure, here it is:

https://jumpshare.com/s/8jjkkxpY2ihsBHoLkauN

And thanks again for excellent job!

Yep, this confirms what I thought. The app detected your GPU correctly, but failed to find the correct right sensor title because (dedicated) seems to get tagged on to Memory Used for AMD GPUs. While I could come up with a quick fix, I am also toying with another way to get GPU memory used without needing gpu-z to be running, which would make such a fix obsolete, and that would be more suitable for the masses. I would appreciate it if you could try out the next test version I put out, which ever way I go with this.

1 minute ago, Reset XPDR said:

 I am also toying with another way to get GPU memory used without needing gpu-z to be running, which would make such a fix obsolete, and that would be more suitable for the masses. I would appreciate it if you could try out the next test version I put out, which ever way I go with this.

Without the need of running gpuz, it would be even better!

It will be a pleasure to try it.

P.S.

I live in GMT+1, so if you'll get late answers, it's just because of different timezone.

 

1 hour ago, Reset XPDR said:

New test version 17 here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test, with a few minor tweaks to VRAM overflow protection, the most significant of which is TLOD can now be reduced all the way down to 10, the sim minimum, should the overflow be severe enough (I'm looking at you @Cpt_Piett!😄).

Hello @Reset XPDR, with the latest version, when I'm on the ground, it locks well at 100, but if the GPU doesn't reach its maximum load, I've seen it go up to 130 and then drop to 100 with the lock icon and VRAM at 85%.

14 minutes ago, TVOpium said:

Hello @Reset XPDR, with the latest version, when I'm on the ground, it locks well at 100, but if the GPU doesn't reach its maximum load, I've seen it go up to 130 and then drop to 100 with the lock icon and VRAM at 85%.

Did you modify the VRAM thresholds in the config file by any chance? They should be the following by default:

  <add key="VRAMOverflowHoldTLOD" value="95" />
  <add key="VRAMOverflowReduceTLOD" value="98" />

2 hours ago, ConairMSFS said:

Without the need of running gpuz, it would be even better!

It will be a pleasure to try it.

P.S.

I live in GMT+1, so if you'll get late answers, it's just because of different timezone.

 

Well I have crashed and burned so far getting the app to detect GPU memory used without gpu-z. Without gpu-z the process is different for each GPU manufacturer and DX12 complicates things even further with not providing direct access to GPU memory used without all kinds of trickery that sometimes works and sometimes doesn't.

As such, for now I have kept the need to run gpu-z with this app to get VRAM overflow protection. I have updated the code to allow the gpu-z Memory Used (Dedicated) sensor to be used if that is what is found, which seems to be the case with AMD cards.

Acknowledging our time differences, when you get a chance could you install test 18 or later from here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test and see if you can now see VRAM use % shown when in a flight session. Thanks

2 hours ago, Reset XPDR said:

Well I have crashed and burned so far getting the app to detect GPU memory used without gpu-z. Without gpu-z the process is different for each GPU manufacturer and DX12 complicates things even further with not providing direct access to GPU memory used without all kinds of trickery that sometimes works and sometimes doesn't.

As such, for now I have kept the need to run gpu-z with this app to get VRAM overflow protection. I have updated the code to allow the gpu-z Memory Used (Dedicated) sensor to be used if that is what is found, which seems to be the case with AMD cards.

Acknowledging our time differences, when you get a chance could you install test 18 or later from here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test and see if you can now see VRAM use % shown when in a flight session. Thanks

Hi, I have run test 18 OK. Log file sent.

Edited December 31, 20241 yr by Harrier77
Log file found

55 minutes ago, Harrier77 said:

Hi, I have run test 18 OK. Log file sent.

The log looks good. Thanks for the feedback.

Looks like it's working, just loaded fbw a380 at eddf in 2024, later will try better during a flight.

fsautofps+gpuz:

Heere is log file:

https://jumpshare.com/s/YamEKPfDSAruUpWpfuuq

https://ibb.co/nDN29Mb

 

Edited December 31, 20241 yr by ConairMSFS

Add the command into *.config