It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hello, I have run into a bug where after I set a course through the Nav map my ship undocks from a star fort, I am wished good hunting by said star fort, and then my ship doesn't move. The sub light bar moves to .1 and only moves further if I press arrows or other keys on my keyboard but the ship never moves.

I haven't been able to reproduce it 100% of the time but I have noticed it happens on mission start after I launch probes into neighboring star systems without leaving the starting starforts dock (so the probes get automatically resupplied). After I have launched the probes and I give the move order like normal the bug happens where my ship doesn't move, I get all the normal dialog however. I have tried emergency stopping, the ship does move to a stop but I can't even manually navigate after the bug happens, setting a course through nav or system map doesn't fix it either.

Every time I get this bug I have to restart the game. I have completed the first 2 missions successfully by moving out of the starbase before I launch probes in order to avoid the bug.
No posts in this topic were marked as the solution yet. If you can help, add your reply
Huh, this sounds like a bug we thought we fixed. If it happens again, can you try something for me and report back?

Next time it happens, hit CTRL-V or CTRL-Q to save your game and let me know if it stays stuck or resumes moving as normal.

Thank you for reporting this and for any further help you can provide.
Hey, I haven't been able to reproduce this on my end. Have you had any luck?
avatar
Veloxi: Hey, I haven't been able to reproduce this on my end. Have you had any luck?
I have not yet but also haven't had much time to play. I will hopefully have some time later tonight, I had it happen to me a bunch yesterday, I ended up reinstalling the game after the update which, along with not launching probes right away, allowed me to beat the first 2 missions.
Post edited November 21, 2023 by TheRealThorgrim
avatar
Veloxi: Hey, I haven't been able to reproduce this on my end. Have you had any luck?
avatar
TheRealThorgrim: I have not yet but also haven't had much time to play. I will hopefully have some time later tonight, I had it happen to me a bunch yesterday, I ended up reinstalling the game after the update which, along with not launching probes right away, allowed me to beat the first 2 missions.
Congrats on finishing your first two missions, Altern! ;) Looking forward to seeing if you can replicate the problem!
avatar
TheRealThorgrim: I have not yet but also haven't had much time to play. I will hopefully have some time later tonight, I had it happen to me a bunch yesterday, I ended up reinstalling the game after the update which, along with not launching probes right away, allowed me to beat the first 2 missions.
avatar
Veloxi: Congrats on finishing your first two missions, Altern! ;) Looking forward to seeing if you can replicate the problem!
I got the bug again trying mission 3, I launched 2 probes before leaving the star base then tried to jump to a F class star. Hitting CTRL-Q did nothing but CTRL-V making a new save file did make the game continue properly.
Post edited November 23, 2023 by TheRealThorgrim
avatar
Veloxi: Congrats on finishing your first two missions, Altern! ;) Looking forward to seeing if you can replicate the problem!
avatar
TheRealThorgrim: I got the bug again trying mission 3, I launched 2 probes before leaving the star base then tried to jump to a F class star. Hitting CTRL-Q did nothing but CTRL-V making a new save file did make the game continue properly.
Thank you, I will pass this on.
This is an old bug that is caused by a "feature" of a standard C library call. I removed all these calls from the game a couple years ago and this bug has never reappeared until now. However, when I put in debug statements I sometimes use this C function because it is convenient. It appears that I must have missed one of these debug statements, so I'll search my code. You have narrowed down the possible location because of where it occurs for you.
avatar
TrevorSorensen: This is an old bug that is caused by a "feature" of a standard C library call. I removed all these calls from the game a couple years ago and this bug has never reappeared until now. However, when I put in debug statements I sometimes use this C function because it is convenient. It appears that I must have missed one of these debug statements, so I'll search my code. You have narrowed down the possible location because of where it occurs for you.
Awesome glad to help, the game is also very fun by the way.