It might just happen.

sweet! I'm not a member at s2beta but someone should suggest putting support for presenting split screen games that get squished on a normal tv to proper ratio.

someone had a topic on this not to long ago in Sonic 2 how they said the system could handle it but no one had a tv with double the vertical resolution (obviously) so that would be a cool addition if someone could mention it.

Well ideas and goals are one thing, accomplishing them are another. We'll see where it goes. It's going to take quite a bit of work to reach said level of accuracy.

Works here.

Ok, their registration quiz is way too pretentious. Oh well, I was going to post some information for Nemesis.

Sounds like we have a lot of goals in common, so perhaps I've already tried some things he's done and could offer insight. Or maybe not, guess we won't find out now, as I really, truly don't give a shit which levels were shown in Sonic on Nick Arcade fifteen years ago.

I could be wrong, but it sounds like he is using pre-emptive threads for processor synchronization (eg one thread for 680x0, one for Z80, etc). While this works for rough accuracy pretty well (eg PS2 or Saturn emulators that only need to sync a few hundred times a second), it's absolutely terrible if you're going for perfect accuracy. If you actually sync on every memory access that could affect another thread, you'll spend most of your time in the kernel handling context switches. An older system like the Genesis would benefit a lot more from either cooperative threads or finite state machines. They're also a lot more portable. The former gives you cleaner code, the latter gives you faster speed.
True, you only get to take advantage of one core, but you have to look at the platform, too. A Genesis emulator probably won't tax a single core of any dual core processors, so optimizing for those processors probably isn't ideal.

I'm also curious how he plans to use threads, and yet still have savestate support. Threads of any sort are dependent on the host OS, which is a state you cannot reliably save, unlike finite state machines where your functions are sloppy and hideous, but fully reentrant. Lots of small issues like this you don't realize until well into development of an emulator.

On the bright side, it's looking really promising so far. I can really emphasize with his recent troubles, you speed things up, but then immediately lose all your speedups when you add in more timing accuracy. A cycle that unfortunately persists for potentially years.

Amusingly, it has almost the same system requirements as mine, a Core 2 Duo E6600 :D

Jesus Christ. How can anyone be expected to know all of that? O_o

"You must be at least this elitist to post at our board." *holds a sign with a line*

That particular quiz is almost valid, except half the shit there has nothing to do with the point of the board. \

You know, we DO offer skipping the quiz for those who have stuff to offer, but can't be arsed with the quiz... I may not be an admin any longer, but if you just throw an email in the general direction of LocalH, I'm sure he'll hook you up.