When I try to start a campaign, the DCG freezes.

[mizusummer]

I was trying to create a DCG campaign and test play it, but when I selected the allcamapigns.dcg file from the ThirdPartyDataFolder and clicked the start button, the DCG stopped responding and I had no choice but to close the program.

I have a few other maps that I made myself, but this is the first time this has happened, so I don't know what to do.

I've attached a zip file containing the dcg error.txt and the folder that was in the process of being generated, so could you help me find the cause?

testmap.zip

[Lowengrin]

That's strange because the log shows that the campaign data files loaded fine.  

Are you using mods?  I ask because they make the process of figuring out the error(s) a lot more difficult for me as compared to just "vanilla"?

[mizusummer]

Thank you for your reply. This is a campaign created in the BAT v4.3 environment.

[Lowengrin]

A quick look at your files and it might be that you assigned skins for your planes and/or that you started the flights on the runway.  Neither are something I do when I create my master mission file.

If you want to assign a skin to a particular squadron, do it through the timetable.dcg file.

[mizusummer]

I did indeed specify a lot of skins in the FMB, so I reset all the plane skins to the default and generated them again, and then I got this error log:

Quote

[2025/06/13 22:54:06.118] New Campaign Selected.
[2025/06/13 22:54:06.119] Setting new log file date.
[2025/06/13 22:54:06.126] New Campaign Begun
[2025/06/13 22:54:17.341] Campaign Start Button Clicked.
[2025/06/13 22:54:18.410] The map is OperationKikusui.
[2025/06/13 22:54:18.416] Setting up patrol areas.
[2025/06/13 22:54:18.416] Patrol Area moved into action radius.
[2025/06/13 22:54:18.416] Patrol Area moved into action radius.
[2025/06/13 22:54:18.417] Setting up patrol routes.
[2025/06/13 22:54:18.417] Target Locations processed.
[2025/06/13 22:54:18.417] Patrol Route check has reset the Minimum Action Radius to 1502 Kilometers.
[2025/06/13 22:54:18.418] Manual Campaign Import Begun
[2025/06/13 22:54:18.419] Ship names and classes loaded.
[2025/06/13 22:54:18.439] Import of Squadrons Begins.
[2025/06/13 22:54:18.449] Squadron Merging Begins.
[2025/06/13 22:54:18.450] Import of Squadrons Complete.
[2025/06/13 22:54:18.461] Campaign Preferences Saved.
[2025/06/13 22:54:18.462] Manual Campaign Import Finished
[2025/06/13 22:54:18.566] No entry found for Player Squadron in the squadids.dcg file.
[2025/06/13 22:54:19.410] No entry found for Player Squadron in the squadids.dcg file.
[2025/06/13 22:54:19.857] The replacement plane for the  ("") was not found in the Class.DCG file.
 

The last line says "The replacement plane for the ("") was not found in the Class.DCG file." This is strange because when I generate other campaigns with this Class.dcg, I don't get any similar errors. And the strangest thing is that every time I try to generate the campaign again, the replacement plane changes. Sometimes it's SBD5, sometimes it's KI-21II, and sometimes there's no description at all like in the log I submitted this time, and the problem changes. Of course, there were no mistakes in the descriptions of these planes in the class.dcg file.

[Lowengrin]

If you could repost your campaign and data files, I'll have a look.  

