Matrix Games Forums

So, after some time it's time for .... an update to witpdecoder. Since in addition to having maintain my own spreadsheets I also didn't like to have to click on everything just to find out some basic information, this updates adds the Map Overview (and some other minor points, see below).

You can update by downloading the updated .jar file, rename it to witpDecoder2.jar and overwrite your current witpDecoder2.jar file with it (you DO need to install witpDecoder0.4.zip first). As always, if your download is not a .jar file but a .zip file, your browser is broken (AKA Internet Explorer) and you should use the right mouse button to download.

Database will again update automatically. Alas that will probably not be the case with the next version. Note that you will need to read in at least one savegame file (can be the last one you read in) before the new features will work.

New Features:

• AirGroups are in, so now also Airgroup leaders can be selected using the Leaders Tab (see below)
• The Storage Tab now assumes that researching ACs does not use any HI or engines.
• The Storage Tab now shows factory expansions in the "Produced in" sub tab as "(+XXX)".
• Map Overview: Ship Repair shows the utilization of your ports from ship repairs (see picture one below)
• Map Overview : Naval Search shows the coverage of the current placement of naval search planes (see picture two below).
• Map Overview : Support Levels shows how well the troops are support by Support Troops (see picture three below).

The Ship Repair overview shows 3 columns per harbor with at least portsize 3:

Left column: Size of Harbor (Size 7 fills one hex) plus indications of stationed HQs (light green), ARs (brown), ADs (orange), AS (light blue). Only locally available HQs are shown (ignoring command distance) but they are assumed to stack. The AS blue is a bit difficult to see. An example with everything can be seen in Kwajalein (sp?).

Middle column (not always there): Amount of ship repair points the harbor can store maximally (200 points fill one hex) vs. the points currently available (the green part of the column). Everything is cut off at 450 points to avoid clobbering the map. So as one can see, Tokyo can have quite a lot of repair points stored but is currently below half its maximum. And it is even worse for Nagasaki.

Right column (not always there): The number of damaged ships (Sys Damage >1) disbanded in the harbor. 10 ships fill one hex, cut off at 30. So seemingly a lot of ships need to be shifted from Kuching to elsewhere.

The red points on the map shows the location of seriously damaged ships (sys damaged >20 or flooding/fire>10) in TFs. The size of the dots is relative to the number of damaged ships.

The Naval Search view in the Map overview tab hints at the coverage achieved by naval search planes. Search areas are painted orange with different amounts of transparency. It takes into accounts the number of planes actually flying (i.e. size of group*search %) for determining the transparency and the range for determining the area to paint (according to some research by Apollo (?) range does not influence search efficiency). Both LBA and ship based planes are included.

On windows this view shows serious flickering, apparently Windows has some problems with painting partially transparent circles. If you want to see this view really snappy, you have to run witpDecoder on Linux.

The support view shows whether your troops are receiving enough support in each hex (independent of base or no base). If the column shown is green, enough support troops are in the hex. If too few support is available, the column is red. The length of the column indicates the amount of the problem but using a quadratic scale (so that also small amount of lacking support will be visible). 15 support too much/too few will fill 1/4 hex, 60 support will fill 1/2 hex, 230 support too much/too few will fill about 1 hex, 500 support will fill 1.5 hexes and more is cut off.



Note that the picture quality is not as bad as it looks from the jpeg files, but there is some problem with a) the fact that the map is basically a blown up version of the small map used by WitP and b) that the green color used is not that well visible everywhere (but there seems to be no unused green tone available).

For me, the tabs showed up, but only the shipyard one showed anything. The search and support just flashed and nothing but the basic map was displayed. I am running it in Windows XP.

