Fatal Application Exit

Post Reply
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Fatal Application Exit

Post by stephenterrell »

Reporting as requested:

Unhandled Exception! ExpCode 0x80000003 ExpFlags: 0 ExpAddress:0x00511C3D

Was preceded by report index>=0 ..\..\Archon\Util\ParserFile.cpp(921)

How i got there:

Loaded a previous campaign: went to main menu to start a new campaign, selected Macedonian 260-148 then Galatian changed field sizes and number of battles then clicked create.
rbodleyscott
Field of Glory 2
Field of Glory 2
Posts: 28015
Joined: Sun Dec 04, 2005 6:25 pm

Re: Fatal Application Exit

Post by rbodleyscott »

Thanks. Please can you see if you can find the correct date stamped error log file in /Documents/My Games/FieldOfGlory2 and attach it here.

Also can you remember what you changed the First and Last battle size and the number of battles to?
Richard Bodley Scott

Image
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Re: Fatal Application Exit

Post by stephenterrell »

I put the whole file here because i got the error Invalid file extension: error20191008_085810.log when i tried to attach the file to the message box

I can repeat the error sequence.

1. Load an existing campaign - in this case Macedonian 260-148 BC vs Bosporan 348-85 BC (battle 15/15 perhaps)
2.Press esc to get options
3. select main menu
4. yes to are you sure about loosing unsaved data
5. select campaings then FOG II campaigns and Lanunch
6. The pick boxes show above armies - other boxes have gone to default
7. click on pick enemy army, select Galatian from drop down list
8. click Create and error occurs

No other options need touching for this to occur






20191008_085810
VER:10512 BUILD:10009
PLATFORM: WINDOWS
WinVer:10.0.18362.329
0: NVIDIA GeForce GTX 1050 Ti
CPU String: GenuineIntel
Stepping ID = 9
Model = 14
Family = 6
Extended model = 9
CLFLUSH cache line size = 64
CPU Brand String: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
Cache Size = 256K
Found DirectX Version Number: 4.09.00.0904
Creating Device.....
MonkeyInitStart
MIS: Found DD
MIS: IsHW
MIS: SetCoop
MIS: Setting Disp Mode
MIS: Done Init 3D Device
MIS: Tex Enum
MIS: SDRS
MIS: Init Decal Render
TS: Start
TS: IAPSent
TS: UILoaded
INITIAL LOAD 7888
TS: BattleObj
TS: Managers
TS: BFBB
TS: LT
TS: InitDLUI
TS: Messages
TS: Ended
WARNING: SCRIPT ID: duplicate script id found (93000001 for CAMPAIGNS/2MPSRISEOFROME/DATA/UI/CAMPAIGNDISPLAY.BSF [C:/Program Files (x86)/Slitherine/Field of Glory II/CAMPAIGNS/2MPSRISEOFROME/DATA/UI/CAMPAIGNDISPLAY.BSF])
C:/Program Files (x86)/Slitherine/Field of Glory II/CAMPAIGNS/2MPSRiseOfRome/DATA/UI/CAMPAIGNDISPLAY.BSF exists
WARNING: SCRIPT ID: duplicate script id found (92000002 for DATA/UI/UNITLIST.BSF [C:/Program Files (x86)/Slitherine/Field of Glory II/DATA/UI/UNITLIST.BSF])
C:/Program Files (x86)/Slitherine/Field of Glory II/DATA/UI/UNITLIST.BSF exists
RESET
Playing as: 0
VOLUME TEXTURE: DATA/LIGHTING/CLUT_NE_Day_SummerLow.DDS
VOLUME TEXTURE: DATA/LIGHTING/CLUT_NE_Night.DDS
LOADTIME: 12937
RESET
ERROR
index>=0
..\..\Archon\Util\ParserFile.cpp(921) : Failed
ERROR

