I do get Paste not complete: not enough blocks! when pasting now, seems I either did not saw it or it was fixed along the way.

Issue seems to be fixed in v0.201.129.

Issue seems to be fixed in v0.201.129.

Obsolete issue.

Still happens to cores that existed before the fix (checked in v0.200.334)

Fixed in v0.200.332.

Turret axis are not compatible with rail systems, so I am inclined to believe they do not contribute to this bug. Also, your rotator arrow is not facing any of the adjacent rail blocks.

Sounds like a worse case of T2484 Turret Orientation Desync

(0.200.172, but I am very sure this was present before power update) Additionally, docked parts on turrets can spasm out into very odd orientations. However, these cannot be reset as "reset turrets" does not reset fixed docks. As such, the docked parts have to be deleted, or they will undock in that weird orientation, which 99/100 times is clipped into the turret, causing mass chaos.

Negative, in version 0.200.172 cross-sector beams still only reduce AHP, no actual damage to blocks.

Have you turned on the target ship's AI? Turrets don't target inactive AI ships regardless of IFF.

This is no longer an issue. (v0.199.535a)

I have just tested it, and it teleports to the correct position promptly. When I reported this I believe the rail entity was stuck and teleported to the original position, but it seems to be okay now.

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 have not been able to reproduce this on non-rail clocks as their frequency is far too low for this to happen.

Huh, I can't seem to replicate it now. (version 0.199.357)

logstarmade (snipped due to excessive repetition of Exception: Projectile physics null for sector x

I have tested it in the latest version (v0.198.485) and found it 100% reproducible, I am not quite sure why you can't reproduce it.