Published Oct 8th, 2013, 10/8/13 2:10 pm
- 455 views, 2 today
- 28 downloads, 0 today
6
The APower2 GPU
This is the final upgrade for the APower Series.
In fact this is an old project which I found and decided to upload it.
What it does?
It takes 64 redstone wires, puts them in ram, splits them into 4 packets and sends it them to the display.
How does it work?
First there needs to be an image which can be drawn at the drawing board.
You can save the image to the prototype storage or simply store it on the gpu by turning the "Write Dis X" on for a couple of seconds and then turning it back off (so the lamp is off).
The redstone signals will be saved on the ram.
Then you can activate the gpu itself with the lever, a clock should start doing all the work ( the clock is inside the AP II GPU chip).
If the clock does not work, try to update it manually, this only happens when the gpu is running on save and quit.
The signal should be split up, send to the display and decoded for the pixels on the display.
This project is pretty intensive on system resources.
I was able to run it very well on bukkit using ChunkKeeper.
In survival it did work but when the chunks with the clock unload it all just falls apart.
I recommend you use optifine and set the render distance to far or more,
and use a least 1GB of ram.
This is the final upgrade for the APower Series.
In fact this is an old project which I found and decided to upload it.
What it does?
It takes 64 redstone wires, puts them in ram, splits them into 4 packets and sends it them to the display.
How does it work?
First there needs to be an image which can be drawn at the drawing board.
You can save the image to the prototype storage or simply store it on the gpu by turning the "Write Dis X" on for a couple of seconds and then turning it back off (so the lamp is off).
The redstone signals will be saved on the ram.
Then you can activate the gpu itself with the lever, a clock should start doing all the work ( the clock is inside the AP II GPU chip).
If the clock does not work, try to update it manually, this only happens when the gpu is running on save and quit.
The signal should be split up, send to the display and decoded for the pixels on the display.
Additional Notes
Problems you will probably run into!This project is pretty intensive on system resources.
I was able to run it very well on bukkit using ChunkKeeper.
In survival it did work but when the chunks with the clock unload it all just falls apart.
I recommend you use optifine and set the render distance to far or more,
and use a least 1GB of ram.
| Credit | Texture Pack in pictures: Faithful |
| Progress | 100% complete |
| Tags |
tools/tracking
2522431
2
apower-2-gpu
a1star
Cornbread_Alphanumeric
Stubbs1
garlicbreathinator
traincrisis
SpellmakerTheHybrid
ScotsMiser
Acul0s
1368
Create an account or sign in to comment.
- Since it stores 64 pixels pictures isn't it faster to hook the storage directly up on the screen and at a memory controller?
- How old is this project? I mean I encountered some command blocks inside the cpu.
- How many pictures could be saved? in other words what capacity does it have?
- Can it power up multiple screens?
Connecting the storage to the screen would have been a lot faster, but the point was to encode it and send it to the display.
I built in 1.5.1, the command blocks were helping me debug the redstone, so they are not needed.
You can save 10 pictures in the storage unit, and the load them onto the display.
It does power both screens, you can write to them individually.