Proper I heard the delay has to do with the infinite loop bug. But the code
to check for this is very long and takes too long soo updating is random
because of that. not sure though but if this is the case then I think the
will fix it after all it is the first snapshot lot's of things can change.
Come on, I know you. You go evil monkey man if someone even pronounced XOR
as [ex-o-aur]. I think that he did wonderful. Now I know that XOR is where
one of them must be on while the other must be off, they can't both me on,
and they can not both me off. Thank you, PI19, you helped me a lot.
i have a question for you is it possible to create a gate that if you flip
a lever a door opens then flip a lever on the other side of the door and
the door closes and when you flip the first lever the door opens that
possible now?
The difference is that this one is two wide tileable, meaning you can stack
them up against each other. That design is fantastic if you don't need to
do that, but for most of my applications it wouldn't work.
What you're looking for is a type of memory called an RS NOR latch. If you
look it up you'll find plenty of designs and you'll probably find tutorials
that show you exactly how to do what you just described.
Right now it appears to be two ticks - when comparators were 0 ticks it
would have been 1 tick. :( We'll see what happens in the coming updates,
but if they return to 0 ticks this will be a very useful gate.
Thanks! I'm not sure - this was the first design I came up with and I'll
probably see if I can compact it a bit more. :D And you're right - I think
I was sitting away from the mic a bit for this one! :P
Nice! Maybe it interests you, that Im just uploading a video about a
converter, which converts current strength into a digital signal. If you
want to see it, look on my channel in 2 hours... xD
I just did it too and I'm pretty sure I know EXACTLY what you did. Did you
turn the output comparators to subtract and switch the repeaters (along
with a block move or two) with comparators?
Woo Redstone Week! So this is a special set of tutorials focusing on redstone, I decided to seperate these as redstone is a huge topic, and is far easier to explain ...
In this tutorial I give a basic overview of the redstone comparator (Not at all a full explanation being that there would be a lot to go through). We take a brief look ...
Dutchj - Redstone For Beginners Lesson 2: XOR and Memory Cells
In this second lesson I will be explaining the last logic gate, as well as delving into some simple memory cells, namely the XOR gate, the RS NOR latch and the ...
This is a fantastic looking module. Thanks for the video!
Redstone Concept: Anti-Burnout Logic (Torchless and Pistonless)
In this video I explain a concept I'm calling "anti-burnout". Anti-burnout involves using comparator based NOT gates to build highly responsive redstone circuits.
well we know how long time it took to fix repeaters... wonder if it's going
to take just as long now. Oh wait there are still repeater bugs... It's sad
that even though redstone got an overhaul it's still buggy as hell.
Repeaters that eat signal, comparators that sometimes doesn't know what
state it's in and that they sometimes have no delay or has too much delay.
If they set everything to 1 tick as I've reasoned for a year then most of
these bugs would disappear, well at least timing bugs.
Yep it's possible to do a 10Hz computer using this, you just have to be
careful in your timing to make sure the devices that take longer than 1
tick to finish will propagate the 1 tick signals through properly. See
BIGWUNuvDbunch's (guy1234567890) video of his 3 tick alu using this
principle of careful timing to get a max speed torch based alu.
That's exactly what I was thinking. I'm hoping Mojang decides to give
comparators a delay of 1 tick because it makes so much more sense to have
as many blocks as possible functioning with the same delay. If they do my
2-wide stackable anti-burnout XNOR will be 2 ticks and the XOR can easily
be synced at 2 ticks - this could be pretty cool!
Hey, the comparators are being completely consistent, they just have a 0.5
tick delay, and repeaters are only updated at every whole tick, so if the
comparator goes off at a half tick later than you expected, you could get a
10001, or a half-tick early and you could have the 101 situation.
Inversions are very useful for doing logic. With OR and NOT gates we can
build any of the binary logic gates and comparators (when set to subtract)
give us a simple and fast NIMPLIES (does not imply) gate, so you can think
of these as our basic components for building more complex logic.
I will build one soon! I'm just waiting for the timing issues to be fixed
so I can make sure everything is synced. The 2 wide tileable XNOR and XOR
I've built would both be synced 2 ticks if comparators get a delay of one
tick (which I think is what they were intended to have).
Ooh that's interesting indeed! 1 tick pipelines open up a whole new level
of CPU speed. :D Too bad about those timing issues, though. I've when they
make a corner with comparator -> block -> comparator, in 2 of the 4
directions they will both update in the same tick.
Very nice! But now that it's possible to do 1 tick logic, I wonder why
Mojang keeps the restrictions on torches - would be so much easier (less to
learn and maybe even less code) if those reacted to 1 ticks properly.
Finally comparators have a fixed delay of 1 tick on every side in every
situation. Too sad that they no longer respond to 1 tick pulses. Anyway,
it's still faster than redstone torches.
Dinnerbone just closed the bug report on inconsistent delays on comparators
this morning as fixed, not sure on which way but looking forward to 13w04b
or 13w05a whichever comes next.
I hope you guys are talking about 1 game tick (half a red stone tick)
Because its the comparators ability to be half a red stone tick that makes
it any better then using repeaters.
Great ! :D I hope the comparator will have a fixed delay soon, it will be
awesome ! (and that the whole bunch of very strange redstone bugs will be
fixed too)
It's hard to say because of the strange comparator delays. My hope is that
comparators end up with a single tick of delay in which case it'd be 2
ticks.