"Restoring order" bugged

[Von Shadowsong]

So I'm revisiting this game for the first time in years, and oh goody, the DLC's main quest is broken.

TLDR: I hate this DLC and just want to be done with it already, please send help.

I'm trying to complete Restoring Order. I've talked to the Mechanist and convinced her to stand down. She gave me the password, but I can't unlock the terminal. Any time I try, I get stuck~ it's like I'm walking toward the terminal on a loop, and nothing happens.

This issue is not mentioned anywhere on the Wiki page, despite Google turning up a ton of complaints about it, and none of the proposed fixes have done anything for me. I've reloaded a bunch of times, and I tried using console commands (tcl and unlock specifically) too, but those don't work either.

I haven't changed anything since the last time I played~ no new mods or PC parts, so I'm not sure how to fix this other than the completeQuest console command (although that just completes the quest, it doesn't unlock the terminal).

I'm about ready to tear my hair out. Any suggestions?

[SuperSledgeNY]

Are you running the game higher than 60FPS? I found a thread here in the forum that looks like your issue and running the game higher than 60FPS seems to trigger it. See if capping your FPS to 60 will fix it.

Here's the thread if you want to read it:
https://steamcommunity.com/app/377160/discussions/0/392184522702765062/

BTW, running this faster than it was designed for can and will cause all kinds of weirdness, sometimes not right away but usually when you least expect it. It's recommended that you cap your FPS at 60 for this game,

[Shadowrun]

i've experienced bugs with this quest too. not this bug i don't think, but you might be able to advance the quest using console commands. first we have to know if you have all the DLC or not and we need to know what # mod slot holds the automatron DLC

default load order if you own all the DLC is

PLUGINS:
[00] Fallout4.esm
[01] DLCRobot.esm
[02] DLCworkshop01.esm
[03] DLCCoast.esm
[04] DLCworkshop02.esm
[05] DLCworkshop03.esm
[06] DLCNukaWorld.esm

so assuming this is the same for you the slot number for us here will be 01 when making the form ID. the form ID of this quest is: xx0010F5. xx we will replace with our DLC slot number 01 so in order to manage this quest in the console we will need to call up quest by form ID number: 010010F5.

what i would do is (save your game first and be prepared to use it), try this in the console

setstage 010010F5 900

now see if it lets you access the console. if not then try this line to advance the quest tot he next stage

setstage 010010F5 1000

now try the console. if it doesn't work try talking to ada to see if the quest is now completed. if not then roll back to the save game and try another solution. this one didn't work.

also if it doesn't seem to work it's possible your robot.esm is in a different mod slot, not # 01.

https://fallout.fandom.com/wiki/Restoring_Order

[Von Shadowsong]

Originally posted by SuperSledgeNY:

Are you running the game higher than 60FPS? I found a thread here in the forum that looks like your issue and running the game higher than 60FPS seems to trigger it. See if capping your FPS to 60 will fix it.

Here's the thread if you want to read it:
https://steamcommunity.com/app/377160/discussions/0/392184522702765062/

BTW, running this faster than it was designed for can and will cause all kinds of weirdness, sometimes not right away but usually when you least expect it. It's recommended that you cap your FPS at 60 for this game,

Thank you! You indirectly solved this for me, lol.

I was too tired to go mucking around with my settings, but I had a look at that thread you posted and someone mentioned switching to windowed mode to fix this issue. So I did that and was able to complete the quest.

I'll keep that thread, and the info Shadowrun posted, handy in case this happens again. Thank you both so much!

[SuperSledgeNY]

My pleasure :)

[Shadowrun]

good job, solving it without a console command is the better solution.

[Mord Fustang]

Originally posted by SuperSledgeNY:

Are you running the game higher than 60FPS? I found a thread here in the forum that looks like your issue and running the game higher than 60FPS seems to trigger it. See if capping your FPS to 60 will fix it.

Here's the thread if you want to read it:
https://steamcommunity.com/app/377160/discussions/0/392184522702765062/

BTW, running this faster than it was designed for can and will cause all kinds of weirdness, sometimes not right away but usually when you least expect it. It's recommended that you cap your FPS at 60 for this game,

Thank you a thousand times, my friend. FO4 has been bugging me for years and I've tried all kinds of things to resolve it, but this is by far the best solution of all! The game runs so much better at 60 FPS than any other - higher or lower.

[Chronocide]

Originally posted by Von Shadowsong:

So I'm revisiting this game for the first time in years, and oh goody, the DLC's main quest is broken.

TLDR: I hate this DLC and just want to be done with it already, please send help.

I'm trying to complete Restoring Order. I've talked to the Mechanist and convinced her to stand down. She gave me the password, but I can't unlock the terminal. Any time I try, I get stuck~ it's like I'm walking toward the terminal on a loop, and nothing happens.

This issue is not mentioned anywhere on the Wiki page, despite Google turning up a ton of complaints about it, and none of the proposed fixes have done anything for me. I've reloaded a bunch of times, and I tried using console commands (tcl and unlock specifically) too, but those don't work either.

I haven't changed anything since the last time I played~ no new mods or PC parts, so I'm not sure how to fix this other than the completeQuest console command (although that just completes the quest, it doesn't unlock the terminal).

I'm about ready to tear my hair out. Any suggestions?

I suggest going back to an earlier save, or just reloading the game after letting your PC rest for a while.

I've done this quest recently and it worked fine for me.

There is more than one PC in the mechanist's lair, perhaps you are doing the wrong one?

[hot.bean.dip]

I was having this issue as well but what i did was that i put ToggleCollision into the console command and used the computer.