Scenario database checker

Please post here for questions and discussion about scenario design and the game editor for WITP.

Moderators: wdolson, Don Bowen, mogami

User avatar
michaelm75au
Posts: 12457
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

Scenario database checker

Post by michaelm75au »

Greetings fellow scenario modders[:)]

I have completed an utility to perform an integrity check on a scenario database files.

I have used the Editor manual's requirements to perform some of the checks, but I also included other checks based on observation/requests/crashes.

I am not releasing the program until after the patch comes out, so that I can verify the program against the OOB changes.

The attachment contains a README file and a sample output.

Feedback is always welcomed.

[Download the attachment. Rename it to a ZIP file.]

27/11/04
I have deleted attachment. Program is available from Spooky's site.

Michael
Michael
User avatar
michaelm75au
Posts: 12457
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

RE: Scenario database checker

Post by michaelm75au »

The contents of the previous attachments:
War in the Pacific checker
Version 1.14

The integrity checks are performed on a specified scenario database.

To run the program:
witpchk.exe /d <location of scenario base> /s <scenario number> /i [use default directory]

Example:
To check scenario number 26 in the default directory, run witpchk.exe /i /s 26.

Most of these checks are based on the Editor manual, while the rest are based on "simple" logical extensions.

Only active items in a scenario are checked. Active items are where the item description is not empty and the item
type (if applicable) is not "NONE".

Items where the available or arrival date is 9999, or the date is past the end of the scenario, are not checked as
they are deemed to be outside the timeframe of the scenario.

The program also reports any items that are defined in the databases, but is not referenced/used within the scenario
scope. Bear in mind that just because an item is not referenced does not mean it is not used by WITP.

Note:
Not all messages indicate an error in database. In some cases, the error may have been designed for. Eg a ship is
scheduled to arrive as a particular class. But by the arrival date, this class has already been upgraded. For the
scenario however, we don't want the ship upgraded.


A. Devices

Message
Device ID: # (Name) - not an industry/resource item (Type#)
Device ID: # (Name) - not an OHKA bomb
Device ID: # (Name) - not an ATOMIC bomb
Device ID: # (Name) - not AIR ORDNANCE
Device ID: # (Name) - not an Engine, Engineer or Support squad
Device ID: # (Name) - error in Available date (Date)
Device ID: # (Name) - invalid upgrade path (Device#)
Device ID: # (Name) - upgrade path to NULL device (Device#)
Device ID: # (Name) - zero replacement rate

B. Classes

Message
Class ID: # (Name) - NULL name for class
Class ID: # (Name) - error in available month (Month)
Class ID: # (Name) - cruise speed exceeds maximum speed
Class ID: # (Name) - zero maximum speed
Class ID: # (Name) - zero cruise speed rating
Class ID: # (Name) - zero manuever rating
Class ID: # (Name) - zero durability rating
Class ID: # (Name) - zero endurance rating
Class ID: # (Name) - zero fuel load
Class ID: # (Name) - invalid upgrade path (Class#)
Class ID: # (Name) - upgrade path to NULL class (Class#)
Class ID: # (Name) - upgrade path to a different class (Class# - Name)
Class ID: # (Name) - upgrade from (Class Date) to older class (Name/Date)
Class ID: # (Name) - carrier type class has no Air Ordinance defined
Class ID: # (Name) - carrier type class has zero aircraft capacity
Class ID: # (Name) – bitmap (Name) not found
Class ID: # (Name) – no bitmap defined
Class ID: # (Unknown) – AK/PG conversion ship class missing

Class ID: # (Name) - Air Ordnance (#195) must be in last weapon slot, not weapon slot #99
Class ID: # (Name) - zero Air strikes in Air Ordnance slot
Class ID: # (Name) - non zero values in number, turret or ammo in Air Ordnance slot
Class ID: # (Name) - weapon slot #99 has invalid device (Device#)
Class ID: # (Name) - weapon slot #99 assigned to NULL device (Device#)
Class ID: # (Name) - zero value in number and/or turret of weapon slot #99 (Name)
Class ID: # (Name) - zero value in ammo of weapon slot #99 (Name)
Class ID: # (Name) - zero units in weapon slot #99 (Name)
Class ID: # (Name) - zero turret/bank in weapon slot #99 (Name)
Class ID: # (Name) - odd turret # in weapon slot #99 (Name)
Class ID: # (Name) - values in empty weapon slot #99


