Alpha Centauri 2

Community => Chiron News Network => Topic started by: Yitzi on August 07, 2013, 03:23:07 AM

Title: Yitzi's unofficial SMAX patch 2.2d
Post by: Yitzi on August 07, 2013, 03:23:07 AM
Yitzi's unofficial SMAX patch 2.2d

http://alphacentauri2.info/index.php?action=downloads;sa=view;down=141 (http://alphacentauri2.info/index.php?action=downloads;sa=view;down=141)

I hope this fixes the last of the bugs up to version 2.2.  In any case, thanks to everyone who helped with beta testing (i.e. finding bugs.)
Title: Re: Yitzi's unofficial SMAX patch 2.2d
Post by: tyrone slothrop on August 07, 2013, 05:36:23 AM
Thanks for the update, Yitzi. In this thread (http://alphacentauri2.info/index.php?topic=3870.15) I linked to two saves that produced crashes, and this patch does fix the one in zak_crash_2.sav, but I'm still getting the same problem in zak_crash_1.sav.

Additionally, I've run into something else weird. In the attached .sav, none of the University bases have any ecodamage--but when you end the turn, you suddenly get about 5 fungal pops and the bases then all have massive ecodamage. University Base goes from 0 to 90. Here's the thing: I've rush-built a Tree Farm in Marine Biology Lab, but if I change the Tree Farm to something else and end the turn, the catastrophic ecodamage doesn't go off. Some kind of overflow in however the clean minerals are being counted? I tried the save in unpatched SMAX, but it starts off with huge ecodamage as soon as you load it. I'm guessing that's due to the clean mineral count not being "updated" when clean mineral facilities are built, since your patch counts the number owned instead. However, ecodamage doesn't increase on the next turn in the unpatched version, even with the Tree Farm built.
Title: Re: Yitzi's unofficial SMAX patch 2.2d
Post by: Yitzi on August 07, 2013, 04:37:10 PM
You're close; it was actually rolling over the number of bases (as the 128th base was built that turn), so it didn't count the facilities in any bases after what it thought was the total number (-128), other than the first (which doesn't check if it's more than the maximum number).

Both problems are fixed in 2.2e.