We're not sure what's causing it yet. Please go to the pinned thread and follow those steps.

I don't know if the solution is already known, I had the same problem, for me the solution was that there should be no finished structures in space that are only connected to the ship via a construction site

I can confirm Daniel statement.

No errors in log, except 2 ships are detected on main map when it should be one. Only one engine fire, engagement stalls at railgun range.

I have repairs undergoing:

https://steamcommunity.com/profiles/76561198005645309/screenshot/2505772116900254050/

As soon as i connect the lone hull, combat resume, all engine fires etc.

https://steamcommunity.com/profiles/76561198005645309/screenshot/2505772116900255610/

Toggling ship map physics option make no difference (i mean the orphan wall is not ejected or anything).

Read through the git of the unstable as of today and haven't seen anything, although i haven't tried that version yet, maybe it's already solved.

https://github.com/KentHaeger/SaveOurShip2/tree/unstable

There is a new unstable build up on our git, that should address many of the issues here.

Give this a test and report to discord and it will go on steam when we are confident these changes haven't destroyed the game.

The one engine bug, the enemy shuttles landing inside your ship, the quest shuttles refusing to land on your shuttle pads, several QoL enhancements such as new heat warnings on cloaks and an "auto-zone" for breathable areas of the ship, among many other fixes

All right, i'll sure check the unstable. Thank you!

English is not my native language. I had a similar problem, in my case it was solved by installing axial engines, which are necessary for turning the ship. I hope this will help you too.

make sure there is no unattached hull/flooring anywhere on the map. even if a random single tile from a wreck is somewhere on your map not attached to your ship it will make your engines bug.