Can no longer steal landed ships

[Bleys Albion]

Anyone else having this problem?

I've hit a situation where every ship that lands now has no landing parties exiting, and the boarding ramp is shut so you can no longer board and steal the ship. I went back a couple of days in my game (I'm at lvl 62, and I stayed at lvl 62 but a few days earlier) and I managed to grab a few ships, and then the same situation.

It seems to be only/mainly pirate/bad guys ships since I can sometimes have UC, colonist or other 'good' NPC ships land which I CAN board.

And also I am constantly being bombarded by Starborn ships, almost every time I try to reload the game to RNG a decent ship landing, THEY turn up! I have deliberately avoided killing them since I thought it might have been the trigger for why I can no longer board pirate ships, but now doesn't seem to have made any difference.

*** EDIT ***

I was in orbit around a moon and got jumped by a pirate ship asking me to pay a ransom or be destroyed. This time I fought it, blew the engines and docked and boarded it. Empty! Nobody onboard!! It seems all instances of the pirates either on ground or in space are broken for me. :o(

[WarRaven]

I'm having similar issues stealing ships on the ground(havent tried in space yet) If I try and board and kill all the pirates in the ship it wont let me in the pilot seat until I take care of all of the pirates on the ground. If I un-board and kill that last pirate the ship takes off(with no one aboard) even if I manage to get on the ramp as its taking off I can no longer get into the ship and usually have to boost pack to the ground (or fall to my death) This use to be my favorite way to get ships as in space my weapons tend to blow the pirates away too fast

[Fanto]

This bug occurs when a corrupted starborn ship (in my case, a V model) lands on the surface of a planet. From then on, all hostile ships will no longer see their crew when you board them, and their docking bays will no longer function when they land on a planet. This bug seems to occur over time, and nothing can be done about it. Capturing ships seems to speed up the process, but it's bound to happen sooner or later. It's as if there's a maximum number of boardings to be made before the bug arrives. Once the game has been corrupted by this bug, the only way to get rid of it is with an NG+, but it's likely to come back with time in this new game...

[shokwavxb]

I ran into the same issue (ramps not dropping) this past weekend. I'm able to board starborn ships now (not NG+) but I never see starborn leave the ship when it lands anymore. I'm at 165ish hours and level 74(?). Love to take ships from the ground. This bug has killed that way of making credits for me. Ran into a bot bug in outposts too. I stopped playing the past few days. Kinda killed my experience for now. Loved the game until now.

[Bleys Albion]

Originally posted by Fanto:

This bug occurs when a corrupted starborn ship (in my case, a V model) lands on the surface of a planet. From then on, all hostile ships will no longer see their crew when you board them, and their docking bays will no longer function when they land on a planet. This bug seems to occur over time, and nothing can be done about it. Capturing ships seems to speed up the process, but it's bound to happen sooner or later. It's as if there's a maximum number of boardings to be made before the bug arrives. Once the game has been corrupted by this bug, the only way to get rid of it is with an NG+, but it's likely to come back with time in this new game...

Hmmm ... wonder if avoiding the main storyline will leave the starborn out of the loop ... perhaps might allow you to keep going a bit longer in the first/main game. I've started a new character to see if that will solve the problem, I'll keep going with this until either I get to a later level without any issues, or the problem re-appears. It put a bit of a sour note to the enjoyment of the game, the immersion factor gets completely derailed.

[evnant]

Originally posted by Bleys Albion:

Originally posted by Fanto:

This bug occurs when a corrupted starborn ship (in my case, a V model) lands on the surface of a planet. From then on, all hostile ships will no longer see their crew when you board them, and their docking bays will no longer function when they land on a planet. This bug seems to occur over time, and nothing can be done about it. Capturing ships seems to speed up the process, but it's bound to happen sooner or later. It's as if there's a maximum number of boardings to be made before the bug arrives. Once the game has been corrupted by this bug, the only way to get rid of it is with an NG+, but it's likely to come back with time in this new game...

Hmmm ... wonder if avoiding the main storyline will leave the starborn out of the loop ... perhaps might allow you to keep going a bit longer in the first/main game. I've started a new character to see if that will solve the problem, I'll keep going with this until either I get to a later level without any issues, or the problem re-appears. As https://steamcommunity.com/profiles/76561198151354508 said, it put a bit of a sour note to the enjoyment of the game, the immersion factor gets completely derailed.

so im doing a fresh game and i havnt talked to sarah to start the old neighborhood, justto the point where you can say "let me think about this" then started leveling via exploring and board missions, havnt had it start happening yet, i usally run to, wipe out, board to steal every landed pirate ship when im doing a planet side bounty and i board,kill and steal the last ship standing in my ship bounties and it still hasnt happened. level 70 now, 40 ish hours on the fresh game

[Brome]

Originally posted by Fanto:

This bug occurs when a corrupted starborn ship (in my case, a V model) lands on the surface of a planet. From then on, all hostile ships will no longer see their crew when you board them, and their docking bays will no longer function when they land on a planet. This bug seems to occur over time, and nothing can be done about it. Capturing ships seems to speed up the process, but it's bound to happen sooner or later. It's as if there's a maximum number of boardings to be made before the bug arrives. Once the game has been corrupted by this bug, the only way to get rid of it is with an NG+, but it's likely to come back with time in this new game...

That is extremely annoying. Encountered another starborn guardian ship and was surprised as the number has steadily rose from rank 1 to 4 and reached a cap, or so I thought. Encountered a starborn guardian rank 5 and was surprised as it was the firstbid seen. Not even an hour later an ecliptic hyena landed and that was the first instance of no boarding ramp. I've gone back to the save before the rank 5 starboard ship and even then, the first enemy ship to land, didn't drop a ramp.

It'd quite annoying and I hope it's fixed or patched soon, even a mod to fix it would be nice.

[A.Fern]

There's a lot of info now on this bug that appears to be focused on the issue being as follows: (i) there are 24 ship "quest" slots that ships grab when you encounter them in space or on the ground, (ii) Starborn ships bug out and don't release their quest slot sometimes, even if you killed all the starborn or you just ignored the ship (iii) eventually, all 24 quest slots fill up and all later ship encounters fail to start their quest -- so in space, they fly around and shoot you, but you board and the quest to take over or leave doesn't start so the ship is empty, captain's locker empty -- the cargo hold won't be empty because that is unrelated to the quest, you can see cargo from scanning so it doesn't rely on a quest starting (iv) THERE IS A FIX -- but only on PC -- you use console commands to clear out ALL 24 quest slots. This brings your game back to normal for a while, but alas, the bug isn't fixed, the bug will eventually result in the 24 ship quest slots filling up again, and you'll once again see the problem. But at least you can console-wipe the slots again when that happens.

NG+ fixes the issue temporarily because it resets a few of the quest slots based on resetting relevant questlines with ship encounters, but that is only temporary because the bug will fill those slots again soon enough.

Here's the thread for scripts you run to reset the ship quest slots: https://steamcommunity.com/app/1716740/discussions/0/3882722163301954365/?ctp=2

And last -- achievements get f'cked when you use the console commands, as you all know, so before you do any of the above, I would recommend you finish any long-term achievements that require you to grind a lot (like find all star systems, or collect 500 each of organic/inorganic). Or use a re-enable achievement mod (though it seems not to always work, so beware).

[pike]

Do you have mods ?
Do you have the beta patch ?

[amperage]

Originally posted by A.Fernando:

And last -- achievements get f'cked when you use the console commands...

For whatever it's worth, the game creates a text file documenting your use of console commands, which causes your save files to fork into a category marked modified.

You can verify this by going to Load>Select Character. After you've used a console command, there will be two characters the next time you restart the game. One will be marked modified

In Windows, you can delete the log file StarfieldConsoleHistory.log. It can be found at: Documents>My Games>Starfield

Once you've deleted the file, start the game from your last exit save and then resave. Achievements will be re-enabled (And the "modified" character should be gone.)

[smithlcg60]

https://www.nexusmods.com/starfield/mods/4704

This mod fixes this issue

[nilsross]

I have not tried it yet but this looks like a prommising work around. (resetquest)
Look a bit down in the comment trail for resetting 25 generic quests

https://www.starfieldpatch.dev/issues/268

Lots of other interesting stuff on that site

[Trist Munter]

this works
https://www.nexusmods.com/starfield/mods/5668

[I Denizen I]

Pretty sure the OP, who posted on October the 2nd, either got his issue resolved, or is no longer playing.

Why do people keep necro'ing old topics? Look at the date when you open a topic, it's right next to their name at the top of the page.

[Drake Ravenwolf]

Originally posted by I Denizen I:

Pretty sure the OP, who posted on October the 2nd, either got his issue resolved, or is no longer playing.

Why do people keep necro'ing old topics? Look at the date when you open a topic, it's right next to their name at the top of the page.

If someone had the same issue, it'd be fine for them to bump an old thread rather than create a new thread on the same issue.

[I Denizen I]

Originally posted by Drake Ravenwolf:

Originally posted by I Denizen I:

Pretty sure the OP, who posted on October the 2nd, either got his issue resolved, or is no longer playing.

Why do people keep necro'ing old topics? Look at the date when you open a topic, it's right next to their name at the top of the page.

If someone had the same issue, it'd be fine for them to bump an old thread rather than create a new thread on the same issue.

True enough, and yet not what was going on here, hence my post pointing out it's probably been resolved by now.