SpritesMind.Net

There's notes on that in the 32X docs, but no, it's not reset. One of the things I do in my MD side hardware init code is clear RV and wait for the 32X side to reboot. | wait on Mars side move.w #0,0xA15104 /* set cart bank select */ move.b #0,0xA15107 /* clear RV - allow SH2 to access ROM */ 8: cmp...

Very cool. Thanks.

Yes, the same thing would apply to the 512 wide mode of the SNES. But with 256 colors from a palette of 32768, it's not nearly as needed as the 16 colors of the MD and PCE.

Pretty cool. Not bad for an old 68000 and 16 color tile graphics.

It looks really nice. I'll have to try out the demo.

You might try ARES. It has better mode 1 support (it's the emulator Vic uses for testing mode 1 support in D32XR). The main problem with ares is that it takes a pretty beefy computer. If it acts the same, then the problem is likely in the code rather than the emulator. Vic posted his Genesis+CD pcm ...

Also, depending how the person encoded the video, the artifacts might have been mitigated. Most video encoders have special processing for interlace to eliminate or reduce interlace artifacts. It's like those modes TV have/had that I talked about, but often better since encoding doesn't need to be r...

So, is this combing basically constantly present in Sonic 2's 2-player mode then? Pretty much. High end TVs used to have modes where they did various processing on interlaced signals to make them look better. Given how little interlace tends to be used any more, I'm not sure what most modern TVs do...

I haven't tried playing around with every setting of the PWM steering, but I know that how you are supposed to set it works as documented. If you want mono, you shouldn't try to map both channels to the both outputs (or the same output), you should use the PWM mono register, which writes the word wr...

The ZDoom wiki is great for a lot of different info on Doom files and such. Here's their page on the WAD format: https://zdoom.org/wiki/WAD It's a really straightforward method of grouping data for a game and finding the data in the game. Knowing the wad format, it should be trivial to make your own...

Yeah, that's a better way to describe it. The two fields interleave, and if there's motion, half the lines will be with the moving objects in one place, and the other half in another place. This kinda blurs the object as well.

If the release flags have -O1 for hardware files, that's probably what you want for real hardware. Not sure why you'd use something different for debug... :lol: As to noise in the sound, that could be due to many issues: Filling/playing the wrong buffer. If you look at my code, I tend to fill the fi...

The 74F174 is a hex DFF - it's what selects the particular game. More than likely, you write the bank to select to 0xA130xx, which latches the value into the D flip-flops. This bank select then sets the upper address bits of the rom die under the epoxy. Bank 0, the default when you turn it on, will ...

Please note that running an interlaced game at 60Hz can result in tearing from one frame to the next. For some games, this isn't a big deal, so they run at 60Hz for more fluid action. Games that can't accept screen tearing are forced to lock the game to every other frame, or 30Hz to avoid tearing. Y...

For C/C++ code that directly bangs on the hardware, you need to compile it with NO MORE than optimization level 1. If you go with 2 or higher, you need memory fences around the hardware accesses, and gcc doesn't seem to have memory fences defined for the SuperH family. What we do in D32XR is to defi...