The replacement plane issue is because DCG code is optimized to the shorter naming convention used by the vanilla game and not the full naming convention used by the mods (at least from the class files I've seen).  It makes much of the selection code irrelevant and leads to much more random replacement choices.

[mizusummer]

Thank you for your reply.
I see... it's true that some of the aircraft in class.dcg have their own abbreviations by the manufacturer...
I will upload the file again.
I would also like you to take a look at the requirements in the article

https://forum.jg1.org/topic/16911-dcg-created-missions-are-not-displayed-correctly-in-fmb/
This is a campaign that uses the Japan1/load.ini that comes with the IL-2.
I included it in the .zip file, so I would appreciate it if you could take another look at the cause of this.

testmap.zip

[Lowengrin]

mizusummer, please download the latest IL2DCG build (3.50 #19) and see if that helps with your issues.  

[mizusummer]

Thank you for releasing the new version. I downloaded it and tried it right away. In conclusion, it didn't solve anything. First of all, I got the following error log for the kikusui zip file I uploaded previously.

Quote

[2025/06/16 17:10:14.735] New Campaign Selected.
[2025/06/16 17:10:14.735] Setting new log file date.
[2025/06/16 17:10:14.742] New Campaign Begun
[2025/06/16 17:10:19.499] Campaign Start Button Clicked.
[2025/06/16 17:10:20.540] The map is OperationKikusui.
[2025/06/16 17:10:20.543] Setting up patrol areas.
[2025/06/16 17:10:20.543] Patrol Area moved into action radius.
[2025/06/16 17:10:20.544] Patrol Area moved into action radius.
[2025/06/16 17:10:20.544] Setting up patrol routes.
[2025/06/16 17:10:20.544] Target Locations processed.
[2025/06/16 17:10:20.544] Patrol Route check has reset the Minimum Action Radius to 1502 Kilometers.
[2025/06/16 17:10:20.545] Manual Campaign Import Begun
[2025/06/16 17:10:20.546] Ship names and classes loaded.
[2025/06/16 17:10:20.566] Import of Squadrons Begins.
[2025/06/16 17:10:20.578] Squadron Merging Begins.
[2025/06/16 17:10:20.578] Import of Squadrons Complete.
[2025/06/16 17:10:20.594] Campaign Preferences Saved.
[2025/06/16 17:10:20.595] Manual Campaign Import Finished
[2025/06/16 17:10:20.603] No entry found for Player Squadron in the squadids.dcg file.
[2025/06/16 17:10:21.446] No entry found for Player Squadron in the squadids.dcg file.
[2025/06/16 17:10:21.820] The aircraft assigned to IJN_AG_601_FS0 has been switched to the BF_109F2.
[2025/06/16 17:10:21.831] The aircraft assigned to IJN_AG_601_FS1 has been switched to the BF_109F2.
[2025/06/16 17:10:21.841] The aircraft assigned to IJN_AG_601_VB0 has been switched to the BF_109F2.
[2025/06/16 17:10:21.852] The aircraft assigned to IJN_AG_601_VB1 has been switched to the BF_109F2.
[2025/06/16 17:10:21.862] The aircraft assigned to IJN_AG_Miyazaki0 has been switched to the BF_109F2.
[2025/06/16 17:10:21.872] The aircraft assigned to IJA_F_C_104z0 has been switched to the BF_109F2.
[2025/06/16 17:10:21.884] The aircraft assigned to IJA_F_C_85z0 has been switched to the BF_109F2.
[2025/06/16 17:10:21.894] The aircraft assigned to IJA_F_S_111z0 has been switched to the PBY.
[2025/06/16 17:10:21.904] The aircraft assigned to IJA_F_D_2z0 has been switched to the PBY.
[2025/06/16 17:10:21.916] The aircraft assigned to IJA_F_TS0 has been switched to the PBY.
[2025/06/16 17:10:21.926] The aircraft assigned to IJA_F_S_71z0 has been switched to the PBY.
[2025/06/16 17:10:22.285] Campaign folder (F:\IL-2BAT\IL-2 Sturmovik 1946 BAT\Missions\Campaign\JA\DCG\) selected.
[2025/06/16 17:10:22.295] Set Target Nation Began.
[2025/06/16 17:10:22.296] Set Target Nation Ended.
[2025/06/16 17:10:22.297] Checking Stationary List
[2025/06/16 17:10:23.601] IJNFishJunk_18 is transporting 4-HaGoRadio_27 from Blank.
[2025/06/16 17:10:23.616] IJNFishJunk_19 is transporting 4-HaGoRadio_28 from Blank.
[2025/06/16 17:10:23.631] IJNFishJunk_20 is transporting HoHa_29 from Blank.
[2025/06/16 17:10:23.651] Set up patrol routes for CV groups.
[2025/06/16 17:10:23.655] Column List routine complete.
[2025/06/16 17:10:23.796] Stationary Objects Check.
[2025/06/16 17:10:23.798] Ship names and classes loaded.
[2025/06/16 17:10:23.800] Campaign Preferences Saved.
[2025/06/16 17:10:23.800] The scenario is "OperationKikusui".
[2025/06/16 17:10:24.172] Campaign Data Files = Z:\IL2DCG350b19\IL2DCG\OperationKikusui\
[2025/06/16 17:10:24.173] Campaign Backup Files = 
[2025/06/16 17:10:24.551] Campaign Info processed.
[2025/06/16 17:10:24.552] The map is OperationKikusui.
[2025/06/16 17:10:24.553] Setting up end campaign parameters.
[2025/06/16 17:10:24.557] Campaign Preferences Saved.
[2025/06/16 17:10:24.558] Campaign Preferences Saved.
[2025/06/16 17:10:24.559] Completed reading Territory information.
[2025/06/16 17:10:24.560] Reset Objects.
[2025/06/16 17:10:39.440] Stationary Objects Check.
[2025/06/16 17:10:39.745] USN_VF_6A0 #10 pilot's name changed due to duplication.
[2025/06/16 17:10:39.767] USN_VF_50A0 #10 pilot's name changed due to duplication.
[2025/06/16 17:10:39.773] USMC_VMF_524z0 #4 pilot's name changed due to duplication.
[2025/06/16 17:10:39.980] USN_VB_18A0 #7 pilot's name changed due to duplication.
[2025/06/16 17:10:39.991] USN_VB_19A0 #6 pilot's name changed due to duplication.
[2025/06/16 17:10:40.49] USMC_VMSB_142z0 #11 pilot's name changed due to duplication.
[2025/06/16 17:10:40.279] Campaign Preferences Saved.
[2025/06/16 17:10:40.280] Determine the starting location of a column.
[2025/06/16 17:10:40.297] Determine the airfield of all squadrons.
[2025/06/16 17:10:40.299] USN_VF_14A0 attached to USS_Ticonderoga
[2025/06/16 17:10:40.302] USN_VF_21Bz0 attached to USS_Ticonderoga
[2025/06/16 17:10:40.304] USN_VT_51A0 attached to USS_Ticonderoga
[2025/06/16 17:10:40.307] USN_VBF_88A0 attached to USS_Ticonderoga
[2025/06/16 17:10:40.309] USN_VF_18A0 attached to USS_Bunker_Hill
[2025/06/16 17:10:40.312] USN_VF_19A0 attached to USS_Bunker_Hill
[2025/06/16 17:10:40.314] USMC_VMF_217z0 attached to USS_Bunker_Hill
[2025/06/16 17:10:40.317] USMC_VMF_218z0 attached to USS_Bunker_Hill
[2025/06/16 17:10:40.319] USN_VBF_19A0 attached to USS_Intrepid
[2025/06/16 17:10:40.322] USN_VF_31A0 attached to USS_Intrepid
[2025/06/16 17:10:40.324] USN_VB_18A0 attached to USS_Intrepid
[2025/06/16 17:10:40.327] USN_VB_19A0 attached to USS_Intrepid
[2025/06/16 17:10:40.329] USN_VF_20A0 attached to USS_Enterprise
[2025/06/16 17:10:40.332] USN_VF_6A0 attached to USS_Enterprise
[2025/06/16 17:10:40.334] USN_VS_6B0 attached to USS_Enterprise
[2025/06/16 17:10:40.337] USN_VT_6B0 attached to USS_Enterprise
[2025/06/16 17:10:40.339] USN_VF_7A0 attached to USS_Hancock
[2025/06/16 17:10:40.342] USN_VF_50A0 attached to USS_Hancock
[2025/06/16 17:10:40.344] USN_VB_11A0 attached to USS_Hancock
[2025/06/16 17:10:40.346] USN_VT_5B0 attached to USS_Hancock
[2025/06/16 17:10:40.349] USMC_VMF_524z0 attached to USS_Bataan
[2025/06/16 17:10:40.351] USMC_VMSB_142z0 attached to USS_Bataan
[2025/06/16 17:10:40.354] USMC_VMSB_144z0 attached to USS_Bataan
[2025/06/16 17:10:40.356] USN_VF_33Az0 attached to USS_Kitkun_Bay
[2025/06/16 17:10:40.359] USN_VF_47A0 attached to USS_Kitkun_Bay
[2025/06/16 17:10:40.361] USN_VF_51A0 attached to USS_Sanjacinto
[2025/06/16 17:10:40.364] USN_VF_26A0 attached to USS_Sanjacinto
[2025/06/16 17:10:40.366] USN_VB_88A0 attached to USS_Sanjacinto
[2025/06/16 17:10:40.424] Player squadron is tentatively based at Unknown.
[2025/06/16 17:10:40.424] Player squadron is based at Unknown.
[2025/06/16 17:10:40.425] Removing nearest matching non-player squadron.
[2025/06/16 17:10:40.426] Deleting squadron IJA_F_S_22z0.
[2025/06/16 17:10:40.441] Pilots saved.
[2025/06/16 17:10:40.442] Squadrons saved.
[2025/06/16 17:10:42.25] Squadron base routine started.
[2025/06/16 17:10:42.285] IJA_F_S_22z0 has bad airfield coordinates.
[2025/06/16 17:10:42.285] Player base is Unknown
[2025/06/16 17:10:42.286] The player squadron has no legitimate airfield or carrier.

I was just loading the new version of DCG's optional3rdpartyDataFolder, and I hadn't changed anything in the file description, but I started getting these errors, which was a real headache.
Also, with the other MinamiKyusyu campaign, I was able to generate missions, but when I loaded the generated missions with FMB, they were like the ones in the picture, and there was no improvement...

https://i.postimg.cc/52Bb1GYD/dcg.jpg

 

 

[Lowengrin]

I'll have another look, but my suspicions are that it's an issue with the DCG data files for the mod and not DCG itself.

[mizusummer]

I'm sorry to bother you during your busy schedule, but I would appreciate your help.

You said it's a problem with the mod data file, but is there an error in the description in the XXX.dcg file, or is there a problem with my BAT environment?

[Lowengrin]

My guess is it's an error with one of the XXX.dcg files.  Likely the class.dcg or squadids.dcg.  

[mizusummer]

see, I understand.

What about the issue of it not loading in FMB? I'm very frustrated that all the campaigns I've made have ended up like this.

[Lowengrin]

I'm unsure why they won't fully load in FMB.  It could be that something in the mission format has changed over the years or it could be errors in your DCG files that use objects from BAT.  I haven't had time to test to see if it's a change in the mission format.  If it is, I'll correct it.  If it's not, then (again) it's something in the data files.

To use BAT, did you create your own data files for DCG?  Or use an existing set?

onyx1999 has posted campaigns using BAT 4.3 and is probably the most knowledgeable person on combining BAT and DCG that I know.  His "compatibility" mod is here:

https://www.sas1946.com/main/index.php?topic=74038.msg804297#msg804297

 

[Lowengrin]

The latest beta (#20) should fix the FMB issue.  If not, let me know.

[mizusummer]

I downloaded the latest beta version. The mission I created in FMB was displayed.

Thank you. The problem I've been having since the beginning of the year has finally been solved!

However, the kikusui error log still appeared.

Just to be sure, I used the file from the link you posted before, but the result was the same.

I usually use my own file where I added data for the BAT aircraft that is not written in the class file.

Similarly, armor, object, shipsname, etc. are my own files where I added BAT ships to the default DCG file.

I still can't create the anti-ship attack missions that I want to do, so I think I should modify the master missions a bit more in this area...

[Lowengrin]

Quote

[2025/06/16 17:10:42.285] IJA_F_S_22z0 has bad airfield coordinates.

This is an interesting error.  It suggests something is wrong with the .rds file and/or airfields.dcg file.  Alternatively, check that the player squadron is in the squadids.dcg file.