Supermodel Forum

I've tried the MAME debugger so far - it's pretty extensive, and you can set memory watches. The ROM set is compatible, i.e. the 0x4D4B4 function is at the same address, as is the in-memory high score list at 0x00106F50. The game runs, but unfortunately isn't playable. Also the NV dump is in a diffe...

I've put together a webpage that reads the NV file and displays the high scores using both of the calculation methods you found in the source: function calculateTime1(nFrameCount) { const nSeconds = Math.floor(nFrameCount / FPS); const nFrameCount_subSecond = nFrameCount - (nSeconds * FPS); const nC...

Regarding the settings, I would just like to disable throttling (Alt + T), but it doesn't work for me. Supermodel always throttles to 60fps. Are there any settings that allow me to disable throttling using Alt + T? (The command line option -no-throttle also doesn't work for me.)

Hmm, interesting. It just tested the NV file from the zip (daytona2_20250401.nv) with a fresh Supermodel directory and waited until the attract mode showed the times from the beginner track (after about 7:30 min). The times show up like this: D2_HighScore_20250401_D2.jpg In your case, do the default...

The times in the NV Dump are at these offsets: Offset 22DE: 1EAA (Game displayed time: 2:17:71 / your algorithm results in: 2:17:71) Offset 22FE: 1EAA (Game displayed time: 2:17:71 / your algorithm results in: 2:17:71) Offset 231E: 1EBA (Game displayed time: 2:17:99 / your algorithm results in: 2:18...

I've updated to the latest Git version (12e3b6a), the displayed times in Daytona2 remain the same. I also took a look at Daytona2PE (with the old Git version), and the displayed times are as follows: Beginner Track: 1 - ZER - 2:17:989 2 - ZER - 2:18:012 3 - ZER - 2:18:349 4 - ZER - 2:18:741 5 - ZER ...

Thanks for your detailed analysis.

I'm using Supermodel Version 0.3a-git-c499584 and I've attached a logfile and the NV dump with the following times:

Beginner Track:
1 - ZER - 2:17:71
2 - ZER - 2:17:71
3 - ZER - 2:17:99
4 - ZER - 2:18:05
5 - ZER - 2:18:10

Interestingly when I look at the dump of some game predefined high-score times (e.g., Beginner Time Attack), the outcome of your algorithm matches the display 100% for every rank (though these scores don't have centiseconds). Framedivider (int) 57 hex num_f num_f_sub total_sec centi_sec 1EAA 7850 41...

By chance, I just drove another 2:17.71 time. I used this opportunity to compare the relevant parts of the two hex dumps and marked the bytes that have changed in yellow. It looks like there are 12 bytes somehow connected to the times. Between rank 1 and rank 2, only the 1E AA word is the same. It s...

Yep, double checked the scores again and they are correct. The algorithm in D2 and D2PE could be different as PE shows milliseconds instead of centiseconds as high score. Thanks for updating the code. Is the Python code the translated PowerPC assembler code, or does it represent an algorithm that ru...