Wire factory

  • MachineMan
    15th Nov 2021 Member 0 Permalink

    I'm working on a PSCN/NSCN wire factory.  But the 2 STOR pixels inside the machine sometimes spawn to much LAVA, which causes the machine to either stop or go haywire.  What do I do?  Here is the save below:

     

  • EnganK
    15th Nov 2021 Member 0 Permalink

    Apparently, you sometimes have problems synchronizing mechanisms that are difficult to track down due to excessive use of WIFI. Try to slow down the factory a little, maybe then you can find the error (or even avoid it).

  • cyberdragon
    16th Nov 2021 Member 0 Permalink

    I've buit several factories like this before and always use DLAY for sequencing. Also keep the lines inputing to the wifi only a few pixels, you don't want the spark lingering to long (can also be achieved with INST).

  • MachineMan
    16th Nov 2021 Member 0 Permalink

    Thanks.  I'm working on it now.

  • MachineMan
    19th Nov 2021 Member 0 Permalink

    I replaced some of the WIFI with INWR/CRAY(SPARK) and used DLAY to slow down the process a little.  I found no obvious reason why each STOR pixel sometimes spawns multiple pixels of LAVA at a time.  Also I found a new problem:  how to make sure the LAVA pixels always spawn in the same place.  If the spawn in different places than each other, it could lead to problems.

  • EnganK
    19th Nov 2021 Member 0 Permalink

    You can use DRAY to copy the lava itself, not STOR. You can also close all exits at STOR, except one, so that LAVA appears exactly there.

  • MachineMan
    20th Nov 2021 Member 0 Permalink
  • MachineMan
    8th Dec 2021 Member 0 Permalink

    Sorry to bring this up after such a while, I had other stuff going on.  Anyways, replacing the STOR pixels with DRAY mechanisms solved that problem, but now I have another problem.  Sometimes the machine goes haywire during the process of sorting out the resulting PSCN and NSCN.  It may have to do with the fact that the LAVA pixels don't always fall side by side; they're always in the correct x coords, but sometimes one is in a different y coord than the other while they're falling.  Is this correctable and if not, how can I work around it?