C. Ships

Message
Ship ID: # (Name) - invalid class # (Class#)
Ship ID: # (Name) - NULL name for class # (Class#)
Ship ID: # (Name) - error in Delay date (Date)
Ship ID: # (Name) - invalid slot for nationality (Nation# - Name)
Ship ID: # (Name) - error in Sunk date (Date)
Ship ID: # (Name) - ship sunk (Date) before scenario starts
Ship ID: # (Name) - ship sunk (Date) before arrival date (Date)
Ship ID: # (Name) - experience is too high (D:99/N:99)
Ship ID: # (Name) - damage is too high (S:99/F:99)
Ship ID: # (Name) - taskforce number (#99) in error
Ship ID: # (Name) - taskforce number (#99 - Name) assignment error
Ship ID: # (Name) - base number (#99 - Name) assignment error
Ship ID: # (Name) - base number (#99) in error
Ship ID: # (Name) - starts on map in [Location Name] as class (Name/Date), newer class (Name/Date) available
Ship ID: # (Name) – arriving on [Date] as class (Name/Date), newer class (Name/Date) available
Ship ID: # (Name) – not assigned location at scenario start
Ship ID: # (Name) - invalid leader (Leader#)
Ship ID: # (Name) - assigned to NULL leader (Leader#)
Ship ID: # (Name) - assigned leader (Name/Nationality) is wrong nationality for ship (Nationality)
Ship ID: # (Name) - assigned leader (Name/Leader Type) is wrong type for ship
Ship ID: # (Name) - ship arrives on [Date] with leader (Name) who is not yet due (Date)

Ship ID: # (Name) - Air Ordnance (#195) must be in last weapon slot, not weapon slot #99
Ship ID: # (Name) - zero Air strikes in Air Ordnance slot
Ship ID: # (Name) - non zero values in number, turret or ammo in Air Ordnance slot
Ship ID: # (Name) - weapon slot #99 has invalid device (Device#)
Ship ID: # (Name) - weapon slot #99 assigned to NULL device (Device#)
Ship ID: # (Name) - total #(999) exceeds class #(999) for weapon slot #99 (Name)
Ship ID: # (Name) - zero value in number and/or turret of weapon slot #99 (Name)
Ship ID: # (Name) - zero value in ammo of weapon slot #99 (Name)
Ship ID: # (Name) - zero turret/bank in weapon slot #99 (Name)
Ship ID: # (Name) - odd turret # in weapon slot #99 (Name)
Ship ID: # (Name) - odd disabled # in weapon slot #99 (Name)
Ship ID: # (Name) - no damage set on ship with disabled weapons in slot #99 (Name)


D. Aircraft


Message
Aircraft ID: # (Name) - error in available month (Month)
Aircraft ID: # (Name) - cruise speed exceeds maximum speed
Aircraft ID: # (Name) - zero maximum speed
Aircraft ID: # (Name) - zero cruise speed
Aircraft ID: # (Name) - zero manuever rating
Aircraft ID: # (Name) - zero durability rating
Aircraft ID: # (Name) - zero endurance rating
Aircraft ID: # (Name) - zero maximum altitude
Aircraft ID: # (Name) - zero climb rate
Aircraft ID: # (Name) – invalid upgrade path (Air#)
Aircraft ID: # (Name) - upgrade path to NULL air (Air#)
Aircraft ID: # (Name) - upgrade from model (Date) to older model (Name/Date)
Aircraft ID: # (Name) - zero replacement/production rate

Aircraft ID: # (Name) - non ENGINE (Device#) defined in last weapon slot
Aircraft ID: # (Name) - weapon slot #99 has invalid device (Device#)
Aircraft ID: # (Name) - weapon slot #99 assigned to NULL device (Device#)
Aircraft ID: # (Name) - zero units in weapon slot #99 (Name)


E. Air Groups

