REPORT TEMPLATE Post your bugs here using the following template: Build: v1.4 b3259, but also since at least Alpha 11.5 Mode: Survival, possibly all Mode: Multiplayer, possibly all SERVER NAME: Eleon Studios - Official US Server, and every other server I've played on SEED-ID: N/A Reproducibility: Often Severity: Minor Type: Signals, Blocks Summary: Ship hangar doors stop obeying signals open themselves after server/playfield restart Description: When building a CV with hangar doors controlled by motion sensors on an MP server, it seems the hangar doors will randomly end up wide open for no good reason after a server and/or playfield restart and/or playfield change, and stop responding to the motion sensor signals. Changing playfields appears to temporarily fix it, but it is quite annoying that the doors will stop responding and often default to open, which you really don't want, especially if its a base in PvP space. Steps to Reproduce: Build a CV with hangar doors and/or ramps set up to open/close with motion sensor signals, go in and out a few times, turn it off, log out return to the server after a playfield restart. Video link:
Hangar door sensors on CVs seem to stop responding all the time for me when I'm on a server, especially if I have them linked to an OR circuit so I can hold them open with a switch. I find that going to a door and either just accessing the signals panel, or re-binding the signal will typically reset them and make them work correctly. The same is true of motion-controlled lights. I have not been able to reproduce this behavior in single player though.
It turns out that if you do not change anything, and travel to another playfield, they start to work again too, but then there is a good chance that even if you logged out and ensured your hangar doors were closed before you powered off the ship, the next time you log in to the server they will be open again and not responding to the motion sensor signal until you change playfields. So it's not a problem that actually requires redefining the signal, it's something to do with signals just stopping being listened to after certain conditions occur with the playfield on a server.
Haven't seen this bug happen in the last two months, since I stopped playing on the Eleon Official US server. May have been resolved at some point, or may have been specific to the official server, since it was started up back around v1.3
