Put together a fleet of 3 and accelerated at 78 m/s, turned around and see the two other ships flying into each other:

-Validated-

Current State in: v0.19590
NOT changes a high to low state change
flip flop changes on low to high and high to low
AND gates trigger on low to high
OR gates trigger on low to high
Activation modules trigger on low to high

-QA Testing-

Cargo blocks do not seem to update at all anymore.

-QA Testing-

-QA Testing-

-QA Testing- Part 2

Yes.

Yeah true, is a bit older that report and some internal optimisation may have fixed it already. Going to close it then.

yes, looks like that is the case.

-QA Testing- (virtual =))

Old dockers will be removed shortly, they cause a lot of issues to keep them working at all.

I was able to reproduce but its not something consistent from what I can see. Were you flying the flagship yourself?

Tested on 2 more AMD Cards now.

This is a part of the problems reported in T1021

Turning on AA breaks mipmapping. With AA off the mipmapping is acceptable, but when it's on it gets just as bad if not worse than the initial screenshots I posted.

Supposedly you can't type chinese/japanese in the chat box (no idea about other input fields)

-QA Testing-

The original issue is fixed, might want to improve the permission system a bit more at a later stage though.

Closing

Agreed, some information regarding registry issues, or a more clear message when you fail to connect to the registry should help a lot.

-QA Testing-

Closing

It's fixed for an Nvidia GPU but might be different for AMD, waiting for confirmation.

-QA Testing-

I don't have access to that?

-Confirmed-

Alright, glad to see somebody else found this, but the way I tried to search for it didn't reveal T19. I know this can be avoided using orientation, but I still felt like I should have reported it.

A salvager drone shouldn't even attempt salvaging if it isn't hooked up to cargo (chest). And also give some notification if that's the case, that pop up red text over factories that run out of power could be used here, but instead it pops up over the salvage module?

Managed to get them to mine by just leaving the sector and coming back, leaving the sector with the flag ship and coming back worked too.
They mine 1 asteroid and then they stop till you reset that queue.

-Confirmed-

-Confirmed-

In T1232#47124, @Kingofanime wrote:

If your drones are docking backwards, then putting the rail docker on the very back end of the drone, with nothing sticking out past it, might help. That way the rail docker gets in range of the docking point before the drones collision box does.
You can also change your fleet to idle mode just before your drones reach the docking points and they will drift into position.

If your drones are docking backwards, then putting the rail docker on the very back end of the drone, with nothing sticking out past it, might help. That way the rail docker gets in range of the docking point before the drones collision box does.

I tried to stick the pickup point/rails outside of the ship's bounding box like @lancake suggested. Didn't work... Changing the orientation of the docked on the drone also doesn't make a difference FYI.

-QA Testing-

This is true even when the pickup block is much more accessible. Ships are unable to dock no matter the size/position of rail unless they get lucky and dock thanks to the inertia.