Naaa, “Intel Pentium required” ringing any bells? Even if the highend 486 would have been fast enough…
1 Like
So true, this release is a new record for incompetence at all
If we didn’t “blcth about it” they wouldn’t be fixing the problem, so you’re welcome
2 Likes
Pre ordered on 20th of February and waited for more than half a year for this.
never again.
1 Like
Same problem! i-760, 1060 3 GB.
After patch - black screen,
Error code: D99CC4C5-78DF-4A86-AA02-8972F2CCF40E
blz-log.txt:
9/25 09:15:19.798 [Render/4] [<>:0]: NVSDK_NGX_D3D12_Init failed, error code: -1160773631
1 Like
same problem here, last night i asked for refund (bought 4 weeks ago) and got confirmation today.
Decided to not go with the pc version and bought the ps5 version. Works great and no issues for now.
Here is mine after black screen…
00530728-E037-4836-BCC0-A06ECB1BD53A
Black screen and error message after update: 362F520F-EA1C-4955-B70D-E3A137024286
Error popping up now…
Please describe what you were doing when encountering this error:
Complaining about the DR2 launch on the forums
3 Likes
I respect your decision ,i understand the frustration though.
But i am not going to because they will keep patching/investigating until everyone can play it.
What happens when windows 11 gets released? D2R may have some problems then as well just like every other game.
I have faith in Blizzard ,every time a new game gets released we can expect issues regardless of what company makes it… that’s just the way things are.
The problem is that they have hired the same windows 11 developers that forced the use of new hardware… so this problem will be automatically fixed on windows 11.
You are good. It’s just BLIZZARD! My friend has a brand new $3.5K PC with all the twerks and meets all the system requirements to play D2 Resurrected and it still crashes at the third window from start up, that’s as far as we get before we get returned to the start button. Blizzard might come up with a patch in a week or two. I have a i5 PC that meets all the minimum requirements to play D2 resurrected and the same stuff happens. There are millions of players that have the same problem that we have, its only the selected few that have the privilege to play first, as Blizzard see’s fit. That’s how Blizzard rolls. they do not care about the common player as long as they (Blizzard) get’s their money. $39.99 is no sweat off my back, keep the money Blizzard choke on it! Sooner or later you will have to let us play!
3 Likes
Thats the error i get now 4F652E6B-03B4-4CFF-A59C-11731CE7CEAB
1 Like
Stopped gaming altogether after the original Diablo 2. Heard the game was back. Decided to buy and download the game. Is this how game releases are these days??? Release a game and hope it works for everyone? LOL WHAT A JOKE. Its been 21 years guess I can wait a few more weeks LOL…
1 Like
Same issue for me. I played the beta fine even played the game yesterday, but today games crashes when I join a game and now started crashing at the loading screen…
Problem is I probably have to upgrade to play this old a$$ game. I might just go back playing the old a$$ version of this old a$$ game instead, were it not for my friends playing the remaster. It’s so absurd because the beta worked just fine.
this is not the same issue we have in this thread
Oh damn how many issues are there. Aight I go look for another thread then, gl.
Why isn’t this game crossplay across all the platforms? It would solve the problem temporarily for me atleast, and it makes 0 sense to restrict it when you can swap save files.