The sensor appear not to trigger its actions if it is turned on while an object is already in range. Is this a glitch?
Automatic door tutorial
Could someone PLEASE fix the tutorial? The edit section is too confusing to me.
Simply put, using 2 sensors to open a door is just too complicated. I mean if someone comes from the other side at the same time, the sensor will slam the door shut in their face.
Just put up one sensor only and set it to open the door if a player is nearby and close it when he isn't. Much less complicated and MUCH more reliable. Also works with airtight hangar doors.
- The tutorials and some information were written by someone else. I have been making my way slowly down the list from A to Z and completely rewriting them. I will also make a note to revamp or remove the tutorial and put into better detail how to use it. If you want to help, you can edit the section yourself. If you want to delete the tutorial entirely, you are free to do so (we can always revert changes here). After you're done, be sure to say in the summary "removed tutorial" so we can queue unused images to be deleted. Don't worry about making it fancy. If you want help with that, write whatever information you like, and when I come to the page, I will give it a clean look. Otherwise, I will eventually get to it. Thank you for the heads up! --Sapphire (talk) 00:47, 11 August 2015 (UTC)
I corrected the component list and "Functional" threshhold as of v1.185.7 this date. I don't know how to add the "Hack" threshhold to the components box, nor how to check systematically if other component lists are wrong or outdated. First edit so feel free to advise and correct. Signed, intern space engineer --SCol Jasmine Chen, CAF (talk) 21:46, 10 January 2018 (UTC)
Thanks for your recent edits. A quick look at Template:Itembox, reveals that lcomponentproperty and scomponentproperty are probably what you're looking for to add the hack threshold. -- Cryptkeeper (talk) 04:37, 14 January 2018 (UTC)