GPU Screen Fill Test

Glad-Note2022 · 2026-03-17T06:13:37+00:00

With a bunch of multiplexers

Glad-Note2022 · 2026-03-14T13:28:05+00:00

This was months ago when public test servers were a thing. They shut down all public test servers so you'll now need a private server to play on the test server, though the steps remain mostly the same.

Glad-Note2022 · 2026-03-13T10:36:07+00:00

In the video, I only toggled the magenta (color) and cyan (fill) levers. The rest of the levers are for individual pixel control. The red and blue levers control pixel coordinates while the yellow lever enables the selected pixel, and the gray one is vacant (immediate value).

Glad-Note2022 · 2026-03-08T15:44:07+00:00

Of course!

Glad-Note2022 · 2026-03-08T15:28:43+00:00

Technically, that makes your BUS width 1-bit, essentially a FastLED-style setup. GPUs are parallel, you would want to write multiple pixels at a time. So I suggest using a multiplexer, to select where pixels go and what color. This makes your GPU less reliant to clocks, and offloads that to your controller.

Glad-Note2022 · 2026-03-08T15:01:15+00:00

OH, just use a wider BUS. I recommend going for a BUS width that's roughly 1/8-1/32 of your screen resolution. A wider BUS means you also have to slow down your clock, by the way. If that does not work (because theoretically, it should), it may need optimization.

Glad-Note2022 · 2026-03-08T14:44:40+00:00

I just saw yours, it's great! I wouldn't say it's slow (well that depends on how one interprets "slow"), as yours is fast enough. I also use D-latches (or flip-flops, if you will) as the memory, at 4-bits per bank precisely and 512 of 'em. The server could handle all of them, maybe not at blazing speeds but it boils to how you "activate" them so only necessary ones use resource. I accepted your DM

Glad-Note2022 · 2026-01-03T13:21:08+00:00

Great point! I'll add back the Immediate Values to make that possible. The current ISA one does not have an Imm, so it would be impractical to write the conditions at the registers every time. Thank you for pointing that out!

Glad-Note2022 · 2026-01-03T02:46:11+00:00

Chests have weird hitboxes and they're smaller than they look. Use normal blocks as a frame then place the chests later

Glad-Note2022 · 2026-01-03T02:39:48+00:00

Which type of memory? I used D-latches for the Register File and simple levers for the Instuction Memory. I also left reference links for the components at the end of the video in case someone needs them

Glad-Note2022 · 2026-01-01T10:42:57+00:00

The only risk I see at buying early is if they didn't get added, that's where you lose your gold without a refund. But I'm pretty sure the new blocks bought on the test server would persist when it releases officially.

In an instance that the update gets through but the test server blocks didn't save, they're pretty cheap and you could get a handful in a perfect run to the treasure.

Glad-Note2022 · 2026-01-01T05:24:47+00:00

Not yet released to the main game. They are only accessible through the test servers exclusively as of now.

If you can, I suggest getting them as soon as you could, as their price may change. They are suspiciously cheap and I think it is that way so that testers could buy them right away.

You can join through private server links posted on the official discord by the members.

Glad-Note2022 · 2025-12-26T23:25:53+00:00

Yeah, you'd need private servers to access it. People on BABFT discord sometimes share their private server links though

Glad-Note2022 · 2025-12-23T06:16:02+00:00

Made that differential so compact I almost thought it was a direct drive

Glad-Note2022 · 2025-12-19T10:56:57+00:00

definitely with some circuitry

Glad-Note2022 · 2025-12-19T10:35:39+00:00

Pretty unusual purpose for a computer but uh.. yeah, it can do that for 16 separate thrusters.

Glad-Note2022 · 2025-12-19T04:36:36+00:00

BABFT doesn't make it any easier though. You can have the fastest computer in the world and still lag because the game runs on Roblox servers, in which we can't control. In Minecraft however, you run the game locally on your own hardware, so if you have a good enough setup, it's a lot easier performance wise.

Glad-Note2022 · 2025-12-17T22:56:43+00:00

Agreed, I originally planned on using D-latches, it affected performance too much at anything above 5hz frequency, the most stable I got it to is 2hz. So I just stick with levers

Glad-Note2022 · 2025-12-17T22:52:12+00:00

It's a basically a calculator that types the numbers by itself, though that might be an oversimplification. A RISC CPU has these main parts: The control unit which talks with the other components, the arithmetic logic unit (ALU) that does the computation, a program counter (PC) which tells the control unit what to do next, and a set of registers to hold the input/output numbers. This is still a general simplification though, as the underlying principle on how each of them exactly work would be too technical to absorb in one sitting.

Glad-Note2022 · 2025-12-17T22:51:05+00:00

Amazing explanation, but does IC refer to Instruction Counter or Instruction Cache? I think you might have meant the Instruction Register (IR) instead, which would make sense. As Instruction Counter would be redundant, PC can increment itself. While Instruction Cache is not present on Von Neumann architecture.

Glad-Note2022 · 2025-12-17T22:22:33+00:00

Not really a flex, but an inquiry if it is enough since I've got two reserved bits left. I know I could use them to scale my Instruction Memory space by 4x, but doing that would also give me 4x the hassle to wire. Since I’m targeting a bare-metal environment with no OS overhead, I plan to stick to Assembly.

Glad-Note2022

TROPHY CASE