The set-up explained in the original description does not replicate it anymore, however I still do get the error but it is very hard to reproduce it reliably (however when using a missile system that causes it, it happens very reliably), I have only experienced it twice since then, both in multiplayer. I am using a Nvidia card as well. However, another SM player has this issue on AMD cards as well.

I'm pretty sure I have triggered this myself on many different public servers unknowingly. Right now I'm playing on Brierie (running .472) and I attempted to "move" my shop to another physical position on my station. Pretty sure it caused the server to need to hang/be restarted. But post restart things are still acting quite wonky at least in my sector.

Update: this issue continues to occur, even after switching away from the professional to a consumer-grade GPU card.

Yeah, better to upload those to be sure although I should be able to reproduce with this sector crossing part.

Okay, removing the task then.

Test-Change for project related e-mail

Unfortunately not enough with just this snipped. need at least full log. Essentially this is a state where a player character was hidden but is still in the physics which is illegal. I suspect either sector change or F1+F8 to be involved

T1004 has been fixed. Not sure if this one is happening. A station turning into a red platform would only be possible if there is no data to load. Need logs if this should happen still

This is what I see, while logged-in as a normal user, about 2 minutes after running /add_admin against my user.

@lancake I repeated the test as requested, and sure enough with both ships in the same sector I can damage blocks with the beam weapon as normal immediately after spawning. However, If I train on a second target (same blueprint, same firing ship) in a different sector, it exhibits the problem I was describing.

I have tested this bug out and found where the issue lies:
If you have a drone docked to a mother ship on a rail, then change out the rail it is docked on for a shoot-out rail the invalid position error occurs.
A workaround for this is to only swap out the direction of the rail your ship is docked to and have it lead to a shoot-out rail.
I was able to re-produce this bug with the supplied blue-print and the workaround consistently solves the issue.

Is there any update on the progress of this bug?

This still occurs, just try to run any tutorial on macOS, and the same crash happens.

Still seeing this issue. I suspect it's related to our application of the /add_admin and /remove_admin commands.

@lancake asked that I upload our factions.fac file. It is attached.

No idea why this is repeatedly being tagged as "Waiting on Author"; without further input from Schine or more feedback from other players, all has been said as far as I am concerned.

Impossible to solve without log