Lowengrin

If you add a location mid-campaign it will mess up the numbering of your locations (and therefore mess up mission generation).

I don't see how this is possible as I have made no changes to the code related to the Squadron Editor panel in years beyond a minor change to the visibility of the "AI Only" dropdown for coop mode.

As Fhechene has said, you actually have to add a route to the .rds file. It will automatically populate the territory and locations file (however, there's is a good chance it will also mess them up in the process as it's not designed to have edits mid-campaign). So it's best to back the campaign up and then add it to the rds file, see where it appears in the territory and locations files and then manually edit your back up file to slide it in.

50b3. Ouch! Okay, back to the drawing board. As for the trucks, did you happen to know the start locations of the two missions? Is it just a really long road route? (Or an edit in the .rds file between missions?)

Are you using the latest beta when you say sometimes they start too close and crash? There was an issue with an earlier build, but I think/hope I've fixed it with the most recent beta. Truck convoys and tanks shouldn't start deep inside enemy territory. They should only start in friendly and/or contested areas and only if in friendly territory, should they advance to enemy territory (making it contested). A single vehicle may advance into enemy territory (as a scout), but never a column.

So instead of TCapture Contested, you're suggesting putting a new type in the allcampaign and/or grandcampaign file. That might work...

A quickie update that unhides the "AI Only" dropdown on the Squadron Editor Panel when in Coop Mode.

Look in the \IL-2 Sturmovik 1946\NGen\ folder. You'll find the "new" missions there. They aren't really missions at this point, just data files to set them up.

If you are playing "coop" mode (not campaign), you can set DCG to "dogfight" mode and then go to the squadron panel and set all the squadrons you want to "IA Only", and then switch it back to "coop" mode before generating the mission. I don't know how long this has been a bug, because you should be able to switch them in "coop" mode. I will fix this soon....

That's a good idea. I'll start adding some as I tweak the code.

I've used TCapture on the start dates of a couple of my Solomon Island campaigns and it works fine. Perhaps I can create a new command for one that would work for past dates...but the problem with that is that it would over-ride any future capture by the other side's forces. Which would be fine if the ground war was completely controlled through the timetable (and Timetable Off was used).

I keep IL2DCG outside of the IL2 Sturmovik folder, but I guess you can keep it there. Either way, it should be in it's own folder.

The first group of commands in the first post are all those that are valid before the start of the campaign. Neither TCapture nor AddSquad will work. The first of those can be set up in the allcampaign.dcg file and/or grandcampaign.dcg file (depending on whether it's the first campaign being played or a branching one). And the second, you can just add the squadron to the template mission file.

PriorityLandingSite is hidden in the [Solomon4310] section. 19431111 PriorityLandingSite Axis = Numanuma

I've been slowly working through them (but mostly for Pacific campaigns). You can set them yourself on the aircraft class settings panel. Once you make the change, it's permanent for all campaigns using that class.dcg file (which are all the stock ones).

Build 3 is now available. It includes tweaks to missions, particularly CAP over ships. Also has further tweaks to Berlin campaign and airfield limits. Added a new TimeTable Command: PriorityLandingSite Armor/Trucks will always unload from ships at a designated priority landing site (only one can be designated per side at any given time). Edit: Removed attachment.

Time Table Information The following commands will stay activated from the activation date forward (until overridden by another command). TimeTable On/Off ShipsRemainSunk BeachheadResets BugOutRadius SetMaxTroopLevel Transfers On/Off SetMissionTime DeployDistance SetTaskForceSpeed NameColumn AlwaysActive PilotType Radio On/Off SetFuel SetEscort NewPayload BanPayload RoadBlockOn RoadBlockOff PriorityLandingSite* The following commands will active only on the specified date. NewsBrief TCapture SetDate SetTimePassage RemoveColumn ShowMovie AddSquad RemoveSquad NameSquad MoveSquad NewPlane FlightSize SetSkill SetPaint MaxPlanes MinPlanes ActivePlanes AddStatic NewColumn SetTroops SetSupply SetOilSupply AttackRendezvous *New with DCG 3.50 Build 3...

You'll have to put restrictions on all of the German held airfields (or at least the ones between the Soviet lines and Berlin). I'll be back later with the list of timetable date settings. Edit: See new thread on the time table.

I just gave your mission a try in coop mode (although solo). I'm running 4.14, DCG 3.50 beta with no mods and it worked fine. Maybe someone else can chime in who has more experience with the multiplayer server side of IL-2.

I'd have to look at the code to remind me what works on the day and what works after the day.... Meanwhile, I have an idea of how to fix your issue and that's by using the airfieldrestrictions.dcg file. Just restrict USAAF/RAF planes in your campaign from Myedricz Airfield and PLM one's from the English_Airfield.

I'm surprised that this problem is still happening. I'll take another look at it when I can. Transfers only occur on the date so if your Berlin campaign carries over from another campaign (so doesn't have a set start date), it's pretty much impossible to use the time table to transfer them. However, if you are starting the campaign on a set date, just transfer everything on that date.

While it's on the "to do" list, unfortunately, it's a manual, tedious job to do so I keep putting it off. DCG was originally designed when most monitors were 1280 x 720 and 800 x 600.

Ugh! I thought I'd removed all references to the old site. Thanks!

To continue where Fhechene left off, #3, bombers will target based on the richness of the target...unless they're designated dive-bombers and then they're more likely to go after tanks/columns. Also, escort changes are a bit reduced for the French compared to their British allies and the Germans. #4. The success of a rendezvous between bombers and escorts is dependent on a number of factors including the distance between their airfields and the location of the target in relation to those airfields. In addition, the accuracy of the cruise speeds for them in the class.dcg file, and whether the options for air starts and/or delayed start times and the number of flights/squadron will effect the likelihood of a rendezvous happening. #5. Lag is bad at the start as, if I understand correctly, all the objects and skins are loading into virtual memory. The more unique planes and paint schemes in your mission, the worst it will be. #6. DCG (compared to DGEN/NGEN) has a lot more going on in the mission files. This could be why. #7. There can be multiple contested locations (which behave exactly like the one "front" location). The front location is only defined to determine the action radius from. If all your units are bottle-necking at one point, it must be the way the road network is designed. Hope this helps clarify some things.

They appear to work now, thanks!