FOW option causes crash

[Jonathan Pollard]

A scenario I designed works fine without FOW, but when FOW is enabled from the starting menu, the game crashes the very first turn. I did not modify anything in the "ZOC, Recon, and Autoconquer" rulevar group, and the only new SFT type I put in was an "armored trains" SFT. However, when I deleted that SFT type and all of the units containing armored trains, the crash still took place.

The scenario in question is "Blitzkrieg Module System" available in the scenario bank. If it's of any help, an unfinished preview version of my scenario in the "deleted" section of the scenario bank does not have this FOW crash.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WindowsApplication1.GameLoopMainWindowClass.DoPresentStats()
at WindowsApplication1.GameLoopMainWindowClass.handleTimer()
at WindowsApplication1.ScreenClass.HandleTimer()
at WindowsApplication1.Form1.Timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WindowsApplication1
Assembly Version: 1.0.4927.21396
Win32 Version: 1.0.4927.21396
CodeBase: file:///C:/Advanced%20Tactics%20Gold/AdvancedTacticsGold.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
irrKlang.NET
Assembly Version: 1.3.0.0
Win32 Version: 1, 1, 0, 0
CodeBase: file:///C:/Advanced%20Tactics%20Gold/irrKlang.NET.DLL
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.84.0.0
Win32 Version: 0.84.0.0
CodeBase: file:///C:/Advanced%20Tactics%20Gold/ICSharpCode.SharpZipLib.DLL
----------------------------------------

EDIT: I get a similar error when I enable the "hardcore logistics" option.

[Jonathan Pollard]

I think I found out what I did to cause the problem. The version of my scenario that has the defective optional naval units button has FOW that works fine, but apparently something I did to get rid of the optional naval units button also messed up FOW. So hopefully I will be able to take care of this problem myself.

EDIT: I took care of the problem by going back to a previous version that had a functional FOW button and a non-functional naval button. I couldn't figure out how to get the FOW button to work without having the naval button, I have no idea why what I did to get rid of the naval button caused the FOW button to malfunction.