go into ~(command prompt on PC)(TGM=god mode)(YCM walk through walls) then use (Killall) needed to use when near the mechanist as it was the only way I could get on with the game.
I did too orginally, then found the no walls mode so I could finish it. Use the~the TCL(no collision) to get in the control room where there Mechanist is. Then I used killall to finish him(only way for me). Here's a link to cheat codes(copy n paste)www.vg247.com/2015/11/16/fallout-4-console-commands/
So I found another work around instead! I was skeptical but heard the following: Completely Uninstall Fallout 4 including All DLC’s. Far Harbor, Nuka World etc. and of course the Automatron DLC (which is where the glitch is). Then reinstall Fallout 4 and each DLC (except Automatron). Start a game and when it loads use “continue”. It will respawn you at Sanctuary at the level you were on before going in to face the Mechanist. Do a save game now, and then load the Automatron DLC to be able to replay if you want. It worked for me! This time I’m going back in with highest computer hacking skill and gathering the 3 halotapes to avoid having to fight the Mechanist.
Haha thanks. I just gave up 3 years ago, and reloaded a save from around 30 play hours earlier. Saved before i went in and it worked 2nd time around no problem.
Noel Immermann nope. I just reloaded a previous save, my save was like 20 levels prior so it sucked.. but i made it back and saved again at the door right outside the fight and made it through the 2nd time no problem.
@@I_FITZ i had to use the second way in order to do it. Nick was not able to hack the terminal, therefore i had to level up realy quick to get the master perk in hacking and load the three holotapes found in the facility.
go into ~(command prompt on PC)(TGM=god mode)(YCM walk through walls) then use (Killall) needed to use when near the mechanist as it was the only way I could get on with the game.
Philip settimi Ps4 doesn't have console commands, sadly.. as I wouldn't be stuck here anymore lol.
Id teach it to fly, I had to go back to level 54 from 70 as something already cause a glitch. Isn't there an ^V thingy still on PS4?
Philip settimi nope we got shafted, completely. I had to go back to lvl 53.
I did too orginally, then found the no walls mode so I could finish it. Use the~the TCL(no collision) to get in the control room where there Mechanist is. Then I used killall to finish him(only way for me). Here's a link to cheat codes(copy n paste)www.vg247.com/2015/11/16/fallout-4-console-commands/
Philip settimi yes that is a solution for people playing on PC, however this is on Playstation 4.
So I found another
work around instead! I was skeptical but heard the following: Completely Uninstall Fallout 4 including All DLC’s. Far Harbor, Nuka World etc. and of course the Automatron DLC (which is where the glitch is). Then reinstall Fallout 4 and each DLC (except Automatron). Start a game and when it loads use “continue”. It will respawn you at Sanctuary at the level you were on before going in to face the Mechanist. Do a save game now, and then load the Automatron DLC to be able to replay if you want. It worked for me! This time I’m going back in with highest computer hacking skill and gathering the 3 halotapes to avoid having to fight the Mechanist.
Haha thanks. I just gave up 3 years ago, and reloaded a save from around 30 play hours earlier. Saved before i went in and it worked 2nd time around no problem.
Still not fixed
Noel Immermann nope. I just reloaded a previous save, my save was like 20 levels prior so it sucked.. but i made it back and saved again at the door right outside the fight and made it through the 2nd time no problem.
@@I_FITZ i had to use the second way in order to do it. Nick was not able to hack the terminal, therefore i had to level up realy quick to get the master perk in hacking and load the three holotapes found in the facility.
have you found any solution so far?
Nope. Nothing I have read or been suggested has worked. Bethesda support has no idea what to do, or if and when there will be a fix.
damn, thanks for the response though. i just started a new account and hope that there'll be a fix