Diablo 2: Resurrected will test your resolve to boycott Blizzard

Yeah no crashes here either. And I haven’t even had a server problem in the last few weeks.

Not a bad idea, I’ll give that a try. I know I had seen other posts in the forums with the same type of crash. Frustrating because it will work for 20-30 minutes before crashing. But ultimately, having to rerun the same areas over again because all the enemies respawned isn’t fun when it’s involuntary.

I’m sure you’ve tried all the usual driver updates, shut off background programs, run as admin, but if you haven’t could try that as well. 9 times out of 10 times, stuff like this is a driver conflict. I have a fairly crappy comp and vid card, and I haven’t ever had a crash. That doesn’t mean much, because component makeup on individual comps can be such a black hole to try and troubleshoot.

What vid card do you run?

The other thing you could try, would be to set all the game graphic settings to low, and see if you still get crashes. My guess would be, your vid card/driver is hitting some particular special effect that doesn’t happen all the time, and it may be related to one setting or another. If you can play without crashing on the lowest settings, add back the stuff one at a time, you might be able to figure out what the specific problem is.

I wasn’t quite Irene the Infirm last night, but I created a Sorceress and trying to get past the first couple of quests.

Blood Raven kept kicking my ass, so I kept retreating back to town and trying new strategies.

First I went in there with 3 Fire Bolt, where I got her down to half health, but ran out of potions and retreated.

I went back with more potions but Blood Raven got a lot better about interrupting me from firing off my Fire Bolt with her arrows. So I retreated again when I was out of potions.

Hmmm. So then I tried this sword that I found. That should be able to kill Blood Raven, surely. It did decent damage, and it was a rare sword, it had a bunch of enhancements, including cold damage that should slow her down.

I went in and finally got close enough, but started firing arrows and kept interrupting me, and I couldn’t drink potions fast enough to live.

D. E. D.

Blood Raven is the hardest fight in Act I, unless you’re twinking right away.

The best thing I’ve found is to a) get into a rhythm of manually dodging her shots, since she doesn’t attack all that fast and b) be skittish and run the hell away. It’s not uncommon for her to hit for 25% or more of your health at that point.

I straight up won’t fight her unless I have some kind of decent weapon. It’s worth tooling around until you find something with sockets or a couple decent mods.

Anyone else having the issue where your mercenary just decides to stop moving? Not pathfinding issues, though there’s plenty of that. Just decides she ain’t going anywhere. Have to waste a portal scroll just to wake her up.

Yeah, merc AI ain’t the best. If you move far enough away she’ll teleport to you and that should restart her AI.

Any teleport skill instaports your minions to your same destination, btw. Sometimes a useful thing to know.

Btw, I tested Leap Attack yesterday on the controller. It’s not good. Basically how you target enemies right now by facing them, that’s how leap attack is targetted. So it’s not a good skill to get you out of any situation like it is with the mouse. I forgot the excellent term Adam used upthread, escape skill? It’s not a good escape skill with the controller.

Now I’m really curious how they implemented Teleport on the controller. The same useless way as Leap Attack?


The funny thing, of course, is that Grim Dawn did it about as correctly as you can, years ago. But then everything about GD’s controller interface is better than D2R’s, so big shock I guess.

My mercs haven’t met a fire or poison cloud that they didn’t want to run through at least once, even if it’s in a wildly out of the way spot.

The ranged mercs have exceptionally stupid AI. That alone is enough to make the melee mercs better, but then there are so many additional reasons the melee mercs are better on top of that, heh.

Heh, yeah, my Amazon did the Tower last night, and Countess’ opening move was to put a firewall down, and my rogue merc stood in the firewall the whole time (and died, of course), leaving me without a companion through the whole battle.

Yep, tried repairing the install, upgrading graphics drivers (980ti), running lower settings, reboot entirely before playing, etc. Hidden among all the server whining on the forums are a subset of people who also get pretty consistent crashes. Seems like it’s an all or nothing thing with this game.

My favorite was when I stopped for a moment to take a few bites of food in a lull and observed my idiot merc just stand half a screen away, idling all while some skeleton wandered from another direction off screen and started pelting me with arrows until my character died. Merc did not move at all from that spot.

Are you getting crashes with offline characters as well?

I’ve exclusively been playing offline.

Weird. The only thing I’ll add is: are you using some kind of overlay program like Geforce Experience? If so, close that. In fact, try closing all extraneous programs just to rule out any kind of software conflict. Mouse software, etc…

And to add to this, anti-virus or other similar types of third party programs can also cause applications to crash.

They say it’s partly because more people are trying to sign on than ever did for classic Diablo 2. Well duh, you guys got rid of the option for LAN play, so of course they are. Back in the day I knew a LOT of Diablo 2 players, and none of them played on Battlenet. But now there’s no other choice if you want to play multiplayer eventually with any of the characters.

Everybody I know played on closed Battle.net, because open and LAN games were full of cheaters and dupes.