SpritesMind.Net

Hmm, well I don't think it matters if you set TH HIGH or LOW first, it just makes more sense to me to do it this way for many reasons. There's no reason at all why you'd need to set it high at the start AND end of the code either. I'm pretty sure the pad will return standard 3-button data for longer...

What's REALLY weird is that the six button code doesn't work on Kega Fusion - I'd REALLY like to know why that fails. Gens doesn't do this in a hardware accurate way, just in a way that works with games. Looking at the source you posted in another thread I can tell you how to make this work reliabl...

Good stuff What sort of speed are you getting?

I did ask, because even in Japanese, it would have been useful. But apparently it hadn't been written up yet. As to whether Japanese developers got better documentation, well, obviously they would get most of it first. But I usually got hold of (very bad) translations pretty quickly. I got quite goo...

maybe one of our two former genesis programmer here could tell us what timings they were told to use to do fast display modifications during HBLANK ;-) Hey, nobody was told anything other than what was in the manuals. Which you've seen, right? ;) It was basically just a case of 'try it and see, mod...

This stuff definitely works. Maybe you didn't enable V-INTS on the VDP? It's unclear if what you posted is all of your code.

1/ right border + right blank is still 23 pixels count: however, this is meant to be 15 +8 pixels, not 14 +9 pixels as you measured... That documentation is probably highly accurate for 32 cell mode, there does appear to be some very minor difference in 40 cell mode. Of course there may be a differ...

TmEE co.(TM) wrote:There's quite a bit of flicker on real HW, but on last line of the separation bar. I don't recall flickering on 1st line... I need to pay more attention.

It's there. It's VERY, VERY difficult to see, though, because of the interlacing.

(43 "H40" pixels and 30 "H32" pixels) Hmm, I'd like to see this stuff specifically tested in H32 mode. It seems to me the timing is a little different, but you'd really need a scope to tell for sure. It's probably not different enough to be important, but still ;) The stuff I wanted testing isn't r...

Jorge Nuno wrote:Snake don't bother yet, because my programmable cart isn't ready (read: it doesn't work, and I don't know why)

Ah, ok. For future reference, when it IS ready, how big a ROM will it support?

Matches my info

There's some other VDP stuff you could test, but that probably requires a custom test ROM. I'll PM later

PC-Engine isn't SNES and 65c816 isn't 6280, but the cycle timings should at least be in the same ballpark Agreed, and is kinda the point. The SNES CPU runs at under half that of the Genesis CPU, at best. It also tends to beat it simply because there *are* lots of very useful instructions that do th...

Interesting

I'll think about this some more at a later stage, it'd be handy because I'm constantly reusing components in different projects, and this would just make it easier. But I also must do this with an extremely minimal overhead, or it defeats the object.

Chilly Willy wrote:Want to? No! Have to? Quite often.

On 8 bit systems, absolutely

But this is a SUPER nintendo. For SUPER games

I rewrote the core in C++. Hm, and what benefit it gave you? CPU object? (just wondering why people may want to use OOP in emulators). I was going to ask the same thing :) I've often thought it would be really nice to do this. 68K, Z80, sound chips, video, bus, etc. all nicely hidden away inside th...