SpritesMind.Net

src/font.c

That one I had to look up. I remembered reading it, but not the exact boundaries. Sega did the same thing with the Master System, but it was a bit more restricted as TVs of the time had larger overscan areas due to wildly differing specs of TVs at the time. A Trinitron might show virtually the entir...

According to the official software standards Sega published with the devkit, you are not to put important info like the score, text, or time in the top or bottom tile rows, and not within the first two or last two tiles of a row.

You're doing very well on this. I do like that this is more open than other light gun projects I've seen. I'd love to see something that winds up compatible with every old console still in use, from the NES to the PS2.

The biggest problem with light guns I've run into is hooking up the old CRT monitor. Can't use the guns on my new LCD TVs.

I hang onto my TIMM 21" CRT for just that reason. It's about the only CRT I have left that I still use.

I wrote most of the controller code in the current SGDK. It automatically supports the Menacer and Justifier guns, and will support the Phaser if you set the support type - it's not automatic as MS controllers cannot be detected like MD controllers. The joytest sample included shows how to setup and...

Sorry, but I've never used either. Might I suggest looking at Code Blocks or Geany? I personally use Geany for all my program editing needs. Many people use Code Blocks.

Picodrive has good banked rom support. I use it for testing 32X bank selected bins (big 32X video player roms in this case). Fusion works fine, but only up to 6MB. They apparently didn't support bigger since there was no rom bigger at the time. The NeoMyth MD cart works up to 8MB since that's all th...

Sonic needs some speed boots there - he's a bit slow...

I actually tried but I find it sometimes difficult to interpret the low-level hardware terminology. "Associative purge space"... uhhh, sure. The SH2 has three cache modes: no cache at all (all the cache data array being used as 4KB of fast scratch ram), 2KB two-way set associative cache + 2KB scrat...

Whoops! Big whoospi on my behalf... it's 0x40000000, not 0x60000000. Sorry about that. Don't know how I confused the two. :oops: In case you are wondering and don't want to actually go read the SH2 hardware manual... 0x00000000 = cached access 0x20000000 = uncached access (they call it cache-through...

1) The sprite pointer and the struct it points to both need to be either uncached OR flushed (you don't need to do both, and the flushing is by the other CPU, not the main one). The pixel data doesn't need to be flushed, and should only be uncached if the draw routine floods the cache with pixel dat...

When I was younger, I'd have baited the crazies. As I've gotten older, I find it much less trouble to just think ahead and avoid the hassle. Choose your battles. I choose not to fight the idiots over such a minor matter of terms. Primary and secondary works just as well, and doesn't trigger the idio...

The SH2 does write-through on writing, so writes will always be in ram. So the other SH2 needs to flush its own cache of the range over all parts of the struct before reading it in order to get the current data. That's assuming the cache is used, and you aren't using uncached access to all parts of ...

That makes sense if you're rusty on C/C++. Static in C/C++ makes a local variable hold its value between calls to the function. So it's a like a global in that it always exists and holds its value, but it's still local to the function where it's defined. My standard method of doing FPS is to increme...