Special Aircraft Service
The SAS Factory - Tech Help, Ancient Mods etc. => Community Universal Patch (C.U.P.) => The Keepsake: Old Mod Packs, Game Versions and Guest Mods => C.U.P. Missions and Campaigns => Topic started by: sniperton on May 11, 2016, 05:16:01 PM
-
Il2 Data Integrity Tool for DCG (by sniperton)
v0.22 (first release as public beta)
v0.26 (hotfix)
Changelog v0.26
--- maximum range is now 1000km (was 600 before);
--- fixed a bug causing DIT to crash when the user tries to set a value while no plane is selected;
--- fixed a bug causing a pink plane issue (new weapons files for 4.12, 4.13.1 and HSFX; a hotfix for WAW#20 will follow soon)
Changelog v0.25
--- as from 3.49beta4, DCG's class file format changed to enable flight altitudes greater than 9999m; DIT now supports both the old and the new format (you don't have to bother about the input format);
--- an option 'Export Class.Dcg in new format' was added; users of DCG 3.49beta4 and beyond are requested to check this option (the option is saved in DIT's config file so that it has to be set only once);
--- if the option is not checked, Class.Dcg will be exported according to the old format and flight altitudes greater than 9950m will be automatically reset to that value on export;
--- default (X) and none (Y) loadouts cannot be redefined (and messed up) by the user any more;
--- VP MOD is fully supported now (see below);
Changelog v0.24
--- initial auto-assigment of loadouts is made specific for each plane type; if the type is not set, a generic scheme is used;
generic: A(X), B(X), B(X), T(B,Y), A(X), D(Y) (any available loadout)
fighter: A(X), B(X), X, T(B,Y), A(X), D(Y) (any except level bombing)
bomber: X, B(X), B(X), T(B,Y), Y, Y (any except aerial attack)
transport: X, X, B(X), Y, Y, Y (only paradrop/level bombing)
attack: X, B(X), X, T(B,Y), Y, Y (only ground and see attack)
recon: X, X, X, Y, Y, Y (nothing)
float: X, X, X, T(B,Y), Y, Y (only sea attack)
dive: X, B(X), X, B(Y), Y, Y (only ground and see attack)
--- option 'disregard payloads.dcg' added to the Config tab: by checking this, all loadouts will be auto-assigned, even those which normally would be imported from the DCG payload file (this can be handy when you have a manually messed-up DCG database and want to make sure it complies to DCG’s conventions; otherwise stay away from this option);
--- data import made more fool-proof: inappropriate uses of the 'none' and 'default' loadouts are automatically corrected according to DCG's conventions;
--- a bug with ’Quick assign’ fixed (unchecking the option had no effect before);
--- aircraft lists are now sorted alphabetically;
Changelog v0.23
--- autosave in every minute to DIT's working directory (where you installed it);
--- on exit you're asked if your auto-saved session files should overwrite your permanent DCG export files (which are to be loaded next time);
--- when a country is selected, the aircraft now automatically switches to axis/allied (changing sides or adding extra countries is unfortunately unsupported by DCG);
--- when a plane type is selected (and the 'Quick assign' checkbox is checked), proper loadouts are automatically assigned to the aircraft;
--- now it suffices to only select a country and a plane type for an aircraft to be 'verified' for DCG;
--- after 'verifying' a plane, the cursor jumps to the next item in the list instead of disappearing;
--- a horizontal slider is added to the loadout section of the aircraft editor so that long loadouts are displayed correctly;
DIT verifies DCG plane and payload data on internal game data and enables you to edit the rest in a half-automated way (auto-assigment of available loadouts, etc). The basic trick of DIT is that it uses plane designations and loadout assignments imported from the game.
You don't need DIT if you don't use DCG. Furthermore, DIT requires an accessible air.ini and weapons.properties, so it's best use is for modded games. Nevertheless, the base files of stock 4.12.1 and 4.13.1 are also included in this package, so that you can test DCG's vanilla database on them.
For CUP/WAW, it's strongly recommended to enable DCG compatibility mod for WAW#20 via JSGME (https://www.sas1946.com/main/index.php/topic,51330.0.html (https://www.sas1946.com/main/index.php/topic,51330.0.html)).
For VP MOD, it's strongly recommended to install patch #3 and to enable VPMOD_DCG_compatibility_mod_v1.0 via JSGME (https://www.sas1946.com/main/index.php/topic,50919.msg561040.html#msg561040 (https://www.sas1946.com/main/index.php/topic,50919.msg561040.html#msg561040)); please apply this hotfix (overwrite JSGME folder, then re-enable): https://www.mediafire.com/download/vygj8c8v4nlcw7x/%23VPMod_DCG_compatibility_mod_v1.0b.zip (https://www.mediafire.com/download/vygj8c8v4nlcw7x/%23VPMod_DCG_compatibility_mod_v1.0b.zip)
Download:
https://www.mediafire.com/download/jt22g12vy9ufgkz/il2_dit_024.zip (https://www.mediafire.com/download/jt22g12vy9ufgkz/il2_dit_024.zip) (previous version)
https://www.mediafire.com/download/lf3ckrijhmnohap/il2_dit_026.zip(update)
How to use:
1. Unpack to a folder of your choice and run.
2. Specify the location of a few files. For your comfort, relevant files are included for stock 4.12.1, 4.13.1, and HSFX.
3. Hit the 'Work from scratch' button.
4. Go to the 'Aircraft editor' tab.
5. To the left you find planes which are not available in your install. The reason is given below as 'Not in Air.ini' or 'Disabled in Air.ini'.
6. In the middle column there are 'verified' planes that have all the needed info and can be used in DCG without further editing.
6. To the right there are planes that you have to edit to make them usable.
7. Missing info is red. It turns to its normal colour as soon as you adjust the data properly.
8. You can set and adjust data by clicking, typing, or simply hovering the mouse over the control and scrolling up and down.
9. To assign a loadout to a plane, the loadout has to be prefixed either as 'Bomb', 'Torpedo', 'Air attack', or 'Droptank'. Select a loadout from the list and press the appropriate key (b, t, a, or d).
10. Once the loadout is prefixed, you can drag it to one of the loadout slots. There are restrictions, though. You can't drag a torpedo to the ground attack slot, for example.
11. Once the data sheet of the plane is properly filled, a green led to the bottom right lights up: now you can 'verify' the edited plane for DCG by pushing the above button with the check mark.
12. Only 'verified' planes and prefixed loadouts are exported on exit. You find your generated class.dcg, allpayloads.dcg and payloads.dcg files in the 'DIT' folder of your DCG directory.
13. The next time you run Il2_DIT, you can continue editing by choosing the 'Reload previous session' startup option.
With special thanks to Paul Lowengrin for his excellent campaign generator (http://forum.jg1.org/forum/8-lowengrins-dynamic-campaign-generators-dcg-for-il-2-cfs2/ (http://forum.jg1.org/forum/8-lowengrins-dynamic-campaign-generators-dcg-for-il-2-cfs2/))
Further thanks to JG7_X_Man for his interest, feedback, and ideas.
Package content:
- il2_dit.exe
- readme_dit.txt
- folder [basefiles_4.12]
- folder [basefiles_4.131]
- folder [basefiles_4.12+HSFX]
Known problems (to-do list):
- Zero error checking;
- Application not properly scalable and must be run in a min 820 vertical resolution;
- Aircraft editor: upgrade and downgrade types cannot be set or changed;
- Planeset editor not implemented (will extend the functionality of the aircraft editor by enabling you search, sort, and select verified planes and by specifying upgrade and downgrade types);
- Various small glitches.
(http://s32.postimg.cc/49wgzkv5x/interface.jpg) (http://postimg.cc/image/3kdon7um9/full/)
-
Wonderful. I know what I am looking at, just trying to wrap my head around it. Amazing.
Cheers
Gubi
-
JG7...I've been working a long time, manually editing these files...never completed, just a bit at a time. A quick look at the corresponding "data" files, I believe will offer the answer you are looking for, to do it manually. There will need to be some manual work, yet, but this is a Godsend.
Thanx Snipes
Gubi
-
So...as an example: My DBW 1938, which is 1919-1938...Unavailable=996, understood and expected; Verified=126, yay; Available=142, wonderful. Now to get to work.
Again, Cheers
Gubi
-
Excited and energized for a few hours...I think range, for me...should be 0.5 times published range, then minus...anywhere from 0.20 to 0.33, I think, for forming and farting around, to represent true range in DCG.
-
Outstanding sniperton! Great work - waiting on 'DCG compatibility mod for WAW#20! :)
-
Doing ranges now...my option: range (say1000)km x.5, x.8=true range...
Cheers
-
If you leave the range at zero, it will be exported as "default", and "default" range is 300 km in DCG (if Paul remembers correctly) :)
If a value is red in DIT it means you have to adjust it for DCG to use. If a value is black (as range is) it means that you may adjust it, but it's not required for DCG to work.
If you work from scratch, the second row of values (range, altitude, speeds) comes with pre-set "default" values and will be exported as such even if you don't touch them.
For DCG to work, only the first row of values has to be set in any case (side, country, type, flyable/AI, skin folder, if none was found)
-
Fantastic! This is just great! Thanks a lot!
-
sniperton - is there a way to assign Empty and Default weapons X and Y :) Loving this! Also - the weapon section in the aircraft editor needs a slider to see the super long weapon entries.
Issues:
The Bf 109 G2 CRP, 1943 - R1/U2: weapon string looks hosed.
The Bf109V48, 1943 R6/U1: weapon string hosed
-
the weapon section in the aircraft editor needs a slider to see the super long weapon entries.
Added to to-do list
The Bf 109 G2 CRP, 1943 - R1/U2: weapon string looks hosed.
The Bf109V48, 1943 R6/U1: weapon string hosed
They are taken over from the quite messy original weapons.properties. I noticed them, but I had a strict working principle: not to do anything by hand. :P ;)
-
They are taken over from the quite messy original weapons.properties. I noticed them, but I had a strict working principle: not to do anything by hand. :P ;)
I hear you brother!
-
sniperton - is there away to add the ability to "save" the current data I am working with as is (i.e. ask to copy and paste the current "DIT" folder before I close). So that when I make a mistake and "build from scratch" the application does not overwrite my previous allpayloads, class and payloads files.
-
This is why it's beta. What's about this:
- autosave at regular intervals to temp files in working directory (not DCG\DIT);
- final autosave on exit to temp files in working directory (not DCG\DIT);
[this way the full session is automatically saved]
+ user input to finalize temp files as DCG\DIT
[this way you can choose whether the changes you made are meant seriously; if you respond with "no", you still have the last session (as temp files), but your working files remain intact]
Workaround till then: before you exit, tab out and copy your exported DCG files to another location.
-
Sounds good! :)
-
Hey sniperton - When Germany is selected, the aircraft doesn't automatically switch to Axis. It works with Japan and Italy - is there a way to correct this?
-
It works with Japan and Italy - is there a way to correct this?
I wonder how its does, as I haven't hardcoded nations as axis or allies. 8)
Sure it could be done, but you would lose the option to define Italy as allied or France as axis. I have to ask Lo how exactly DCG is handling countries and what are the chances to have e.g. a Forgotten Countries support. Anyway, added to "to-do" list.
-
It works with Japan and Italy - is there a way to correct this?
I wonder how its does, as I haven't hardcoded nations as axis or allies. 8)
Sure it could be done, but you would lose the option to define Italy as allied or France as axis. I have to ask Lo how exactly DCG is handling countries and what are the chances to have e.g. a Forgotten Countries support. Anyway, added to "to-do" list.
This isn't that important - in the grand scheme of things - this can be way down on your "nice to have" list :)
-
* updated *
-
Loving it!
-
Question sniperton - Since Lo said that the 1st 3 weapon slots cannot be (Y) can the "Quick Assign" check for that every time you open it and automatically insert A,B or (X) were appropriate (...at random even)? A way to protect us (...OK me) from ourselves? Or is that asking too much since this is a labor of love an all :)
-
DIT is fool-proof to 50%. It's also made for me ;)
1) You can't do anything wrong when you assign loadouts manually (drag and drop);
2) You can't do anything wrong when you assign loadouts using the new 'quick assign' function;
3) You can't do anything wrong when DIT auto-assigns loadouts on startup.
They are all made according to Lo's rules, that is, working from scratch is safe. (Or at least I believe so; notify me if you find a bug.)
DIT is not fool-proof in two respects:
1) It cannot prevent you from prefixing a torpedo with "B" or a droptank with "A";
2) It doesn't check or override loadout assignment info imported from a former DCG database. It works just the other way round: first it auto-assigns loadouts based on game data and the prefixes taken from allpayloads, and then overrides them with slot assigments if available (taken from payloads).
When doing so, it does check whether the given loadout is really available in the game database, but it doesn't check whether it is also available for that particular plane, or whether it is really a valid loadout option for that slot (according to Paul's rules). It was not supposed that the user works with a manually messed up DCG database. ;D
What I can do fast and with relative ease is to implement a startup option to the effect that former slot assigments (payloads data with all the good and wrong editings) are disregarded and everything is auto-assigned according to plane type (as 'quick assign' does); for planes whose type is not set the general scheme would be used: A(X), B(X), B(X), T(B,Y), A(Y), D(Y) (as is done now on startup).
Another option is that on startup I check slots 1 to 3 for 'none' and auto-replace them with 'default', then I check slot 6 for 'default' and auto-replace it with 'none'. Sorting out fatally wrong assigments such as B,T,A,D,B,T would be too much a work for now.
-
Bingo! I like your alternate option of "...checking slots 1 to 3 for 'none' and auto-replace them with 'default'" - Perfect!
-
* updated *
-
Hey sniperton - here is something I noticed in the last version:
F2G Grumman F2G Super Corsair, 1945 un 1 4 0 194501 194512 none F2G none 485.00 kph 600 km 485.00 kph
BF_109B1 Mdtt Bf109B1, 1936 de 2 1 1 193601 193612 BF_109B2 Bf-109B-1 none 5000 Meters 340.00 kph 600 km 340.00 kph
The Bf 109 B1 is an original entry in the class.dcg. The line above it for the F2G is an aircraft I added using DIT v0.24.
Notice that the data lines are in sync until the Service Ceiling - looks like it's not writing to the class.dcg file.
The way I edit DIT is to use the rotary knob and the click the green (check) to save the aircraft. I will rebuild and see if it still occurs. If it does, I will let you know :) No big deal!
confirmed - I went to v2.3 - same thing. I will test your next update, as long as it's not during F1 Grand Prix Monaco Go Fast time! :-|
It seems that the "Default" range entry works - but when you change it to something else - it doesn't write. I wonder if it only works for entries under 9000M.
BINGO! seems it's a # of character - max is ####.
-
You're right, it's a limitation of DCG. In the next release I'll max the value you can enter at 9950.
-
Ahh! I just learned something :)
-
sniperton - another tweak I would recommend is for the user not to have the ability to change "Empty" and "Default" from (Y) and (X). If there is a reason to change them to A, B, T or D - we should have the option to change them back. :)
-
* updated *
-
Outstanding! :)
-
Once I generated those 3 files. Do I need move them into DCG\data\ folder and overwrite the older files already there?
-
A. If you are familiar with how to create a 3rd party campaign, you can use those 3 files in a 3rd campaign folder.
B. If not, you can simply overwrite the stock files in DCG's 'data' directory. (Not a bad idea to copy the original files to a safe place previously).
-
Gotcha. Thanks, Sniperton. Oh, another quick question. For some aircraft, there are multiple loadout configurations for a single mission type. For example, for ground attack, P-51D-30NA has 2X250+6X4.5HAVR, 2X500+6X4.5HAVR and 10x4.5", all these options. But the tool only allows one setup for ground attack. Just wonder if I can get to choose the loadouts ingame or it's set stone you can't change it anymore.
-
DIT is only a tool for DCG, and DCG only allows you to select one loadout for each mission type slot.
However, you can change the chosen loadout mid-campaign:
A) via DCG's interface;
B) via a timetable command
19410810 NewPayload JU_88A4 GAWeapon = 2xSC1000
-
Oh, I see. Thanks a lot.
-
Pandacat this is why DCG, PAL Mission Pro + DIT+ WAW Weapons Mod is so powerful.
snipertion's WAW Mod - fixes all the weapons in CUP, PAL Mission Pro allows you to change weapons on every aircraft prior to mission launch, thanks to DIT - DCG will recognize the weapon and the logfile will not blowup :).
-
Pandacat this is why DCG, PAL Mission Pro + DIT+ WAW Weapons Mod is so powerful.
snipertion's WAW Mod - fixes all the weapons in CUP, PAL Mission Pro allows you to change weapons on every aircraft prior to mission launch, thanks to DIT - DCG will recognize the weapon and the logfile will not blowup :).
I don't use Mission Pro, so I don't know what happens when you change a loadout ingame to one unrecognized by DCG; possibly nothing, as all this happens outside DCG, but the next mission will be generated with the previous loadout, won't it?
-
Two questions Gentlemen: In DCG, is "range", absolute range or is it "radius"? #2: Once range is set, is it considered with or without droptanks, if they are available. Do drop tanks, increase the set "range"?
Cheers and wonderful tool.
Gubi
-
A second mini discussion: I am setting "altitude" at 0.5xthe published ceiling. I believe DCG will operate the aircraft "up to" the "altitude", or does it always have them operating at that altitude? For IL-2 purposes, I'm wondering if I should set "altitude" at 0.33-0.40xpublished ceiling. Any thoughts?
Cheers
Gubi
-
Range is, I think, radius in DCG (without droptanks). Default is 300 kms. Droptanks definitely increase range, but only Paul knows how much. Honestly, these are questions you should put Lowengrin; I've never seen one single line of code of DCG.
-
Loving your tool. The scientist in me, has me, researching each and every aircraft, for their "specific" capabilities. I'm a nut.
That notwithstanding, I have assumed range to be "radius" and, for now, am using 50% of ceiling, and assume the aircraft will operate "up to" that altitude...seeing range maxed at 600km...it's good enough for IL-2, but I'll have to proof my assumption for altitude. Unless, I have a published "cruising" speed, I am using 0.8xmax speed, for multiplace a/c and 0.85xmax speed for single seaters. "Ingress" speed, I am assuming to be 0.95xmax speed.
Again, Bravo, for such a tool.
Cheers
Gubi
-
No, default radius is 300 km only if you don't enter any value (or you leave it at zero); if you enter 30, it will be 30; if you enter 600, it will be 600. DCG doesn't know about actual aircraft ranges, actual mission range depends on the value you set. It is used to set effective range: planes won't fly beyond that distance, as simple as that.
As to droptanks, ask JG7_X_Man, he has fiddled quite a lot with long range missions with droptanks.
As to altitudes, I'm pretty sure DCG will use the value you enter as a flight altitide for that plane. So if you set 12 000, planes will climb to 12 000 (if they can), and will be flying there until their misson is finished.
-
Very good, and understood. I am setting ranges (radii), individually. For playability then, I think I will set " altitude to 0.33xPublished ceiling. My experience with the clowns, indicates that most missions, by time alone, will not allow the capability to climb above, say, 3-4000meters, and engage. I will fiddle with altitude.
Again, thanx and cheers
Gubi
-
Pandacat this is why DCG, PAL Mission Pro + DIT+ WAW Weapons Mod is so powerful.
snipertion's WAW Mod - fixes all the weapons in CUP, PAL Mission Pro allows you to change weapons on every aircraft prior to mission launch, thanks to DIT - DCG will recognize the weapon and the logfile will not blowup :).
I don't use Mission Pro, so I don't know what happens when you change a loadout ingame to one unrecognized by DCG; possibly nothing, as all this happens outside DCG, but the next mission will be generated with the previous loadout, won't it?
Yes. The in game change is a 1 time thing.
-
For playability then, I think I will set " altitude to 0.33xPublished ceiling.
Just to make clear: ceiling is the maximum flight altitude possible for a given plane, while transit altitude is the typical operating altitude for a given plane in the given scenario. Something like top speed and cruise speed. Sturmoviks could climb well above 5000 but were mainly used below 2000.
-
No, default radius is 300 km only if you don't enter any value (or you leave it at zero); if you enter 30, it will be 30; if you enter 600, it will be 600. DCG doesn't know about actual aircraft ranges, actual mission range depends on the value you set. It is used to set effective range: planes won't fly beyond that distance, as simple as that.
As to droptanks, ask JG7_X_Man, he has fiddled quite a lot with long range missions with droptanks.
As to altitudes, I'm pretty sure DCG will use the value you enter as a flight altitide for that plane. So if you set 12 000, planes will climb to 12 000 (if they can), and will be flying there until their misson is finished.
Gubi - When DCG generates a level bombing mission for a unit, it looks for a fighter unit to escort the bombers (usually a fighter unit based closest to the bomber's base). If the fighter's range is less than what is required to complete the mission, DCG checks to see if there is an entry in the Long Range (Fighter) Payload in the aircraft Information - if there is one, that is the loadout DCG will use generate the mission. Note: if there isn't a fighter unit that meets this criteria close to the bomber's airfield - the bomber unit will be flying the mission without escort.
DCG will not calculate the range of the mission and determine which loadout in the Long Range (Fighter) Payload class to choose. For that functionality, DCG wouldn't be free. :)
Sniperton - In the Range drop down in the Aircraft Information module in DCG goes from 50KM - 1000KM, your tool maxes out at 600KM - or did I miss something?
-
Gentlemen, thanks for the interest. Yes, I am making assumptions for specific types and their operating altitude. I'm just concerned, primarily for the "level bombers", to not have them operate too high. But, "too low", sucks too. On the SAS server, we have a couple of "historically, realistic" missions with enemy bombers approaching at 6000m...you should hear the groans, from the Clowns. I'm not quite convinced IL=2 FMs handle altitude as well as they might. I'm probably wrong, but "time", becomes such a factor then. Yes, 600km is the max range allowed in the tool, and as I mentioned, I think that's probably, pretty good, as much more than that and we then have the same issue as too much altitude. Just my two cents.
Cheers everyone
Gubi
-
Gubi - Not sure what bombers you have in your mission, but B-17s and B-24 operated at 7600M (25,000 ft). Question though - who are the Clowns? :)
-
Yeah, I know about the altitude. Real high. The Clowns are here: https://www.sas1946.com/main/index.php/topic,41394.0.html
Cheers
Gubi
-
Funny! The reason I took my flying off line.
-
Come join with us on Sundays. We are offliners too.
Cheers
Gubi
-
Sniperton - In the Range drop down in the Aircraft Information module in DCG goes from 50KM - 1000KM, your tool maxes out at 600KM - or did I miss something?
My mistake, will be corrected soon (or later) ;)
-
LOL :D
-
Actually, the major reason is that I picked up ransomware from my thinking HyperLobby.
-
I don't join through hyperlobby.
Cheers
Gubi
-
I must say again, this is a wonderful tool Sniperton. What I will do with the results, who knows? But, a really good job.
Cheers
Gubi
-
This is only 10% of the whole problem. The problem is that some 75% of the maps are not supported by DCG. I'm considering expanding DIT towards map editing. Won't be a milk run, though.
-
Yep. Maps. Years ago, I was working with the "COOP Generator" and added a bunch of maps to it. It is a "real", pain. Truely a labor of love. I still have the files, which include locations and airbase coordinates, if they might be of assistance.
Cheers
Gubi
-
The problem is that some 75% of the maps are not supported by DCG. I'm considering expanding DIT towards map editing. Won't be a milk run, though.
I guess you would like to run your script against single object name entries of an extracted actors.static?
As a map maker, currently creating a new map, I have at the back of my mind that I want to have support for DCG and DGEN.
Seeing that I already committed to have roads/railroads all done manually, the labour of love of creating their entries for DCG/DGEN will just be another (masochist) effort ...
I really think it should (ideally) be up to the map maker to create the files for DCG/DGEN.
Same thing as creating QMB missions, to get people interested in your work, wouldn't it be nice if your new map was DCG ready from the get go?
Picking up airfields locations via an extracted actors.static using a script does not seem too difficult.
Same with text entries for city names, when creating the map, place it dead center on the town/village and then extract from actors.static.
I will have to assess this for (manually done) roads, but I can visualize having a custom actors static with just the main road/rail you want to extract for DCG/DGEN and processing the coordinates of the objects constituting the road/railway.
-
Sounds like a plan for future maps, but I'm a bit sceptical about existing ones. I've seen several maps where the road network is not continuous or there are obstacles that prevent ground units from moving as designed. It would be great if the work in the FMB could be spared, but at the moment I don't really see how it could be done without maps made with DCG in mind. Sorry, now I have to leave...
-
As a DCG user one might have two major problems. One is that you have to create maps with road networks and units, which is a lot of work in the FMB. Second, to make such a 'labour of love' usable in DCG, you have to edit half a dozen text files (*.rds, *.rls, *.srd, airfields, allcampaigns, bridges, endcampaign, grandcampaign, maps). This latter involves a lot of copy-pasting and manual editing, without any check provided for data integrity . What I would like to do first is to enable this in one single database, and through one single interface, where you can (re)name (existing) locations, assign them to sides, set supply bases etc, set scenario date limits and victory conditions, and, finally, set the campaign flow. Using DCG's own data files, it will take me one month to get to the point where I'm able to import, display, modify, and correctly export DCG map/campaign data.
Once this is achieved, I will certainly look at maps not covered by DCG's vanilla database. Here comes in what you brought up. I know nothing of map editing, and I will be very happy to learn about it. And it's simply great that you 'have at the back of your mind that you want to have support for DCG and DGEN'. Please never forget that a clear and unobstructed network of roads is the pre-requisite for 'having a custom actors static with just the main road/rail you want to extract for DCG/DGEN and processing the coordinates of the objects constituting the road/railway'. :D
-
Fair enough for legacy maps, there is a great deal of work.
By obstructions you mean solid objects that prevent vehicles to go across, like a house placed on top of road, right?
I have not dived in DCG but it does not look different from what map building is, text files you can edit and XY coordinates similar to those you have in any FMB mission file. Certainly something that can be processed either using database queries or a bash script under Linux (my preference ...).
All objects placed on a map having coordinates, it would be fun to have clash detection to get all these entries that are in the way deleted ... (add Dr.Evil laugh !).
Back to virtual reality, this road going down to Porog, Lyubytinsky District you see below is done manually (bends, straight bits and so on):
(http://i.imgur.com/qk9mYgGh.jpg)
Seems smart to use the coordinates of the objects constituting the road instead of manually placing a vehicle to pick the data you are after. The classic IL-2 zig-zag roads also have their entries stored (although I am less familiar with them, not to my taste!).
As for what you need to learn for map making data handling, actors.static manipulation is probably all you are after.
In this tread (https://www.sas1946.com/main/index.php?topic=46734.0) Uzin posted a link to a tutorial https://www.mediafire.com/download/jk32ohj01yp0e6h/Actors_Tutorial.rar (https://www.mediafire.com/download/jk32ohj01yp0e6h/Actors_Tutorial.rar)
I am looking at the moment at using Geo-positioning for generating the names of cities (instead of doing them by hand), what a great deal of fun this hackable game is!
-
Thanks for the hints!
And yes, by obstructions I mean solid objects that prevent vehicles to go across. A clash detection would not be too hard to make, provided we have to deal with classic zig-zag roads with straight segments. It would be fairly easy to create a 'clearance zone' for each segment by computing neighbouring coordinates.
What I don't understand regarding bending roads is how do you force vehicles to stick to the road and not to 'cut' bendings? Classic mis files (and those generated by DCG) store waypoint coordinates where vehicles travel in a straight line between such coordinates, right? I understand that you can create curved road objects, but I don't understand whether and how it is possible to make vehicles follow a curved movement pattern. What am I missing?
-
Correct, straight lines only and vehicles will not snap to curves like they snap to zig-zags. You cannot either stretch your zig-zagging like on a regular map ... but you can place waypoints close enough so that the succession of (small) straight lines appears like a curve.
Trains cannot be placed directly like this but you can use any vehicle to start with to get your "curves" and then replace the jeep in the .mis by a train object.
The principle is explained at http://www.mission4today.com/index.php?name=Knowledge_Base&op=show&kid=547 (http://www.mission4today.com/index.php?name=Knowledge_Base&op=show&kid=547)
-
Wow! This would be so cool!
-
but you can place waypoints close enough so that the succession of (small) straight lines appears like a curve.
Just a workaround, not a real solution, and would exponentially increase the number of waypoints (if you include those waypoints in the .static file). And practically impossible to do in the FMB (except for a few and short road sections).
The real solution would be to re-code the game engine to support bezier-curves, so that any ground movement, straight or curved, could be parametrized the same way as now the straight movement is. But this won't happen, I'm afraid, we can't dig that deep into the code.
Anyway, is there any map with bent roads published? I'd like to test one in the FMB and see what happens when I put some vehicle onto it.
-
I am pretty sure Rabaul has got some : https://www.sas1946.com/main/?topic=39938.0 (https://www.sas1946.com/main/?topic=39938.0)
Otherwise I could send across mine but it would be a bit more leg work for you to get it running.
On the number of entries you have to put in for a DCG campaign to run (roads/rail-wise) how big can the file be? This is where I need to have deeper look into it.
I though that if you wanted to DCG depict Germans passing through Narva on their way to set up the Leningrad blockade, you got to have the coordinates of all the main roads from Estonia towards Leningrad? Correct me if I am wrong but it means the red ones on this map:
(http://i.imgur.com/hY30PXKl.jpg)
I think a also we may want a start a separate topic, what do you think?
Seems more like map-dev v DCG-dev question than data integrity related. Up to you!
Thank you for your time and consideration, I have done about 15% of the roads for my map so any DCG input is greatly appreciated.
-
Going to be a great map, Zoran!
I'll check out the Rabaul map and report back, but I'm still sceptical about curved roads. Anyway, they pose a totally new problem, and first I have to find a feasible solution for the 250+ old maps (legacy ones and modded alike).
DCG doesn't use internal map data such as you work with. Check out this guide how it works: https://www.sas1946.com/main/index.php/topic,20873.0.html (https://www.sas1946.com/main/index.php/topic,20873.0.html) You'll see there the lot of manual work I want to automate.
DCG doesn't use the whole road/rail network, but it can use any part of it. It means that quite different scenarios can be created on the very same map, depending on the campaign designer's choice and fancy. That is, a bit of time must be spent in the FMB in any case, but if I can make the following process a lot more easier, then there will be no need for internal map data at all (except for a 2D bitmap to visualize campaign data on it).
And yes, please, start a separate topic! ;D
-
Thanks, I am familiar with Lonestar guide but not with creating my own DCG campaigns.
I should clone myself and start building a DCG campaign ...!
The 15% I have done on the map is on the very right hand side and I am getting close to be able to do a DCG push towards Tikhvin - end of 1941 / reconquest by Soviet troops.
All bendy roads, quite straight railways and 15 airfields all custom made in their historically correct (or believed to be correct) locations.
Actually I really want to have a crack, I think I'll sack the clone ...!
The idea is that I can pick what I need to fix - DCG-wise - before going too far ahead.
I will start a separate topic when I get map maker membership (the request is pending).
Back to map building now or new airfield testing actually ...
-
Hey sniperton - The Ju 388 is giving me a world of a headache. DIT will not install it in my class.dcg Can you please take a look when you get a sec.
-
Yep, you're right, the problem is that Junkers Ju388 'St\u00F6rtebeker', 1944 has a length of 38 characters, while DCG only allows 36 -- for this reason DIT suppresses it on export.
DIT is smart, but not smart enough to change \u00F6 to ö or to tell you you've been censored :P
Anyway, edit your weapons file manually and change this
################################################################################
# JU_388K ## JU_388K ### "Junkers Ju388 'St\u00F6rtebeker', 1944" #### 194301--194506
################################################################################
to this
################################################################################
# JU_388K ## JU_388K ### "Junkers Ju388 'Störtebeker', 1944" #### 194301--194506
################################################################################
-
Outstanding! Thanks.
How about the Csd Liberator GRV? :-[
-
DIT silently suppresses any plane/payload exceeding the DCG character limit. OK, with the next version I'll add a warning.
Edit: Added. As to the Csd Liberator GRV, that poses a different type of problem. Generally, aircraft name and loadout name are separated by a dot in the weapons file, but it's quite difficult to decide by code which is the plane part and which is the loadout part when any of them has an extra dot, e.g.
L-5_Sentinel[.]2x2.36in_rockets
vs
LiberatorGR.V[.]Hispanos+12x250lbs
I'll have to rewrite a complete section of code to properly handle this type of exception. :(
-
Thanks for your continued efforts!
-
Can anyone tell me where the required files are for this? Air.ini weapons properties and plane properties? I can't find them in the bat install or any installs for that matter. Thanks.
-
[BAT]\#WAW3\STD\com\maddox\il2\objects\air.ini
[BAT]\#WAW3\STD\i18n\plane.properties
[VPMOD]\#SAS\STD\...
Beware, it's an old util made for CUP in 2016, no guarantee it still works (or even needed) for newer versions of BAT and VPMOD.
It was made to help campaign designers, normally you don't need it if you only want to run a campaign specifically made for BAT or VPMOD (such as https://www.sas1946.com/main/index.php/topic,54992.0.html (https://www.sas1946.com/main/index.php/topic,54992.0.html)).
-
[BAT]\#WAW3\STD\com\maddox\il2\objects\air.ini
[BAT]\#WAW3\STD\i18n\plane.properties
[VPMOD]\#SAS\STD\...
Beware, it's an old util made for CUP in 2016, no guarantee it still works (or even needed) for newer versions of BAT and VPMOD.
It was made to help campaign designers, normally you don't need it if you only want to run a campaign specifically made for BAT or VPMOD (such as https://www.sas1946.com/main/index.php/topic,54992.0.html (https://www.sas1946.com/main/index.php/topic,54992.0.html)).
Ah, I was hoping I could just import the planes into the stock DCG campaigns.
-
Ah, I was hoping I could just import the planes into the stock DCG campaigns.
Stock DCG campaigns won't use non-stock planes unless someone adds them manually to the DCG campaign files.
DIT only automates importing of, and error-checking for, the new weapons entries coming with added planes. It filters out non-conventional ones which might make DCG hang or would result in a pink plane issue.
-
Hi Sniperton, i cant find the vp-mod-fix for DCG anymore. Is there a link to it? thanks in advance.
-
Hi Sniperton, i cant find the vp-mod-fix for DCG anymore. Is there a link to it? thanks in advance.
It's on the main VP modpack page. Just take a look.
And thanks sniperton saved me a lot of time I guess. Appreciate it.
-
Thanks. I use this tool a lot for offline Playing with DCG cause i often play with not so common aircraft. So this tool is not only useful for campaign designers (Just have to say cause its a great tool).
-
Hey sniper,
I figured out how to use the tool for the most part, but I added say the p-51 d-30 to DCG created a custom campaign but when the planes spawn they all spawn on top of eachother in the air and blow up, this is normandy map thats why they are air spawning. Any idea what could cause this to happen?
This tools awesome btw.
-
Hard to tell, there are too many possibilities given the complexity of campaign mission generation.
Invalid plane designation, invalid loadout entry, invalid squad ID, can be anything.
First step is to run DCG and check if your custom campaign is the active one and that it actually has your added planes (Squadron Settings, Aircraft Class Settings).
Second step is to load the generated .mis file into the Mission Editor and see whether it works.
-
Good tip, they do show up in the squadron panel. I will check the mis file. What is important to note however is that with this tool, you can run custom DCG campaigns with the stock maps and the new airplanes if you add them in. Do they work? I dunno yet my p-51-d-30 keeps blowing up, and I just realized that is the pacific version of the p-51 and I was flying it over normandy... I am not too historical I guess ahaha.
-
Thing is that DCG is a hack on the stock game, BAT is a mod, and making a hack work on a mod is not for the fainthearted. This is the base problem ;)
DIT can only automate the process if you're otherwise very clear about how DCG works. Now add that I made it more than 2 years ago for CUP, and since then I haven't even tested it on newer versions that might introduce changes with no respect to DCG compatibility.
Anyway, my advice is to add just one plane manually to get the hang of custom campaign creation. If you succeed, you can add more, this time using DIT to speed up the process. It's not the Holy Grail, just an outdated tool to reduce the handwork.
-
As soon as i start the tool and hit "Reload previous session i get this error message: >> "" is an invalid integer. Press OK to ignore and risk data corruption. Press Cancel to kill the programm. <<
everything went correct last time i used it.
Reextracting and setting up the same tool again doesnt help.
What can i do? I really dont want to start from scratch again. I already verified about 200 Plane from BAT.
-
Sounds like a system error message. I guess DIT crashes because it doesn't find some of files specified on the "Config" tab.
Please check for the existence (and correct path) of those files first.
As to your previous work, go to your DCG directory (as specified on the Config tab) and look for the "\DIT" folder. It should contain the three *.dcg files that you (hopefully) saved after your last DIT session.
DCG also creates auto-saves every minute. Those files (*.dcg) can be found in the folder where you installed DIT. Hopefully you didn't delete them when you reinstalled DIT.
-
Okay i was not aware of the \DIT folder in my DCG directory, i thought i should point the conf-paths to the /Data folder.
I always save these 3 .dcg files of the DIT directory when im finished for one session, so i was able to paste them into the DIT/DCG directory and load the pre-previous session.
What about the 3 .dcg files in my DIT directory? Are these autosaves?
I noticed a bug while validing planes. Sometimes the toggle-buttons for "Side" and "Plane-type" disappear. When i try to continue then, i will get an error message and have to kill the programm. But when i press escape instead of continuing, save the session and restart the programm, its working again. Idk why this is happening sometimes.
-
Okay i was not aware of the \DIT folder in my DCG directory, i thought i should point the conf-paths to the /Data folder.
I always save these 3 .dcg files of the DIT directory when im finished for one session, so i was able to paste them into the DIT/DCG directory and load the pre-previous session.
What about the 3 .dcg files in my DIT directory? Are these autosaves?
Yep, it's a bit perplexing. My bad.
The "config" tab is meant to define your data input files, that is, the DCG\Data\*.dcg files (just as you used them).
The DCG\DIT folder is your output folder: here you find the approved results of your editing work. Once content with them, you may want to copy them to the DCG\Data folder (so that DCG can actually use them)
The 3 files in your DIT directory are indeed autosaves: they are refreshed every 60secs to ensure that you don't lose data if something gets f....d up.
I noticed a bug while validing planes. Sometimes the toggle-buttons for "Side" and "Plane-type" disappear. When i try to continue then, i will get an error message and have to kill the programm. But when i press escape instead of continuing, save the session and restart the programm, its working again. Idk why this is happening sometimes.
Sorry about this. What OS do you have? (DIT was made on 32bit Win7 4 years ago).
-
What OS do you have? (DIT was made on 32bit Win7 4 years ago).
Im running Win10 64bit
Will there be an update for the "planeset" feature?
Or is the progress freezed?
Great work by the way. Its still timeconsuming but 10x faster than before.
-
Frankly, back then when I made this tool for myself I didn't expect it would be in use after so much time.
Since then I moved to a new rig, new OS (64bit Win10 here as well), I don't even know where I have put the source files. Now I fly BoX in my limited flight time, and haven't run DCG for years.