You need to read in at least one turn, before it works (the database update updates the schema but can't magically include the content). Windows XP should not be the problem, I'm using that also.

OK, I'll wait for another turn.

Great work Markus! looks very nice Thanks!


Does it suppose to work with ongoing games. I'm getting this error with new version:

Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent AGsShipMustExist table: Ships
java.sql.SQLException: Integrity constraint violation - no parent AGsShipMustExist table: Ships
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at de.retsiemuab.witpDecoder.bt.a(Unknown Source)
at de.retsiemuab.witpDecoder.Q.e(Unknown Source)
at de.retsiemuab.witpDecoder.Q.c(Unknown Source)
at de.retsiemuab.witpDecoder.H.d(Unknown Source)
at de.retsiemuab.witpDecoder.ap.a(Unknown Source)
at de.retsiemuab.witpDecoder.bz.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at de.retsiemuab.witpDecoder.y.a(Unknown Source)
at de.retsiemuab.witpDecoder.b.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at de.retsiemuab.witpDecoder.M.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.main(Unknown Source)

is there any new integrity checks which were missing in previous version?

> OK, I'll wait for another turn.
You can just re-read the last turn. Currently witpDecoder is idempotent (isn't too much mathematics at university a great thing


> Integrity constraint violation - no parent AGsShipMustExist table: Ships
This very much looks as if you have an airgroup which claims to be located on a ship but the ship no longer exists. Since airgroups are in for the first time this is indeed a new integrity constraint. Is there no indication in the log file which group is the culprit so you can check in game? You could also send me a savegame.

BTW, just to be sure: You also do get the Error pop-up window, don't you? I changed the internal workings of those windows, so I just want to be on the safe side.

Much better, thank you Woos. I like the search coverage picture, but the support picture has way too much red. [:D]

The ship repair is very hard to read. Is there anyway in the future you could allow some kind of zoom in function?

Anyway, thank you very much for the decoder, [&o] [&o] it is extremely useful. In fact I will not play a game senario that is not supported by it. It is not worth it.

ORIGINAL: Woos


> Integrity constraint violation - no parent AGsShipMustExist table: Ships
This very much looks as if you have an airgroup which claims to be located on a ship but the ship no longer exists. Since airgroups are in for the first time this is indeed a new integrity constraint. Is there no indication in the log file which group is the culprit so you can check in game? You could also send me a savegame.

BTW, just to be sure: You also do get the Error pop-up window, don't you? I changed the internal workings of those windows, so I just want to be on the safe side.

I have fragments form sunk CV, could they cause the problem? Nothing in the logs to point on them. Yes I'm getting pop-up.

Have sent you everything.

I get a following error:

There is a problem with Airgroup 2371 (F3/Yokosuka Daitai/A) as follows:
Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses
java.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at de.retsiemuab.witpDecoder.bt.a(Unknown Source)
at de.retsiemuab.witpDecoder.Q.e(Unknown Source)
at de.retsiemuab.witpDecoder.Q.c(Unknown Source)
at de.retsiemuab.witpDecoder.H.d(Unknown Source)
at de.retsiemuab.witpDecoder.ap.a(Unknown Source)
at de.retsiemuab.witpDecoder.bz.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at de.retsiemuab.witpDecoder.y.a(Unknown Source)
at de.retsiemuab.witpDecoder.b.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at de.retsiemuab.witpDecoder.M.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.main(Unknown Source)

I can't find F3/Yokosuka Daitai/A in the game - possibly a corrupted ghost unit?

ORIGINAL: Woos

You can update by downloading the updated .jar file, rename it to witpDecoder2.jar and overwrite your current witpDecoder2.jar file with it (you DO need to install witpDecoder0.4.zip first). As always, if your download is not a .jar file but a .zip file, your browser is broken (AKA Internet Explorer) and you should use the right mouse button to download.

I tried downloading both ways and still got a mess of files. Using IE7

I have not been able to use IE to download the necessary files, I use FireFox instead.

Could not create or initialize the databasejava.sql.SQLException: Not all ship classes could be read into witpDecoder. This is probably causedby ship update cycles in the scenario. As a result the database can not be initialized.
The classes which weren't read in are: 402, 1811, 1812
java.sql.SQLException: Not all ship classes could be read into witpDecoder. This is probably causedby ship update cycles in the scenario. As a result the database can not be initialized.
The classes which weren't read in are: 402, 1811, 1812
at de.retsiemuab.witpDecoder.aT.a(Unknown Source)
at de.retsiemuab.witpDecoder.bt.b(Unknown Source)
at de.retsiemuab.witpDecoder.aP.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at de.retsiemuab.witpDecoder.y.d(Unknown Source)
at de.retsiemuab.witpDecoder.i.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at de.retsiemuab.witpDecoder.M.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.main(Unknown Source)

Any help? - Disregard they pointed to empty slots...

Markus, I am getting a similar error to Helpless. The relevant extract from my log as is follows:

"There is a problem with Airgroup 750 (Shinano-1 Chutai) as follows:
Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent AGsShipMustExist table: Ships
java.sql.SQLException: Integrity constraint violation - no parent AGsShipMustExist table: Ships
(etc)"

Our game is CHS 157; from memory v2.06. I imagine Shinano-1 Chutai is the A6M5c component of Shinano's airgroup, but neither this nor any other aircraft in the Shinano AG are yet in production, as our game's date is 1/1/1942 (A6M5c still just a twinkle in Horikoshi's eye [;)]). Shinano's construction has been halted; might that make a difference? Since reference is to a Shinano chutai, can't be due to air unit being orphaned from sunk ship - as yet I've suffered no losses of ships having attached airgroups.

So far as I can see, there's also a problem with the air unit leaders display on my installation. It's showing air leaders (I recognise Fuchida at top of list), but it's not displaying the units they are assigned to command, or their locations. Suspect this may be byproduct of the first error noted above.

Aside from that the update seems to have gone fine except that Naval Search in Map Overview shows nothing, yet Ship Repair and Support Balances are showing fine. Again, this seems likely to be a byproduct of the air unit-related error.

If it will help, I can send you copy of the savefile that is throwing these errors.

Even with these glitches this latest update is a fantastic improvement - thank you very much![&o][&o][&o]

Ditto that.
The message I get:
"There is a problem with Airgroup 1157 (S1/GVT-11) as follows:
Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent AGsShipMustExist table: Ships" etc.

Naval Search shows the map OK with no search circles (and no flickering either under XP).
Everything else is fine.

There is a problem with Airgroup 233 (16th-S2 Chutai) as follows:
Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses
java.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses
 

Everyone's consistency constraints problem should be solved: WitP marks AGs as lost by simply setting their "available Aircrafts" field to 0 (instead as with all other things which get there arrival date set to somewhere in the 70's). I should get more of my carriers sunk. Thanks to Martti for the save.

Fixed version 0.4b is available.

Additionally sunken ships are now retained in the database much more often than before (good for the Ship History). Let's see if that creates new problems.

@Local Yokel
The fact that you did see anything of the new functionality after the failed save game read was another bug. Database rollback was not working as intended. From now on, a failed read does not partially update the database. If you still see leader problems after reading in a save game with the new version, please report.

@Skyros
Downloading the file should work with all browsers. Just press the right mouse button on the link, choose something like "save as" from the menu, really do save (and not pipe it into Winzip or something), make sure the suffix of the file is ".jar" and not ".zip", rename it to witpDecoder2.jar and copy it over your file. Now, using a non-user-goading browser might make things easier

*edit*
The new version also increased the scaling of the overview map (from 2x to 2.3x). This should help a bit with the Ship Repair view without mangling the Naval Search view too much. To actually experience this, you have to delete MainMap.jpg and BigMainMap.jpg from witpDecoder's directory before starting witpDecoder. The files will be recreated.

ORIGINAL: treespider

There is a problem with Airgroup 233 (16th-S2 Chutai) as follows:
Couldn't write things to the DB due tojava.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses
java.sql.SQLException: Integrity constraint violation - no parent ACClassMustExist table: ACClasses

I discovered what is causing this error...in Treespider's CHS the F1M2 Pete Floatplane in Slot 43 Upgrades (Downgrades) to F1M2 Pete Floatfighter in Slot 11 .....and Slot 11 upgrades to Slot 43 ....so players can alternate between the two types of aircraft if they prefer. witpdecoder cannot handle that upgrade path. When I set both slots to upgrade to themselves the program worked fine.