v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Difference between revisions of "v0.31 Talk:Pre-Toggled Mechanical Logic"
Jump to navigation
Jump to search
(Created page with 'Did you test any of this before writing this up and linking to it from the mechanical logic page? This doesn't work the way you seem to think. Once your inputs have toggled once,…') |
|||
| Line 1: | Line 1: | ||
Did you test any of this before writing this up and linking to it from the mechanical logic page? This doesn't work the way you seem to think. Once your inputs have toggled once, your pre-toggled gears will revert back to normal and you will, for instance, instead of a NAND gate, have an OR gate. When an object sends a state, it sends an OFF/ON signal corresponding to the input's state. It does not send a TOGGLE-STATE signal. Here, I built one of them and tested it: Your NAND gate is actually an OR gate, because pre-toggling doesn't do what you think it does. http://mkv25.net/dfma/movie-2151-pre-togglednandbecominganorgate --[[User:SL|SL]] 20:56, 2 May 2010 (UTC) | Did you test any of this before writing this up and linking to it from the mechanical logic page? This doesn't work the way you seem to think. Once your inputs have toggled once, your pre-toggled gears will revert back to normal and you will, for instance, instead of a NAND gate, have an OR gate. When an object sends a state, it sends an OFF/ON signal corresponding to the input's state. It does not send a TOGGLE-STATE signal. Here, I built one of them and tested it: Your NAND gate is actually an OR gate, because pre-toggling doesn't do what you think it does. http://mkv25.net/dfma/movie-2151-pre-togglednandbecominganorgate --[[User:SL|SL]] 20:56, 2 May 2010 (UTC) | ||
| + | :Actually, when you're dealing with gear assemblies, levers '''DO''' send a "toggle" signal. Given that gear assemblies default to being "on" rather than "off", what's actually wrong is that the article has the notion of "non-toggled" and "pre-toggled" completely '''backwards''' - when an "non-toggled" gear assembly receives an "on" signal, it STOPS transmitting power, and when it receives an "off" signal, it STARTS transmitting power (and technically, it doesn't matter whether the signal was "on" OR "off", since either will result in a toggle). --[[User:Quietust|Quietust]] 21:06, 2 May 2010 (UTC) | ||
Revision as of 21:06, 2 May 2010
Did you test any of this before writing this up and linking to it from the mechanical logic page? This doesn't work the way you seem to think. Once your inputs have toggled once, your pre-toggled gears will revert back to normal and you will, for instance, instead of a NAND gate, have an OR gate. When an object sends a state, it sends an OFF/ON signal corresponding to the input's state. It does not send a TOGGLE-STATE signal. Here, I built one of them and tested it: Your NAND gate is actually an OR gate, because pre-toggling doesn't do what you think it does. http://mkv25.net/dfma/movie-2151-pre-togglednandbecominganorgate --SL 20:56, 2 May 2010 (UTC)
- Actually, when you're dealing with gear assemblies, levers DO send a "toggle" signal. Given that gear assemblies default to being "on" rather than "off", what's actually wrong is that the article has the notion of "non-toggled" and "pre-toggled" completely backwards - when an "non-toggled" gear assembly receives an "on" signal, it STOPS transmitting power, and when it receives an "off" signal, it STARTS transmitting power (and technically, it doesn't matter whether the signal was "on" OR "off", since either will result in a toggle). --Quietust 21:06, 2 May 2010 (UTC)