Data Error: PZL P-38 Wilk

[RERomine]

I stumbled on a data error in the Polish OOB. Fighter bomber PZL P-38 Wilk in September, 1939 is showing as carrying 1x1000lb bomb with an ammo count of 20. I'm running CD version 4.0 (just updated with patch). Screen print below.

[nuNce]

How could the poles lose the war?

[reverend]

Originally Posted by nuNce

How could the poles lose the war?

They probably couldn't take-off with 10 tons of explosives fitted.

[DRG]

That has been a 20mm cannon for years. I have no idea how that got changed to a 1000 pound bomb or why since there is already a 1000 pound bomb in slot 183.

I'll dig into this further

Don

[DRG]

This is what happens when we accept work from third parties without checking every last frigging detail. And this is why we don't do that any longer.

That aircraft is a prototype. It shouldn't even be in the OOB as there were only two in existance and the project was cancelled in the Spring of 1939 with both prototypes captured by the Germans "in a damaged state"

On top of that the 20 mm cannon that somehow got turned into a 1000 pound bomb was only "Planned" it was never installed in either prototype.

Sometime in the next week or so I will decide if we are going to ignore it until we issue another patch sometime in the future and recommend it not be used or issue a corrected OOB. I think all the aircraft in pre 1939 Poland needs a good looking at and maybe building a "prototype aircraft" formation using UC 243

For now, don't use it

Don

[RERomine]

I tried to keep it real and passed on this plane when I saw the error. It was a 1939 campaign and was surprised to even get a chance at Polish planes in the first place.

Originally Posted by DRG

This is what happens when we accept work from third parties without checking every last frigging detail. And this is why we don't do that any longer.

At least you have a choice. I've written up program changes for offshore work in detail to fix problems just to find those fixed, plus other things I didn't ask to be changed altered and broken.

I'm not sure if you have tools that can do a compare between different versions of an OOB. If not, MS Word does a nice job of comparing .CSV files and can handle a pair of files at least 370KB each.

Cheers,

Ray

[DRG]

Originally Posted by RERomine

I'm not sure if you have tools that can do a compare between different versions of an OOB. If not, MS Word does a nice job of comparing .CSV files and can handle a pair of files at least 370KB each.

Cheers,

Ray

We have an extensive data check system but looking for any fighter bomber with more bombs than it should have is a rather specialized question. We could spend hours and hours dreaming up questions that could all come back blank

This would find it though but realistically why would we ask that question unless we suspected an error like that and who would suspect an error like this for a unit that's been perfectly OK since winSPWW2v1.0?

Don

SELECT DISTINCT
D.NationID,
D.Slot,
D.Name,
D1.NationID,
D1.UnitSlot,
D.Unitclass,
D1.WeaponSlot,
D1.Weapon,
D2.WeaponName,
D1.HEAmmo,
D2. HEKill,
D1.APAmmo,
D.LastYearAvailable
FROM
"Units.DB" D,
"UnitWeapons.DB" D1,
"Weapons.DB" D2
WHERE
(D1.NationID = D.NationID)


AND (D1.UnitSlot = D.Slot)
AND (D2.NationID = D1.NationID)
AND (D2.WeaponID = D1.Weapon)
AND( D1.HEAmmo >8)
AND ( D. Unitclass = 44)
AND (D2. HEKill >15)

and there is a lot of ways to write this that would miss that error and no we don't do comparisions of one OOB from the previous version becasue there are usually hundreds of changes made

[RERomine]

All quite true. A compare tells you what changed, but not why it changed. You know better than I do the volume of changes being made. This one stood out because I couldn't picture a 1939 Polish plane with a bomb load the same as an American B-29. As you pointed out, the SQL statement wouldn't help much because it would have to be coded for a specific error. If you know the error is there, you would just go and fix it.

Cheers,

Ray