cancel
Showing results for 
Search instead for 
Did you mean: 

General Discussions

JohnRambo82
Journeyman III

Red Dead Redemption 2 is broken on AMD RX 6000-series (and 7000-series?) cards

Hello, I would like to report that this game on AMD RX 6700 XT 12 gb has some stability issues. The rest of the PC includes a Ryzen 7 5700x, RAM 32GB DDR4 3200Mhz, Samsung NVME SSD, 144 Hz FreeSync monitor, AMD driver 24.10.1. The game is set to 1920x1080 resolution, High/Ultra settings.

 

I'll start by talking about what happens with AMD Smart Access Memory enabled (the default setting).

The game with Vulkan (the default API) runs terribly, it has bad frametime. To "stabilize" the frames I have to enable Triple Buffering but it shouldn't be required with a FreeSync monitor (it doesn't happen with other games). The game uses all the available video memory but this causes the "unknown error FFFF" crash after a while (it can take even more than an hour for this to happen).

The game with DirectX 12 runs better, It's smoother and doesn't require Triple Buffering, but it has a problem with VRAM. The game performs a forced video memory dump whenever it reaches a certain limit imposed by the game engine. In the benchmark it is clearly visible where once the game reaches 6.1GB of VRAM usage, it suddenly drops to around 5.4GB causing a stutter, after which usage starts to rise again and the same thing happens over and over again. This happens often in populated cities like Saint Denis, very often, it is annoying.

 

With AMD Smart Access Memory disabled, performance is lower so I haven't tested it much.

DirectX 12 suffers from the same issues, it changes the maximum VRAM usage to 5.7gb which then drops to 5.0gb.

Vulkan has the same frametime issues but not the VRAM issue. In this case it uses about 7 GB of video memory, but the performance seems to be significantly lower and I don't know if it crashes.

 

So we have two graphics APIs and neither of them works well 😅

 

Some have found that changing the aiTextureMaxMem_3_Base value in the "gameconfig.xml" file located in "update_1.rpf/common/data/" from 2500 to a higher value (e.g. 4500) helps to avoid memory dumps. In my case it works in DX12 but it requires external software to be able to load the modified config file, so it would be better if Rockstar Games or AMD would fix this issue to make at least DX12 the API that works (I imagine figuring out what's wrong with Vulkan would require more work).

0 Likes
0 Replies