so im at the quest no ransom, i have three ships at the location but i cant pick up the hostages.
found a few old reports in the old forum with the same problem, is this quest really still broken after all the time?
And how can i continue now?
so im at the quest no ransom, i have three ships at the location but i cant pick up the hostages.
found a few old reports in the old forum with the same problem, is this quest really still broken after all the time?
And how can i continue now?
Hey @isilenna , welcome to the forums! Thanks for your post about the Pay No Ransom quest, and I'm sorry to hear you've run into an issue with it.
We'd resolved a few issues with this quest back in 2019, so it's unfortunate to see that something has gone with it for you. Can you check our troubleshooting guide for me? In particular from that guide, please make sure you've updated your operating system fully, you've verified the game files, and you don't have any unnecessary background programs interfering with the game. This makes sure the game is fully updated, and has all the files it needs to run as it should.
If it still doesn't work, can you answer the questions below for me?
• What happens when you try to pick up the hostages?
• Do you have an older save you can reload and try the quest again from scratch?
• If possible, can you capture some video footage or take some screenshots of what happens when it doesn't work?
Thanks again for your post - I'll keep an eye out for your response
Thanks for getting those two videos across to me, @isilenna - that's most helpful!
As far as I can see, this specific issue with this quest has never been reported. I've gone ahead and reported this to our team now, to investigate further internally, and we'll look to get it resolved as soon as possible. Sorry for the inconvenience.
In the meantime, just in case we need it, would you be willing to share your save file with us? This article describes where they are stored on your machine.
Thanks again
Hey, @isilenna - thanks for sending that across. I've added it to our report.
Our team has got back to me to say that this issue had been reported quite some time ago, but we'd been unable to reproduce the error, and this makes it rather difficult to solve. However, last time this was reported, an effective workaround was to restart the program and try again. Can you give that a go for me, and see if that lets you progress?
Hey @isilenna,
Thank you for your update and for sharing the solution that helped you.
It is great to hear you are now able to progress.
Any further trouble just let us know and we will be happy to help.