######## EXCEPTION: 0x80000003 at address: 0x00511C3D
Starting Debugger
SEARCHING: C:\Program Files (x86)\Slitherine\Field of Glory II;C:\Program Files (x86)\Slitherine\Field of Glory II;C:\WINDOWS
C:\Program Files (x86)\Slitherine\Field of Glory II;C:\Program Files (x86)\Slitherine\Field of Glory II;C:\WINDOWS
SGA: KernelErrorHandler
KernelErrorHandler
c:\dev\kernel\kernelerror.cpp(276) : +0 bytes (KernelErrorHandler) 0
SGA: CParserFile::GetChunk
CParserFile::GetChunk
c:\dev\archon\util\parserfile.cpp(921) : +26 bytes (CParserFile::GetChunk) 0
SGA: CBattleScriptHandler::CallFunction
CBattleScriptHandler::CallFunction
c:\dev\archon\util\battlescripthandler.cpp(4629) : +42 bytes (CBattleScriptHandler::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2345) : +27 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2049) : +24 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::GetValue
CScriptHelper::GetValue
c:\dev\archon\util\scripthelper.cpp(3102) : +24 bytes (CScriptHelper::GetValue) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2437) : +53 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::GetValue
CScriptHelper::GetValue
c:\dev\archon\util\scripthelper.cpp(3102) : +24 bytes (CScriptHelper::GetValue) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2437) : +53 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2345) : +27 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2049) : +24 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2345) : +27 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2049) : +24 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CScriptHelper::FunctionCall
CScriptHelper::FunctionCall
c:\dev\archon\util\scripthelper.cpp(3533) : +43 bytes (CScriptHelper::FunctionCall) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(2345) : +27 bytes (CScriptHelper::Execute) 0
SGA: CScriptHelper::Execute
CScriptHelper::Execute
c:\dev\archon\util\scripthelper.cpp(3483) : +0 bytes (CScriptHelper::Execute) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2046) : +0 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2049) : +24 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::ExecuteBlock
CCScript::ExecuteBlock
c:\dev\archon\util\c_script.cpp(2049) : +24 bytes (CCScript::ExecuteBlock) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(409) : +40 bytes (CCScript::CallFunction) 0
SGA: CCScript::CallFunction
CCScript::CallFunction
c:\dev\archon\util\c_script.cpp(240) : +33 bytes (CCScript::CallFunction) 0
SGA: CCScriptInstance::CallFunction
CCScriptInstance::CallFunction
c:\dev\archon\util\c_scriptmanager.cpp(191) : +32 bytes (CCScriptInstance::CallFunction) 0
SGA: CUIObject::ProcessMessage
CUIObject::ProcessMessage
c:\dev\archon\ui\uicomponents.cpp(1224) : +113 bytes (CUIObject::ProcessMessage) 0
SGA: CUIObject::Message
CUIObject::Message
c:\dev\archon\ui\uicomponents.cpp(1137) : +18 bytes (CUIObject::Message) 0
SGA: CUIButton::Trigger
CUIButton::Trigger
c:\dev\archon\ui\uicomponents.cpp(2724) : +0 bytes (CUIButton::Trigger) 0
SGA: CUIButton::HandleMouse
CUIButton::HandleMouse
c:\dev\archon\ui\uicomponents.cpp(2656) : +0 bytes (CUIButton::HandleMouse) 0
SGA: CUIManager::MsgProc
CUIManager::MsgProc
c:\dev\archon\ui\uimanager.cpp(3317) : +53 bytes (CUIManager::MsgProc) 0
SGA: WndProc
WndProc
c:\dev\archon\platform_windows.cpp(689) : +32 bytes (WndProc) 0
SGA: AddClipboardFormatListener
AddClipboardFormatListener
SGA: CallWindowProcW
CallWindowProcW
SGA: CallWindowProcA
CallWindowProcA
SGA: Direct3DCreate9Ex
Direct3DCreate9Ex
SGA: AddClipboardFormatListener
AddClipboardFormatListener
SGA: CallWindowProcW
CallWindowProcW
SGA: DispatchMessageW
DispatchMessageW
SGA: DispatchMessageA
DispatchMessageA
SGA: CPlatform::ProcessPlatformMessages
CPlatform::ProcessPlatformMessages
c:\dev\archon\platform_windows.cpp(332) : +0 bytes (CPlatform::ProcessPlatformMessages) 0
SGA: CPlatform::MainLoop
CPlatform::MainLoop
c:\dev\archon\platform_windows.cpp(1044) : +8 bytes (CPlatform::MainLoop) 0
SGA: WinMain
WinMain
c:\dev\archon\platform_windows.cpp(568) : +11 bytes (WinMain) 0
SGA: __tmainCRTStartup
__tmainCRTStartup
f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c(578) : +29 bytes (__tmainCRTStartup) 0
SGA: BaseThreadInitThunk
BaseThreadInitThunk
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
Debugger Cleanup
rbodleyscott
Field of Glory 2
Field of Glory 2
Posts: 28015
Joined: Sun Dec 04, 2005 6:25 pm

