Be Careful about using old maps

[troopie]

I decided to ask how Russian armour would perform in the African bush, so I used an old map dating from SPWW2v5. I could select a map and buy units but when I tried to deploy, the programme crashed. I was using a hacked oob for one side so I tried using default orbats for that side. The programme crashed. I tried using the hacked oobs with a later map. It worked fine. I conclude that the map, it dates from 2003, is somehow not compatible. Nothing needs to be changed, just be careful.

troopie

[DRG]

Which map ?? If it's not in the game post it. There should not be any compatibility issues UNLESS the map DAT file is corrupted in some way. The oldest map in the game is ww2 #8 from 2000 and it works perfectly with the latest version of the game, no crashes on deployment

Seriously..... I WANT to test that map on my computer. I assume it was a ww2 map used in MBT? That alone would not cause an issue as both games use the exact same map code

Don

[troopie]

The map is not a standard map. I made it for a dead mod but it has never posed a problem before.

troopie

[DRG]

Confirmed it will lock up the game on deploy.........looking for the reason now

[DRG]

This will require further digging as I REALLY want to understand why this happened but strangely-------if you auto deploy troops it runs OK and if you rearrage units after auto deploy it runs OK......but try to simply deploy units and it locks the game up.

I have tried the same thing with other maps made from that time period and so far everything works perfectly. I tried making a small change to the map and resaved in another slot but it still locked up on a simple deploy.....why autodeploy is OK is a mystery ATM

Further....... there seems to be an issue with hex 1,1. Earlier when I auto deployed I only went as far and seeing that they had deployed and move a couple to another position.......this time I tried scrolling the map upwards and when it got to the top it went black......it did not lock up the game but the entire map screen was black but the side deploy menu was OK and it just happened again when I simply loaded the map....and that corrupts any map you try to load afterwards unless you restart the game.

I just tried loading the original map after a restart and it was OK until I scrolled to the top row.....after a restart I tried doing some editing to the grass areas to see if I could re-set the map save..... I set up a scenario and loaded the map then bought units for both sides....player one in this case was a right side deploy and it went perfectly.....player 2 was a left side deploy and the game locked up because on manual deploy there is a unit placed on hex 1,1. ( or at least the top row

Bottom line here is.....DON'T USE THAT MAP :) and I will continue to poke around with it but this problem seems to be confined to this map only as others I have tried from 2004 and earlier work perfectly.........right now I'm putting this down to serious data corruption in the DAT file that is not being "fixed" by editing and resaving

Or, put another way...that map is cursed

[DRG]

the creation date for that is 2004.....any chance it was started with an early, pre 2000 DOS version ??

[troopie]

It was started for the now defunct SPWW2 WW1 mod. It was used for the scenario, 'Amiable Roughnecks.' It dates from 2003/4. I remember the name of the scenario only. I no longer have it.

troopie

[DRG]

I tried cutting the entire map out and pasting it into a blank map that was slightly larger......game locked up on deploy......tried again pasting it into a slightly smaller blank map....game locked up on deploy....I'm afraid that map is hopelessly borked

[RightDeve]

That map has a disease on it.

[DRG]

The " good news" seems to be that the issue is confined to that one map

[troopie]

It works fine in a Dos version of SPWW2 I have installed. I tried transferring it to WinSPMBT, renumbering it and trying it there. It locked the game. If you have it in a Windows version, throw it away. It will be nothing but trouble.

troopie

[DRG]

I think the problem could be originating here. Why it works in a DOS version is a mystery


http://forum.shrapnelgames.com/attachment.php?attachmentid=14869&stc=1&d=1502932617