Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JG7_X_Man]

OK sniperton -1st I am going to say WOW! then I am going to say - HELL YEAH! This tool of you and Moezilla have put together is AWESOME! I finally got a sec to look at it on Sunday night and I was really impressed with it's potential.

OK I may have renamed it but - I see this being the answer to our prayer.

Let me ask:

1. is the plan is to extract the data needed from IL-2 to populate the DCG files? This could be run after every IL-2 update to keep DCG and the game objects in sync.

2. Have you tackled the issue of weapons that are not listed in the weapons.properties file like the Fw 190T?

[Moezilla]

This one is all sniperton's!

My contribution was to a JSGMEMOD to make CUP-WAW20 and DCG play nicely together.

I'll let sniperton answer your questions.

[JG7_X_Man]

LOL Mission accomplished! Thank you for correcting me too. I didn't know who did what (...which of you is Steve Jobs vs. Steve Wozniak or Bill Gates vs Paul Allen), all very talented individuals in their own right

So without updating to #20, I am seeing a lot of "false negatives". I saw some naming differences like the Wellington III.

[sniperton]

Hi, the problem is threefold:

1. DCG needs more data than what is stored ingame (e.g. plane type or transit altitude). You have to add/adjust them manually. DIT makes it easier.
2. DIT works with data taken over from weapons.properties. Once a loadout A is assigned to plane B in weapons.properties, you have no other choice than to use these assigments. That is, DIT forces you to use (only) ingame loadout assigments. It's fool-proof, you don't have to bother about weapons names: just select one or more.
3. Weapons.properties files are frequently incorrect or incomplete. For WAW #20, Moe made them complete and reliable. You can be sure that what you have in your weapons.properties is exactly what you have ingame.

As to your questions,

1) you'll have all the extractable data for stock 4.12.2, 4.13.1, HSFX, WAW#20, and VP MOD within 'two weeks';
2) so that you can hand-create DCG records based on ingame data (which you won't loose in case the game gets updated).
3) we extracted everything from ingame, so that the (modified) weapons.properties we use is for all the planes and all the loudouts found in the game, and not just for those which are available in the published weapons.properties.

You can re-enable any 'false negatives' provided they are listed in your air.ini. That is, you can use our full WAW #20 weapons.propertites with any former air.inis; planes not available in your game install won't be available for you, that's so simple.

[JG7_X_Man]

Hey Sniperton: Can you explain what the 1st, 2nd and 3rd windows are telling me



Here is my aircraft editor tab: Can you tell me what I am looking at panel by panel


So the contents of the DIT folder are the aligned allpayloads, payloads and class files that are in my air.ini, weapons.properties files. What I don't get is the 96 unavailable aircraft - disabled in air.ini? I want them all Grrr!! How can i get them Grrr! Do you have them? I love this program! What's this planeset editor coming?

[sniperton]

Left panel displays what is unavailable in your install.

In case of loadouts, they are considered unavailable as they are not listed in your weapons.properties. There can be two reasons for that. First, they are not available in your game version at all, e.g. because they belong to planes (like jets) not available in WAW. For some reason your DCG database has them, but you can't use them in the game version you selected. The second possible reason for their unavailability is that your weapons.properties does not fully cover the content of your game (it's incomplete). At the moment I cannot tell which is the case. Anyway, we are at 99% to release a fully complete weapons.properties for WAW #20.

In case of planes, they are typically unavailable as they are not listed (or commented out) in your air.ini, meaning that you can't have them ingame. Jets are a case in point. You seem to use a DCG database which was originally created for HSFX.

You have 96 unavailable and 999 available + verified planes.
Using a stock DCG database I have 35 unavailable and 1018 available + verified planes.
The difference between these latter figures is what really matters. You're missing 19 planes. Check e.g. Curtiss CW-21B, it's in WAW and should be available to you: check whether you really have it in your air.ini and that it is not commented out.

As to the planeset editor, it will extend the functionality of the aircraft editor towards searching, selecting and sorting 'verified' planes according to various criteria, adding upgrade and downgrade types, etc.

[JG7_X_Man]

Thanks for that through explanation.

When I started to update DCG files I used HSFX as my base, since that was before CUP came along. I excluded several aircraft that didn't see action in WW II, non-combat aircraft, modern jets and the aces from my class.dcg because the intent was to have a separate DCG install for each version of CUP (combat only aircraft). If I want to sight-see, I load up FSX.

Question:
When you say "unavailable" what is the program comparing? My air.ini/weapons.properties/plane.properties to my allplayloads/payloads/class files? or something else?

Is there an air.ini included in WaW #20? If I am missing aircraft, I might need a total reinstall - I guess finding out what the app is comparing my files with would be very helpful.

Thanks again on a great tool!

[sniperton]

Air.ini is typically in #WAW\STD\com\maddox\il2\objects (uless you use a lightened air.ini which might reside elsewhere)
The two other files: #WAW\STD\i18n

DIT takes everything from class, allpayloads, and payloads on the one side, and from air.ini, weapons and plane.properties on the other. It merges everything into one single database, where every record (planes and loadouts alike) are flagged like this: 'I was found in class, payloads, air.ini, weapons.properties, etc' (=verified), or 'I was found in air.ini, but not found in class' (=available), or 'I was found in class, but not found in air.ini' (=unavailable), or 'I was found in weapons.properties, but not found in air.ini' (=unavailable).

There can be only one reason for a plane being considered 'unavailable': it's not in the air.ini you specified (or is disabled / commented out). If it's only commented out, the led is black, and you can re-enable it for DCG the same way as you do for a blue ('available') plane. (To enable it for WAW, however, you have to manually edit air.ini). If a plane is completely missing from the air.ini, then the led is bright red.

Hope it helps

[Flying H]

Where can I find this tool, please?

[sniperton]

Will be released as a public beta in a few days, but until then you can have it as an early alpha: https://www.mediafire.com/download/h7zey8az84pckyd/il2_dit_alpha.zip

[JG7_X_Man]

Sniperton - I did some digging and I think I like how this works! Some thoughts...

I looked in the 1st window where I had 96 aircraft that were unavailable. The 1st one on my list is the Go-229NJ[WP2] ...not sure what [WP2] means.  I looked in my air.ini and plane.properties and didn't see it. However, I found it in the weapons.properties file (...maybe some correlation to the [WP2]?). But that aircraft is a straggler because there there is also Go-229 A1, A2, A3 and A2NJ (..which should be A3NJ but it was mislabeled).

However, I like how I can assign weapons to an aircraft by drag and drop - very cool.

[sniperton]

Thnaks for the feedback!

Yep, [WP2] means that the plane was added to the database from the weapons file as a strangler (there was no such plane in the air.ini). Data import has the sequence: air.ini, weapons.properties, plane.properties, class.dcg, allpayloads.dcg, payloads.dcg.
Anytime you see such extensions means that tha plane/loadout was taken not from where it was expected to be found.

As to drag and drop, be careful with it, now it allows more options than DCG; I'll correct it tonight according to the info I received from Lowengrin on the JG1 site.