Interesting... I can give it a run tomorrow.

Awesome - thank you.

I'll give it a try too, I've got it on a 386DX and a P233MMX so it might be useful to see if they give the same result.

BTW please please please call your emulator "Lemulator." Just saying.

xjas wrote:

I'll give it a try too, I've got it on a 386DX and a P233MMX so it might be useful to see if they give the same result.

Thanks

BTW please please please call your emulator "Lemulator." Just saying.

In my head I've been calling it "The Lemulator" but the program itself is just called "WinLemmi.exe" - to match the original game's "VgaLemmi.exe" 😀

Is it 4 minutes for stage 1 or 3 minutes? My copy starts at 3-00 on the timer. The file name is also VGALEMM2.EXE (not VGALEMMI as said above). Are there different versions of this game?

Anyway, I was approaching 4 minutes on my stopwatch for that (vga, high quality) but the level ended early with all lemmings accounted for. This is on a DX4 100MHz running MS-DOS 6.22. I suspect you are right that the timing is inaccurate, too slow. Will try it again

I don't have time to look at the code right now (it's available??) but if it's counting 85 retraces per second as you say, then the result is always going to be slower than a real clock on a system running at 70hz. The above user saying they would run it on a pentium and a 386 will either get the exact same result on both systems, or it will take longer on the 386 if the code is waiting for a vertical retrace at the end of each loop and the system isn't fast enough. I would assume they had that odd counter going for some other AI or game event and just decided to tie it to the in game clock as well. Games that use retraces for the timer shouldn't have any unusual speed issues outside of running slower on a modern 60hz display.

edit: Ahh, I didn't notice the game difficulty setting, now it's 4 minutes.. let's try again.

UPDATE: My result was 4:51 on my android using the timer app, +/- a bit of reaction time. I think "The Lemulator" is good to go!

Trying it on a Dell Optiplex GX1 with MS-DOS 6.22, Pentium II 350MHz, 256MB RAM. Bit oeuvrekill but hopefully it helps.

Elapsed time was 4:50

Seeing 4:52 on my Pentium II 400MHz in REAL DOS 7.1.

BeginnerGuy wrote:

Is it 4 minutes for stage 1 or 3 minutes? My copy starts at 3-00 on the timer. The file name is also VGALEMM2.EXE (not VGALEMMI as said above). Are there different versions of this game?

Not sure but note this is Oh No More Lemmings, not the first Lemmings. The first level is called "Down and Out Lemmings".

I don't have time to look at the code right now (it's available??)

I'm just looking at it in debugger/disassembly listing.

but if it's counting 85 retraces per second as you say, then the result is always going to be slower than a real clock on a system running at 70hz.

That's definitely what it looks like - at inner loop of 5 cycles (throttled by vertical retrace) and an out loop of 17 cycles before updating the current time. 5 x 17 = 85.

UPDATE: My result was 4:51 on my android using the timer app, +/- a bit of reaction time. I think "The Lemulator" is good to go!

Great - thanks for checking it out for me.

oeuvre wrote:

Trying it on a Dell Optiplex GX1 with MS-DOS 6.22, Pentium II 350MHz, 256MB RAM. Bit oeuvrekill but hopefully it helps.

Elapsed time was 4:50

static- wrote:

Seeing 4:52 on my Pentium II 400MHz in REAL DOS 7.1.

Thank you. Pretty sure we can say this was a bug (or weird design) of the original game.

I think the question is a different one. If it counts 85 retraces per second and if I concede the Psygnosis programmers to know how long 4 mins is, where does the 85 comes from?

Could it be that originally the graphics mode for lemmings was 43 Hz interlaced? This would be 86 retraces/s.
Have you checked if the 85 is different whether you choose High Performance PC or PS/2.

Maybe a 70 Hz mode is just the wrong graphics mode in regards what the game expects the card to actually set.

Probably ought to time it on an Amiga.

elianda wrote:

Could it be that originally the graphics mode for lemmings was 43 Hz interlaced? This would be 86 retraces/s.

Interesting idea - possibly I suppose, although the game is definitely selecting video mode 0x0D which is 320x200 @ 70Hz (according to this) and I don't think it's tweaking any of the CRTC timing registers.

Hmm and what about the other modes, e.g. for tandy?

elianda wrote:

Hmm and what about the other modes, e.g. for tandy?

My emulator doesn't support all these modes so it's a bit hard for me to say for sure, but I just tried running every different mode in dosbox debugger and all report 320x200 and ~70Hz and in all cases 1 game minute = 73 real seconds.

Given that real DOS machines show this behaviour, that dosbox and my emulator show this behaviour, that the code looks like that's what it's doing and that the code/math points in this direction I think it's fair to say this is a bug/quirk of the original game that was just always there.

Wonder if the devs just lazily re-used some timing code when it was ported over from the Amiga, resulting in this?

Hi, I've done that test with the normal setting, since I've got no High-Performance PC at hand right now..
In a case it's of any use - the PC was a 286@10MHz and 4 minutes in-game time equaled ~5 minutes and 50 seconds.

xjas wrote:

Wonder if the devs just lazily re-used some timing code when it was ported over from the Amiga, resulting in this?

That's an interesting thought. But then why did they spend some exra time for that level where they used the AdLib as a DAC ?

Jo22 wrote:

That's an interesting thought. But then why did they spend some exra time for that level where they used the AdLib as a DAC ?

Which level uses Adlib as a DAC? I am pretty familiar how Lemmings Adlib music/sfx driver works and have found no such evidence.

Took the machine around 280 seconds a 4 minutes 40 seconds.

amadeus777999 wrote:

Took the machine around 280 seconds a 4 minutes 40 seconds.

Thanks - closer to what the emulators are doing than what it should be 😀