good to know how it happened from your description.

-Confirmed-

Just to make sure:
you are not playing with zero-friction right?

Having spawned hundreds of drones to do testing I can attest that this is true. I think that when they're too close to each other they try to turn to look at entities around them (notice how they do this with the player, even without being hostile). However, when there's a ton of ships around it leads to a cluster-derp.

Thanks. I might add that when changing lights resolution in-game 3/4 of blocks just disapear from sight when going from faster to normal. Does not happen every times tho. Changing back to faster lighting quality i see the blocks again.

-Validated-
Not happening with your settings.cfg in my windows system

I just set a storage block, activated pull (everything) linked it to all my other storages and added a few thousand cargo space blocks (2k at once till everything fitted in).
Then I logged out before the hotfix.
The admin has send me the log of my crash: https://storage.googleapis.com/starmade/urza%20login.txt

putting in queue with logfile

I concur, placing and removing blocks work very differently since the last 3 updates, maybe 4. Aiming at the side of a tetra (for exemple) i could easily place a hepta. Now i have to be very, very precise where my mouse pointer is to be able to do that.

will see if this is enough info to try a fix ...
something with the setup of the storage that breaks it i guess ...

just draging and dropping what ever file in here is fine usually

Sorry for the 2 deleted comments (i tried copy paste the .txt like the client config but the long txt freezed my browser...)

as described .. cant move through teal rod lights

Please add the log.txt.0 log file of one of those crashes here.

pretty easily visible and reproduceable effect

Also found: T967

-Validated-
-Confirmed-

Just checked my cargo, i left it near full, it is now empty.

Might it be possible for Rail Dockers to project an extra 1/4 block slab collision area, or automatically place an invisible placeholder 1/4 slab on top of the docking surface? That would give you a nice, neat defined point of contact.

Bandwidth is over 1Mb/sec and it lets me download torrents so I imagine multiple connections are OK (sometimes connected to 25 peers at a time)

-confirmed-

Known problem

The rotated and pasted camera is on an entity docked to something and the view direction is to the front view orientation from the docked entity core ?

Well, seeing the log I cant really see any unusual things happening.

Tried another of the same type of phone (OnePlus One) and the results were the same, working but a strange startup sequence (and slow).

I am able to reproduce the stated affect.

In T944#35135, @Napther wrote:

Perhaps they dont need to touch? When the "Distance to re-dock" code is implemented, a much lower ranged one could be used to snap rail dockers onto rails when they are 1-2 blocks away. That is unless the code for distance stems from the entity itself, and not where the dockers are placed

How do I attach the log file?

Packed the log in a 'readable' comment

server.txt.0 (again clean before trying)

ISP is unlikely the problem, I can do all sorts of naughty things without a problem. Trying to figure out how to attach the log files as Feedback.

-Testing-

-Testing-

Also noted that the favorite place to spawn seems to directly under the core block. So I removed a floor block so that there is a 3 meter clearance under it and now it seems to work fine. I thought it was supposed to favor spawning to the rear of the block....

I've noticed the same. These are the same turrets that can't be detached, even if the entire docking mechanism is removed.

Okydokey. I tested the behaviour on my machine based on orientation. It does change based on how the ship is lined up with the 'universe'.

quote: "was your ship stationary docked in a fixed orientation while doing this ?" - SmilingDemon

i agree .. T820 is a serious problem ... but not the same as this one ... probably related yes, because i do asume it is caused by the same part of the code.

this issue has been ongoing since 498: http://phab.starma.de/T820

-Confirmed-