A fix for "Commandos: Behind Enemy Lines"

[cluxter]

Hi,

I was able to run "Commandos: Behind Enemy Lines" v1.0 (the French edition) on Wine v10.7 (on NixOS).

Side note: it required a No-CD patch because Wine didn't detect the ISO file as a CD-Rom and blocked a new game from launching, I don't know why. I also had to set "Windows 95" as the OS in the Wine settings.

The game works very well, too well actually because I noticed that the scenes, the animations of the characters, the blinking of the menus, and the animation of the lights in the "Credits" page are all way too fast. The game itself is too fast, which is okay (as it's not ultra fast) but not optimal as you must be way more reactive in game, and the voice of the briefings at the beginning of a new mission doesn't match what is shown on the map.

This is what we have right now in the ddraw.ini file:

; Commandos
[comandos]
maxgameticks=-1

; Commandos
[comandos_w10]
maxgameticks=-1

I fixed the issue with these new settings:

; Commandos
[comandos]
maxgameticks=32
limiter_type=2
; Commandos
[comandos_w10]
maxgameticks=32
limiter_type=2

Using another value for limiter_type either won't work (still too fast) or will be buggy (the game stutters).
The value of 32 for maxgameticks is the right one for the voices to match the animations on the map during the briefings of the missions. It also matches the speed I was used to when I played this game back in the days.

With these settings the game works exactly as it used to originally. The experience is way more satisfying in my opinion.

I still want to test a few things (like fullscreen/not fullscreen, etc.), then I will submit a PR so we can land this fix in.
Meanwhile, for those who can, I would love if you could test these settings and give me a feedback about them.

[cluxter]

I made a Windows 95 virtual machine and ran the game in it.
Then I moved a character from a very precise location to another very precise one and timed how long it took.
Then I made the same thing in the game ran in Wine with different values of maxgameticks until I found the right one that would reproduce the exact same time I measured in Windows 95. This value turned out to be 32.
I edited the first message to reflect that.