Problem with the Last Voyage of the U.S.S. Constitution side quest!

[amg]

Hello, I've been having this problem ever since my first playthrough of Fallout 4, but now I've given up on trying to fix it myself. Every time I approach the USS Constitution the ship crew are already hostile towards me. I have never been there before in this playthrough, I tried waiting 7 days but nothing changed. Please help. By the way, I sided with the institute (just incase that matters)

[ronr42]

If you have Garvey with you the robots will automatically become hostile. You can either not take Garvey or just stay back from him and the robots will only shoot at him and not you.

If you're wearing PA with telsa coils they will be hostile when you arrive. Get out of the PA before you get to the ship.

Those are the only 2 things that will cause them to attack when you approach the ship in a vanilla game.

Do you possibly have some mod that is causing that?

[amg]

Originally posted by ronr42:

If you have Garvey with you the robots will automatically become hostile. You can either not take Garvey or just stay back from him and the robots will only shoot at him and not you.

If you're wearing PA with telsa coils they will be hostile when you arrive. Get out of the PA before you get to the ship.

Those are the only 2 things that will cause them to attack when you approach the ship in a vanilla game.

Do you possibly have some mod that is causing that?

Strange... I never use a power armor and I had Curie with me as a companion.
I have some mods installed, they are however only terrain and weapon mods, I'll try deactivating them.

[ronr42]

Only other thing I can think of is that they Might be hostile if you did Nuka World siding with the Raiders. Got no clue if that would happen as I killed all the NW Raiders. It just seems that siding with them has the potential to cause problems with other quests.

[Simpson3k]

This is so unfair. Quest npc´s can attack him by default but we are cursed to be his eternal miniman general slave.

[amg]

Originally posted by ronr42:

Only other thing I can think of is that they Might be hostile if you did Nuka World siding with the Raiders. Got no clue if that would happen as I killed all the NW Raiders. It just seems that siding with them has the potential to cause problems with other quests.

As expected turning the mods off didn't change a thing.
I sided with the commonwealth in Nuka-World, so that shouldn't be the issue.
How strange.

[ronr42]

Originally posted by Simpson3k:

This is so unfair. Quest npc´s can attack him by default but we are cursed to be his eternal miniman general slave.

It's the witches at the Museum of Witchcraft that did it. Their ghosts got bored with just watching a deathclaw devouring intruders. So, they wandered through the Commonwealth placing curses on all unsuspecting Lone Wanderers. They knew in advance that the greatest curse they could stir up in their cauldron is the Curse Of Garvey!

[ronr42]

Originally posted by mijusth:

Originally posted by ronr42:

Only other thing I can think of is that they Might be hostile if you did Nuka World siding with the Raiders. Got no clue if that would happen as I killed all the NW Raiders. It just seems that siding with them has the potential to cause problems with other quests.

As expected turning the mods off didn't change a thing.
I sided with the commonwealth in Nuka-World, so that shouldn't be the issue.
How strange.

Sorry that didn't help. I'm fresh out of ideas what may be causing that.

[amg]

Originally posted by ronr42:

Originally posted by mijusth:

As expected turning the mods off didn't change a thing.
I sided with the commonwealth in Nuka-World, so that shouldn't be the issue.
How strange.

Sorry that didn't help. I'm fresh out of ideas what may be causing that.

Thank you for your trying

[ronr42]

You're welcome.

There is something you can try. First, verify the integrity of the game files, then try again. Second, go to Documents/My Games/Fallout 4 and delete the Fallout4.ini and the Fallout4Prefs.ini. Then verify the game files again and launch the game. That will create new .ini's.

Since your issue is quest related, I'm not sure deleting the .ini's will fix it. It is worth trying if nothing else works.

[amg]

Originally posted by ronr42:

You're welcome.

There is something you can try. First, verify the integrity of the game files, then try again. Second, go to Documents/My Games/Fallout 4 and delete the Fallout4.ini and the Fallout4Prefs.ini. Then verify the game files again and launch the game. That will create new .ini's.

Since your issue is quest related, I'm not sure deleting the .ini's will fix it. It is worth trying if nothing else works.

I'll try, thanks.

[ronr42]

Good luck. Hope you get it to work.

Last thought. You said you tried waiting 7 days, try fast traveling to Nuka World[it's a different world space]. Then go back to the Commonwealth and do a different quest before you go back to the ship. And start that by loading a save from before you went to the ship in this playthrough.

Now I'm Really fresh out of ideas.

[ronr42]

Read the last bug on the wiki;

http://fallout.wikia.com/wiki/USS_Constitution

Siding with the Institute will cause a BOS Lancer to appear and Ironside will become hostile and all bots will shoot at him. The Lancer can't be killed and the quest cannot be started. Are you sure the robots were shooting at you?

Since it's a bug, reloading a save a few times from before you went there might trigger the Lancer bug to not happen. Just a thought.

OOOOOOO! New thought. If it is the Lancer bug causing it, you might be able to remove the Lancer from the game. If you try, wear some very good armor or power armor and take plenty of stimpacks with you.

You will have to find the Lancer, who does not move once he appears. Walk up to him, open the console[tilde key ~], click on him and type markfordelete, then hit Enter and close the console. Now get away from there, fast travel somewhere then return. See if the robots are still hostile.

[Kittekassitar]

Fix for PC players: PC If before the quest starts, the robots are hostile, typing player.AddToFaction 0008c9db 1 will add the player to the faction, thus making the robots friendly, and allowing the quest to begin normally.[verified]
PC If the Lookout refuses to talk to you, type setstage MS11 55, which will start the quest, and allow the Lookout to speak again. [verified]
PC Playstation 4 Xbox One During the scavengers' first assault on the ship, the game's music may be stuck in an infinite battle loop even after the battle is over. One can fix this by saving the game, closing the application, then rebooting Fallout 4. The music should be back to normal upon resuming the game. Fast travel should also work.[verified]
PC Playstation 4 Xbox One The player can also ride the ship to the destination and survive by using a companion to activate the auxiliary generator in the last step and then sprinting to the dinghy elevator at the back of the ship (one must reach the dinghy before the companion activates the switch, try sending them to a spot down a couple floors first and then set the command to activate the switch. The hatch into the USS Constitution remains accessible until the countdown ends and the ship begins moving. Talking to Ironsides inside the ship while in flight may cause a crash of the game.[verified]
PC Playstation 4 Xbox One It is possible that the scavengers will not attack the ship after the player has talked to Ironsides, making the quest uncompletable. A possible workaround for PC is typing setstage MS11 200 in the console, which will continue the mission by setting the scavengers to attack. Typing setstage MS11 840 will set the quest to the very last stage.[verified]