Re: Fatal Application Exit

Post by rbodleyscott »

Thanks. I have not so far been able to reproduce this - perhaps it depends on the specific saved campaign.

Please could you package the game save in a .zip file, which you should be able to attach as an attachment in the forum.

The easiest way to identify which is the correct save file is to load it, save it again, and then it will be the most recent .LSF file in /Documents/My Games/FieldOfGlory2/SAVES.

Many thanks.
Richard Bodley Scott

Image
pipfromslitherine
Site Admin
Site Admin
Posts: 9702
Joined: Wed Mar 23, 2005 10:35 pm

Re: Fatal Application Exit

Post by pipfromslitherine »

An alternative is that you can open any LSF file with a text editor and the first line shows it's display name.

Cheers

Pip
follow me on Twitter here
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Re: Fatal Application Exit

Post by stephenterrell »

Hi, renamed battle as test case and zipped.

I did a limited test (i.e. only 1) and it does not seem to matter which new enemy (step 7) is selected on the main menu for the new campaign.
Attachments
390.zip
(109.47 KiB) Downloaded 57 times
rbodleyscott
Field of Glory 2
Field of Glory 2
Posts: 28015
Joined: Sun Dec 04, 2005 6:25 pm

Re: Fatal Application Exit

Post by rbodleyscott »

Great, many thanks, that should help us to track down the bug.

Has this happened just with this one saved campaign, or can you make it happen with other campaigns?

Has it only happened on the last battle of a campaign?
Richard Bodley Scott

Image
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Re: Fatal Application Exit

Post by stephenterrell »

Hi, first time i have seen it. I usually end a campaign with "Accept" so this was unusual.
I could not remember which enemy i had been fighting so loaded the last save to see who it was then went via Esc to start a new campaign.
rbodleyscott
Field of Glory 2
Field of Glory 2
Posts: 28015
Joined: Sun Dec 04, 2005 6:25 pm

Re: Fatal Application Exit

Post by rbodleyscott »

stephenterrell wrote: Wed Oct 09, 2019 1:10 pm Hi, first time i have seen it. I usually end a campaign with "Accept" so this was unusual.
I could not remember which enemy i had been fighting so loaded the last save to see who it was then went via Esc to start a new campaign.
We shall certainly look into it. However, if it happens again, or you think of any other factors that might be different about this particular save, please let us know.

Thanks again for reporting the issue.
Richard Bodley Scott

Image
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Re: Fatal Application Exit

Post by stephenterrell »

Same issue with this campaign.
Attachments
388.zip
(112.26 KiB) Downloaded 58 times
pipfromslitherine
Site Admin
Site Admin
Posts: 9702
Joined: Wed Mar 23, 2005 10:35 pm

Re: Fatal Application Exit

Post by pipfromslitherine »

Thanks for helping us track this down. The crash will be fixed in the next update.

Cheers

Pip
follow me on Twitter here
rbodleyscott
Field of Glory 2
Field of Glory 2
Posts: 28015
Joined: Sun Dec 04, 2005 6:25 pm

Re: Fatal Application Exit

Post by rbodleyscott »

In the meantime, the workaround is that if you have played or loaded another campaign, you should close the game and restart it before starting a new sandbox campaign.

[The issue occurs if the AI side in the previous campaign used an ally, and then the new campaign setup cannot find a valid ally for the AI side. In your example the Bosporans had, it seems, used allies (Skythians incidentally) in at least one battle. This set a flag which did not get re-initialised when you started the new campaign. (That being the bug). In the new campaign, the Macedonians only have one possible ally, Greeks. The Galatians have no permitted allies, and the Carthaginians (apart from Hannibal in Italy) don't have any that are geographically compatible with both Macedonians and Greeks. Because the aforementioned flag is still set, the game attempts to add an ally contingent for the AI side in Battle 1, and because no ally is specified, the crash is caused.]

Restarting the game re-initialises the aforementioned flag, thus avoiding the problem. As Pip says, the bug will be fixed in the next update.
Richard Bodley Scott

Image
stephenterrell
Senior Corporal - Ju 87G
Senior Corporal - Ju 87G
Posts: 92
Joined: Fri May 06, 2011 5:53 pm

Re: Fatal Application Exit

Post by stephenterrell »

Thanks for the quick response and advice
Post Reply

Return to “Field of Glory II: Tech Support”