MoM bugs reports (to do list)

[I like Serena]

Could it have something to do that Demon Lord has life draining attacks and can have more than 100% HP that way ?

Thanks for thinking along, but with my new information I don't think so.

I've used dosbox-heavydebug to set a memory-breakpoint on the hitpoint-per-figure of the Galley and started the battle again.
And yes! it stopped, immediately at the start of the battle.
I continued and during the battle I used the Tweaker to change the hitpoints of the Galley back to 20 and lo and behold, the game did not crash anymore!

We have the following code in IDA:

Code:

ovr114:03A3 90                                      nop
ovr114:03A4 90                                      nop
[COLOR=Red]ovr114:03A5 20 53 90                                and     [bp+di-70h], dl
[/COLOR]ovr114:03A8 89 36 82 C5                             mov     w_unit_on_move, si

I believe the red line is responsible for the corruption.
I suspect it should be "90 90 90" instead of "20 53 90".
Kyrub?

[kyrub]

Yes, ILSe. Definitely. Fantastic find. I am very grateful to you for sparing me searching it.


Thanks all posters for reporting. Please stop reports for a short while, before we see and confirm that the thing was / wasnt solved.


EDIT:
No point in blaming Joel's editor. It was my own fault.

[I like Serena]

EDIT:
No point in blaming Joel's editor. It was my own fault.

So what did you do?

[kyrub]

I did not noice I moved a far call. Bad call, bad fonction, data problems.

Strange. I usually check them carefully. A change in relocation table was necessary. This is a typical combat bug, so I wonder if we have more of them in overland part (pet basilisks). Or not.

[Dymlos]

You guys rule.

[I like Serena]

You guys rule.

Thanx!

[kyrub]

Sorry for the delay, I am fully into my superbusy period. I'll post the correction shortly.

Full kudos to you, ILSe.
By the way, seeing how powerful was your debugging effort, you simply have to try your skills on THE Call lightning bug.

Narrowing the region where data corruption (access violation or how you call it) occurs = 4/5 of the solution. And one of the best testers out there told me that after +- 10 fights with Call lightning, the game crashes, the scope of internal damage must be therefore massive.

[Wintermute]

Thanks for the patch.

I tried searching but didn't see any mention of it, and I'm not sure if it's your patch or not, but I keep getting a repeatable crash when ever the computer uses a magician in a tactical battle. I don't remember this happening in v1.31, but it has been awhile since I last played that version.

I uploaded a save file here:
http://www.mediafire.com/download.php?dk9q8c31u8056ya

If you attack Sss'ra's Saradash city on Myrror, the crash will happen every time, as soon as the magicians take their turn, with an illegal instruction error msg, like this one:

16 bit MS-DOS Subsystem

MAGIC.EXE
The NTVDM CPU has encountered an illegal instruction.
CS:0378 IP:05cb OP:0f f0 0f 40 10 Choose 'Close' to terminate the application.

I'm using WinXP, and have the Insecticide 140i patch installed. I found a work around is to enable Strategic Battles whenever fighting a computer stack with a magician in it. You can get past the battle that way, but you can't always see them coming when they attack you, and I do prefer the tactical battles.

If this isn't your patch and just my installation, my apologies.

[I like Serena]

Full kudos to you, ILSe.
By the way, seeing how powerful was your debugging effort, you simply have to try your skills on THE Call lightning bug.

Do you or anyone else have save games that (easily) reproduce THE Call Lightning bug?

[I like Serena]

TI tried searching but didn't see any mention of it, and I'm not sure if it's your patch or not, but I keep getting a repeatable crash when ever the computer uses a magician in a tactical battle. I don't remember this happening in v1.31, but it has been awhile since I last played that version.

I uploaded a save file here:
http://www.mediafire.com/download.php?dk9q8c31u8056ya

This could easily be the result of the bug we discussed in this thread earlier.
Would you check if the bug still occurs after the fix?
Or check if the bug occurs in 1.40h or Vanilla?