Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GPU Overload message 2024

Featured Replies

I never used to see this message before.  I haven't fired up the sim in about a month and decided to the other day after I updated 2024.  When in the Fenix or FSlabs, when I get into the screen where it says click to fly (i think), a box comes up that says something along the lines of "GPU overload, my GPU isn't capable and that I need to reduce my settings for performance".  I never felt like i had performance issues nor do I feel like I have a bad GPU (in my signature).  Is this something new or could something have changed on my system that i need to address? 

Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU   32GB G.Skill Performance DDR4 SDRAM 3600MHz       Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System   2TB Western Digital, NVMe M.2 Solid State Drive

 

 

 

 

Welcome to MSFS 24. It's a popup that came in with SU2. 

The good folks at Asobo have taken all the VRAM complaints and redirected them back at the consumer to inform them that their systems are inadequate for the settings chosen.

Mind you even for the highest system specs in the requirements there is no mention of needing over 16 GB of VRAM but this is where we are today pending someone at ASOBO getting some enlightenment and optimizing the sim to bring the VRAM levels back down to something looking reasonable. 

AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2

Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders

I guess Asobo doesn't know how to program. Using 16 GB VRAM RTX4080 cards doesn't cut it anymore—they are already obsolete within 6 months!

Edited by SP2472

Kind of like blaming the brewery because you drink too much beer

dd

13 minutes ago, Sky_Pilot071 said:

Kind of like blaming the brewery because you drink too much beer

dd

That analogy would have made sense if only the brewery correctly stated the alcohol content on its product labels so the informed consumer could appropriately set expectations and self regulate themselves accordingly.

Edited by Maxis

AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2

Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders

I don't think it is possible for simmers to set expectations.

Gimmee, gimmee, gimmee.

dd

Edited by Sky_Pilot071

51 minutes ago, Zimmerbz said:

I never used to see this message before.  I haven't fired up the sim in about a month and decided to the other day after I updated 2024.  When in the Fenix or FSlabs, when I get into the screen where it says click to fly (i think), a box comes up that says something along the lines of "GPU overload, my GPU isn't capable and that I need to reduce my settings for performance".  I never felt like i had performance issues nor do I feel like I have a bad GPU (in my signature).  Is this something new or could something have changed on my system that i need to address? 

I got that message with some KSTL scenery that isn't 2024-native. 

That's with a 4090.  Heh.

Are you getting it with 2020-in-2024 3rd-party scenery?  Because that's the only time I have gotten that message.

Rhett

7800X3D 96 GB G.Skill Flare  Gigabyte 4090  Crucial P5 Plus 2TB

  • Author
11 minutes ago, Mace said:

I got that message with some KSTL scenery that isn't 2024-native. 

That's with a 4090.  Heh.

Are you getting it with 2020-in-2024 3rd-party scenery?  Because that's the only time I have gotten that message.

Good question... I am pretty sure it is with scenery that is compatible with both.  I don't mind the message if I can ignore it.  I just didn't know if I needed to do anything

Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU   32GB G.Skill Performance DDR4 SDRAM 3600MHz       Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System   2TB Western Digital, NVMe M.2 Solid State Drive

 

 

 

 

@Mace

It happens on my installation of bone stock scenery.

 

@Zimmerbz

If it only pops up and there are no noticeable stutters following you can ignore. If you’re having the stutters around that message then you’re gonna have to start looking at some remedial action.

AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2

Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders

I get the message at bigger airports like CYYJ and FSDT KSFO.  

Could be VRAM and or CACHE related I'm thinking.

dd

14 minutes ago, Zimmerbz said:

Good question... I am pretty sure it is with scenery that is compatible with both.  I don't mind the message if I can ignore it.  I just didn't know if I needed to do anything

If you get good performance I guess I wouldn't worry about it, but for me when I got the message I got a bad stutter.   I turned on dev mode and saw it was maxxing out my 24 gb vram (!).

Tonight I'm going to run it without the aftermarket KSTL scenery see what happens.

Rhett

7800X3D 96 GB G.Skill Flare  Gigabyte 4090  Crucial P5 Plus 2TB

Hi, yes Zimmerbz , frequently have the same pop up suggesting that my modest graphic card is not up to it and suggesting that I reduce my settings. And like you have been wondering if I can continue to safely ignore it given that my PC seems to be performing perfectly satisfactorily when viewed through my ancient eyes. And I would rather not have load my MSFS 24 SU 2 with the further  clutter of a graphics card health monitoring app. Unfortunately people continue to comment around the question without addressing it. Too common an occurence in this forum I feel.

 

 

There is no way that ASOBO can win on this one but I appreciate the effort.

In the old days we would say "the biggest, most powerful computer will almost be fast enough".

dd

Edited by Sky_Pilot071

I still believe it's an Asobo bug.  

I had written about vram in a semi productive thread a few weeks ago.

Because I sim with a lot of non native addons in 24 I feel there a memory bug somewhere in the 24 code, especially when it relates to 2020 addons in 2024 environment.

I basically have to restart the sim between flights now for sure.  But recently I decided to disable photogrammetry/TIN in favor of running TLOD 400.

I haven't seen the out of resources popup since.  I realize that isn't a good solution but the base imagery is pretty nice even with the autogen type buildings.  I only miss TIN when I'm down at 1000agl and lower.

Anyway long story longer - over at the dev forums, Asobo is working on this but perhaps it may not make SU3.  As they're currently tracking down CTD issues.

For now I wholeheartedly recommend disabling PG/TIN.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.