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
i run perfectly on my I5 + GTX1660 Super + 2tb of storage
Half and half so SAM isn't the problem. It's the game engine NOT Wiping old Vram data as you move from section to section of the map.
If you stay in the same area or die alot you could play for hours with no issues.but I rarely die and I move around the map ALOT.
What I started doing was to save the game,then reload that save.doing so wipes the vram and allows you to play crash free but you just have to keep msi afterburner running and an eye on your vram usage..
Tried both Vulcan and DX12 and if anything dx12 crashes quicker..
Running smooth isn't the issue. I'm near max settings in 4k at a locked 60fps.
The game engine lacks Proper Vram management and I suspect that 4k combined with me rarely dieing AND Traversing the map as often as I do is why the vram fills up so quickly.
Regardless Rockstar should have coded the engine to wipe the vram.as it is now the game will literally try to store EVERYTHING about its self completely unchecked within Vram,and for me atleast once it gets up around 15gb I've had my whole pc bluescreen with the windows :( ,black screen,driver crash,completely shutdown and restart my pc,crash the game and throw up error codes and a whole host of other crashes.
But since I realized what was going on and started saving then reloading that save when my vram gets to around 12gb I've had ZERO crashes..
You are most likely playing at 1080p or lower and at that resolution the vram usage will be much smaller then compared to 4k and or maybe this bug doesn't happen on lower settings and or resolutions..
Did you even read the OP?
In real time I watched the Vram climb to nearly 16gb from simply riding my horse across the map.not a single time did the game clear any of that vram,THAT IS A TEXT BOOK MEMORY LEAK!! And it's happening because the games engine IS NOT Purging any older unnecessary data out of the vram.
Now if this is a bug only on Amd cards,or at 4k,or only Max settings idk I haven't tested it that far.but if you search online you will find a TON of people that have crashing issues with this game.
Since I Discovered this,I now save and then Immediately reload that save,and again watch in real time as the game clears the vram while reloading and I've had ZERO CRASHES since doing this.
Yet somehow I have misunderstood something?
The end user should NOT have to run 3rd party software and keep track of this sorta information just to play the game.
Stuff like this is what is wrong with the gaming industry. These devs release half baked products that require the end user to fix or find work arounds just to use the product they spent full price for and NOTHING happens to these companies.
Instead of saying I am mistaken or that I do not understand, why don't you run your own tests and try and disprove me with Evidence?
When game came out i had zero crashes.
Perhaps its Vulkan causing the problem? give DX12 a try and see if that helps, I don't see any mention of it in your OP
Same here, I've got a GTX 1080 and have most of my settings at ultra/high at 2560x1440 QHD and have no issues when playing for 5-6+ hours at a time . . .
I was getting some micro-stutters at times, but switched back to DX12 and updated my drivers and that fixed it for me.
My system is a 4.2ghz i7-7700K with 32GB of ram and liquid cooling, so it can take the load with no strain, but I haven't noticed any issue at all with vram leaks . . .maybe your GPU is the issue?