Application crash when loading unit from coastal hex in Blizzard

[Beryl]

During Blizzard, application crash after trying to load a unit from a costal hex
Bug report already sent via e-mail, reproducible

[Beryl]

Here is the save game to reproduce the error
Instructions :
Go to China Sea
Pick a TRS in Haichow
Move the TRS in Sea of Japan
Try to load the Hiroshima MIL

[Cad908]

ORIGINAL: Beryl

Here is the save game to reproduce the error
Instructions :
Go to China Sea
Pick a TRS in Haichow
Move the TRS in Sea of Japan
Try to load the Hiroshima MIL

Beryl,

Using your save I was able to move a TRS to the Sea of Japan, load the 29th GAR and then place the loaded TRS in the 2 Box. No issues.

Did this repeat after a reload? Try the same unit I used and see if an issue arises. If so, please indicate which unit and I will try to recreate.

-Rob

[Beryl]

The 29th GAR in Tsing Tao borders China Sea. As I wrote move the TRS to the Sea of Japan and try to load the Hiroshima MIL

[Cad908]

ORIGINAL: Beryl

The 29th GAR in Tsing Tao borders China Sea. As I wrote move the TRS to the Sea of Japan and try to load the Hiroshima MIL

Beryl,

Sorry about my confusion, I tried to run the test quickly and should have looked closer at your post.

Used your saved game and ran the test again and, as below, I had no issue.

Do you recall the sequence previous to the crash? There might be something going on, but I cannot confirm your problem.

-Rob

[Beryl]

I did some further tests. The game crash on two different XP SP3 machines, but works on a windows 7 netbook !
I did a reinstall on my XP PC + patch 1.09, the game crash exactly the same way, always at the same address
I sent the bug report a second time.
The Access violation occurs at address 0079DAFE in MWIF.exe. Read adress 8080008C
Call stack is TUnit.GetUnitType

[Shannon V. OKeets]

ORIGINAL: Beryl

I did some further tests. The game crash on two different XP SP3 machines, but works on a windows 7 netbook !
I did a reinstall on my XP PC + patch 1.09, the game crash exactly the same way, always at the same address
I sent the bug report a second time.
The Access violation occurs at address 0079DAFE in MWIF.exe. Read adress 8080008C
Call stack is TUnit.GetUnitType

I'll investigate this some more but at first reading there is nothing obvious in your MadExcept bug reports.