Game-breaking bug: can't dismiss x6-86. : Fallout 4

» Fri Jan 15, 2016 7:31 pm

I can no longer stop x6-88 from following me around, even if he is not my companion. This is a game-breaking (or at least, story-breaking) bug. Some details in spoiler tag.

I have tried switching to another companion. I am given the menu to select where to send x6, but he does not go.

I have tried dismissing x6 outright, with same results as above.

I have tried murdering x6, which doesn't work for obvious reasons.

I have tried saving the game, quitting, and doing a full reload, and the behavior persists across game restart.

After dismissing or switching companions, x6 continues to follow me physically, and via fast-travel. His menu options have him asking me "is it time to go again?" - so he clearly knows he is not supposed to be my companion any longer.

I have found this bug reported on the Fallout wikia under the x86 entry. It was marked as Console and verification needed. I set it to verified, and added the PC platform.

Spoiler

I am at the "Kill Desdemona" stage of "End of the Line".

I am at the "Talk to Desdemona" stage of "The Nuclear Option" and "Rocket's Red Glare".

I used x6-86 as my companion during the Rocket's Red Glare quest.

Therefore, I can no longer continue the Railroad storyline because x6-86 always comes with me, turning the Railroad hostile.

» Sat Jan 16, 2016 9:40 am

That's a gllich. And if that happens: Fix is unknown.

» Sat Jan 16, 2016 12:32 am

Reload earlier save time...try biffing him on an earlier quest.

» Sat Jan 16, 2016 4:47 am

Yes I know it's a glitch. That's why I reported it.

» Fri Jan 15, 2016 7:49 pm

I understand how to workaround the bug by throwing away hours of gameplay. As a professional software engineer, I don't consider that to be an acceptable workaround. So, now it's up to Bethesda whether they want to fix it.

» Sat Jan 16, 2016 1:08 am

They're not going to fix it in time for your next play session, can guarantee that

» Sat Jan 16, 2016 12:40 am

lol. The answer wasn't from me. It's from Fallout 4 wiki.

» Sat Jan 16, 2016 9:10 am

A professional software engineer should know to save often. Reverting to a prior save before the bug appeared is likely your only option.

» Fri Jan 15, 2016 8:09 pm

Should, and do.

Sadly, even though I have saves every 20-30 minutes, I have to roll back ~8 hours (of gameplay) to get to a state that is not horked. You see, it's not about how often one saves, it's about how long has the game (and thus the save files) been in a horked state before you try the bugged activity and notice.

Anyway, I really wasn't looking for random people on the Internet to tell me what I already know: that it's a bug that no one is going to fix before my interest in the game has faded into "oblivion" (heh see what I did there?). Rather, I came here to post a bug report in the "bug report" forum (shocking).