Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
We're getting GPU bottleneck for some weird reason. The way I solved the issue for the most part is switching to Vulkan, using FSR 2.2, and releasing frame limiter. Kill any and all metrics in adrenaline, kill all metrics running in the background, and trying toggling freesync on and off. Fullscreen with freesync on works for me.
I am running a Ryzen 9 3950X Alienware R10 @ 4.3ghz PBO with a flagship RX 6900 XT, and 32 gigs of RAM, and SSD on Windows 10. I still get slowdowns or load chugs when new scenery pops up for the first time, and sometimes when exiting or entering a cut scene; this will happen to me on Vulkan or DX11, so there is no getting around it so far as I have tested. These issues will happen on any quality setting and frame rate, but are vastly reduced when playing with FSR 2.2.
My reasoning for thinking it's a bottleneck is evidence from a system analysis I did while playing some time back. I noticed that while the GPU was running at 100 percent, the VRAM held steady at a low level. I think the numbers were something like 4gb/12gb being used, and at the same time the CPU was under 12 percent on all 16 cores. The active cores were running BG3, but they were only just under 30-50 percent on 4 cores while a main core was running the game at 100 percent. It's weird for a CPU intensive game to not draw more resources from less than 6 cores, even in DX11. I also noticed that some of the compute effects were being offloaded onto the CPU, and this might be where the chunky frame rates are coming from.
I gave my metrics and info to Larian, but it's been months since then. They keep getting better at it though; now I can play on PC again, whereas before I couldn't stand it. I had to buy the game on PS5 just to try and finish my save game it was so bad. So, even if things look bleak now, just know that they are getting better. The performance for custom AMD rigs is getting better.
Sorry for the double post, but yes I noticed this as well. FSR 2.2 disables AA, and for the better. FSR 2.2 has a far superior AA mode than TAA. It WILL reduce the strain for particle effects and cases where your rig stutters for compute effects and lense effects. For some reason I keep forgetting the name of the setting.
A little more sysinfo would be nice.
Your system is a bit underpowered and on my older computer with a 6900XT and lesser processor had issues in Act 3, but none really show stopping before hand.
I was able to run the game decently at 1440p, if and only if....
-I disabled the Larian Launcher, or close it once the game has launched. This sounds dumb and unlikely, but just do it and see. Its a very simple fix and tends to fix many people's problems with perf in the game.
-If in Act 3, disable Dynamic NPCs.
Finally... What may really help you given your CPU has always has lagged in the single thread perf and 1080p perf is to ...
... bump the CPU priority of the application up to High, no higher, no real time, just switch it from normal to high. You can create a registry fix for that so you don't have to always manually bump it up each time you run the .exe.
Many people on older architectures and Win 10 are seeing CPU bound issues and the game doesn't multi-thread very well, if at all, and this can help some whom the disable launcher fix doesn't help and who aren't running the game off a spinning disk drive.
Hopefully for someone like you, those xbox changes to memory will help when that patch hits the rest of the builds and is released into broad adoption.
If you are running this game off a spinning disk hard drive, you will be having problems with perf.
Those weird drops are likely loading assets as you move around in the world. Take a look at drive usage when you play the game, its clear as day and very extreme.
That aspect was never really optimized in this game until the Xbox problems and need to launch there required them to figure some things out.
This game doesn't really use much active RAM because it needs to run on consoles. It swaps pages in a very extreme manner and moves loads of data from disk constantly especially when you move your characters.
This may be and is likely why you may be getting CPU bound, or if you are running on a spinning disk hard drive and not an SSD or PCI NVME based drive. You can try the slow drive option in the settings, no idea if that really helps as I have no computers in my life anymore with spinning disks save a home NAS with a few hundred TB of striped storage.
If your system pagefile and the game is on a spinning disk....sorry to say that's likely the big problem and your main bottleneck.
Windows does not, and has never, managed memory very well for something like this by default as its settings are more general purpose for typical users.
And yet I can reach 60fps average with a 6 cores of the same generation running at stock and teh same GPU in .... 1440p high.
Theres clearly something else than his CPU/GPU causing problems here.
Nope.
I'll try, thanks, eventho I don't really have complaints with around 60fps average. BG3 ain't a multiplayer shooter needing lighntning fast reflexes.
Still, if I get a few free frames I won't complain so thanks. also plan to swap for a 5800X3D later this month tho :D
https://youtu.be/dU5qLJqTSAc?si=j_Iye-_Dj8snO7MX
I used this one
This is a very important point, hence i mentioned it as well.
Very few games nowadays that have these sort of graphic quality will run well on a Hard drive.
Besides that, this user's whole comment is the most useful so far so i suggest OP take a look. However without more info and response, i doubt you'll get anything solved