Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
i should also mention im on acer nitro 17 laptop rtx 4060 windows 11... yeah i tried getting win7 on a separate partition but that's impossible
1) Just double check that the game is in fact using DX11 and not 12
12 is just a spaz fest of i think i will crash here.
I do wish the devs would revisit BL in an act of love, and rewrite the DX12 implementation
and then compile the exe for 64bit
2) try a game files validation
3) If validation does not help, temporarily rename your documents\my games borderlands goty folder
What this will do is temporarily make the game start with blank configs and no previous save files, so you can check if one is possibly corrupt etc.
If that seems to work, then you can try to see which the problem was, configs or save game
by moving the save game back and testing if it still works.
Should not crash, we got 10 machines here (literally) ranging from potato machines that don't even have GPU's to actual decent gaming desktops, and it runs on all of them.
Not what you want to hear but, it may be your OS install.
And yea, i have had people IRL insist, my PC is fine this game sucks it's broke, not touching my PC.
So i took an HDD of mine, plugged it in, did a clean windows and drivers install.
Installed current release of VC++ runtimes, then steam, then BL2 (minus HD textures DLC)
and it ran and ran and ran.
I said Welp, now you know what you need to do.
This is one reason why any game that recommends tweaking any aspect of the OS
or anything that does not pertain to only that game itself only when it is running, i say gtfo.
Just comes back to bit you later when if affects something else.
Also both installs had HD texture pack. Another note is last i played i think I was using 2700x and 1660ti. (When HD pack released)
HD texture pack will make it crash, guaranteed at some point you will begin getting crashes
Error will be out of video memory
Reason:
DX12 rendered is F'd.
BL2 has a very early implementation of DX12 and it was buggy as hell, and remained that way.
And DX12 renderer is the only one that can virtualize video RAM to make 4gb available to a 32bit app (doesnt matter if you 4gig patch the app, that only affects system RAM use.)
So that forces you to use DX11
DX11 is incapable of virtualizing VRAM to present 4GB of it to a 32bit app
And the HD texture pack spikes VRAM use to over 2GB.
Not always, it is sporadic, but it builds up and overflows
So, you ditch the HD texture pack
Which is actually fine because
Much of it is broken.
Animated textures, that are not animated
Textures that are just plain bad and devoid of detail etc.
So removing that is no loss at all, it is actually an improvement not to have it honestly.
DX12 sadly is just too jacked up.
It just randomly crashed with a DXGL_ type of error that basically means
Your GPU just disappeared, as if the driver crashed
Except the driver never crashed, the renderer did.
It is a shame because people with lower end GPUs could benefit from DX12
In your particular crash, i wonder if something was jacked with the cut scene media/data
that somehow did show up in file validation?