Matrix Games Forums

After completing the Iron Rangers scenario in the Big Red One campaign, error messages indicated a failure to find the national data for the third scenario. At that point this bug report was created. Before I down loaded and installed the Beta I did not have this happen.

date/time : 2023-02-17, 15:33:03, 406ms
computer name : DESKTOP-AS5L0SA
user name : Tdeck <admin>
registered owner :
operating system : Windows 10 x64 build 19045
system language : English
system up time : 2 days 4 hours
program up time : 8 hours 1 minute
processors : 8x Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
physical memory : 8689/16295 MB (free/total)
free disk space : (C:) 113.11 GB (E:) 1426.19 GB
display mode : 2560x1080, 32 bit
process id : $5be4
allocated memory : 898.47 MB
largest free block : 131025.84 GB
executable : FlashpointCampaigns.exe
exec. date/time : 2023-01-31 04:45
version : 2.1.8429.26780
compiled with : Delphi 10.4 Sydney
madExcept version : 5.1.2
contact name : Ted
contact email : tdeckel@comcast.net
callstack crc : $72416d27, $a256415f, $a256415f
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 0000000001BC5514 in module 'FlashpointCampaigns.exe'. Read of address 0000000000000140.

main thread ($57fc):
01bc5514 +5a4 FlashpointCampaigns.exe Avatar 190 +35 TfAvatar.comboNatEraChange
01bc6bea +2da FlashpointCampaigns.exe Avatar 384 +17 TfAvatar.FormShow
00ac45e5 +565 FlashpointCampaigns.exe sSkinProvider 8996 +94 TsSkinProvider.AC_CMShowingChanged
00aacc67 +e57 FlashpointCampaigns.exe sSkinProvider 3959 +232 TsSkinProvider.NewWndProc
00acaa27 +0c7 FlashpointCampaigns.exe sSkinProvider 10679 +10 TsSkinProvider.AC_WMVisibleChanged
00aacad2 +cc2 FlashpointCampaigns.exe sSkinProvider 3915 +188 TsSkinProvider.NewWndProc
02102920 +2e0 FlashpointCampaigns.exe Unit1 9196 +38 TfMain.miStartPregameClick
020f874a +20a FlashpointCampaigns.exe Unit1 7453 +25 TfMain.miPlayNextScenarioClick
017a1653 +073 FlashpointCampaigns.exe PopupListEx 44 +13 TPopupListEx.WndProc
0260569e +07e FlashpointCampaigns.exe FlashpointCampaigns 263 +5 initialization

Did the error say what file was missing?

I get the following two error messages. I should also say I have repeated this several times and get the same result.

X Get NationalityO-Unable to fetch nationality instance for unit "FSJB 253" ref "CW 80s West-German +LL+Pio (1980-1989)

X There wan an error loading this file (2): Access violation at address 00000000023F8C64 in module "Flashpoint Capaigns.exe" Read of address 00000000000000F0 for file US1-SN$ Percutio.scn

Sorry. I just noticed a typo in the second error message. The $ in US1-SN$ should be a 4. It should read:

X There was an error loading this file (2): Access violation at address 00000000023F8C64 in module "Flashpoint Capaigns.exe" Read of address 00000000000000F0 for file US1-SN4 Percutio.scn

T

Just noticed that this is exactly the same as an issue reported earlier shown below. My screens were similar and the error messages are exactly the same.

Problem loading fourth Big Red One scenario
Post by WABAC » Wed Feb 08, 2023 6:57 pm

Sorry, it is a bad datafile reference in the scenario. We are working on a means to fix it.

yes, during development of the campaign the author slipped in some extra units as part of a modified national era XLS file that did not ship with the core game. The last I heard the modifications are going into the standard national era file so this problem will go away. We will also ask the authors not to add in their own modified national era files.

In the meantime, if you unzip and drop this file into your <game install folder>\Modules\Common\Data\West-German\ directory alongside the existing "CW 80s West-German.xls" file then I think the scenario will run fine.

The official release will remove the need to have this file.

Thanks for reporting this! Rob C

I just checked to see if there was any further follow up, and after copying the new file to the West German data directory all is well again. Thank you for continuing to stay with this and provide a way to continue this campaign.

Ted

The 2.1.1 update will have this fixed for good in a few weeks.