Problems with version 9.1

DRG · #1 December 5th, 2015, 08:41 AM

There are a lot of "gotachas" like that in this game and yes it really doesn't like faulty SHP files

HcK · #2 January 10th, 2016, 04:54 PM

Hi,

I have a Acer 7560G running Win7, game(s) are installed on a SSD. Since upgrading to 9.1 I have started to get a lot of crashes ("Program has stopped working, Windows is looking for a solution"), as far as I can tell only during the campaign repair screen or the campaign support unit purchase screen (and the map editor opened from there).

I installed the 9.1 by making a copy of the game directory of version 8.0 and installing 9.1 there. Did this for the previous two upgrades, too, and didn't get any crashing problems then.

I do have custom OOBs and use them in the campaign I continued after upgrading to 9.1.

Anybody else get a lot of crashes? Are the custom OOBs to blame?

Mobhack · #3 January 21st, 2016, 03:26 PM

Quote:

Originally Posted by HcK

Hi,

I have a Acer 7560G running Win7, game(s) are installed on a SSD. Since upgrading to 9.1 I have started to get a lot of crashes ("Program has stopped working, Windows is looking for a solution"), as far as I can tell only during the campaign repair screen or the campaign support unit purchase screen (and the map editor opened from there).

I installed the 9.1 by making a copy of the game directory of version 8.0 and installing 9.1 there. Did this for the previous two upgrades, too, and didn't get any crashing problems then.

I do have custom OOBs and use them in the campaign I continued after upgrading to 9.1.

Anybody else get a lot of crashes? Are the custom OOBs to blame?

Actually, I can confirm a crash when using the "Review" button in the campaign repair/upgrade screen.

It has now been fixed for the next release (both games). But meanwhile - don't use the Review function to inspect your troop's data.

HcK · #4 January 21st, 2016, 05:57 PM

Well, finding and reporting bugs is my Real Life (TM) job, too, but I still didn't twig to the fact that it was the Review function that triggered this.

And as in real life, it's still the dev who, using oftentimes a vague and only peripherally helpful description, has to find the defective code and figure out how to fix it without breaking anything else. Glad if I could help, but kudos to you for nailing it down.