MT15.DRV reverse engineering project

[llm]

there are isub-Functions (internal helper functions) that all get multiple called from the pluing-interface functions - i've ported all the isub functions to C now!
these are the mostly used functions - this is a big step for the C port, now i need others to re-check the behavior

attached are the version 1.0 and 1.1 binaries partially based on C-code (will release the source later when its clean)

i've compared mine and the original and they seems to be identical
bugs could be: it would sound strange (like a very slow free style jazz session for example), do just nothing, hangs, hickups, or too fast or slow or just crazy - that is all i've  heard while porting

can someone re-check the sound/music behavior compared to the originals? Im looking at you, Duplode

i don't know which wild stunts 1.0/1.1 + my driver version 1.0/1.1 combination should/can be tested

[llm]

these Stunts 1.0/1.1 MT15.DRV version are nearly fully ported to C - ~2000 lines of assembler reduced to ~600 lines well(over) documented C

but there is still is a risk that i introduce micro bugs while porting
for me the both version are sounding identical to the original + comparing midi output etc.
but wider testing would be great

there are only 4 (of 29 functions) left to port, so its nearly done

source is released when im done with the full port - then i really need help to understand the complete midi-sound values pushed through the driver

[llm]

only two functions left

[llm]

one function left

[llm]

fully ported to C !!!

would be great if someone can test a little bit

[Daniel3D]

I would love to. I've you can tell me how.
I don't know (understand) what I need to setup to use the driver.
(I have WX [Windows 10] and defend dosbox manager)

[llm]

>I would love to. I've you can tell me how.

no problem

>I don't know (understand) what I need to setup to use the driver.
>(I have WX [Windows 10] and defend dosbox manager)

you need original dosbox with munt patch or dosbox staging (develop version with already integrated MT32)
and the MT32 roms

grab the develop-version of staging which already integrated MT32 support:
i've uploaded the current development version (im also using) to: https://easyupload.io/nbo5r5

create following pathes

C:\temp\mt15_tests\romfiles <- fill that with the mame rom files: seach for "mame mt32 rom" you should find a mt32.zip and a cm32l.zip (extract copy all .rom/.bin into this folder without sub-folder)
C:\temp\mt15_tests\stunts11 <- your stunts 1.1 copy AND unpacked game.exe from the restunts projects (also attached)
C:\temp\mt15_tests\dosbox <- put in here the dosbox staging alpha files AND the attached dosbox.conf

then run the dosbox exe - stunts should start automaticly
relevant lines in the dosbox.conf are marked with "# !!Daniel3D!!" but should work out of the box if you can use the pathes as stated above

then you can check if
reMT15/10/MT15.DRV sounds/behaves the same as the stunts 1.0 MT15.DRV (org/10)
reMT15/11/MT15.DRV sounds/behaves the same as the stunts 1.1 MT15.DRV (org/11)
used with stunts 1.1

attach-info:
game.exe from the restunts project - copy into the stunts11 folder
dosbox.conf - copy into the dosbox folder
reMT15.7z - contains my 1.0 and 1.1 version of the Stunts MT15.drv
org.7z - contains the original 1.0 and 1.1 version of the Stunts MT15.drv

[llm]

Big question: do the sound glitches that Duplode talked about sill occure, in the first step the driver should behave exactly like the original

[llm]

@Daniel3D - did you get it running?

[Daniel3D]

@Daniel3D - did you get it running?

Haven't had the chance to work on it yet (late shifts). Maybe tomorrow.

[Daniel3D]

Got it running without any problems.
Strange to play with this sound. I never heard it live before.

I played a while without and with the new driver.
The only thing I noticed, that is new for me.
That is that there seems to be a fade out between music (from intro to main menu en from there to racing)
With the new driver that fade seems longer...

[llm]

That is that there seems to be a fade out between music (from intro to main menu en from there to racing)
With the new driver that fade seems longer...

the original MT15.DRV 1.0 uses a different timing method then original MT15.DRV 1.1 - does the delay also happen there?

so its very relevant to first test the difference between original 1.0 and 1.1 MT15.DRV
to give you a feeling was the original differences are

and then compare

orginal 1.0 to reMT15 1.0

and then

original 1.1 to reMT15 1.1


comparing original/MT15.DRV 1.0 with reMT15.DRV 1.1 makes no sense because i think even the orginal version 1.0 and 1.1 are different in behavior

[Daniel3D]

I only tested 1.1 stunts with the old and new 1.1 driver.

[llm]

using stunts 1.1: comparing original 1.0 and original 1.1 drv -> "fading out" is slower with 1.1 - isn't that the case in your installation? or did you maybe mixed up the versions?

[Daniel3D]

I only tested 1.1 stunts with the old and new 1.1 driver.

The new 1.1 driver seems to fade slower than the original 1.1 driver.

I'll double check. I will also check if my original driver is the same as your original one.