Lowengrin

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.

The airfields are included in the Crimea41.rds file. Instructions can be found inside this (old) document by Lonestar.

Generally when this happens (but not always), it means that one of the folders that DCG accesses is read only. Make sure that your DCG folder and all subfolders and files in them are NOT read-only. Also, make sure the main IL-2 folder, subfolders and the files there are not read-only as DCG must write to them (and it makes a back up copy of DGEN and NGEN as it over-writes these).

The download still works, but only for build #21, which is five posts up.

That's a good question. I don't remember, but I'm guessing no. You could simulate it by skipping a few days, which you could do while on the debrief screen. While on that screen, tab out of the game and run DCG, go to the General Campaign Settings and change the "Time Passage" to "Fast". Tab back into the game and generate the next mission. It'll skip a few days. Just remember before the next mission generates to set the "Time Passage" back to "Normal". (Or whatever setting you like to use.)

There is an option to not have them reset on a KIA or MIA.

That's strange. I'm fairly certain your timetable as shown should work. And if it doesn't, I must have introduced a bug. I'll have a look and get back to you in a day or two.

I can certainly add a timetable command to transfer ships from a srd to a prd. Should be a simple addition (famous last words). I'm not sure I follow your second request. Transferring from a carrier on a srd to a land base or to another carrier in that srd? Or a carrier in a prd? Transfers are limited by the number of squadrons already based on an airfield/carrier as well as the distance (restricted to being within the range of the planes and the "action radius").