Lowengrin

That is correct.

Okay, I remembered that way back before adding columns was a thing, I wrote a routine that forced every ship AFTER a transport ship to act as an escort to that ship and use the same sea route. Of course, back then, it required the order of ships in the template mission file to be ordered with any carrier task force first and then transports and escorts after. But being able to add ships through the timetable can break that ordering.... So now I've changed it so that if a ship is assigned to the patrol route, it will never be assigned to transport escort duty. Or at least that's what should happen with this build.... IL2DCG350b24.zip

Okay, I'll have another look.

They don't appear at all? Not even in the first Japanese sea route location?

Okay, I think I found the bug for ships jumping out of the patrol area and into a sea lane. IL2DCG350b23.zip

Can you do me a favour and post the dcgerror.txt for the first mission of the test campaign? And the .srd and .prd files. Thanks!

Check the latest beta.

This beta should fix the issues around ships not appearing in the patrol zone (.prd) when they are added to a campaign through the time table. This build should also require ship names (and not their "chief" designation for the timetable command to move squadrons onto carriers. As always, appreciate any feedback regarding these changes...particularly if they don't work as expected.... IL2DCG350b22.zip

Strange. While the starting location is determined for .srd, it should be totally independent of .prd position. I'll review.

Let me review the code and try and discover why it doesn't accept transferring the aircraft on the same day the carrier is spawned/named. Also, are you sure you can't spawn a ship into a .prd route during the campaign???

The class file has a very "delicate" structure and if you don't maintain the exact alignment between columns, you will mess it up. I make no guarantee that DCG will work with BAT (or any other mod). That DCG can work with them is due to modders tweaking and re-posting the DCG data files. At that point, the data files are their responsibility.

From the following: [2026/06/30 06:57:04.363] The replacement plane for the Yak-9U ("None") was not found in the Class.DCG file. I assume the error is with the class.dcg file created by the designer of the campaign to integrate DCG with the BAT mod. You could try yourself to change "None" everywhere in the class DCG file to "none" (because from memory it should not be capitalized - although I may have coded an exception???) But if that doesn't work, you'll need to contact the campaign designer.

And summer has only just started....

The "beep" usually means the DCG install has some issue. Try running DCG and re-checking the auto-generation mode toggle. Also, make sure that you have a Data folder and a Masters folder in your DCG folder (and files in each). I don't think it's very common these days, but some old unzipping options dumped everything into the main folder. Finally, check that the DCG folders and the IL2 folders are not "read only". Hopefully one of those issues will solve it. If not, let me know and I'll try to dig up some other causes.