03-08-2015, 09:45 PM
(This post was last modified: 03-09-2015, 12:16 AM by Apocryphan.)
A fellow redditor pointed out that this is caused by race condition in the coding, currently I am getting the 1-2 tick visual by knocking out part of a 4 tick signal with 2 interruptions, but it will not act like a 1.5 tick.
If I can knock it down to a 0-1 tick visual that acts like a 1 or 1.5 tick. It may actually jump across wire when appearing as a 0 tick but still travelling at the speed of 1tick. I know half ticks have trouble transferring thru comparators, but if it can be backed with a 1.5 tick, we may be able to send it with only 1.5 tick limitations.
If this is possible it may be the key to storing 2 values in a 2 comparator loop without the greater value combining with other 1 ticks. I will also try and string the 1-2 tick values to see if i can make a signal appear solid or striped.
Ironically this was discovered while proving that they travel at the same speed regardless of side inputs. At first results were as expected. And then I wanted to go as far as to say that even pulsing in the side input will not hinder the speed of it. And had i not placed the torch down at the exact off tick during the 3 trials, i wouldn't have seen the occurrence and went on trying to find a pattern to the directional bug, and testing for game tick delay between transferring signals through blocks and other ways transferring.
If I can knock it down to a 0-1 tick visual that acts like a 1 or 1.5 tick. It may actually jump across wire when appearing as a 0 tick but still travelling at the speed of 1tick. I know half ticks have trouble transferring thru comparators, but if it can be backed with a 1.5 tick, we may be able to send it with only 1.5 tick limitations.
If this is possible it may be the key to storing 2 values in a 2 comparator loop without the greater value combining with other 1 ticks. I will also try and string the 1-2 tick values to see if i can make a signal appear solid or striped.
Ironically this was discovered while proving that they travel at the same speed regardless of side inputs. At first results were as expected. And then I wanted to go as far as to say that even pulsing in the side input will not hinder the speed of it. And had i not placed the torch down at the exact off tick during the 3 trials, i wouldn't have seen the occurrence and went on trying to find a pattern to the directional bug, and testing for game tick delay between transferring signals through blocks and other ways transferring.