Jump to content
Stray Fawn Community


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bdew54

  • Rank
  1. Thanks, The NOR gate is indeed helpful (NAND even more), I guess it's back to the lab and build some! Plus: I have solved my own problem of efficient keymapping (perhaps this is beginners knowledge, but anyway...) I now resort to ONLY using Tags and leaving the Keys blanco or: 'add key' (by pressing "Escape", otherwise they all are mapped to "left mouse button"...). This way I can use words/designations instead of single keys and such to relate input/output ports. In relation to my first item in this thread: switch has Input: "T" and Output: [Tag: "Test_1", Key: none]
  2. Ok that explains it. My question is: why would they be handled this way? Could you give me a good example how this is useful? If they were handled via 'and' logic, you would be able to differentiate much more and keep track of all the functionality and keys. For instance you have two turrets that use two different sensors, I would like to be able to have the Tags either to 'turret_one' or 'turret_two' and the functionality of e.g. 'shoot' in both cases mapped to Key '1'. In short, with 'and' logic, you would have effecively much more and more organized 'keys' at your disposal. Wouldn
  3. Hi, I have the following problem with Tags (essential for "programmer" mode, right?) 0.9.6 (early access) The following switch has Input: "T" and Output [Tag: "Test", Key: "."] and is activated in my example screenshot. The LEDs are linked in the following way: upper left (Red) responds to: [Tag: none, Key: "."] upper right (Green) responds to: [Tag: "Test", Key: "."] down left (Red) responds to: [Tag: "Foo", Key: "."] down right (Red) responds to: [Tag: "Test", Key: "/"] If I understand the idea behind "Tags" correctly, only the green LED should have been activated
  • Create New...