r/AtariJaguar • u/angus_macgregor • Apr 20 '26
r/AtariJaguar • u/40yearsofinvading • May 05 '26
Yoshi's Story on Jaguar
This may be a bit silly, but this sort of thing is always interesting to me. I asked ChatGPT what N64 games could be ported to the Jaguar in a reasonable fashion and Yoshi's Story was one of them. I had it generate a theoretical screenshot. Do y'all think this would actually be possible or is ChatGPT off base?

r/AtariJaguar • u/the_matrix_kid • Oct 20 '18
Fast Food 64 (Atari Jaguar) OFFICIAL GAME TRAILER - Semalt
r/AtariJaguar • u/IQueryVisiC • Sep 01 '24
2 cycles per JRISC instruction
I think I now understood how a missing revisions lead to the effect that only some instructions have access to results from the previous cycle. JRISC was meant to be a minimalistic processor implementation. Also they say that they use RAM for the register file. Still it has two ports and is not of the standard variety. But then again this building block (macro) does not specify what happens when read a value in the same cycle that it is written. Maybe they optimized for something else. So the Jaguar designer wanted to stick with a single input register for the second operand. Complications arrive when we have three instructions. The first instruction writes it result into the register file, while the second instruction is executed. In the second cycle the result could be read back and used by the fourth instruction. So one of the operands skips two instructions. The shortcut and flags skips one instruction to better match this?
Another explanation would be that the bus to transfer values from 5 pipeline registers ( ALU, shifter, multiplier, LOAD, short cut and register file ) to the two input registers of the next processing unit is slow. Or at least we would save current and heat, if address and values are all set before we broadcast anything on the bus. It just feels weird to save power at the heart of the chip.
Another weird design is to give the flag evaluation for a branch its own cycle. I think the manual lumps registers and flags in the same sentence in a wrong way. Register values are 32 bit values and routed. Flags are 1 bit and there is some logic to combine them with the 5 bits of the conditional flag. So the opcode needs to be available for this. This is the execution step, isn’t it? Or is there a whole pre- processing step to set the zero flag? Most instructions don’t even set flags. An ALU spits out flags as part of their internal operation. Even if some logic was required, it could easily work. Ah scrap that. MUL, barrel shifter and ALU can all set flags. To easy routing , the zero flag is probably evaluated in the second cycle. Thinking of it, an adder does not know if something is zero. It is more interested in sequences of 1 which propagate the carry. The zero calculation flag needs a sequence of 3 NANDs for 32 bit. So there is some delay, but not much. Maybe Atari used the pipeline stages for debugging . So confusing that RISCV does a comparison between two registers in a single cycle, while JRISC needs three CMP, NOP, cons. JMP + delay Slot .
ALU and shift can set the carry flag independently of the value. So actually, 33 bits are needed on the bus.
I guess that MUL and DIV units were designed internally of Motorola and could be optimized in detail and run basically at twice the speed. FPGAs get their programming as the register transfer logic. Like in the Jaguar manual the hardware exposes non-transparent register bits. These are made of a sequence of two data flip flops. The first closes its input. So it need to wait for the final, stable value for this. The second flip flop then opens its input so that its output moves straight to the new value. The CMOS 386 puts some logic between these data flip flops. Preliminary data or voltages between the logic levels may reach the next stage for a short transient. But on the flip side, we don’t waste as much time on safety settling.
The difficult part is to find a place along the circuit where we have a low number of wires. Luckily, MUL consist of a Wallace tree with 64 bit out put and an adder . So we just need 32 more flip flops. The division unit on Jaguar spits out 2 bits per cycle. Obviously, the division circuit is duplicated. Information goes ping pong between data flip flops.
I once thought if this trick can be applied to the 4 bit adder in the Z80. The result would be 2 odd bits and 4 even bits to pass through the ripple carry. But an adder has side effects. We need to feed the inputs. There would be two input shift registers which shift on alternating phases. Likewise there would be two output registers. Overall, cost is as high as carry look ahead.
Motorola internally surely used these tricks for their Macros, which Atari then wired together.
With such a conservative design, I wonder how the blitter got its pipeline bug.
Ah, the blitter is different. It has 64 Bit registers and 4 16 Bit adders, possibly even with ripple carry. It needs two cycles for an add because is does fractions in one cycle and integer part in the other cycle. For this it needs 4 carry flags and 3 port memory. And either reading or writing to registers need to be part of the ALU cycle to achieve the 2 cycle round trip. Maybe the blitter is even old and optimized enough so that the ALU sits on the odd phase. The blitter can alternate between intensity and z values. So it is not a closed cycle. Also the ALU can add a signed shading value to the source pixels (so destination pixels are darker ). So the state machine can make the ALU address these registers. This is clearly more optimized than JRISC. I just wish that there was no saturation. Why did they not think about it?
I should now probably consult the net list. But it feels like the blitter register file is fully custom. For example there would be accumulator registers and increments. So no two random out ports. Like the LOAD register on JRISC the source register can be written from the outside (only from outside). Like the STORE in JRISC the destination register can only be read from the outside. The CPU can write only to these registers, obviously to save a multiplexer for the read ports. There is only a tiny number. F0227C is total wild. It needs additional skewed word lines ? Or read modify write..but CPU cannot write! I can just assume that JRISC really had a hard time to ROR color and intensity when going to the next scanline.
r/AtariJaguar • u/Uranium____________ • Sep 07 '25
Just wanted to promote my website again (sorry if this breaks the rules, it's been like a month, so I wouldn't call this spam)
https://atari-jaguar.neocities.org/ My account don't work no more so i made a new one. also, to prove that I made the website, send an email to the address at the bottom of the homepage, comment that you emailed, and then I will tell you exactly what you said.
r/AtariJaguar • u/Impulst24 • Feb 06 '26
Atari Jaguar - spiritual precursor to the original Xbox?
One of the reasons I love the Jaguar so much is that it has so much in common with the first Xbox from 2001, which is a sixth-generation console. Both the Jaguar and the original Xbox have large controllers, can play audio CDs (except the Jag requires an add-on for that), link to multiple consoles, and feature games from well-known franchises like Pitfall, Rayman, Doom, Wolfenstein, Worms, Defender, etc. There's also the fact that the original Xbox was the first video game console produced by an American company since the Jaguar.
Cybermorph, a game I praised not long ago for having such a badass title, is what I like to call the Jaguar’s Halo. The game has a similar vibe that reminds me of Halo. For instance, Skylar is basically Cybermorph’s version of Cortana, and you also can't tell who is in the wargriffon, much like how you can't see who's wearing the master chief armor in Halo. Not to mention both games were launch titles. Other examples include Iron Soldier, which is basically Atari’s Steel Battalion, and Skyhammer, which is basically Yager before Yager existed.
Alien Vs. Predator is also what I like to call the Jaguar’s Splinter Cell. Alien Vs. Predator was very influential on the Jaguar when it first came out in 1994, much like how Tom Clancy’s Splinter Cell was very influential when it came out on the Xbox in 2002. Both of these games were very impressive for their time. Even to this day, I am still in awe of the gorgeous visuals in the original Splinter Cell, and it came out over 20 years ago. I feel very much the same way about Alien Vs. Predator on the Jaguar, and it came out in 1994 (over 30 years ago!!!!!). No wonder Alien Vs. Predator is considered to be one of the best Jaguar games. It aged extremely well graphically and looked just as good as most games in its era, and the first entry in the Splinter Cell series looked even nicer than most of the games that came out in its era.
Interesting fact: I wrote this last year for fun and I forgot to post it here. Not long ago I was just scrolling through my notes, saw this, and wondered if I shared this here, and I quickly realized that I haven't until now.
r/AtariJaguar • u/dmar3000 • 28d ago
Made with AI (Vibe-coded) JagBoom - A Bomberman clone for the Jaguar!
A Vibe-Port of the open sourced game Mr Boom.
Tested and works on original hardware with use of the Game Drive cartridge as seen here on video. Available now for free download!
r/AtariJaguar • u/IQueryVisiC • Apr 24 '23
JPEG and the second register bank
So the values in the second register bank are packed for one reason: 32 registers times two values each = 8x8 coefficients of JPEG. For MPEG they expect you to do chroma sub-sampling independently. Though with one or two fast DCT-inspired SUBs, we can have 16x8 coefficients effectively.
Atari depends on the fast DCT for the two dimensions, but not along each dimension. Still so weird that the two MAC units idle most of the time.
I am not into FMV. So I don’t care. Maybe I find a jpeg2000 lossless use or WebP.
r/AtariJaguar • u/IQueryVisiC • Apr 06 '23
Score Board
There is a description about the score board in the Cray 1, but in JRISC it is much simpler. There is a lot wrong with JRSIC ( 2 cycles latency for flags? After any ALU operation, a JUMP ( even unconditionally) , ADC, and SBC wait a cycle. So no interleaving for 64 bit arithmetic..
But for Load and DIV JRISC works well. There is a second register file with two read ports and one write ports. It stores only 1 bit values. An instruction checks both source register flags and waits until clear. Then it sets the target flag. When an instruction finishes, it clears the target. If the last target is the source of the next instruction, JRISC does not access the register file. Also it does not need to check the score board, only clear it.
I feel like JRISC is not smart about the order it loads registers. So it probably also only reads one score-flag from the board. I don't see how the board can be viewed as a single 32 bit register. Maybe for some pipelining? But access mode is more as I write: Bit Set and Clear!
The manual states that results from the ALU, the division unit, internal SRAM, and the external system bus can collide. So there is a multiplexer and some detection logic. And it may take 4 cycles to clear everything up.
r/AtariJaguar • u/IQueryVisiC • Mar 11 '23
Is the two step conversion: 64 bit - 32 bit - 16 bit a good idea or a sign of bad architecture?
At first I wanted the system to be more simple. But then I remembered that for example for a sprite circuit on old CMOS technology I would try to use a series of multiplexers. On an IC ( with enough space ) there would come the whole scanline of the sprite, then a multiplexer to select left and right and then a whole tree until a single px emerges at full px clock.
Now for the Jaguar we have the 64 bit system bus with its long wires at all the latency from memory and the controller ( does the page change or not? ). It runs at half the clock. Then we have some 32 bit busses which run at the full clock. The DIV and MUL circuits were apparently generic circuits made by Motorola experts and do/could run at twice the clock. Now MUL only deals with 16 bit at a time. DIV is a miracle.
Anyway, for JRISC code it goes like: 64 bit DRAM -> 32 bit SRAM -> 16 bit instructions in a (short) queue. For the Objects it goes like: 64 bit DRAM -> 32 bit LineBuffer -> 16 bit px ( -> converted to 24bit RGB ). For JRISC data it goes like 64 bit DRAM -LoadP-> 32 bit registers - rotateQ 16 -> 16 bit factors for MAC.
Funny thing is that the blitter does not know about 32 bit. It goes from 64 bit to pixel and back. No intermediate step. It has a weird way to remap the 32 bit fixed point values for Intensity and Z onto 64 bit registers. I can't quite recognize it from the manual, but I guess it does the 6502 trick : First add the fractions, store 4 carry flags, then do the integer parts. This takes two cycles which matches the speed of the DRAM. Interestingly, the blitter can interleave between different sets of registers: I or Z. Hence adding and DRAM write always match in speed .. uh unless you read and write z-buffer. Okay so it matches for the sky box ( zbuffer write only ) and for transparent objects ( z-sorted, zbuffer read only ?huh transparency would need a texture .. or colored Gouraud? ).
It is really difficult to shoehorn 32 bit into the blitter. Even the basic 2d blit: Load Phrase alternating into one of two source registers, a barrel shifter maps them onto the destination Phrase register, write back to memory. It just gets awkward that you may want to avoid the two page misses and hence blit a whole line into 32 bit memory (GPU or line buffer) and then back (16 bit this time??) to DRAM, which in the end gives you no speed advantage. Anybody tried to blit directly from ROM? Don't care for compression and its artefacts. Ah, but that won't even work well in 64 bit because those "cache" memory is on the other side of the system bus. No convincing argument for 32 bit. SRC shade is said to have a bug because again the same adder is used .. in another pipeline stage. What pipeline? Ah, would be so cool if there wasn't bug. It would just be so cool if the blitter would use its 64 bit registers in px mode. Even if loading may not be easaly made perfect, a fixed function pipeline or some JRISC like code where we could then access the whole 128 byte source register in any pixel format ( run address generator twice ), do transparency, source shade, z-buffer, Gouraud .. the whole program on it without hogging the bus and then write back .. ah destination register is 64 bit. Ah I see a pipeline: Memory -> SourceRegister --pixel addressing -> Source2Register -> 64 bit pipeline . I guess that here I am not allowed to request more register. For example one could run the z-buffer calculation first, to reject pixels early. But then we would need to store a mask somewhere ( if only part of the 64bits are rejected ). For some reason the Jaguar can blit behind transparent objects ( with no speed benefit ) and has a 1 bit pixel to any other px format speed up mode to render text !? Can't we just put text in a 1 bit Object ?? In previous posts I was concerned about fast full screen Doom. Now I just want to show how bugs prevented an easy way to make a fast battle sphere or fight for life ( easy, like launch set-up ).
The address generator is 32 bit because that is the width of the address bus. Memory has only one port and hence the Jaguar only needs one generator, but two sets of registers (there is one bug where both generators use the same register, while specs wanted it otherwise). It has 32 bit fractions and 32 bit integer parts similar to the JRISC ADD und ADC instructions. Again, just like the blitter the Address generator ADC can use the C from the previous cycle ADD. I really wonder what went wrong with JRISC. Just two many registers? Just two many operations: classic ALU, shifter MUL, DIV? The scoreboard, the 2 way to 3 way translation? The possibility that DIV will spit out its result some unexpected time?
r/AtariJaguar • u/Impulst24 • Oct 25 '23
Hot take: I hate to say it, but I don't like Tempest 2000 that much. Change my mind.
Don’t get me wrong, the soundtrack and visuals are great and all, but I gotta be honest, I find the gameplay to be overwhelmingly aggravating. It gets repetitive quickly, and the worst part is that it becomes infuriatingly difficult in later levels to the point of it being pretty much impossible to slog through. Certain enemies are very annoying in this game, particularly the little yellow curvy thing that immediately fries you after facing it. The SuperZapper doesn’t seem to help as much as I would’ve hoped, and I also hate the fact that you lose the ability to jump each time you progress to the next level. The game would’ve been easier if you could jump anytime so you could avoid a swarm of incoming enemies that are otherwise very difficult to avoid. Because of this, I ended up losing every single one of my lives at the 58th level.
It’s a crying shame because I really, REALLY want to like Tempest 2000, especially since it is loved by many and it features a fantastic soundtrack as well as stylish visuals, but I hate certain aspects of the gameplay so much that it makes me want to throw my controller at the wall. Ultimately, I think this game is good for anyone who enjoys the challenge of many arcade games, but if you’re like me who can’t deal with some pretty frustrating parts in an otherwise addictive game, you’ll have a pretty bad time. I will say Tempest 2000 is one of the most stylish games on the Jaguar, but just keep in mind that I really do not think it’s one of the best games ever made or even in the top 10 best games on the Jaguar. I like most Jaguar games, but this ain’t one of them. I’d rather play Cybermorph.
I apologize to all of those who thought I would give nothing but praise on Tempest 2000, considering that I enjoy most games on the Jaguar, but sadly, I have a very hard time doing so because I don’t think this game really deserves all the love that it gets (soundtrack aside). I feel like I’m the only one in the Jaguar community that doesn’t care about Tempest 2000 as much and maybe I’m just really bad at the game, but I can’t get over the fact that this game has some serious flaws that prevent me from enjoying the game. Admittedly, I'm a young guy (I turn 19 in a few months) and I never really grew up with a game like this as a kid, so that might have something to do with my controversial thoughts on the game. I love old-school games, but perhaps there's something I don't understand about Tempest..
So PLEASE, I’m begging y’all to help me change my mind!!!
r/AtariJaguar • u/notsoscaredboy • Nov 11 '23
Listed a nearly complete Atari jaguar, lynx and 7800 collection (plus some extras) cib last week. Some of the jaguar games are coming up for sale today in maybe 8 hours. Thought I’d share this video of what is up for auction here🙇🏻♂️
r/AtariJaguar • u/IQueryVisiC • May 05 '24
alternate history: z-buffer reject
Jaguar is not really optimized to load textures into TMEM. And this could be okay. It can use very large maps, which even don't need to have a width of a power of two. I lacks wrap around .. what the word "texture" kinda implies. So I kinda hate the non-power of two thing. Would anyone have problem with a framebuffer with 512 or 1024 px ( uh, and the zbuffer)? Could put some textures on the side if the screen calls for 320 or 640px. But for an atlas. With colorful 16 bpp texels and the low screen resolution and no mipmapping, the polygons far way pull each pixel from a different phrase. So pixel mode it is.
Just it would be so cool if the blitter would still use phrase for the write side. So it could load the z-buffer values, check the pixels for which to look up the texture ( like a modern GPU does it ), only load those values, write back a phrase of colors and a phrase of z-values. This would speed up indoor levels and scenes where the enemy or explosions in the foreground cover much of the screen. For maximum speed, two phrase writes could be interleaved: Load the next z-phrase. While the z values are compared, write the old z phrase and color phrase. Three phrase access inside a memory page in a burst. And also I want this per-word write-enable trick, which is used to limit writes to the range of the span, to also work for z. No need to read colors, if we don't do shadow or lighting effects.
I am a bit disappointed that for the foreground polygons with large texels, a texture cache is not that desperately needed. What is needed is a shortcut to the palette to allow 4 bit textures. And a signal line from the address generator, if the phrase address really changes (carry bit). If not: do not reload the input register. In a lot of games (not Doom) texels really stretch like 2 to 3 pixels. So phrases stretch to like 5px. This would really reduce the required memory bandwidth. I still have not found out if the blitter really needs two cycles per pixel just to do the math. I would match the speed of the RAM. Just uh then it still has to wait for the write? Anyway, the math for 4px in pixel mode takes as long as 4 fast-page mode RAM accesses. So this matches the 1 read and 2 writes if using the z-buffer plus an average 1 read from the texture quite nicely.
This looks so simple. No multiplication, which the designers seem to be afraid of. Just some control lines and some Boolean logic. And place the blitter next to the palette for the shortcut. With 2 clock ticks per pixel, we don't care if the color LUT adds another 2 cycles latency. Z-buffer writeback hides this. Would this slow down the object processor in 8bpp mode?
It really hurts me that all the ideas of a texture cache go down the drain.
r/AtariJaguar • u/PopFrank68 • Feb 03 '26
New 3ds XL..
I have one in excellent condition! Looking to trade for an Atari jaguar..they both seem to be overpriced and coveted. What are my chances?
r/AtariJaguar • u/atari_guy • Jan 07 '16
Retro Atari Podcasts app free for Android
r/AtariJaguar • u/[deleted] • Oct 26 '21
Last post here, Anyone have a Jag (any condition) to trade for?
Last console I need for my holy grail collection. Any condition is fine! Even without hookups. Thanks! I have a bunch of gameboy, Xbox, GameCube, Dreamcast, switch stuff, etc.
r/AtariJaguar • u/IQueryVisiC • Mar 31 '23
6 Asynchronous BusGrant can crash the bus arbitration state machine
Why on earth did Atari use async arbitration? I thought that one reason for the relatively high clock rate ( compared to 3do ) was that we don’t mind to wait for the clock. The division circuit even demonstrates double data rate.
So it would really make sense that the bus sends out a clock and each device requests the bus within a clock cycle. Where does the extra time base come from? User input? Network?
The arbitration circuit may need a pipeline like almost everything in the Jaguar. So the grants are based on requests a few cycles back.
Memory has RAS CAS to read the address bus and extra WE and OE for the data bus. So I don’t see how a synced pipelined bus arbitration logic cannot govern the address and databus in different pipeline stages.
It should even be possible to do the page logic while the shift register puts the words of the phrase onto the 16 bit bus.
I guess that the problem lies with the dumb OP and blitter. JRISC LOAD STORE has no problem
r/AtariJaguar • u/dmar3000 • 25d ago
Made with AI (AI WIP) Lugaru attract demo testing on original Atari Jaguar hardware
Coming soon for free download!
r/AtariJaguar • u/adrianoarcade • Apr 01 '24
How iconic was the jail escape cut-scene in Another World? Well, to honour this amazing game, I have recreated the this amazing cut-scene on a budget! Imagine terrible acting, dodgy Lego animation and weird alien faces. Yup, its as bad as you can imagine!
r/AtariJaguar • u/Plastic_Dingo_400 • Jan 22 '25
Block Buster rental case
Hey everyone, I haven't thought of the jaguar in years and came across this sub.
I have a jaguar rental system from blockbuster in storage (sorry that I don't have pics for yall)
The system is complete, with the lamentated instructions on how to set it up. I feel like the centerpiece is the travel case, says jaguar is big embossed letters and has a holographic jaguar sticker on the front.
I'm wondering what it's worth these days but couldn't find one for sale. I can't believe how much just the consoles are going for these days, it's been worth very little most of the time I've owned it lol.
So my question is as people who enjoy jaguar and like to collect it what would you pay for a block buster rental case? Would you be more likely to just buy the case or is the system being a block buster rented console make it cooler?
If you're wondering how I got it my mom was a store manager of a block buster in the 90s and she just brought it home one day lol.
It's always been the centerpiece of my video game collection due to its rarity and I'm just curious what Jaguar people would think it's worth, thanks for reading
r/AtariJaguar • u/SupremoZanne • Feb 14 '26
Hardware the reasons for bragging about being "64-bit" can vary in plausibility.
as the Angry Nerd once said:
"where did the other 48 bits go?"
64 - 16 = 48
This was because the 16-bit era of video games was at it's second half when the Jag came out.
Now, let's explain this 64-bit concept.
I'm aware there's things called 64-bit data types, for example there's DOUBLE PRECISION floating point numbers, and they are 64-bit data type we sometimes found on 16-bit machines like the IBM PC. However, one might call that "64-bit" by accounting for the fact that there's eight consecutive bytes (actually 8-bit intervals of data) to form the math, and this is another reason to say the phrase "do the math".
Now, regarding what many say about Jaguar, some say that the Atari Jaguar used a 32-bit processor as the main CPU, but accounted for a 16-bit graphics processor, and some other 16-bit chip, as a way to sum it up to 64.
32 + 16 + 16 = 64
So in away, doing the math, yup, "do the math", was a thinly veiled reason to brag about the system being "64-bits".
I really get technical when trying to explain the reasons for trying to use sales pitches such as bragging about numbers when they are really a sum rather than just single-handedly the architecture bits.
Sometimes we might have 64 bits as a sum of some graphics processing.
8 bits for a red color channel
8 bits for a green color channel
8 bits for a blue color channel
32 bits for LONG INTEGERS to render 3D-modelling which 3D graphics were used on the Jaguar
and, maybe 8 more bits for miscellaneous data that minimized glitches in the graphics processing.
or, maybe 64 bits of programming code.
a 32-bit LONG INTEGER might be used for containing a multitude of values which include a combination of modulo and integer division.
a 16-bit INTEGER for some data which may require fewer bits.
8 bits for a byte of some values with a range that never exceeds 255.
and maybe 8 more bits for some error handling and glitch patching.
another way to use 64 bits as a sum of different bit counts, as opposed to, well, architecture widths.
r/AtariJaguar • u/IQueryVisiC • Jan 10 '26
Hardware The motivation behind the Object Processor: Ultimate 2D hardware for 4:3 CRT Atari should have designed at the end of the 2D era on consoles
Sprites live for many frames (and I insist on 60 fps – looking at you Mortal Kombat arcade ). So it makes sense that they are created and then kept in memory. Only some attributes are relevant for display. Unified memory in Jaguar is great because we can just append custom data behind the display properties.
I feel like hardware sprite multiplexing wastes power. Let’s utilize the unified memory and JRISC. So we can accept a 64kiB buffer (DRAM is cheap) with pointers to sprites: 256 scanlines (per field) and max 255 sprites per field (no game needs more than 255 sprites). Clear the counts for each scanline. Then go over all 255 sprites and append them on the first scanline where they appear. A global register sets where the real Objects are stored and how far apart one tick of the sprite index is. Set this pitch to fit all your custom data in between.
The hardware keeps a 256 entry active sprite list on chip “cache” in SRAM. When the “beam falls under the sprite”, the sprite is removed from cache. Sprites from memory are merged in. For this, the cache is actually a queue. The sprites from the last line are dequeued, and the current line is enqueued. The actual rasterizer respects the valid range of the queue. Sprites are rasterized front to back with a coverage buffer like in r/GBA. So only pixels are loaded from memory, which end up on the line. For 16bpp and even 24bitRGBA it makes sense to preface each line of a sprite with a transparency bit pattern to even further reduce loads. The A is the alpha channel meaning translucency. The line-buffer also track translucency. With multiple translucent pixels behind each other, translucency may drop to 0 (rounded) and the transparency bit is cleared. Or rename this: “coverage bit is set”.
Instead of loading sprite lower_y every scanline, memory bandwidth can be saved by inserting sprite delete markers. So the 256 byte pages would contain an insert count and a remove count. Insert indices grow from lower address, while remove indices grow backwards from high address. 254 sprites can be shown on screen.
The game has to provide clipped screen coordinates to make this work. Any scaling, pan, and zoom happens in the pixel shader in a pull kind of math similar to how the blitter DDA works. Yeah, it is a bit ugly, that the transparency pattern would have to be scaled and then the pixels again. Perhaps accept that sprites with 15 colors + 0 = transparent will be faster in this case. This should cover all Sega SuperScaler games.
For shadows and lights, a 9bpp pixel buffer (on chip) is initialized to 0. Then all shadows ( negative -0 .. -255 and lights (+0 .. +255 ) are added. Then the sprites where these apply are painted. The sprite could be the floor for shadow, or a wall which is lit by flares. Flames and glow are different: they use alpha channel.
Some game consoles only use a single line buffer and have the concept of a background. A background is wide and drawn in 8px segments while racing the beam. SNES has 4!! backgrounds. Sprites are drawn while in horizontal retrace. This point is a bit mood because it relies on a specific property of analog CRTs but hm. Anyway, this time about a ¼ of the line duration. To utilize the pixel shader the other ¾ , we draw the backgrounds. In front of the beam we fill in the background backgrounds ( front to back ). After the beam with lower priority we clear the buffers and draw the foreground backgrounds. Each background has a z-value which is written in the z line buffer. Sprites have their z from their drawing order. So this is a whole new circuitry and not really cheap on buffers ( although z buffer here only has 8 bit ) and the developer needs to decide about the pre and post beam backgrounds and some unnecessary pixels are read. For that reason, Jaguar ( and NeoGeo?) rather have two line buffers. And Super Burnout in many scanlines needs all the cycles for sprites.
When a game does not use translucency or lights, then we do not need to look up colors when writing to the line-buffer. We could do it on read-out. It would be great if by means of multiplexers this hardware could also be used for a frame-buffer. Instead of the double line buffer (+ sprite index ), they would act as a short queue for VideoDMA, a buffer for a line of a sprite to duplicate lines on (vertical) zoom, and a buffer of the current frame-buffer target line where we compare coverage and then first only load the required pixels of the sprite and then update the coverage bit by bit and write back in a burst. I dunno if there is cycle time left in JRISC memory for multiplexers, but I feel that for full utilization of memory bandwidth (load Object description, load sprite pixels) and pixel shaders ( load coverage, read modify write in the line-buffer for RGBA and color lookup (ideally, one lookup per cycle because lookup tables are big (256 colors))), the 2d hardware would need to manage many queues and steal all GPU memory: GPU halt ( while on screen ). JRISC seems to be inefficient for queues. Tom has two 8 bit multipliers to transform the color space. If the alpha channel is enabled, this would mean that the multiplication is too slow. A queue is needed to max out the multipliers and prevent stall. Aaaarg, basically I wish that Super Mario on SNES never introduced the ghosts. Now I feel oblique to support them. Also to do this correct, there would need to be Gamma correction, ugh.
With a framebuffer we can use much more complex, narrow Objects because we don’t need to load the shader for every scanline repeatedly. Basically, we cross the domain towards affine texture mapped triangles as on PS1 with Gouraud and fog and colored light (multiplicative) and vertex coloring (addititive), zbuffer. So in a way, a frame buffer is a slippery slope towards 3d. Narrow objects would be Lemmings or Bullet Hell. Tilemaps are easier this way. Frame-buffer has more latency. In hindsght, the limited shader in the Amiga blitter, Lynx, and even Jaguar, is wasted potential.
Mobile LCDs have a low number of scanlines and it may makes sense to just use a frame-buffer like on Lynx and later on Playstation, which has many great 2D games. Frame-buffer add latency. That’s why the gameboy never uses them, not DGM, Advance, nor DS.
Edit: We all hate that the ObjectProcessor can write to (external) memory. I think this was motivated by vertical scaling. Anyways, vertical scaling adds quite a load to memory. Especially, since I want high quality scaling without jumping and ideally even without playstation wobble. So, let's put the burden on the burden on the GPU? It get's the vertical blank to fill in all the y source lines into the buffer? Atari would have needed to give Jerry 64 bit memory access so that the game can run there. So much SRAM !!!