Dry Steppes Side Quest 'Fury Against Fate' Is Still Bugged

[Moriendor-2702]

UPDATE on my original bug report: The quest is even more buggy after the July 6th patch.

After you talk to Ealda inside the 'Wasting Hollow" dungeon, the barrier inside the dungeon called ‘Gore-soaked barricade’ is now invulnerable and can not be damaged nor torn down to reach the actual cannibal feeding grounds.

Please (try to) fix again!

[VitaKaninen-1422]

Did you try these instructions as a workaround?

Fury Against Fate Side Quest Bug

Can confirm limiting your FPS is the workaround for this: Credit here: https://www.reddit.com/r/diablo4/comments/14o2o27/quest_fury_against_fate/ There’s a solution that works 100% of the time make sure your game is in windowed or borderless window set the minimum background fps to 1fps relog outside of the cave click on the cave entry and tab out, wait until everything has fully loaded at 1fps start the conversation and tab out again wait until they start shouting, then you’re safe to cont…

Fury Against Fate Side Quest Bug

Finally found the thread and person where I read about this. It works btw. EDIT 26th July: Did it in seasonal. When you are in front of the cave you change background FPS to 1. Click cave then instantly alt+tab for 20 seconds. other than that nothing else matters (very likely). If it doesn’t work you can try again and also alt+tab right after you click on the npc until they scream (and also stick to lower side of screen from when you load in the cave until NPC click) but I don’t …

[JonathanS42-2259]

Agreed, still bugged after 1.0.4

Completed event outside, enter dungeon, start dialog, barricade highlights as breakable (red outline, health bar) but appears invulnerable (no damage numbers appear when attacking).

After dialog ends red dots appear on mini-map but crane tribe NPC remain stationary. Also rogue shadow step unable to bypass the barricade either (as no monster available within range)

Leave Dungeon into new event outside, ignored that and re-entered, dungeon remained in that bugged state and did not reset.

Leave Dungeon then Leave Game, Start Game into new event outside, ignored that and re-entered, dungeon was reset, but same behaviour as before.

EDIT
…much prefer D4 team to fix…

As suggested above, I did this:

While outside dungeon

1. change Options-Graphics (remember to note current settings for later)

• windowed i.e. not ‘fullscreen’
• limit cut scene=checked (=30 fps)
• foreground fps = 30
• background fps = 1

2. save Options etc., resize window (eg 50% screen)
3. back in game, press CTRL-R to get FPS displayed in bottom left corner
4. click on Dungeon entrance, then ALT-TAB to desktop / another open app
5. while the Dungeon loads the a loading screen is shown and FPS should be 1
6. when the Dungeon appears, ALT-TAB back to the game
7. click the NPC to start the dialog, and again ALT-TAB to desktop / another open app
8. when the dialog ends, the NPCs will charge the barricade
9. ALT-TAB back to the game and join the fray
10. if multiple waves of monsters then Dungeon has run correctly
11. go back to Options-Graphics and reset those settings to original (playable!) values
12. save Options etc., return to game and continue

OK, so not the full D4 graphic experience for a few minutes

My PC is running ‘Low → Custom’ settings (fullscreen, cutscene FPS enabled, 60fps/8fps), not sure why turning down FPS even further helped

[Moriendor-2702]

Thanks for the hint . I actually went with another workaround from here and used the ‘Clumsy’ tool to set my ping to ‘250’. I was finally able to finish the quest with my artificially “laggy” connection .

I guess the workaround you posted is similar in concept. You basically have to artificially teleport your PC or your Internet connection back into the 1990s. Crazy… but it worked.

It’s a little disappointing that Blizzard have not fixed this yet. As far as I can tell, it has been reported numerous times but still no official fix.

@JonathanS42 Try the one from the link in my post. According to the Reddit posts, it seems to have worked for many people and I can confirm it as well. The ‘Clumsy’ tool can be downloaded from reputable websites and is safe and very easy to use.

[Kain-2376]

The fix still works in since last night?

Also, it’s supposed to be invulnerable (until they attack it, if they attack it).

Also, this will all (presumably) go away when they add the DirectStorage SSD tech thingy that’s already partially in there.

[VitaKaninen-1422]

Only way to know is to try it…

It is not a guaranteed thing, and it probably does not work for everyone.

[Moriendor-2702]

@Kain-2376

The fix still works in since last night?

Yes, it works. I finished the quest with the ‘Clumsy’ tool workaround after the July 6th patch (it is July 7th here in EU) this morning.

I tried the quest multiple times before (after almost every patch) and before the July 6th patch, I always had the problem that after breaking down the gore wall and after killing all the initial mobs, the quest would not progress.

The invulnerable gore barrier was actually a first for me after the July 6th patch so I thought it was a newly introduced bug but it seems like some of you have had this problem before. I had not. The barrier was never the problem but the subsequent parts were.

I was skeptical because the workaround sounds a little crazy but if you look at the Reddit thread it has worked for many people, myself included since this very morning .

If anyone is stuck on this quest, it may be worth a shot or try one of the other workarounds posted here or elsewhere. I can personally only 100% confirm that the ‘Clumsy’ thing worked for me on the morning of July 7th CEST time.

[Dexter-13781]

Yes please fix. I shouldn’t have to do work arounds to enjoy the game. While you’re at it make the quest journal show which quest are finished and which ones are not.

Thank you. It’s a great game.