ZSNES board

Sisyphus would be proud. Who says impossible tasks must be impossible?

[SMS pixels are] Not square (square on top, video capture on bottom). Same size as NES/SNES pixels, BTW. Man, major color bleeding. I would've guessed they were going for multi-color text. Actually it's color fringing. As you can see from the RGB image on top, the text is supposed to be black. That...

256x192 almost definitely had black borders on the top and bottom, rather than vertically scaling the image. I'll have to hoook my 99/4a up and test that. I thought it used square pixels, though I admit to not having launched an exhaustive study. Not square (square on top, video capture on bottom)....

But.... the Genesis doesn't have square pixels either.. The 320x224 mode was close enough that you could port the game to a modern device without having to redo all of the original artwork. Even if Nintendo couldn't foresee the portable market in 1983, they should have at least wanted to make it ea...

What about email?

adventure_of_link wrote:Hate to contribute, but this is what happens when you buy from china.

Actually, ROHS is the new "Made in China", only this was done intentionally.

Don't almost all SNES games keep the CPU busy all the time? Hint: even though it's not doing anything useful for the game, it's probably still constantly executing instructions. If you did that on a PC, it would show 100% CPU usage. WAI is about the only way to avoid sitting in a spin loop. It's the...

When I got that error, I got scared. Database errors are bad, but whenever a computer mentions it's trying to "fix" a problem, it usually FUBARs everything.

If you want to do processing on linear RGB values, and all you've got are non-linear, you must convert them to linear, do the processing, then convert back to non-linear. For some processing, using non-linear RGB doesn't affect the result that much, so you can just skip the conversions.

Since the board is going to give me a frightening database error when trying to edit the above post, I'll just add this:

I also recommend Poynton's Gamma FAQ.

People often think of gamma correction as merely compensation for a CRT display's non-linearity. This is only half-true . I highly recommend Poynton's The Rehabilitation of Gamma for full coverage of the issue. The luminance of a CRT in response to a voltage is non-linear. If it were linear, twice t...

"Hey mum, I burnt myself. It required skin grafts ! What do I do?". Mother: "Sue the people who make it unreasonably easy to burn yourself, and who negligently hand you things that are unreasonably hot, beyond expectation. That will make everything better". Fixed that for you. An...

I was wondering how the graphics compared between the PS2 and GameCube versions. I figured the latter might be better, as the PS2 ones look kind of crappy, especially in parts with mist. But I doubt I'd be able to give up HD Loader speeds.

Damn, your link to a UK news site had me expecting it was those crazy people on another continent, but then I see it's California, where everything can cause cancer. There is probably a neurological link between violence and fantasy violence: those who "have it in their system" go to fanta...

Surprisingly, I liked GTA: San Andreas a lot. The detail and size of the world is impressive (and HD Loader eliminates load times). Now I've in love with Resident Evil 4. I just finished the main game and loving all the extras it unlocks, and being able to go back through with all my old weapons.

Any recovery effort should only be if you have no backups, since the recovered files might be corrupt/incomplete. Since you have a backup, that'll be more reliable. Remember, you aren't making backups unless you verify that you can reasonably do a restore from them.

It looks like you can eliminate the *4 by rearranging the blend table. Instead of (simplified example) uint8_t table [4 * 2] = { 0, 1, 2, 3, 4, 5, 6, 7 }; int x = table [index*4 ]; int y = table [index*4 + 1]; transpose to uint8_t table [4 * 2] = { 0, 2, 4, 6, 1, 3, 5, 7 }; int x = table [index ]; i...

I notice you're not using the simpler pixel comparison that only involves two table lookups and a few bit operations. Was that slower or not precise enough?

The question for the SNES is what gamma it applies when encoding composite and s-video outputs (and perhaps RGB). If it uses none, then proper conversion to the linear RGB values of the light leaving the display's surface requires applying a 2.5 gamma. If the SNES uses 0.5, then conversion requires...

Bsnes does not have to care about the luminance because it basically emulates a snes with a RGB out(which by definition provides a 0-255 luminance image) Yes, though it really emulates a SNES with digital RGB out, not that such a thing exists. All analogue and digital broadcast signals are in 16..2...

Sounds like he's been reading up on digital video encoding of luminance, which has some extra range for overshoot and reserved values, and made the (incorrect) leap that the SNES has a digital video interface. The answer is no, it doesn't. The hardware converts ideal RGB values to video signal(s), b...

Remember, for a limited data size, O(1) algorithm A can be slower than O(log n) algorithm B. The point of complexity measures is how the algorithms work as the data grows, and they are critical when the data can grow greatly. For this case, what really matters is the absolute average performance, th...

Minor comments for HQ2x_00 function: - Shorter way to mix two pixels, same result: accum = (accum + l - ((accum ^ l) & 0x0421))) >> 1; - Do you need to use uint16_t for local variables/return values, or would unsigned int suffice? Sometimes compilers generate extra masking when you use shorter t...

How fast does the fast DSP run with the proper settings now?