It's a fairly small design, however, the one big flaw I see with this design is that it doesn't have an edge trigger incorporated into it, so you're pretty much stuck with using buttons with this one, as adding a monostable circuit on top would make this larger than the one in the OP (and it would also add on about 1-2 ticks of delay).
Thanks for pointing that out. I see now. I knew there was a downside :sad.gif: ... I'll add it to the OP anyway, but keep the design I already have (Which is rising edge-triggered). Ah well...
In the meanwhile, anyone else have any good ideas for things on could make vertical?
Thanks for pointing that out. I see now. I knew there was a downside :sad.gif: ... I'll add it to the OP anyway, but keep the design I already have (Which is rising edge-triggered). Ah well...
In the meanwhile, anyone else have any good ideas for things on could make vertical?
half/full adders :biggrin.gif:. Have lots of fun lol. I may try to do that too, if I ever get an idea :smile.gif:
Dude... your XOR doesn't work. It's impossible to make a vertical XOR that small anyways. Same for the XNOR. Plus, the TFF can be way smaller, and not be using a gay minecart. The RS NOR Latch has been made already. And also, the fast clock you made is 2 ticks and not 1. Pretty cool though, but I'm sure you can make it smaller. You don't seem to look for more compactness or speed.
Dude... your XOR doesn't work. It's impossible to make a vertical XOR that small anyways. Same for the XNOR. Plus, the TFF can be way smaller, and not be using a gay minecart. The RS NOR Latch has been made already. And also, the fast clock you made is 2 ticks and not 1. Pretty cool though, but I'm sure you can make it smaller. You don't seem to look for more compactness or speed.
Firstly, do not be rude on my thread. Your immaturity depresses me.
Secondly, my XOR and XNOR do work. Try them out first before saying things like that.. You only need 3 torches for a standard XOR. Most people use more though because those designs have been popularized.
Thirdly, minecarts do not have sexual orientation, nor do they have gender.
Fourthly, if you have a smaller TFF which is edge-triggered, I would LOVE to see it.
Fifthly, I had no idea it has existed before. Then again, most RS-NOR designs in existence have been found at this point.
Sixthly, that clock is a 1-clock. It is one for 1 tick and then off for 1 tick. That is the fastest regular clock which does not rely on the 0-tick principles of pistons.
Finally, I do go for compactness and speed. I want to get the best design possible. Now, I don't always get that right away, which is why I encourage people to submit their own designs.
PS. I see you're new here. Why don't you start off with a better reputation?
alright, well here I am with a 1 wide half adder *yay :happy.gif:*
Inputs A and B are on the right. The Sum is the bottom output and the carry-out is on top. Dimensions are 5x8. It may be able to be compacted further, but yeah (feel free to make it smaller). Oh, ignore the big one in the background. That was just me playing about.
Partial credits to metapig for his xor design (it's the base I used, and then I just expanded off it).
Anyways, I'm gonna start playing around with full adders soon. They're much more complex to build, so I'm not sure if I'll ever get one that's 1 wide, but I sure as hell am gonna try.
Firstly, do not be rude on my thread. Your immaturity depresses me.
Secondly, my XOR and XNOR do work. Try them out first before saying things like that.. You only need 3 torches for a standard XOR. Most people use more though because those designs have been popularized.
Thirdly, minecarts do not have sexual orientation, nor do they have gender.
Fourthly, if you have a smaller TFF which is edge-triggered, I would LOVE to see it.
Fifthly, I had no idea it has existed before. Then again, most RS-NOR designs in existence have been found at this point.
Sixthly, that clock is a 1-clock. It is one for 1 tick and then off for 1 tick. That is the fastest regular clock which does not rely on the 0-tick principles of pistons.
Finally, I do go for compactness and speed. I want to get the best design possible. Now, I don't always get that right away, which is why I encourage people to submit their own designs.
PS. I see you're new here. Why don't you start off with a better reputation?
I may have mistaken on the XOR, though you need a repeater on the bottom input to isolate it, which makes the XOR longer. When I first tried them I guess I did without a lever or a repeater. I still think though, that your TFF is big, and that minecarts in logic gates/latches are nooby. I actually have 1wide edge triggered TFF designs, one of mine that uses a glitch but that is pretty fast, and another one (not mine) that uses a 1wide DFF. Nothing to say anymore about the RS NOR, but the clock is a 2 clock, the output is on every 2 ticks.
And for your last point, I think you're right to ask people for their own design. I think you have a lot to learn. I may upload pics of the TFF designs.
PS : I just wanted to trololololol on the redstone subforum.
I may have mistaken on the XOR, though you need a repeater on the bottom input to isolate it, which makes the XOR longer. When I first tried them I guess I did without a lever or a repeater. I still think though, that your TFF is big, and that minecarts in logic gates/latches are nooby. I actually have 1wide edge triggered TFF designs, one of mine that uses a glitch but that is pretty fast, and another one (not mine) that uses a 1wide DFF. Nothing to say anymore about the RS NOR, but the clock is a 2 clock, the output is on every 2 ticks.
And for your last point, I think you're right to ask people for their own design. I think you have a lot to learn. I may upload pics of the TFF designs.
PS : I just wanted to trololololol on the redstone subforum.
Even if the input needs a repeater, it's not counted in the size.
Anything in the game is acceptable as part of redstone logic.
Feel free to actually contribute if you have improved designs of anything here, or something new.
Here in the Redstone forum we use Redstone ticks to describe Redstone devices.
PS : That's because you're a douche.
I may have mistaken on the XOR, though you need a repeater on the bottom input to isolate it, which makes the XOR longer. When I first tried them I guess I did without a lever or a repeater. I still think though, that your TFF is big, and that minecarts in logic gates/latches are nooby. I actually have 1wide edge triggered TFF designs, one of mine that uses a glitch but that is pretty fast, and another one (not mine) that uses a 1wide DFF. Nothing to say anymore about the RS NOR, but the clock is a 2 clock, the output is on every 2 ticks.
And for your last point, I think you're right to ask people for their own design. I think you have a lot to learn. I may upload pics of the TFF designs.
PS : I just wanted to trololololol on the redstone subforum.
If you had read through the thread, you would have seen that the OP wanted to avoid TFFs and other latches/flipflops/gates that used glitches. Also, it is technically speaking, a 1-clock in redstone ticks. If you mean that the output only goes on every 2 redstone ticks, which is why it's a 2-clock, then it would be impossible to make a 1-clock, because that would mean the output would need to be on every tick, which is just a constant current. In order to make it only last for 1 tick, it must also be off for 1 tick. Therefore, the output will naturally only come on every 2 ticks.
But correct me if I've misinterpreted what you've said incorrectly. Anyways, saying that using minecarts is nooby is like saying that using pistons in your circuit, or anything not directly intended for redstone, is nooby. It should be considered innovative to use mechanics in the game other than the actual redstone to build different circuitry.
Btw, @OP: I think the TFF with the minecart posted in the design actually works based on a glitch unfortunately. I believe it utilizes the glitch where redstone dust affect the mechanics of the piston when they're powered diagonally from them (I'm not sure if they exactly power them, but if the piston is extended, the cause the piston to remain extended when they power). It's a bit difficult to explain but yeah. I'm not 100% sure though, but I'm fairly certain, because theoretically speaking, a tff with that design should not be able to work on a reliable basis, since the torches would be going on and off at the same time.
This DFF operates in 4 ticks (I think). It is 4x7, although the output is a block, which means a repeater is needed. Although I altered it, the credit for this design all goes to Lancelote123. His designs gave me the idea! The reason I changed his design was because it used a 2-tick RS-NOR, so I altered it slightly to use mine. If you'd like to see his design, check them out on page 2, post 18.
I believe this is actually called a D-latch not a D-flip-flop. Flip-flops are edge triggered, not level triggered as noted here:
Firstly, to address the glitch thing: I will consider it a bug UNTIL someone can show me proof of someone at Mojang saying that it is not.
I spent quite a bit of time searching for this evidence today. Sticky piston block-dropping is not a bug; Jeb was aware that his fix (in 1.7.3) for early-1.7's block-duplication glitch "broke stable 1-tick clocks using [sticky] pistons" (See his July 6 tweet, and his post on Reddit about that tweet) I infer the "[sticky]" since other kinds of piston 1-clocks were unaffected. At the time of the tweet, the best-known piston 1-clocks used sticky pistons—e.g., the first clock shown (appears at time 1:25) in the July 1 classic video "Pistons: A revolution for Redstone Circuitry". If you build this design in 1.7.3+, you'll see that when you flip the switch, the piston pushes the wool out and then retracts one tick later, leaving the wool behind—this is the new behavior that Jeb acknowledges in his tweet. Why did Jeb's tweet speak specifically about clocks being broken, instead of the broader implications of the fix as we understand them today? Because Jeb was thinking in terms of breakage rather than introduction of new design possibilities, and because the common 1-clock design was the most visible thing broken. Jeb's response to this breakage ("Oh well, pistons aren't supposed to move that fast anyway :wink.gif:") indicates that he chose to view the new behavior as the "correct" behavior.
So, to summarize:
1) Jeb was aware of the block-dropping, and chose to keep it in the game
2) Jeb viewed the block-dropping as correct behavior, as justified by his belief that [sticky] pistons should not be driven "that fast".
I think we can conclude that block-dropping is not a bug, but instead an acknowledged and endorsed side-effect of the 1.7.3 duplication bug-fix. Hope this helps.
Yeah... the terminology people use to describe redstone circuits is in general a bit off. The most glaring error, I think, is calling an SR-latch that uses pistons (for example, the one in Grizdale's piston logic compendium) an "RS NOR latch." Where are the NOR gates? There aren't any in the piston design! (Also, electronics literature usually uses "SR latch" instead of "RS latch"; I think this makes sense, since "set-reset latch" sounds reasonable, but "reset-set latch" sounds odd.) In any event, the terms used don't really matter as long as we use them consistently, and I think we do a relatively good job of being consistent. :smile.gif:
Thanks for pointing that out. I see now. I knew there was a downside :sad.gif: ... I'll add it to the OP anyway, but keep the design I already have (Which is rising edge-triggered). Ah well...
In the meanwhile, anyone else have any good ideas for things on could make vertical?
half/full adders :biggrin.gif:. Have lots of fun lol. I may try to do that too, if I ever get an idea :smile.gif:
Firstly, do not be rude on my thread. Your immaturity depresses me.
Secondly, my XOR and XNOR do work. Try them out first before saying things like that.. You only need 3 torches for a standard XOR. Most people use more though because those designs have been popularized.
Thirdly, minecarts do not have sexual orientation, nor do they have gender.
Fourthly, if you have a smaller TFF which is edge-triggered, I would LOVE to see it.
Fifthly, I had no idea it has existed before. Then again, most RS-NOR designs in existence have been found at this point.
Sixthly, that clock is a 1-clock. It is one for 1 tick and then off for 1 tick. That is the fastest regular clock which does not rely on the 0-tick principles of pistons.
Finally, I do go for compactness and speed. I want to get the best design possible. Now, I don't always get that right away, which is why I encourage people to submit their own designs.
PS. I see you're new here. Why don't you start off with a better reputation?
Inputs A and B are on the right. The Sum is the bottom output and the carry-out is on top. Dimensions are 5x8. It may be able to be compacted further, but yeah (feel free to make it smaller). Oh, ignore the big one in the background. That was just me playing about.
Partial credits to metapig for his xor design (it's the base I used, and then I just expanded off it).
Anyways, I'm gonna start playing around with full adders soon. They're much more complex to build, so I'm not sure if I'll ever get one that's 1 wide, but I sure as hell am gonna try.
I may have mistaken on the XOR, though you need a repeater on the bottom input to isolate it, which makes the XOR longer. When I first tried them I guess I did without a lever or a repeater. I still think though, that your TFF is big, and that minecarts in logic gates/latches are nooby. I actually have 1wide edge triggered TFF designs, one of mine that uses a glitch but that is pretty fast, and another one (not mine) that uses a 1wide DFF. Nothing to say anymore about the RS NOR, but the clock is a 2 clock, the output is on every 2 ticks.
And for your last point, I think you're right to ask people for their own design. I think you have a lot to learn. I may upload pics of the TFF designs.
PS : I just wanted to trololololol on the redstone subforum.
Get out of here.
Even if the input needs a repeater, it's not counted in the size.
Anything in the game is acceptable as part of redstone logic.
Feel free to actually contribute if you have improved designs of anything here, or something new.
Here in the Redstone forum we use Redstone ticks to describe Redstone devices.
PS : That's because you're a douche.
If you had read through the thread, you would have seen that the OP wanted to avoid TFFs and other latches/flipflops/gates that used glitches. Also, it is technically speaking, a 1-clock in redstone ticks. If you mean that the output only goes on every 2 redstone ticks, which is why it's a 2-clock, then it would be impossible to make a 1-clock, because that would mean the output would need to be on every tick, which is just a constant current. In order to make it only last for 1 tick, it must also be off for 1 tick. Therefore, the output will naturally only come on every 2 ticks.
But correct me if I've misinterpreted what you've said incorrectly. Anyways, saying that using minecarts is nooby is like saying that using pistons in your circuit, or anything not directly intended for redstone, is nooby. It should be considered innovative to use mechanics in the game other than the actual redstone to build different circuitry.
Btw, @OP: I think the TFF with the minecart posted in the design actually works based on a glitch unfortunately. I believe it utilizes the glitch where redstone dust affect the mechanics of the piston when they're powered diagonally from them (I'm not sure if they exactly power them, but if the piston is extended, the cause the piston to remain extended when they power). It's a bit difficult to explain but yeah. I'm not 100% sure though, but I'm fairly certain, because theoretically speaking, a tff with that design should not be able to work on a reliable basis, since the torches would be going on and off at the same time.
It uses 3 torches and 1 redstone (3 sticks, and 4 redstone). I don't know exactly how many ticks it is, but it seems to be pretty short.
Who thinks I should continue with this thread?
I think you should continue... and maybe my D Flip Flop is worthy of the OP?
It is 5 x 5 x 1 and should be two ticks for both on and off.
Hopefully it's worthy of consideration at least.
Thanks!
I do :biggrin.gif:! Totally an awesome idea you have here :wink.gif:
BTW, that DFF is genius! I have already made a four-high six-long version with the same speed.
So expect the OP is be updated later today. I gotta go to school...
I think you should keep maintaining the topic and such. You don't find many topics with a bunch of vertical stuff.
You should keep continuing it.
I believe this is actually called a D-latch not a D-flip-flop. Flip-flops are edge triggered, not level triggered as noted here:
I spent quite a bit of time searching for this evidence today. Sticky piston block-dropping is not a bug; Jeb was aware that his fix (in 1.7.3) for early-1.7's block-duplication glitch "broke stable 1-tick clocks using [sticky] pistons" (See his July 6 tweet, and his post on Reddit about that tweet) I infer the "[sticky]" since other kinds of piston 1-clocks were unaffected. At the time of the tweet, the best-known piston 1-clocks used sticky pistons—e.g., the first clock shown (appears at time 1:25) in the July 1 classic video "Pistons: A revolution for Redstone Circuitry". If you build this design in 1.7.3+, you'll see that when you flip the switch, the piston pushes the wool out and then retracts one tick later, leaving the wool behind—this is the new behavior that Jeb acknowledges in his tweet. Why did Jeb's tweet speak specifically about clocks being broken, instead of the broader implications of the fix as we understand them today? Because Jeb was thinking in terms of breakage rather than introduction of new design possibilities, and because the common 1-clock design was the most visible thing broken. Jeb's response to this breakage ("Oh well, pistons aren't supposed to move that fast anyway :wink.gif:") indicates that he chose to view the new behavior as the "correct" behavior.
So, to summarize:
1) Jeb was aware of the block-dropping, and chose to keep it in the game
2) Jeb viewed the block-dropping as correct behavior, as justified by his belief that [sticky] pistons should not be driven "that fast".
I think we can conclude that block-dropping is not a bug, but instead an acknowledged and endorsed side-effect of the 1.7.3 duplication bug-fix. Hope this helps.
Yeah... the terminology people use to describe redstone circuits is in general a bit off. The most glaring error, I think, is calling an SR-latch that uses pistons (for example, the one in Grizdale's piston logic compendium) an "RS NOR latch." Where are the NOR gates? There aren't any in the piston design! (Also, electronics literature usually uses "SR latch" instead of "RS latch"; I think this makes sense, since "set-reset latch" sounds reasonable, but "reset-set latch" sounds odd.) In any event, the terms used don't really matter as long as we use them consistently, and I think we do a relatively good job of being consistent. :smile.gif:
What do you think?