Bug Rails Undocking

[Micro753]

So, I loaded up a ship I built six months ago, and all the rail doors, landing gears, etc. undock when i toggle the direction of the rails with logic. To be sure I just didn't screw up my logic, I built a simple mockup to test:

Spoiler: Picture

The button is only linked to the flip-flop, the flip-flop is linked to the rail line and the not, and the not is linked to the rail line. It works fine for the first button press, but then the rail undocks when the button is pressed again. It seems the flip-flop and the not gate are acting like an activator does when linked to rails. Am I missing something, or did logic change in an update? If this isn't a bug, then what is the new way to wire up the logic for it?

 

[kiddan]

Just today I was having a very similar issue. I had an activator making a rail turn clockwise, and a slaved NOT gate that made it turn counter-clockwise. It seems as though NOT gates will always undock a ship from its targeted rail, the same thing an activator does if it doesn't have a, adjacent rail block. So maybe NOT gates do have logic output but not rail manipulation?

Edit: The solution to your problem is to slave an activator to each block that has an unexpected effect on the rails. Have the activator manipulate the rails instead of the gates.

 

[Micro753]

Edit: The solution to your problem is to slave an activator to each block that has an unexpected effect on the rails. Have the activator manipulate the rails instead of the gates.

I'll try that out now and see if it works. Good to know it's not only me.

Edit: Yep, that fixed it. Still not sure if that was an intended change. I don't remember seeing anything in an update change-notes about logic changes.

 

[silverfoe]

Coud you share the blueprint please?

 

[Micro753]

Coud you share the blueprint please?

You don't need a blueprint to see it. I rebuilt the rails from scratch on a newly spawned ship, and it happens everytime, no matter how simple.

 

[SmilingDemon]

Screenshot
this setup would work for example (red arrows are the links)
the not undocks on change ... the flip flop should work.
no idea if this is intended for some elaborate reason (maybe there is a way to make clever use of that ??)

however --- test parameters are only for this to work with and/or/button/activator

but could be a bug

 

[kiddan]

There definitely is use in having NOT gates and Flip-Flops(?) ignore adjacent rails, as you can use them in compact logic where an activator would find an adjacent rail block when you don't want it to. =)