Working on computer. Need help

  • Brian101
    7th Apr 2019 Member 0 Permalink

    Lately, I have been developing a computer. It is supposed to be able to crack any problem in seconds. I just finished the ALU and the CPU. I am currently working on the 10 clocks that it needs. The clocks must fire at a pace of 1 spark every frame. I don't want to use subframe because it is very advanced and I want players to just walk in and see how everything works, not stare at a bunch of numbers. So how do I make the clock?

     

    Also, recently I have also been developing a display board. Does anyone know how to use flit ctype in machines? Because lately, I have been looking at animation saves on TPT and they use a long line of FILT and a "scanner" kind of reads it and destroys it. Does anyone know how that works?

    Edited 3 times by Brian101. Last: 8th Apr 2019
  • LBPHacker
    8th Apr 2019 Developer 1 Permalink

    Since the non-subframe definition of a spark firing involves a 4-frame active period (of which only one is considered a real activating spark by most particles that take sparks) and a 4-frame cooldown period, a non-subframe spark sources that fires every frame is impossible. Even if it was, the same 8-frame cycle applies to any non-subframe conductor.

     

    FILT ctype is rather well-documented on the wiki.

  • Brian101
    8th Apr 2019 Member 0 Permalink

    Thanks a lot, LBPHacker. I will try to decrease the SPRK clock. It will lower the computer's speed but it seems impossible through non-subframe means. Also, I thought FILT-ARAY type wires would work. I will also check out the wiki link about FLIT ctypes. Thanks.

     

    Edit: Just checked the wiki link and the wiki was not exactly clear. I just learned that FILT's tmp can be used to change its mode. I still don't understand the way the "scanner" works and how they extract data from lines of FLIT. Also, the computer has been downgraded to one spark every 8 frames. It is a pretty good pace but the computer is having a hard time cooperating with the new changes.

    Edited 4 times by Brian101. Last: 8th Apr 2019
  • LBPHacker
    8th Apr 2019 Developer 1 Permalink

    It's FILT, not FLIT :P Yes, FILT can "conduct" BRAY with no cooldown, but you still have to emit the BRAY somehow, and although ARAY once again can emit BRAY without cooldown, you can only get it to emit BRAY every frame by resetting the conductor that activates it to a life=3 SPRK every frame. That requires the particles to act in a specific sequence and that's basically subframe territory.

  • Brian101
    8th Apr 2019 Member 0 Permalink

    LBPHacker:

    Yes, FILT can "conduct" BRAY with no cooldown, but you still have to emit the BRAY somehow, and although ARAY once again can emit BRAY without cooldown, you can only get it to emit BRAY every frame by resetting the conductor that activates it to a life=3 SPRK every frame. That requires the particles to act in a specific sequence and that's basically subframe territory.

     

    Not trying to make my computer too advanced but what if we used a PSTN to put a new conductor into place after the old one. Then when the old conductor finishes its cooldown, the PSTN will push it back to place. Is that a bad idea?

     

    Edit: I have a new problem. Upon downgrading the clocks, the computer now has time to update its wires. But constant sparking made pieces of METL, which are used to convert NSCN sparks to PSCN sparks, melt. What is the best coolant for a computer? Or should I replace the METL with something like TTAN? Also to make matters worse, the one required piece of METL, used to make a AND gate, is right next to a device that uses PHOT. The DMND surrounding the PHOT machine is not thick and PHOT would sometimes pop out and melt the METL.

    Edited 5 times by Brian101. Last: 8th Apr 2019
  • LBPHacker
    8th Apr 2019 Developer 1 Permalink

    It's not impossible but unless you use solid sparks to drive the PSTN, it'll be *huge*, and even then you'd be using subframe mechanics. In fact, if you build anything with a "clock cycle" of one frame, it's almost definitely uses some subframe mechanic regardless of whether you want it or not.

     

    EDIT: Constant sparking should definitely *not* melt METL. Sparking heats METL up to around ~390C, and METL melts at 1000C.

    Edited once by LBPHacker. Last: 8th Apr 2019
  • Brian101
    8th Apr 2019 Member 0 Permalink

    LBPHacker:

    EDIT: Constant sparking should definitely *not* melt METL. Sparking heats METL up to around ~390C, and METL melts at 1000C.

     

    The PHOT will melt the METL. The sparking will heat it to the point where a quick burst of PHOT will finish it off.

     

    Edit: Good News! I think I just solved another problem of the wire speed. I was looking at the wiki for CRAY when Bang! It hit me. CRAY can basically teleport SPRK. So if I use it to teleport the SPRK over long distances to its target, it is instant wire. Oh, wait there is an element called INST. =(

    Edited 3 times by Brian101. Last: 8th Apr 2019
  • LBPHacker
    8th Apr 2019 Developer 1 Permalink

    That means the PHOT is above 1000C. TPT simulates heat properly at least to the extent that when METL heated to 390C contacts PHOT (with a default spawning temperature of 922C), the METL heats up (but not above 922C) and the PHOT cools down (but not below 390C). This also means that the PHOT in itself is enough to melt the METL. If not, it's a bug and you should upload a save that isolates the phenomenon and report it in the feedback section (so I can fix it :P).

     

    I'm glad you figured something out though.

  • Brian101
    8th Apr 2019 Member 0 Permalink

    The PHOT is over 9000C because I use GOL to heat it. The PHOT was meant to basically go through a prism and temp affects it.

     

    I technically didn't figure anything out. I found the element INST. So, it defies the need for CRAY-SPRK teleportation.

    Edited 3 times by Brian101. Last: 8th Apr 2019
  • LBPHacker
    8th Apr 2019 Developer 1 Permalink

    Oh! That explains it :D And yes, INST is fun. Here's my favourite INST-based computer (it was the fastest back when it was built):