Supermodel Forum

I believe that you have to disable Vsync in your graphics driver as well for this to work.

What do you mean no response? There should be an error message printed. I assume you are running from the command line. You can also look at Supermodel.log afterwards to get an error message.

I don't think the settings matter. All the routines use a rough value of 57 fps and don't appear to be using measured frame timing. What I mean re: your NVRAM file is that when I run Daytona 2 with it, I don't see the scores. Shouldn't they show up for the beginner track after the attract mode?

What sort of CPU do you have? I'm unfortunately going out of town for a couple weeks so may not have time to dig in any further. I'm quite confident the routine I found is the one that prints the times. I can't get the :99 centisecond value even using the exact same frame count you had in your NVRAM...

Ok, so I found that the NVRAM is read only once at boot-up and presumably the game keeps all data in RAM, writing through to NVRAM when something changes. The table in RAM has an entirely different format. The first entry for the beginner course (default: JUN 5:00:00) is here: 00106f50h: 01 00 00 00...

Something weird that I noticed is that it doesn't seem like either 0x4cff8 or 0x4d030 are ever called. I set these breakpoints and they're never hit. I haven't recorded my own lap times, so it's using the default values in NVRAM. Can you attach one of your NVRAM files?

Yeah this is really odd to me. It's *possible* that there is another routine hidden somewhere, or that the calculation happens in some non-straightforward fashion, but seems very improbable. I found the routine by looking for the magic constant 0x0000003C (60) in a disassembly of the entire program....

There is no white flashing issue. It is intentional. This is how the original hardware behaves and it was very recently emulated.

Would be interesting to try to update the README by feeding it into Gemini along with the complete source code and asking it to generate an up-to-date markdown doc.

The README is hopelessly out of date and needs to be redone from scratch, in my opinion. Probably best to do it as a README.md file on the GitHub page.