What To Do When Value Doesn't Propagate
Posted: Wed Dec 17, 2014 10:17 pm
Definitely one of the most frustrating problems I've run into while working in Flowstone is when a value doesn't propagate correctly through a schematic. It will seemingly get stuck at a specific point where the next node doesn't receive the correct value unless you manually click on it, even though everything connected before it has updated correctly. It of course doesn't appear to make any sense, but there does seem to be a solution.
When you find the point at which the value looks to be stuck, place a trigger blocker in the connection between it and the previous node. Then, wire a "trigger pass" (a module that contains only an input wired to an output with both nodes set to trigger) from the beginning of that block of code (e.g. the input of the module you're working in) to the node after the trigger blocker. Make sure this trigger link is connected last.
Cross your fingers and test your schematic again, and hopefully things will be working without a hitch now.
My hope is that if anyone else is finding themselves frustrated with this sort of issue they'll find this post!
When you find the point at which the value looks to be stuck, place a trigger blocker in the connection between it and the previous node. Then, wire a "trigger pass" (a module that contains only an input wired to an output with both nodes set to trigger) from the beginning of that block of code (e.g. the input of the module you're working in) to the node after the trigger blocker. Make sure this trigger link is connected last.
Cross your fingers and test your schematic again, and hopefully things will be working without a hitch now.
My hope is that if anyone else is finding themselves frustrated with this sort of issue they'll find this post!