Thank you for contacting us. We're sorry to hear you're experiencing issues.
We've managed to reproduce the issue you're describing. It's been reported to our internal system. We will update this thread when we have more information.
Kind Regards
Keen Software House
Hello, Engineers!
Thank you for contacting us. We're sorry to hear you're experiencing issues.
We've managed to reproduce the issue you're describing. It's been reported to our internal system. We will update this thread when we have more information.
I have the same bug
Hello, Engineers!
Thank you for contacting us. We're sorry to hear you're experiencing issues.
We've managed to reproduce the issue you're describing. It's been reported to our internal system. We will update this thread when we have more information.
Kind Regards
Keen Software House
Hello, Engineers!
Thank you for contacting us. We're sorry to hear you're experiencing issues.
We've managed to reproduce the issue you're describing. It's been reported to our internal system. We will update this thread when we have more information.
Kind Regards
Keen Software House
Hello Engineer,
We would like to inform you that the issue you reported was fixed in the 1.206 (Fieldwork) update.
While reviewing a list of resolved tickets, we noticed that we hadn’t posted an update here earlier — our apologies for the delay.
If you encounter any other problems, please don’t hesitate to create a new thread.
I’ll now close this one as solved.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Hello Engineer,
We would like to inform you that the issue you reported was fixed in the 1.206 (Fieldwork) update.
While reviewing a list of resolved tickets, we noticed that we hadn’t posted an update here earlier — our apologies for the delay.
If you encounter any other problems, please don’t hesitate to create a new thread.
I’ll now close this one as solved.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Replies have been locked on this page!