Top and bottom textures of blast door slabs are rotated and don't fit to full blocks.

Shouldn't the delay then be 510ms (17*30ms) instead of 555ms (18.5*30ms)?

This bug is still present with the new thruster plumes, it looks even worse now.

I started with a 59 block line in +z, 53 blocks in +x and 53 blocks in +y direction, all with a single click. This should go beyond the 96 x 96 x 96 box, since 96 / 2 = 48 < 53. Then I added 53 block lines in -y and -z direction, again with a single click.

I made a test entity, one 50+ long line in the x-direction and one in the z-direction, without any problems. Then I added another line in the z-direction, which turned all blocks in a 9 block radius around the core unphysical. I don't see any relation to chunk borders, and the problem occured in a place that worked before, it's even the core chunk, so I don't think it's related to uninitialized chunks, at least not directly. Also, the extent of the unphysical part changes when adding more blocks.

I found an error in the suggestion, which I fixed. I also added a section about rotational symmetry, but that's optional. Both is listed under "Edit 2".

Happens for me with both OpenAL on and off and affects power auxiliar explosions, too.

Sorry, forgot that.

It IS exploitable both ways.

Still happens for me (0.199.172). I made a test setup with Core+Rail Turret Axis -> Rail Docker+Core+Rail Turret Axis -> Rail Docker+Core. Shooting at the first core until it overheats makes the other docked entities ghosted. Shooting at the second core (turret base) until it overheats makes the third entity (turrel barrel) ghosted; also, the "OVERHEATING" message and the timer are not displayed in the second case.

If it's really a bug, I can supply a test ship.

AA works without bloom now.

1. It's rather a C than a U
2. Yes
3. Yes

It's about time this gets resolved, especially since it can't even be undone (T574).

Still bloom-dependent for me.

I suggest that either the mass of all docked entities is taken into account for calculating the strength of the ion effect - as long as shield sharing is active! - or that defensive ion on docked entities also affects shared shields (requires fixing of T320/T382).

I prefer two different keys for enter/exit.

Shouldn't the rail docker also emit a docking beam?

I just had a turret (base + barrel) displaced by about half a sector after relogging. (v 0.19519)
The base was made via "Create Docking" (unlike the barrel).

I use an Nvidia GTX 680, for me anti-aliasing works when bloom is activated.

A useless entry in the undo list is also created.