Shadowrun: Dragonfall - Director's Cut

Shadowrun: Dragonfall - Director's Cut

View Stats:
Shajirr May 30, 2016 @ 1:41pm
Unable to complete the game due to a bugged gamestate
It happens after the fight with APEX, and seeing through all the dialogues.

The game goes into non-comnbat state, and stops responding to any in-game commands.
You can't move the character at all.
I can save the game, but attempting to reload the save that I just made puts me into a permanent black screen, so that I have to kill the game process then.

Whether by killing the process or exiting the game through the menu, any saves that I make after the APEX fight just disappear.

Reloading any last saves and completing the fight again leads to the same bugged gamestate, where the character just freezes in place and won't move.

Does anyone have any solutions to this?
Last edited by Shajirr; May 30, 2016 @ 1:42pm
< >
Showing 1-7 of 7 comments
Shajirr May 31, 2016 @ 11:32am 
Well looks like this is a widesporead bug, as I immediately found multiple mentiones of it occuring, and the devs never bothered fixing it... great

Been quite a while since the last time I saw a gamebreaking bug that completely prevents you from playing, certainly did not expect to find one in otherwise mostly fine game
Last edited by Shajirr; May 31, 2016 @ 11:35am
Shajirr May 31, 2016 @ 12:02pm 
Update: finally I managed to "resolve" this

The bug still occures with 100% accuracy for me, but it seems that it is time-based.

So after about 30-40 reloads of the save which I made right before stutting APEX down for good,
on last attempt I loaded the save, desummoned the spirit that I had just in case, activated last terminal, skipped through all cutscenes, and then quickly mashed "leave the area" option, and the game didn't freeze this time.

Waiting some time after the cutscenes guarantees that the game will freeze, but leaving the area before this occurs seems to be possible.

Last edited by Shajirr; May 31, 2016 @ 12:02pm
Came here for this exact issue. This is like a bad joke. Downright shameful on HBS's part.
Last edited by you can't run from the funk; Jul 10, 2016 @ 11:54am
Shajirr Jul 10, 2016 @ 1:00pm 
Yeah its very annoying that the devs, despite releasing what appears to be a successful sequel, just abandoned the previos game maintenance and never fixed this bug despite it occuring for so many people

Nothing brings my opinin of the game down so much as a bug which completely blocks the game progress and which isn't really fixeable or avoidable (reliably) without reloading much earlier game state. At least in a game like Skyrim or previous TES titles you can fix most quest-related bugs yourself through console (or even by mod patches), but for this game I did not find anything of the sort.
Last edited by Shajirr; Jul 14, 2016 @ 7:24am
obbillo Jul 14, 2016 @ 5:51am 
Great.. i've been stuck and annoyed on this mission for a week.. Didn't bother to check on this board cause I thought it was my computer that was the problem (it's been acting weird lately)
Also i didn't thing these kinds of bugs existed in quality games anymore, at least when it's been out for so long
Zadok Jul 15, 2016 @ 1:41pm 
Originally posted by White Spirit:
Update: finally I managed to "resolve" this

The bug still occures with 100% accuracy for me, but it seems that it is time-based.

So after about 30-40 reloads of the save which I made right before stutting APEX down for good,
on last attempt I loaded the save, desummoned the spirit that I had just in case, activated last terminal, skipped through all cutscenes, and then quickly mashed "leave the area" option, and the game didn't freeze this time.

That sounds like a bug I encountered as well. Thing is: it wasn't @APEX. Just casually browsing the sticky APEX thread I was under the impression that the APEX bugs revolve around saving too much (thus I stopped caring). Now I play w/o manual saves - which doesn't mean that I'd necessarily load any less than others.
Now in the case I describe (there were other instances) I certainly didn't load all that much as it was @Kesselhaus, right after the skirmish in front of the vault with that crazed troll. Same as you described: I managed to click the objective, the vault door, in the split seconds right after the fight & before it all tilted. I imagine it still tilted, so I probably could not have aborted my command even if I wanted too. In any case it was carried out and resolved the issue.
StingingVelvet Jan 13, 2021 @ 1:03pm 
This thread comes up on top when you google this issue, so just thought I would add a possible fix:

What fixed it for me was clicking on the door icon (which at first didn't do anything) and then going to the menu (top left button). When I left the menu, the door opened. Characters were still stuck, but with the door open I could now click the yellow level exist icon. Once again, nothing happened, but when I went to the menu and backed out again I got the level transition interface.

Give it a shot.
< >
Showing 1-7 of 7 comments
Per page: 1530 50