Message
Group ID: # (Name) - invalid aircraft # (Air#)
Group ID: # (Name) - NULL name for aircraft # (Air#)
Group ID: # (Name) - error in Delay date (Date)
Group ID: # (Name) - starts on map with aircraft (Name/Date), newer aircraft (Name/Date) available
Group ID: # (Name) - starts on map with newer aircraft (Name/Date)
Group ID: # (Name) - arriving on %d with newer aircraft (Name/Date)
Group ID: # (Name) - experience is too high (99)
Group ID: # (Name) - morale is too high (99)
Group ID: # (Name) - invalid leader (Leader#)
Group ID: # (Name) - assigned to NULL leader (Leader#)
Group ID: # (Name) - assigned leader (Name/Nationality) is wrong nationality
Group ID: # (Name) - assigned leader (Name/Leader Type) is wrong type
Group ID: # (Name) - arrives on [Date] with leader (Name) who is not yet due (Date)
Group ID: # (Name) - invalid HQ (HQ#)
Group ID: # (Name) - assigned to NULL HQ (HQ#)
Group ID: # (Name) - invalid target (Location#)
Group ID: # (Name) - assigned to NULL target (Location#)
Group ID: # (Name) – ship (#99 - Name) assignment error
Group ID: # (Name) – ship (Name/Date) with group before group is due (Date)
Group ID: # (Name) - newer aircraft (Name/Date) on ship (Ship/Date) at arrival time
Group ID: # (Name) - ship number (#99) in error
Group ID: # (Name) – base (#99 - Type) assignment error
Group ID: # (Name) - base number (#99) in error
Group ID: # (Name) – not assigned location on arrival (Date)
Group ID: # (Name) – invalid upgrade path (Air#)
Group ID: # (Name) - upgrade path to NULL air (Air#)
Group ID: # (Name) - non ENGINE (Device#) defined in last weapon slot
Group ID: # (Name) - weapon slot #99 has invalid device (Device#)
Group ID: # (Name) - weapon slot #99 assigned to NULL device (Device#)
Group ID: # (Name) - zero units in weapon slot #99 (Name)



Locations

Message
Location ID: # (Name) - incorrect type (Type name) in this slot
Location ID: # (Name) - no nationality set for this slot
Location ID: # (Name) - incorrect nationality (Number) for this slot
Location ID: # (Name) - TO&E unit does not have Delay of 9999
Location ID: # (Name) - TO&E unit does not have Location of 0,0
Location ID: # (Name) - TO&E unit has leader (Name/Number) assigned
Location ID: # (Name) - mismatch between unit type (Number) and suffix (Number)
Location ID: # (Name) - error in Delay date (Date)
Location ID: # (Name) - invalid leader (Leader#)
Location ID: # (Name) - assigned to NULL leader (Leader#)
Location ID: # (Name) - arrives on [Date] with leader (Name) who is not yet due (Date)
Location ID: # (Name) – starts on map with leader (Name) who is not yet due (Date)
Location ID: # (Name) – type (Name) assigned to different command level leader (Name/Level)
Location ID: # (Name) - invalid HQ (HQ#)
Location ID: # (Name) - assigned to NULL HQ (HQ#)
Location ID: # (Name) - invalid destination (#)
Location ID: # (Name) - assigned to NULL destination (#)
Location ID: # (Name) - invalid load unit (#)
Location ID: # (Name) - assigned to NULL load unit (#)
Location ID: # (Name) - load unit assignment error (LU#/Type)
Location ID: # (Name) - unit not in same location as load unit (#)
Location ID: # (Name) - invalid target (#)
Location ID: # (Name) - assigned to NULL target (#)
Location ID: # (Name) - invalid home base (#)
Location ID: # (Name) - assigned to NULL home base (#)
Location ID: # (Name) - home base assignment error (#/Type)
Location ID: # (Name) - invalid formation (#)
Location ID: # (Name) - assigned to NULL formation (#)
Location ID: # (Name) - formation (#) is out of range
Location ID: # (Name) - no location set at start of scenario
Location ID: # (Name) - weapon slot #99 has invalid device (Device#)
Location ID: # (Name) - weapon slot #99 assigned to NULL device (Device#)
Location ID: # (Name) - zero units in weapon slot #99 (Name)
Location ID: # (Name) - total #(99) exceeds TOE #(99) for weapon slot #%d (Name)
Location ID: # (Name) - different device (Name) to TOE (Name) in weapon slot #%d (Name)
Location ID: # (Name) - values for empty device in weapon slot #%d (Name)


