Devin923

This thread is here to help users understand how to use the Sensors and Logic blocks. Below is a list of the blocks types, and with then are some examples of common use cases to understand how to use them. A more advanced thread will be created to explain more complex logic and sensor setups. Currently this is under development please check back for more updates. Once the base post is completed feel free to leave your comments and updates to examples and I will be sure to update the main thread to reflect different use cases and examples. -------------------------------------------------------------- Button: Activates the output key The button is used to permanently activate a key press, "W". In this case our thruster will now propel us forward, without us having to press, "W" to activate the thruster. Common Uses: Activate Boosters Activate Weapons Activate Mining Lasers Activate Decoupler for Satalite Switch: The Switch is just like the Button, except when toggled the button activate key will be turned on or off. The switch by default is turned off. In the drone example below we use a basic thruster activated by the, "W" key. The Switch will toggle the thruster to activate when the Left Mouse button is clicked. When the Left Mouse is clicked again it will disable the thruster. Common Uses: Activate / Disable Shields Activate / Disable Weapons Activate / Disable Mining Lasers Impulse Giver: The Impulse Giver, acts just like the Button. But instead of pressing the button all the time it is pressed on an interval and for a certain amount of time. There are two setting on the Impulse Giver: Active Time: How long it will hold down the button. Pause Time: How long it takes between button pressesHow long it will hold down the button. In the example below we use a COLOR LED set to activate when we press, 1. But when we introduce the Impule Giver and have it activate, '1' with the Active time of 1 second and Pause time of 1 second. Our LED will stay lit for (Active Time) 1 second, and then turn off (Pause Time) for 1 second. Common Uses: Used to turn a Motorized Hinge Activate LED, to be used as a signal light Logic Connector: Provides a wireless connection to the main part. Key events will be forwarded. Logic Splitter: Cuts the connection to the main part. Key events will not travel through this. Color LED: Sensors: Distance: Speed: Directional: Gates: IF: Activates the output key if the input key IS PRESSED NOT: Activates the output key if the in input key IS NOT PRESSED AND: Activates the output if BOTH keys are PRESSED OR: Activates the output key if ONE of the input keys are PRESSED NAND: Activates the output key if ONLY ONE of the input keys OR NO key is PRESSED XOR: Activates the output key if ONLY ONE of the input keys are PRESSED

That is also my belief, if you allow the option inputs to be NOT and TRUE, we could eliminate the NOT gate and XOR gates, an in return have more flexibility to make all the gate combinations. If done this way, 90% of users will use strictly True conditions, and if this is the default people will not be confused. When a novice user then needs to use a NOT statement and realize they can invert the input, doors will open for them to understand the rest of the gates and using NOT in those as well. Of course that is a theory anyways, but i would love to see this in an update to validate the functionality. I might start a new thread for typical logic structures and use cases, so it can be a start for a wiki of ship components or something like that.

Yes, an imply gate would solve the issue perfectly for this example. I would like to put it to the developers to see if they choose another option, based on the the confusion of non programmers understanding all the variations of logic gates. Given that we are also missing NOR and XNOR, I am personally okay with either solution, but do have some concern about regular users understanding too many gate options. Thank you for describing this properly. The Imply gate would be great.

Yes these solutions work, but the main issue is having to assign the additional output every time you do this, so for one function this is okay. But to do this for say 4 or more, mapping outputs starts to become very cumbersome. This example takes up 4 output bindings, and when you have a limited number of keys on the keyboard in addition to hard coded key mappings for other functions, you start to run out of keys quickly. Wondering if the addition of more attributes on gates could alleviate this issue.

Attached is a Drone I have been working on with this logic issue solved. The problem was, if the mouse cursor is under the drone, and the ground sensors detect the planet. I need to stop movement downwards and turn on the boosters upwards to prevent impact with the ground. Issues with using just an OR gate would result in one or more boosters being activated that were not to be activated at that time. Now that it is fixed the drone will stop at the planets surface before smashing into the ground. For those who download, the keybindings are: TAB - Shields 1 - Mining Lasers / Attack 2 - Currently Disabled ( Assign weapon to F2 ) 3 - Currently Disabled ( Assign weapon to F3 ) Hold Left Mouse - Accelerate in the direction you are moving Cursor in the middle of the drone will allow it to stall, if you need to hover. T-1000.nimbatusdrone

So far I am rather impressed with the fact that things actually work relatively well. I had issues creating the logic for: IF A && !B THEN C To solve this I had to make intermediate output keys and use an AND, OR and XOR to do this. Figuring out what keys are assigned to what gets confusing when choosing a key for physical things, and keys for temporary variables. If Logic could be connected, or have logic gates be able to reference the out put of each other this could be avoided. The other solution is to have the inverse of Logic Gates, so a checkbox for if something that for example could be: ex. AND Gate True and True or AND Gate False and False So the two additions to the game i would recommend would be: [*]a checkbox to invert the state of the variable either true or false. [*]a dropdown list to select the logic gate and use it's output as the input, this or be able to connect the logic gates together to achieve this Addition 1, would add more options for making logic. Addition 2, would prevent complicated setups with a crazy amount of key assignments. Side Note: When using OR, AND , XOR logic gates to press intermediate keys, ie A -> B -> C... The intermediate button can remain true, if A is no longer being pressed. Will try to create GIF to explain this, but this is a bug currently.

Self Balancing, Mouse Controlled Drone. Left Mouse - Boost in current direction TAB - Toggle Shields 1 - Toggle Weapons Set 1 2 - Toggle Weapons Set 2 3 - Toggle Weapons Set 1 This is a platform used to dig or traverse the surface of a planet without having control issues or directional issues with weapon setups. Working on making this paired with surface drones to seek and destroy while the main part can be used to focus on the fun parts, killing the core or being support. Let me know what you think, Thanks!