Horizons Taking missions in a large ship ending up needing small or medium ship to complete it
- Thread starter Levianova
- Start date
The game ties the mission to the player (not the ship), it makes flying large ships very painful.
For what it is worth, in the mission details it will say if the destination is an outpost. One must pay attention to this if they are flying large ships.
For what it is worth, in the mission details it will say if the destination is an outpost. One must pay attention to this if they are flying large ships.
This is a known bug,there's loads of reports in for it already. Just search for destination change.
They're 'looking into it' apparently.
They're 'looking into it' apparently.
Lets call a BUG... A BUG!
This has nothing to do with a player not paying attention or anything pertaining to choices the player makes.
Its a BUG!
The game "SHOULD" be paying attention to the ship used to accept the mission so that if the destination does get changed, which often happens, the new drop off location is still accessible by that ship. The alternative is getting stuck in a Catch 22 with mission specific cargo that can not be transferred to another ship, but which can also not be delivered to the new delivery location because the original ship can not land at Outposts or similar small pad locations.
Your only recourse in this situation is to bite the bullet and ABANDON the mission.
My advice for the long term would be to ONLY fly ships which can land at ALL stations/outposts in the game. The Python is what I use, and it is about the best multi-role ship you can run at the moment.
Until FD fixes this bug, which keeps resurfacing after many of the updates, that is our reality.
Don't be lead down the Primrose Path by all the misinformation some community members continue to spread about things like this. A bug is a bug!
This has nothing to do with a player not paying attention or anything pertaining to choices the player makes.
Its a BUG!
The game "SHOULD" be paying attention to the ship used to accept the mission so that if the destination does get changed, which often happens, the new drop off location is still accessible by that ship. The alternative is getting stuck in a Catch 22 with mission specific cargo that can not be transferred to another ship, but which can also not be delivered to the new delivery location because the original ship can not land at Outposts or similar small pad locations.
Your only recourse in this situation is to bite the bullet and ABANDON the mission.
My advice for the long term would be to ONLY fly ships which can land at ALL stations/outposts in the game. The Python is what I use, and it is about the best multi-role ship you can run at the moment.
Until FD fixes this bug, which keeps resurfacing after many of the updates, that is our reality.
Don't be lead down the Primrose Path by all the misinformation some community members continue to spread about things like this. A bug is a bug!
Last edited:
To give you an idea of how FAR BACK this problem stretches...
When 2.0 was released for the PC, Frontier decided to just bring along the same background sim elements into the Xbox One version. As a result of this SAME BUG, Xbox players were seeing their mission delivery locations change to, GET THIS!...
PLANETARY BASES! [wacky]
Now bear in mind... Back when 2.0 came out for the PC in 2015, the Xbox One version of ED was still running a version of 1.5! The console wouldn't have access to Planetary Landings until June of 2016!
So... Now you start to get a sense for how Looooooooong this particular bug has been floating around in the game code. Despite all the bug reports, and all the threads like this one, here we are in June of 2016 and this same bug continues to screw with us! [wacko]
When 2.0 was released for the PC, Frontier decided to just bring along the same background sim elements into the Xbox One version. As a result of this SAME BUG, Xbox players were seeing their mission delivery locations change to, GET THIS!...
PLANETARY BASES! [wacky]
Now bear in mind... Back when 2.0 came out for the PC in 2015, the Xbox One version of ED was still running a version of 1.5! The console wouldn't have access to Planetary Landings until June of 2016!
So... Now you start to get a sense for how Looooooooong this particular bug has been floating around in the game code. Despite all the bug reports, and all the threads like this one, here we are in June of 2016 and this same bug continues to screw with us! [wacko]