Lowengrin

Okay, it took me a few minutes but now I remember how SetPaint works. In the timetable file, in front of the name of the file, you have to specify whether the new skin has markings on it or whether you want the game to apply the markings by inserting a "1" or "0" before the name of the file. So the command should look something like this: 19400127 SetPaint 4IAP0 = 0I-15Bis_Lt_Abramov_Blank.bmp

Let's make it 1,001!

Yes, the order makes a difference here. The unit must be added before any other changes are made to it. I'm not sure why it's ignoring the paint command and I'll have to do some debugging to find out.

Without debugging, I suspect it's the space in the name of the skin. Try renaming the skin's bmp and the setpaint command so the space between Lt and Abramov is an underscore. I-15Bis_Lt Abramov_Blank.bmp

Hi Torpede_Aeri, It looks like the process you are using is for an older version of IL-2. Try: Full Off-Line Career Mode. Using this mode replaces the in-game generator (DGen) with DCG. Careers can then be created directly from the game set up screens and DCG never needs to be run except to edit the campaign files. 1. Run DCG. 2. Select the off-line Career Auto-Generation mode from the DCG Menu. 3. Select "Replace Career Generator (DGen)" from the DCG Menu "Mode" and click "Yes". Close DCG. 4. Run IL-2 "Forgotten Battles". 5. Select any of the stock or DCG campaigns available in IL2 "Forgotten Battles" or any campaign in "Pacific Fighters" that is designated "*" and "(DCG)". DCG will generate and run a campaign based on your selection criteria. 6. Play the campaign. Note: a copy of DGen.exe will be made called DGEN_bak.exe. It is strongly recommended that your restore your DGen.exe file before installing any upgrades of IL2 "Forgotten Battles". You can do this by clicking "Replace DGen" when it's checked or delete the file DGen.exe and rename DGen_bak.exe to DGen.exe.

Weird, I thought I did.

It should work UNLESS the date that your campaign advances to Burma 1944 is before 19440522 and that's not an error in your timetable... [Burma_1942] 19421221 NewPlane 28Squadron0 HurricaneMkIIb 19421221 SetPaint 28Squadron0 = Hurricane MkIIB BR125, 3 PRU Agartala, India, Nov 1942.bmp [Burma_1942] Shouldn't that second [Burma_1942] be [Burma_1944]...?

Increased the number of supported plane types to 5000 and columns to 2000 (for those using mods with more than 2000 planes types and/or more than 1000 columns/tank types). (Attachment removed.)

Yeah, the SetPaint command is campaign specific and DCG "forgets" about it when it switches campaigns. I'd just drop the SetPaint command into the next subcampaign.

Adding the modded map requires referencing that map in the various DCG files. The old document linked to above gives the basic info.

You'll have to fiddle with the waypoints (adding or removing some to the xxxxx.rds file) to get the artillery where you want them.

Over 2000...yes, that could be an issue. I'll check and update if it is.

"None" should severely restrict GAttack missions, but might not completely prevent them....

DCG will check if the eventlog has been processed when opening one of those panels...unfortunately, it's not the most efficient bit of code....

Do you have the "Stats Reset On Death" unchecked in the options list? (I assume so.) It's been so long since I tested with it unchecked, some funny bug may have been introduced at some point without my noticing. I'll have a look. Meanwhile, as Fhechene said, if you have it happen again, post your log for that mission.

I'll have a look at both cases. Hopefully the answer is obvious and the tweak to the code is, well, just a tweak....

Hi. I haven't touched the promotion code in years, so I'm not sure what's going on there. As for the paint, the date may have an impact. I can't remember offhand if the setpaint command works only on the date in question or if it's a >= to that date. So if the event happens before you switch campaigns, that might be why it doesn't trigger.

The only other tweak I've made is on upgrade/downgrades of aircraft. However, the static object spawning is all related so it's possible that my tweaks to removing statics is impacting the spawning of front line objects.... Ugh. Defending units defend back from the "front" location. When I wrote the code for how routes would work, way back near the beginning of this journey, I did it quick and dirty and have never ever bothered to refine it. The whole DCG thing started as a proof of concept to convince Maddox Games that they could write their own damn dynamic campaign. BTW, you can increase both attacker's and defender's distance from the using the "Contact Distance Level" on the Ground War Editor tab.

Okay, let's try this again. Tweaked the remove stationary code again....

Thanks for being so thorough. I'll have to do some more tweaking...who know code written more than 10 years ago would come back to bite me when adding one little "remove" addition.

Silly me, forgot to remove some debug messaging. Here's beta lucky 13.

Can you be more detailed in how it broke your campaign? Frontline units should appear anywhere both sides have "troops" and the "side" is "contested" ("0" vs "1" for Allies, "2" for Axis).

Here's the latest beta, which should fix the issue with removing statics on the set date. Edit: Please upgrade to beta 13 (or suffer a freeze if the Remove Static command is activated).

I agree this period is a good one for the Pacific to focus on. But the issue with Guadalcanal is that the Japanese were flying bombers from Rabaul which is a distance of about 650 miles. No one would want to fly that. (Though I suppose they could just start airborne at an appropriate distance.) At the Battle of Coral Sea (a better battle than Midway to recreate, IMHO), the distances between the Japanese and American carriers was about 250 miles. Which isn't too bad to fly in real time.