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.
Editing 40d Talk:Mechanical logic
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "40d"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 23: | Line 23: | ||
::The problem, then, however, is that for some of the more complicated gates, and definitely for the memory gates, that it becomes very difficult to know which gearboxes are supposed to be linked to, and which ones are supposed to sit there and spin when powered. | ::The problem, then, however, is that for some of the more complicated gates, and definitely for the memory gates, that it becomes very difficult to know which gearboxes are supposed to be linked to, and which ones are supposed to sit there and spin when powered. | ||
::Also, heh, I know those are confusing. The gates themselves operate on a sort of backwards logic, so even I find it easiest just to look at it and say "okay, I figured this out a while ago. just use the gate, that'll be easiest to think with"--[[User:Sukasa|Sukasa]] 23:04, 6 July 2008 (EDT) | ::Also, heh, I know those are confusing. The gates themselves operate on a sort of backwards logic, so even I find it easiest just to look at it and say "okay, I figured this out a while ago. just use the gate, that'll be easiest to think with"--[[User:Sukasa|Sukasa]] 23:04, 6 July 2008 (EDT) | ||
− | |||
− | |||
− | |||
− | |||
== Not gates == | == Not gates == | ||
Line 38: | Line 34: | ||
We could use some more Clocked Logic designs, since there aren't very many right now. Anybody up for designing a few?--[[User:Sukasa|Sukasa]] 23:15, 6 July 2008 (EDT) | We could use some more Clocked Logic designs, since there aren't very many right now. Anybody up for designing a few?--[[User:Sukasa|Sukasa]] 23:15, 6 July 2008 (EDT) | ||
− | == | + | == OR/AND GATES == |
− | + | I think there are several big errors in the section Unclocked logic , all originated from the inverting of AND and OR functions.. | |
+ | The only case where AND gives as result "TRUE"(powered gear) is when both A and B are "TRUE", and the only case when OR gives as result "FALSE"(unpowered gear) is when both A nd B are "FALSE". Then it follows a big list of errors each time AND/OR are used. | ||
+ | (EG: the actual Equal returns "TRUE" if both A and B are "TRUE" or if they are both "FALSE", but the one posted returns "TRUE" only if one is "TRUE" and the other one is "FALSE") | ||
− | + | Please correct me if there are any errors and try to explain why am i wrong, because i'm pretty sure of what i'm saying. |