Lowengrin

Let me know if you have any issues with it.

Check the latest beta.

Latest build adds a "SetSeason" command to the time table file fulfilling a suggestion by Walter to have a way to switch from Summer to Winter map without having to create a whole new campaign. This was originally hard-coded for the vanilla maps, but now I've made it a time table command so it can be over-ridden. More importantly, it can be used with mod maps. So there's a new command that will just swap the summer map over to the winter map (or winter to summer) in a campaign and keep all the data files from the original map. For example: 19420102 SetSeason Winter Net2Winter/load.ini 19420103 SetSeason Summer Net2Summer/load.ini

I'd say you're halfway there if you know how to make a campaign...but then I know how long it takes to make one so... Good luck finding one to tweak.

It's been a long time since I used a dedicated server, but if I remember correctly, SC should just generate the next mission with no user having to log in. I believe you just have to set how long you want each mission to run in advance (and DCG has a setting for that under Edit/Dogfight Server Settings).

Yes, if you select one starting campaign, DCG will link to the next "logical" one based on which side wins. So if the Germans capture all the Lvov map, your campaign will advance to Moscow. And, you should be able to fly a Bf110 from the start (either by selecting it at the outset, or running DCG and switching it in for your player squadron).

Unfortunately there is no easy way to incorporate the numerous maps from BAT into DCG. Each actually requires a number of data files to accompany it. There have been some campaigns based on some of these maps, but you have to search around to find them.

Sorry I took so long to notice your post. Yes, that makes sense. The stock winter maps are hard-coded, but (of course) the mod maps are not. Let me look at fixing that issue.

Sorry I didn't see this until now, but could you post your log.dcg file as well. But before you post it, in the IL2 conf.ini, make sure the following is set to "0": eventlogkeep=0 If it isn't, set it to "0" and give it a test. What might be happening is your event log is appending to itself and getting so big that IL2 truncates it in the middle of a mission. And that messes with DCG's ability to parse it. By setting it to "0", it will only keep the most recent mission.

Sorry, but adding new nationalities is something I'm not interested in doing at this time. It'd be time consuming and mod dependent. And I said long ago that I wouldn't go down the rabbit hole of trying to support every mod for IL-2. (If I were to do it, I'd get rid of hard coding nationalities altogether. But that's an even bigger job and I don't have the time to even consider what that would require right now.) In the meantime, I'm pretty sure you could swap files in for most (all?) of these data directly into the IL-2 folders. For DCG, just the messages.dcg has an army/nationality section that would need updating.

As long as you use the stock nation codes from the game, for example, "DE" for Germany and "RU" for Russia, your WW1 "mod" should work in DCG. Unfortunately, there's no easy way to add any new codes into DCG - I hard coded them from the very beginning (adding new ones with each new release of the game). So you'll have to use ones like Finland and Slovenia (and other nations not involved in WW2) for some of the others.

Try re-adding the J6K1 data to clean files. Double check that any blank characters between the columns are spaces and not tabs or other invisible characters.

I'm not sure what to suggest now. Maybe a reinstall of DCG?

It looks like the last record has a blank plane. I've removed the record and uploaded. payloads.dcg

Try deleting your other uploads first.

Can you just upload the payload file?

Just thought of one minor thing, DCG doesn't like a blank record in its data. Make sure that you haven't left an empty record at the bottom of the file. Delete everything up to the last character of the last record. Also, did you add the J6K1 to the payloads.dcg file? I don't see that file in this thread.

I don't see anything wrong with the class.dcg file. It may be one of the others causing the "valid...error" file. The access violation might be that one of your data files has too many records.

Make sure the read-only attribute is also removed from the IL-2 game folder and sub-folders. Unfortunately the exploding on spawning is all too common with the BAT mod (and some other mods). I don't know why that is.

Looks like you have a line break in your class entry for the J6K1. Load it up in Notepad and set the word wrap off. You'll see the problem.

If you want to change the experience of any pilot, just double click on their name and you can give them more (or less) missions and/or kills.

Under options, you can check "Squadron Management" and then in the Squadron Editor Panel you can assign who flies with who (but only in your squadron), by swapping the position of one pilot with the other. Just click on the one pilot you want to swap with the other. Each set of four pilots is a flight: flight leader, wingman, leader, wingman. You can also change the skill of the squadron with the "SKILL" drop down on the Squadron Editor Panel. The value chosen is the base skill of the squadron, but individual pilots with more experience will be higher and individuals with little or no experience will be one step lower. (It's not random.)

I ran a few missions for Okinawa in vanilla and had no issues with planes exploding at the start or beginning airborne with the engine off. Is it possible that the VP Modpack modifies either the Okinawa map or makes changes to the game's physics? I checked out the VP 1.2 announcement but it only lists the changes made from the previous version and not all the changes that VP has in it, so I can't pinpoint what it might be. https://www.sas1946.com/main/index.php?topic=69631.0

I finally sat down and looked at the two mission files, not only eyeballing them, viewing them in the FMB and running them in "vanilla". Neither had any issues that I could see. So I'd have to say it's something to do with Wxtech.

I'm not 100% certain but I think this is an issue caused by mods. But I haven't tested the Okinawa campaign in years so it might be a some change to the base game has impacted the spawn points. I'll test and get back to you.