Lowengrin

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.

Yes. But no promises that it works (as it was intended for coop but maybe, just maybe, I made it work for single player).

It's not possible to transfer the player between squadrons in the middle of a campaign. Yes, you can rename your squadron, but it retains all the aircraft associated to it's old name. I did set up a command for coop missions to allow players to fly in different squadrons, but I don't think it works for single player mode. But you could try it.... 19420102 PilotType AI II_JG540 19420102 PilotType Human II_JG770

No, the MoveSquad command should reference the Chief tag. For example: 19420824 NewColumn 7_Chief Ships.IJNCVGeneric 2 @South_Pacific_Ocean1 $IJN Ryujo ~L 19420824 NewColumn 8_Chief Ships.IJNKageroDD41 2 @South_Pacific_Ocean1 $IJN Akigumo ~L 19420824 NewColumn 9_Chief Ships.IJNKageroDD41 2 @South_Pacific_Ocean1 $IJN Maikaze ~L 19420824 AddSquad IJN_C_Ryujo_FS0 19420824 SetSkill IJN_C_Ryujo_FS0 = 1 19420824 NewPlane IJN_C_Ryujo_FS0 A6M2_21 19420824 MaxPlanes IJN_C_Ryujo_FS0 = 16 19420824 FlightSize IJN_C_Ryujo_FS0 = 3 19420824 MoveSquad IJN_C_Ryujo_FS0 7_Chief

I can't say for sure what the problem with the BAT files, but it must have to do with one of the planes or other objects that are in the campaign you are using. Sorry for being vague, but I do not make mods or even use them in IL-2.

Sorry for the late answer, but I think whatever DCG files that you're using with BAT 4.3 have errors. For example: [2026/04/30 21:58:03.426] The replacement plane for the Do_22K ("None") was not found in the Class.DCG file. "None" should be "none" (no caps) in the class.dcg file.

Good point. I will give some thought to how to make the set escort command be more flexible.

It could be the right way.... I could force a "none" to make it impossible for the fighters to do an escort mission. (But in a carrier battle, it's pretty much CAP or escort so I'm not sure how valuable that would be to your campaign.)

Changing the delay between changing escorts shouldn't have any effect. The changes should be immediate. I do know the escort command is not the most reliable. Other circumstances can cause the escort to ignore the command - the most obvious one being the escorted flight isn't active. But other events (like anticipating an attack) can change the escort into a CAP (for example).

Before I do, you could try setting the command to "none". For example: 19420101 SetEscort IV_StG20 = none

(I will look at creating a new command.)

There probably is no way to interrupt/end it....

Hi. Sorry for my slow reply but I was on vacation and away from any computer. It looks like your .ini file is correct and you're not keeping logs from one mission to the next. The issue may be with the BAT files created for DCG. You might want to contact ProblemChild on the SAS forum and ask them to review their data related to the campaign you're wanting to fly.

It appears the mission was generated (according to the dcgerror.txt) bu the game crashes. Not sure why that is and can't tell from these files. If your log.lst is too big to load, that might be the issue. There's a setting so it deletes at the start of a new mission, I would turn it on. I think it's eventlog=1 or something like that found in the il2 ini file.