Automatic access ramps in ships seem to always be in the opened state when you approach them, and then when the motion sensor detects you, the ramp instantly closes and re-opens again. It's been like this for a few days now, I don't remember exactly which patch started it.
Same for me, noticed it with the new 12.3 Patch. This lets not only the Ramps down but also my Hangar Door open and enemies can fire inside my ship. Edit - Just to clarify: This is a new game with A12.3. My CV has a Hangar Door with Ramps attached to a Motion Sensor and the Ramps stay down and the Hangar Door open. There is also a Light attached to the Ramp Sensor that doesn't go off. Other Motion Sensors inside which are only attached to Lights are working fine. Edit2: Deselecting the Motion Sensor from the Hangar Door fixes the problems for me. After reconnecting the Sensor to the Door everythings seems to work as it should now.
on mp servers everytime I load into game, my CV boarding ramps are all open/down, have to manually close them EVERYTIME I log in
Yes this has been the case for me as well ever since the 12.3 update. Then I will go in, close it, and it will open right up again by itself. I'll close it, turn the ship power on, and it opens up again. Have come across unoccupied player CV's in space since the update and they too all have their ramps open. I have not yet taken the time to remove the ramp and replace it however. Maybe that will fix?
Build: v1.0 3047 Mode: N/A SERVER NAME: N/A SEED-ID: N/A Reproducibility: Always Severity: Annoying Type: Device default state Summary: Boarding ramps default to open Description: The CV's boarding ramps are now open by default. Spawn a blueprint, load a save game, or turn the CV on and the ramp will suddenly open. This also overrides signal configurations and can be seen on POI's with boarding ramps (Titan Middle). Steps to Reproduce: Spawn a CV, load a save game, or turn on a CV with a boarding ramp. Example blueprint attached.
Oddly enough, the forum did not give me a notification when this post was moved. I almost posted it a second time because I could not find it.
I didn't get a notification either, so cannot know whether this fix is still awaiting an update or was supposed to have been fixed for 1.0