The bad thing is that it could be a LOT smaller and more versatile. You could probably integrate OR, XOR, and AND within a single 'layer.' then add XORs for conditional inverters to A and B. Another bit for the carry-in on the first adder, and you have an ALU that contains all the logic functions that yours currently has, except shifting. It's possible to add left shifting via another few control bits that control the propagation of A and B, to get A+A and B+B for left-shifting. Right shifting I don't think can be added in any way to the main layer, though I might be wrong.
It's been a while since a major update, but it seems as though you're very close to finishing the CPU & RAM. Looking forward to seeing the fastest CPU to date.
Alright, it's just that in your post you sounded a bit pessimistic. As I said in my previous post I'm not very adept with redstone computers so i cant really tell you which way you should go when building one so to me for now as long as there is improvement in some way then its a plus to me. although i am figuring out more and more for it, pretty soon I'm sure my opinion will change.
What is the point of a 64 bit computer? Not like its gonna be faster heck its gonna be slowers
Having a larger bit count is not just "not better", it will probably end up *worse.* Learning how to build a *fast* CPU before you try to add buzz word tags to it might be a good start. No offense, but the large bit count is obviously just a hype ploy.
The change from 16 bit to 32 bit is absolutely useless unless you have a memory space that can't be addressed with 16 bits. If anything, it'll probably be slower than most CPUs out there, due to excessive size, and without any real benefits over 16 bit CPUs.
Although its big,but it 0 tick.Can be using for a instant d flip flop or something...
Not only is it big, but because it's instant, it doesn't work. An instant NOT gate with input hooked up to output (regardless of the AND) will always screw up, and since it causes the piston simultaneous extended/retracted glitch, it's not easy to fix when it does get stuck. Basically, it's impractical for any project but for the smallest ones that allow manual resetting for every use of one latch.
I have a pulse that outputs 1 pulse every redstone tick. However, I need a way to invert this signal... It's too fast for a sticky piston inverter, as it would just delete the block that the sticky piston uses, and bug the piston.
It's too fast for a torch inverter...
Is there anyway to invert a signal, instantly?
Piston inverters are instant. That's not the same thing as an inverter that operates on a 1 tick clock. And, as far as I know, no, there are no inverters that can handle a 1 tick clock, unless you choose to use mods.
My brain is fried right now, I'll check out your video again when I've gotten some sleep and am mildly sane. I mean, I've watched it once just now, but everything just flew by.
Haha! Another guide that I'm looking forward to on instant logic (sancarn's decoder being the first). I'm good with logic, but the processes of Minecraft updates and pistons escapes me. I've known about sethbling's NOT gates for months now, and I just figured out last week how they work. It was a moment of sudden and overwhelming enlightenment. xD
You're saying that the all changes in inputs cause a change in the outputs instantly, but that it takes 2 ticks for the pistons to extend/retract fully before accepting new inputs, correct? (i.e. instant output, 2 tick clock)
I understand the idea behind the pulse going down one of the two wires. It's just that the internal gates I built as a test weren't instant. I probably just did that wrong, I suppose.
That is very odd... Maybe this is just another reason why we can't use single instant wire and we have to start thinking in dual wires more often?
Ooo and talking about dual wire logic gates. You can use the decoder I made as a programmable Logic gate. I know this isn't exactly new news =P but still. I made a 15x5x9 XOR gate using dual wire. Do you know if you can make an instant RS-NOR latch using sethblings instant not gates?
I'm not sure about that. How do dual wire systems work, exactly? I realize they use pulses and internal piston gates, but the internal piston gates aren't instant (unless I'm doing it wrong).
As for an RS NOR, while it's possible to do it with sethbling's instant NOT gates, it'd be horribly huge and buggy. I would think that there is a more compact way to do it, and still have it be instant.
Strange... That normally happens when you don't have the wire on the bottom right so the pistons output powers the piston... Haha now all you need is a block destroyer to destroy that extended piston =P
When i don't have that wire, it just sets/resets so fast that it loses the stone block. That resets by itself when the piston extends again and sticks to the block. However, when this happens, the piston is permanently stuck in this double state, unless I purposely break it.
You are sure that it isn't just a north-south / east-west thing right?
Not entirely, but both A and B are oriented in the same direction, and since A is working properly, I'm *almost* sure that it's not a direction quirk.
edit:
I just found a really weird glitch. I hooked up the wires for A AND B OR !B slightly differently, and it seemed like it fixed the problem I was having. However, instead of causing a short pulse to set/reset the piston, it somehow managed to make the piston simultaneously extend/retract. Take a look:
0
The bad thing is that it could be a LOT smaller and more versatile. You could probably integrate OR, XOR, and AND within a single 'layer.' then add XORs for conditional inverters to A and B. Another bit for the carry-in on the first adder, and you have an ALU that contains all the logic functions that yours currently has, except shifting. It's possible to add left shifting via another few control bits that control the propagation of A and B, to get A+A and B+B for left-shifting. Right shifting I don't think can be added in any way to the main layer, though I might be wrong.
0
0
The answer to that... is this:
Having a larger bit count is not just "not better", it will probably end up *worse.* Learning how to build a *fast* CPU before you try to add buzz word tags to it might be a good start. No offense, but the large bit count is obviously just a hype ploy.
0
The change from 16 bit to 32 bit is absolutely useless unless you have a memory space that can't be addressed with 16 bits. If anything, it'll probably be slower than most CPUs out there, due to excessive size, and without any real benefits over 16 bit CPUs.
0
Not only is it big, but because it's instant, it doesn't work. An instant NOT gate with input hooked up to output (regardless of the AND) will always screw up, and since it causes the piston simultaneous extended/retracted glitch, it's not easy to fix when it does get stuck. Basically, it's impractical for any project but for the smallest ones that allow manual resetting for every use of one latch.
0
Piston inverters are instant. That's not the same thing as an inverter that operates on a 1 tick clock. And, as far as I know, no, there are no inverters that can handle a 1 tick clock, unless you choose to use mods.
0
My brain is fried right now, I'll check out your video again when I've gotten some sleep and am mildly sane. I mean, I've watched it once just now, but everything just flew by.
1
0
You're saying that the all changes in inputs cause a change in the outputs instantly, but that it takes 2 ticks for the pistons to extend/retract fully before accepting new inputs, correct? (i.e. instant output, 2 tick clock)
0
You do realize that you'd have to understand how a real life web server works first... don't you?
0
0
2) How fast does this send data (bandwidth in bits per tick)?
0
I'm not sure about that. How do dual wire systems work, exactly? I realize they use pulses and internal piston gates, but the internal piston gates aren't instant (unless I'm doing it wrong).
As for an RS NOR, while it's possible to do it with sethbling's instant NOT gates, it'd be horribly huge and buggy. I would think that there is a more compact way to do it, and still have it be instant.
0
When i don't have that wire, it just sets/resets so fast that it loses the stone block. That resets by itself when the piston extends again and sticks to the block. However, when this happens, the piston is permanently stuck in this double state, unless I purposely break it.
0
Not entirely, but both A and B are oriented in the same direction, and since A is working properly, I'm *almost* sure that it's not a direction quirk.
edit:
I just found a really weird glitch. I hooked up the wires for A AND B OR !B slightly differently, and it seemed like it fixed the problem I was having. However, instead of causing a short pulse to set/reset the piston, it somehow managed to make the piston simultaneously extend/retract. Take a look: