Print

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

[sniperton]

WAW's weapons.properties is neither complete, nor accurate. This doesn't impair your gameplay as it's purely a localization file, still it is our only uncoded source of information of existing payload configurations.

I extracted everything I could from the aircraft class files and conflated the data with the existing weapons file. The resulting file has all the planes available in WAW #20 with all their payload configurations except for 10 planes (see attached report).

Where payload info could not be gathered, the plane is marked '# NoPayload ...' You can complete these records by hand if you wish (based on QMB info).

Where a plane is available ingame, but is not enabled via the air.ini, it is marked '# NoAirIni ...' I suppressed those which would surely conflict with existing types. Yet it's safer not to enable the rest either as they may have been omitted on purpose.

Where a plane could not be found in the class files, but is enabled via the air.ini (and seems to work flawlessly ingame), it is marked '# NoClassFile ...'

There is one known problem: some payload designations extracted from the class files are not compatible with the weapons.properties file and cannot be localized therefore. You can easily recognize them by the blank spaces they have in their internal name:

Code: [Select]

F4U-5.1 x 154 gal Central Tank          $1 x 154 gal Central Tank
Instead of (as it should be):

Code: [Select]

F4U-5.1x154galCentralTank               $1 x 154 gal Central Tank
I've converted them to a compatible name format, but I don't have the tools and the knowledge to recompile the files (and therefore I cannot test them ingame either). If someone is willing to volunteer, I attached the corrected java files as well. Please report back if done, I'll update the weapons file accordingly.

https://www.mediafire.com/download/o0hroxrw9nc5ag3/WAW20WeaponsProperties.zip

UPDATED:

https://www.sas1946.com/main/index.php/topic,51330.0.html

[Moezilla]

Check your pm, sniperton.

[sniperton]

Moe, check your PM

[JG7_X_Man]

With all this "check your PM" going on - I hope that's really a pencil in your pocket, or do you two need a private room

[sniperton]

I'm glad you've finally checked your PM too. 
We're just trying to make WAW fully DCG-compatible, but from time to time we discover some new sh.t in the pancake...

[JG7_X_Man]

LOL I know right! The air-conditioner is kaput upstairs right now so won't be on the computer to test until Friday at the earliest

[JG7_X_Man]

I have found a weird thing when the payload.dcg has an incorrect load out - for bombers anyway it only spawns 1 instead of the entire flight. It doesn't product the "pink plane" like an incorrect allpayloads.dcg does.

[sniperton]

Your issue reminds me of a mysterious one I had many months ago, but I could not track it back to a wrong payload that time. What happened me was that only one bomber was spawn and it was sent to a sightseeing tour. I was pretty upset, particularly because I could't find the reason. Are you sure the payload is the culprit?

BTW it sounds likely, Paul said that when no proper mission can be generated for a squad, a recon mission is assigned, which is usually done on a one plane per flight basis. I should check what happens when a bomber squad has an Empty loadout assigned as ground attack or level attack payload. Honestly, dunno how DCG deals with Empty payload assigments: does it suppress that type of missions for that plane (i.e. grounds the squad), or assigns a recon mission?

[JG7_X_Man]

Recon? Ummm that does make sense as it doesn't require a payload. LOL sightseeing seems more fun though. My A-20s had flares as a ground target munition (fat finger error). Once I changed the load to what was available in the allpayloads.dcg 3 aircraft per flight started spawning. It was the same for the Do-17s (this case was changing it from "default" to "Default".

It wouldn't happen to a fighter because at worst it's loadout will still have default and use it to complete its mission. Unless it is plauged by the "default" bug - LOL (...not that I am not grateful to our modders by any stretch)

[Shakaali]

DCG often assigns bomber (and - less frequently - ground attack) squadrons to recon missions with one plane only spawning, even though payloads are correct. That can happen any time, but happens especially often if there is an enemy carrier - dcg will assign a lot of recon missions until the carrier is spotted.

DCG creates a file called recons.dat in the same folder it saves missions (Il-2 Sturmovik 1946\Missions\Campaign\nation\yourcampaign). Check that to see if a certain squadron is assigned a recon mission. 

Done some testing in the past, planes with empty payloads seem to be assigned recon missions.

[sniperton]

IIRC it happened to me in a BoB campaign, where there were no carriers, but next time I will certainly check the recons.dat file as well. BTW I asked Lo what "empty" means for DCG, but there are no guarantees that DCG really works as Lo designed it...

[Shakaali]

Yes, you will get recon missions once in a while.

Which is, by the way, one of the features I like very much in dcg. It is quite realistic (as most IRL squadrons actually flew some kind of recon missions once in a while - weather reconnaissance if not else)  and it offers variety in bomber and ground attack careers.