-QA Testing-

Undeathinators weren't included though, your spawn point is still set even if it was removed so there's no harm done.

that is fine. The exception is being caught. I'll probably switch the output off at some point

(You'll need to start and close the game at least once as the setting you currently have is still using the translation)

-QA Testing-

system will now use bruforce as backup. this means that there wont be any problem even if quickhull fails (which likely only affects small enough reactors in scale)

Ah, forgot to remove status change...

Not sure if it got fixed somehow or if the requirement for reproducing it is different, but I can't reproduce:
https://gfycat.com/gifs/detail/AchingPepperyHogget

-QA Testing-

This should be fixed, but had it happen several times with multiple reactors on my entity. Can't reproduce yet but will most likely run into it again at some point.

-QA Testing-

should be fixed in next build.

More of the same was mentioned here: https://starmadedock.net/threads/since-199-646-open-gl-crash-on-a-mac.29270/#post-344629

I have an additional puzzle piece to add:

I may have another puzzle piece to add.
Recently this error struck on a single player universe. I strongly suspect shipyards, specifically upsizing shipyards to accommodate a too large design that is already loaded, but I don't have proof of that - I continued to play in this world for quite a while regardless, over multiple sessions, so no chance to find any logs from then.

Managed to cause the ship not same as self exception in v0.199.654, happened in trader controlled area.
Log 0-1 for serverlog/logstarmade/npcs included.

I am still having this issue with my station even after the release of the patch on the 28th. It started when I went to dock a turret and it docked to the station but 2 sectors away in the middle of space.

Should have been on resolved since first pre-build.

Potentially related, recently noticed that the behaviour of AI is affected by the relative locations of the COM and the core with behaviour becomming less reliable the further apart these two are. Could be that with larger mining drones the distance between the COM and core is causing the issue. This also may be worth looking into as its own issue.