1
80 Byte Random Access Memroy
I've been refining some 80 Byte RAM I made a while back. Write time is still hideous, the redstone signal has to climb the entire tower but I've got the read time from any address under 1.5 secs. Might soon be possible to actually use this practically.
1 bit
1 bit
Create an account or sign in to comment.
17
1
Pewmanluigi_vampaI've been refining some 80 Byte RAM I made a while back. Write time is still hideous, the redstone signal has to climb the entire tower but I've got the read time from any address under 1.5 secs. Might soon be possible to actually use this practically.
-snip-
-snip-
1 bit
-snip-
fantastic job, friend! quite the intellect you've got there about redstone. never really learned it, to be honest haha.
Thanks Pew
1
Looks awesome, but does it have an actual purpose in MC?
Oh, and can you make a 4.1 Ghz one? Just kidding
Oh, and can you make a 4.1 Ghz one? Just kidding
1
Purpose is to build a minecart track that can be controlled from a central point on the server. One byte can store the open/closed settings for a 4 point cart intersection/junction. I want to be able to stand in a control room and control the direction of a cart where ever it is in the entire server.
1
How in the world are people doing this? All I know is that I'm bad at redstone.
1
luigi_vampaI've been refining some 80 Byte RAM I made a while back. Write time is still hideous, the redstone signal has to climb the entire tower but I've got the read time from any address under 1.5 secs. Might soon be possible to actually use this practically.
-snip-
-snip-
1 bit
-snip-
fantastic job, friend! quite the intellect you've got there about redstone. never really learned it, to be honest haha.
1
Waiting for 1KB memory :p that's 1024 bytes for those who don't know
1
I'm working on it! Put 2020 in your diary!
Edit: Scrap that, Moore's law defines when you'll get it!
Edit: Scrap that, Moore's law defines when you'll get it!
1
I placed all the redstone on different colour wools just to keep track of the paths. I think they were:
Red - intermediate wiring
Green - to set read/write
Purple - data out
Yellow - data in
Light blue - address bus (power here to turn on bit to read/write to/from).
Red - intermediate wiring
Green - to set read/write
Purple - data out
Yellow - data in
Light blue - address bus (power here to turn on bit to read/write to/from).
1
use simg instead of img. simg scales it to fit the post.
1
Thanks.
1
luigi_vampaSearchndstroyHow is this done?
EDIT:
Try to use blocks to represent bits, ex: stone for 0, and dirt for 1.
So lets say I have a render distance of 5 chunks. 5*5 = 25 chunks, each chunk can hold 16*16*255 = 65280 blocks. 25*65280 = 1632000 blocks. So you could theoretically have 1632000 bits, or 204000 bytes of memory in a 5*5 chunk rendering distance. Not sure whether using blocks is the best way though.Click to reveal
that's a great deal more RAM than I've managed! Could you repost the images that were in the spoiler? I can't seethem.
Open the image in a new tab
But that is only theoretically, in those images I've used 11 blocks for one byte instead of 8(1 for stating whether it is unsigned or not, and 2 for the marks of where it starts and where it ends) The only problem is chunks, they are 16 by 16. I'm not sure whether you could do this from top to bottom instead of west to east, or south to north(so you can make sure bytes are stored in a chunk correctly, you can have 252 bit integer SAFELY compared to a 13 bit integer safely)
Unfortunately, there aren't any integers that can hold anything more than 2^64(I'm pretty sure in Java the max is a long, but I'm not so sure on floating point integers) which is, so having the 252 bit integer would be hard to handle.
But then there's the problem of detecting the blocks with commands....
1
SearchndstroyHow is this done?
EDIT:
Try to use blocks to represent bits, ex: stone for 0, and dirt for 1.
So lets say I have a render distance of 5 chunks. 5*5 = 25 chunks, each chunk can hold 16*16*255 = 65280 blocks. 25*65280 = 1632000 blocks. So you could theoretically have 1632000 bits, or 204000 bytes of memory in a 5*5 chunk rendering distance. Not sure whether using blocks is the best way though.Click to reveal
that's a great deal more RAM than I've managed! Could you repost the images that were in the spoiler? I can't seethem.
1
Not sure what all the levers are about...
Also, have you looked into the ORE server? It's great for people like you (and me in my spare time :3) http://openredstone.org
Also, have you looked into the ORE server? It's great for people like you (and me in my spare time :3) http://openredstone.org
1
This is so very far from legit! All the black wool/lever combos are logic gates (mostly ANDs) for space saving from the craftbook plugin.
1
How is this done?
EDIT:
Try to use blocks to represent bits, ex: stone for 0, and dirt for 1.
So lets say I have a render distance of 5 chunks. 5*5 = 25 chunks, each chunk can hold 16*16*255 = 65280 blocks. 25*65280 = 1632000 blocks. So you could theoretically have 1632000 bits, or 204000 bytes of memory in a 5*5 chunk rendering distance. Not sure whether using blocks is the best way though.
EDIT:
Try to use blocks to represent bits, ex: stone for 0, and dirt for 1.
So lets say I have a render distance of 5 chunks. 5*5 = 25 chunks, each chunk can hold 16*16*255 = 65280 blocks. 25*65280 = 1632000 blocks. So you could theoretically have 1632000 bits, or 204000 bytes of memory in a 5*5 chunk rendering distance. Not sure whether using blocks is the best way though.
Click to reveal
1
I don't know how people do this, this is really amazing!
1
thanks.