12-22-2016, 12:48 AM
(This post was last modified: 12-22-2016, 12:54 AM by LordDecapo.)
(12-20-2016, 12:00 AM)EmpirerBAD Wrote: So... how is 1 tick serial done now then? Haven't seen anything which can replace its functionality.
This way:
i just tested this moments ago in 1.11 and it works fine still, its like 2+ yrs old and has worked ever since it was made. Dylanrussel made it a while back when i was wanting to use it in one of my systems. I realized that 1 tick is only good for super large transfers, but even then, the size of the memory needed for 1 tick is much much larger than 2 tick, so the memory will lose a good portion of its speed gains from just the added delay of larger unit sizes and the 15 block signal.
Also no one uses 1 tick serial in serious computation due to its difficulty to process. For instance in my CPU i have a packet sniffer that can process 2 tick serial as its flowing. It merely branches off and uses comparator and repeater logic so u never have to stall the data stream, but can still extract needed data. The way i use it in my system in my Instruction Control unit. the slower speed of 2 tick serial transfers end up being faster than 1 tick, saving it, then decoding and doing logic with it... although timing for the sniffer is rather complication, yet 1 tick serial has its own bugs and has to be handled like a toddler in a candy store.
^ the key word in both of those is "computational" and "memory", RAM that needs access to be super fluent and compact to not take bussing delay and cause more chunk updates. And packet sniffing is faster with 2 tick. YET for super massive storage like 1KB or larger.. if u have the right controller, then it can be the best thing around.
These are all just my thoughts based on past experiences, if u find a way to make 1 tick better in any case i mentioned that I personally couldn't, that's awesome! and you definitely have to let me know.!