@Dr.Venom, if possible run the same game with R1 too, I wouldn't be surprised it was the computer having a bad day (e.g. different screen configuration).
Thanks Calamity, that put me on the right track. I went back to the previous release only to find out that it wouldn't run fd 8 anymore. Quitting/restarting, everytime it would start overrunning from the get go.
Looking at the log, I noticed that the modeline that GM reads for 1280x0 from the registry was different than it by default is. The mode had a different dotclock, making it a 60,7Hz mode, where the default installed 1280 modeline should be at 60hz. My guess is that this could be a leftover from a crashed GM, i.e. that the default 60hz modeline wasn't restored normally. Could it be that GM's dynamic modeline line generation may be influenced by this, causing it to generate a slightly different modeline with different timings?
I restored the default modeline, then rebooted and he! the previous release would work again with FD8. But... not every time. Sometimes it will work flawlessly, sometimes it starts overrunning right after the start or at the first screenmode switch. It seems a bit random whether it will or not. The one thing you can bet on, is that if the start is ok, the rest will be too (at least for the time periods I've been testing). Retesting the R2 release now shows the same behaviour, sometimes it runs smoothly (see the attached graphs), and sometimes it won't. I''m a bit puzzled by this
random behaviour at the start of the emulation, but I guess that's how things work when using really tight settings/timings within a multitasking OS.
This is probably going to be an issue going forward - with a maxed out frame delay setting and ASIO we're really on the edge, and also much more vulnerable to what other processes on the PC are up to.
I think you're right. It's also that the genesis driver runs at 930% unthrottled, so to be honest running FD8 is really pushing it. I'll lower it to FD7 just to be on the safe side.
That's true. I've done two minor changes to this build. Please try it out and see if it fixes the issue. The run below is done with this build. Latency was set to 64 and audio_latency to 2. The slight drops are due to resolution switching.
Thanks, I tried this, but it doesn't seem to make a material difference for the fd8 edge case. Not an issue for me though, now that I know that the previous release (after all) works the same.
With this out of the way, I have to say that this is a -great- release, it works really smoothly and is now even easier to configure. I'm loving it all around. Thanks again (to both you and Calamity)!
My vote goes to bringing this out of the pre-alpha stage, at the very least