ClassiestMedic
ClassiestMedic
1 / 0
8th Aug 2012
28th Jan 2013
WIP D:

Comments

  • ClassiestMedic
    ClassiestMedic
    28th Jan 2013
    Thanks, cracker! My last clock did that too, before updates broke it utterly
  • Pilihp64
    Pilihp64
    9th Aug 2012
    I would guess it is because your wifi next by the INST has inconsistent positions, meaning some fire a frame late and some a frame early (when they happen in succession, the spark is ignored). Try making the different temp wifi's use the same position around the INST. It might not be the only issue though.