Pilots

Message
Pilot ID: # (Name) - error in Delay date (Date)
Pilot ID: # (Name) - experience is too high (99)
Pilot ID: # (Name) - invalid leader (Leader#)
Pilot ID: # (Name) – group (#99) not defined



Leaders

Message
Leader ID: # (Name) - error in Delay date (Date)
Leader ID: # (Name) - command level not defined
Leader ID: # (Name) - no nationality defined

=================================================
WITP database checker utility - Version 1.14
Loading File C:\Matrix Games\War in the Pacific\SCEN\cam015.dat
December 1941 Start by Rich Dionne & Gary Grigsby
Scenario starts on 411207 for 1576 turns
ends by 460401
Japanese Production: ON
Allied Production: ON

Loading File C:\Matrix Games\War in the Pacific\SCEN\wpd015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wpc015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wps015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wpa015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wpg015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wpl015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wpp015.dat
Loading File C:\Matrix Games\War in the Pacific\SCEN\wph015.dat
=============================================
Checking device structure
Device ID: 515 (4in CD Gun) - zero replacement rate
Device ID: 517 (3in CD Gun) - zero replacement rate
Completed

Checking class structure
Class ID: 47 (Shimane Maru) - odd turret # in weapon slot #1 (4.7in/45 10YT Gun)
Class ID: 47 (Shimane Maru) - odd turret # in weapon slot #2 (4.7in/45 10YT Gun)
Class ID: 70 (Tachibana) - zero value in number and/or turret of weapon slot #11 (Type 13 Radar)
Class ID: 165 (S. AK) - values in empty weapon slot #3
Class ID: 165 (S. AK) - values in empty weapon slot #4
Class ID: 178 (Pennsylvania) - zero value in number and/or turret of weapon slot #11 (CXAM Radar)
Class ID: 179 (New Mexico) - zero value in number and/or turret of weapon slot #11 (SC Radar)
Class ID: 203 (London (rebuild)) - upgrade path to a different class (1413 - London)
Class ID: 312 (Dorsey) - odd turret # in weapon slot #6 (Mk 6 Depth Charge)
Class ID: 347 (L.Tanker (US)) - upgrade path to a different class (1472 - L. Tanker (US))
Class ID: 348 (Neosho) - upgrade path to NULL class (1481)
Class ID: 520 (Takao) - upgrade path to NULL class (521)
Class ID: 528 (Oyodo) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 528 (Oyodo) - odd turret # in weapon slot #5 (25mm Type 96 AA Gun)
Class ID: 553 (Zuiho) - odd turret # in weapon slot #8 (5in Rocket)
Class ID: 555 (Ryuho) - odd turret # in weapon slot #10 (5in Rocket)
Class ID: 593 (Tomodzuru) - odd turret # in weapon slot #2 (4.7in/45 10YT Gun)
Class ID: 605 (Soryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 605 (Soryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 606 (Soryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 606 (Soryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 607 (Soryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 607 (Soryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 608 (Soryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 608 (Soryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 608 (Soryu) - odd turret # in weapon slot #7 (5in Rocket)
Class ID: 608 (Soryu) - odd turret # in weapon slot #8 (5in Rocket)
Class ID: 609 (Hiryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 609 (Hiryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 610 (Hiryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 610 (Hiryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 611 (Hiryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 611 (Hiryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 612 (Hiryu) - odd turret # in weapon slot #3 (25mm Type 96 AA Gun)
Class ID: 612 (Hiryu) - odd turret # in weapon slot #4 (25mm Type 96 AA Gun)
Class ID: 612 (Hiryu) - odd turret # in weapon slot #7 (5in Rocket)
Class ID: 612 (Hiryu) - odd turret # in weapon slot #8 (5in Rocket)
Class ID:1213 (Pennsylvania) - odd turret # in weapon slot #7 (20mm Oerlikon AA Gun)
Class ID:1213 (Pennsylvania) - odd turret # in weapon slot #8 (20mm Oerlikon AA Gun)
Class ID:1233 (Portland) - zero value in number and/or turret of weapon slot #11 (SG Radar)
Class ID:1317 (Swan) - odd turret # in weapon slot #2 (4.7in/45 QF Gun)
Class ID:1358 (Barnegat ) - upgrade path to a different class (1359 - Barnegat)
Class ID:1407 (Queen Elizabeth) - upgrade path to a different class (1406 - Warspite)
Class ID:1407 (Queen Elizabeth) - odd turret # in weapon slot #7 (20mm Oerlikon AA Gun)
Class ID:1407 (Queen Elizabeth) - odd turret # in weapon slot #8 (20mm Oerlikon AA Gun)
Class ID:1481 () - NULL name for class
Completed

Checking ship structure
Ship ID: 1 (Akagi) - assigned leader (Eitaro, A./none) is wrong type for ship
Ship ID: 8 (Hiyo) - ship arrives on 420731 with leader (Kameyama, J.) who is not yet due (421015)
Ship ID: 19 (Shoho) - ship arrives on 420126 with leader (Izawa, I.) who is not yet due (420501)
Ship ID: 21 (Ryuho) - ship arrives on 421128 with leader (Furuichi, N.) who is not yet due (430115)
Ship ID: 25 (Unyo) - ship arrives on 420531 with leader (Keisho, M.) who is not yet due (420815)
Ship ID: 26 (Chuyo) - ship arrives on 421125 with leader (Uozumi, J.) who


Checking leader structure
Leader ID:19997 (Cornelis, J.C.) - command level not defined
Leader ID:19998 (Leggatt, G.A.) - command level not defined
Leader ID:19999 (Eitaro, A.) - command level not defined
Completed

Checking references
Device ID: 43 (5.1in/50 M1924 Gun) - defined but not referenced
Device ID: 46 (4.5in/45 QF Mk I Gun) - defined but not referenced
Device ID: 117 (Mousetrap Mk 22) - defined but not referenced
Device ID: 122 (Type 3 Mine) - defined but not referenced
Device ID: 123 (Mk 6 Mine) - defined but not referenced
Device ID: 128 (Mk XVII Mine) - defined but not referenced
Device ID: 130 (Mk 13 Mine) - defined but not referenced
Device ID: 153 (13.2mm FN MG) - defined but not referenced
Device ID: 154 (7.5mm MAC-M39 MG) - defined but not referenced
Device ID: 155 (7.7mm SAFAT MG) - defined but not referenced
Device ID: 157 (7.9mm MG 17) - defined but not referenced
Device ID: 158 (7.9mm MG 15) - defined but not referenced
Device ID: 159 (7.9mm MG 81) - defined but not referenced
Device ID: 160 (12.7mm SAFAT MG) - defined but not referenced
Device ID: 162 (13mm MG 131) - defined but not referenced
Device ID: 163 (15mm Cannon MG151) - defined but not referenced
Device ID: 165 (20mm HS404 Cannon) - defined but not referenced
Device ID: 166 (20mm Cannon MG151) - defined but not referenced
Device ID: 167 (20mm Cannon MG FF) - defined but not referenced
Device ID: 169 (30mm Cannon MK108) - defined but not referenced
Device ID: 170 (30mm Cannon MK103) - defined but not referenced
Device ID: 171 (37mm Cannon BK3.7) - defined but not referenced
Device ID: 205 (2000 lb GP Bomb) - defined but not referenced
Device ID: 209 (800 kg AP Bomb) - defined but not referenced (coded bombload for Torpedo aircraft?)
Device ID: 211 (100lb ICB Cluster) - defined but not referenced
Device ID: 212 (400lb ICB Cluster) - defined but not referenced
Device ID: 213 (Atomic Bomb) - defined but not referenced
Device ID: 215 (100 litre Drop Tank) - defined but not referenced
Device ID: 216 (300 litre Drop Tank) - defined but not referenced
Device ID: 217 (50 gal Drop Tank) - defined but not referenced
Device ID: 218 (75 gal Drop Tank) - defined but not referenced
Device ID: 219 (110 gal Drop Tank) - defined but not referenced
Device ID: 221 (200 gal Drop Tank) - defined but not referenced
Device ID: 222 (330 litre Drop Tank) - defined but not referenced
Device ID: 227 (H2S Nav.Radar) - defined but not referenced
Device ID: 228 (H2X Nav.Radar) - defined but not referenced
Device ID: 229 (Oboe) - defined but not referenced
Device ID: 242 (Mansyu Engines) - defined but not referenced
Device ID: 245 (Kokusai Engines) - defined but not referenced
Device ID: 246 (Toyoda Engines) - defined but not referenced
Device ID: 261 (IJA Motorized Squad) - defined but not referenced
Device ID: 297 (Type 92 Armored Car) - defined but not referenced
Device ID: 298 (Type 93 Armored Car) - defined but not referenced
Device ID: 300 (Type 94 Tankette) - defined but not referenced
Device ID: 308 (Type 2 CS-Tank) - defined but not referenced
Device ID: 309 (Type 4 SP-Gun) - defined but not referenced
Device ID: 348 (British Light Squad) - defined but not referenced
Device ID: 359 (Gurka Squad) - defined but not referenced
Device ID: 375 (Chinese Engineer Sqd) - defined but not referenced
Device ID: 380 (Soviet Guards Squad) - defined but not referenced
Device ID: 385 (Soviet Mech Squad) - defined but not referenced
Device ID: 388 (Soviet Mech SMG Sqd) - defined but not referenced
Device ID: 395 (Soviet Airborne Sqd) - defined but not referenced
Device ID: 432 (160mm Mortar) - defined but not referenced
Device ID: 437 (76mm Howitzer) - defined but not referenced
Device ID: 460 (355mm CD Gun) - defined but not referenced
Device ID: 462 (203mm Howitzer) - defined but not referenced
Device ID: 463 (8in Howitzer) - defined but not referenced
Device ID: 464 (132mm BM-13 Rockets) - defined but not referenced
Device ID: 492 (BT-7 Light Tank) - defined but not referenced
Device ID: 499 (KV-1 Heavy Tank) - defined but not referenced
Device ID: 507 (SU-122 Assault Gun) - defined but not referenced
Device ID: 508 (SU-152 Assault Gun) - defined but not referenced

Class ID: 53 (Mizuho) - defined but not referenced
Class ID: 108 (Large MLE) - defined but not referenced
Class ID: 120 (Gyoraitei #10) - defined but not referenced
Class ID: 121 (Gyoraitei #201) - defined but not referenced
Class ID: 122 (Gyoraitei #241) - defined but not referenced
Class ID: 173 (North Carolina) - defined but not referenced
Class ID: 194 (Wichita) - defined but not referenced
Class ID: 211 (Delhi) - defined but not referenced
Class ID: 217 (Arethusa) - defined but not referenced
Class ID: 218 (Edinburgh) - defined but not referenced
Class ID: 220 (Gloucester) - defined but not referenced
Class ID: 226 (La Galissonniere) - defined but not referenced
Class ID: 227 (Duguay Trouin) - defined but not referenced
Class ID: 230 (Scylla) - defined but not referenced
Class ID: 239 (Wasp) - defined but not referenced
Class ID: 259 (Unicorn) - defined but not referenced
Class ID: 267 (Somers) - defined but not referenced
Class ID: 273 (Bristol) - defined but not referenced
Class ID: 276 (Gearing) - defined but not referenced
Class ID: 278 (L'Adroit) - defined but not referenced
Class ID: 323 (Tacoma) - defined but not referenced
Class ID: 359 (Large MLE) - defined but not referenced
Class ID: 391 (S. Tanker (US)) - defined but not referenced
Class ID: 514 (Ise) - defined but not referenced
Class ID: 521 () - defined but not referenced
Class ID: 522 (Takao) - defined but not referenced
Class ID: 560 (Chitose) - defined but not referenced
Class ID:1315 (Gato) - defined but not referenced
Class ID:1366 (River (RN)) - defined but not referenced
Class ID:1367 (River (RAN)) - defined but not referenced
Class ID:1407 (Queen Elizabeth) - defined but not referenced
Class ID:1481 () - defined but not referenced
Class ID:1482 (Neosho) - defined but not referenced
Class ID:1507 (Elco 80ft PT) - defined but not referenced

Aircraft ID: 15 (D1A Susie) - defined but not referenced
Aircraft ID: 20 (B4Y Jean) - defined but not referenced
Aircraft ID: 60 (L2D2 Tabby) - defined but not referenced
Aircraft ID: 105 (Singapore) - defined but not referenced
Aircraft ID: 173 (P-51B Mustang) - defined but not referenced
Aircraft ID: 189 (B-26G Marauder) - defined but not referenced
Aircraft ID: 195 (B-17G Fortress) - defined but not referenced
Aircraft ID: 212 (I-152) - defined but not referenced
Aircraft ID: 213 (I-153) - defined but not referenced
Aircraft ID: 236 (IL-4) - defined but not referenced

All files have been checked successfully.
Michael
User avatar
tanjman
Posts: 668
Joined: Sat Jan 26, 2002 10:00 am
Location: Griffin, GA

RE: Scenario database checker

Post by tanjman »

Michael,

Great work! Looking forward to using it.
Gunner's Mate: A Boatswain's Mate with a hunting license.
User avatar
pry
Posts: 938
Joined: Fri Dec 06, 2002 7:19 am
Location: Overlooking Galveston Bay, Texas

RE: Scenario database checker

Post by pry »

I beta tested this for Michael while working on the 1.3 patch and made several of the suggestions for the data checks. It is a really great program and will make any scenario designers job a whole lot easier and zero right in to the exact data base entry line for really quick fixes...

Two thumbs up
User avatar
Ron Saueracker
Posts: 10967
Joined: Mon Jan 28, 2002 10:00 am
Location: Ottawa, Canada OR Zakynthos Island, Greece

RE: Scenario database checker

Post by Ron Saueracker »

ORIGINAL: pry

I beta tested this for Michael while working on the 1.3 patch and made several of the suggestions for the data checks. It is a really great program and will make any scenario designers job a whole lot easier and zero right in to the exact data base entry line for really quick fixes...

Two thumbs up

We could have used this earlier, eh Paul?[;)][:D]
Image

Image

Yammas from The Apo-Tiki Lounge. Future site of WITP AE benders! And then the s--t hit the fan
User avatar
Admiral DadMan
Posts: 3395
Joined: Fri Feb 22, 2002 10:00 am
Location: A Lion uses all its might to catch a Rabbit

RE: Scenario database checker

Post by Admiral DadMan »

Wow, this is really cool!
Scenario 127: "Scraps of Paper"
(\../)
(O.o)
(> <)

CVB Langley:
Image
User avatar
Captain Cruft
Posts: 3707
Joined: Wed Mar 17, 2004 12:49 pm
Location: England

RE: Scenario database checker

Post by Captain Cruft »

Great stuff, thanks!
User avatar
Apollo11
Posts: 25170
Joined: Thu Jun 07, 2001 8:00 am
Location: Zagreb, Croatia
Contact:

RE: Scenario database checker

Post by Apollo11 »

Hi all,
ORIGINAL: michaelm

Greetings fellow scenario modders[:)]

I have completed an utility to perform an integrity check on a scenario database files.

I have used the Editor manual's requirements to perform some of the checks, but I also included other checks based on observation/requests/crashes.

I am not releasing the program until after the patch comes out, so that I can verify the program against the OOB changes.

The attachment contains a README file and a sample output.

Feedback is always welcomed.

_GREAT_!!!

Thanks Michael!


Leo "Apollo11"
Image

Prior Preparation & Planning Prevents Pathetically Poor Performance!

A & B: WitW, WitE, WbtS, GGWaW, GGWaW2-AWD, HttR, CotA, BftB, CF
P: UV, WitP, WitP-AE
pad152
Posts: 2835
Joined: Sun Apr 23, 2000 8:00 am

RE: Scenario database checker

Post by pad152 »

Looks good![:)]




Thanks
User avatar
Tankerace
Posts: 5408
Joined: Fri Mar 21, 2003 12:23 pm
Location: Stillwater, OK, United States

RE: Scenario database checker

Post by Tankerace »

This just probably sped up War Plan Orange's release by at least a few weeks.
Designer of War Plan Orange
Allied Naval OOBer of Admiral's Edition
Naval Team Lead for War in the Med

Author of Million-Dollar Barrage: American Field Artillery in the Great War coming soon from OU Press.
User avatar
Spooky
Posts: 801
Joined: Mon Apr 01, 2002 2:16 am
Location: Froggy Land
Contact:

RE: Scenario database checker

Post by Spooky »

ORIGINAL: michaelm

Greetings fellow scenario modders[:)]

I have completed an utility to perform an integrity check on a scenario database files.

I have used the Editor manual's requirements to perform some of the checks, but I also included other checks based on observation/requests/crashes.

I am not releasing the program until after the patch comes out, so that I can verify the program against the OOB changes.

The attachment contains a README file and a sample output.

Feedback is always welcomed.

[Download the attachment. Rename it to a ZIP file.]

Michael

Great [:)]

If you want, I can host it in the Spooky's WITP Fansite ...
pad152
Posts: 2835
Joined: Sun Apr 23, 2000 8:00 am

RE: Scenario database checker

Post by pad152 »

michaelm

Any chance of getting a copy of this program before the 1.3 release?


Thanks
User avatar
Don Bowen
Posts: 5185
Joined: Thu Jul 13, 2000 8:00 am
Location: Georgetown, Texas, USA

RE: Scenario database checker

Post by Don Bowen »

ORIGINAL: pad152

michaelm

Any chance of getting a copy of this program before the 1.3 release?


Thanks

A great idea! A release of the checker now would give us all something to do while waiting for the Patch (and waiting, and waiting ...)
User avatar
michaelm75au
Posts: 12457
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

RE: Scenario database checker

Post by michaelm75au »

Alright .. already. Against my better judgement, here it is.[X(]

Attached is a zip file with program.

Be aware that many warnings will be issued scanning 1.21 OOBs. Pry has worked on a lot of changes for 1.3 OOBs to correct some of these.

Please don't raise any issues based on the checks against 1.21 OOBs.[:-]

Once the patch comes out and I can re-check the program, I will ask Spooky to host it for me.

Michael
[27/11/04 Attachment deleted]
Michael
User avatar
Don Bowen
Posts: 5185
Joined: Thu Jul 13, 2000 8:00 am
Location: Georgetown, Texas, USA

RE: Scenario database checker

Post by Don Bowen »

THANK YOU SIR!

I've downloaded the checker and ran it against my modified scenario. The checker appears to be excellent - it found tons of problems in my changes. Now Matrix can delay the patch for days while I clean up my errors.
pad152
Posts: 2835
Joined: Sun Apr 23, 2000 8:00 am

RE: Scenario database checker

Post by pad152 »

Thanks[:)]
User avatar
Admiral DadMan
Posts: 3395
Joined: Fri Feb 22, 2002 10:00 am
Location: A Lion uses all its might to catch a Rabbit

RE: Scenario database checker

Post by Admiral DadMan »

Ok, how do I get this little app to run in XP? I'm beginning to think that I'm much too stoopid to own a computer.

When I launch it, a little DOS box open, stuff whizzes by, and then it closes? What am I missing?
Scenario 127: "Scraps of Paper"
(\../)
(O.o)
(> <)

CVB Langley:
Image
User avatar
Bodhi
Posts: 1267
Joined: Tue Aug 26, 2003 1:36 am
Location: Japan

RE: Scenario database checker

Post by Bodhi »

ORIGINAL: Admiral DadMan

Ok, how do I get this little app to run in XP? I'm beginning to think that I'm much too stoopid to own a computer.

When I launch it, a little DOS box open, stuff whizzes by, and then it closes? What am I missing?

Sounds like a console app. I'm sure it's written a report, probably a text file file, somewhere, you just have to find it.
Bodhi
User avatar
michaelm75au
Posts: 12457
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

RE: Scenario database checker

Post by michaelm75au »

Sorry, I am a computer nerd and just pipe my screen output to a file, as in
witpchk /i /s15 >report.txt

The next release will create a report file instead, so that it will be easier to view.

Michael
Michael
pad152
Posts: 2835
Joined: Sun Apr 23, 2000 8:00 am

RE: Scenario database checker

Post by pad152 »

Hi michaelm

Can you help clearify the following?

Message "defined but not referenced"

"The program also reports any items that are defined in the databases, but is not referenced/used within the scenario scope. Bear in mind that just because an item is not referenced does not mean it is not used by WITP."

Thanks

This program should help save countless hours designing and testing scenarios.
Post Reply

Return to “Scenario Design”