Page 11 of 29
RE: witpDecoder for the Allies
Posted: Fri Dec 08, 2006 5:54 pm
by saj42
ORIGINAL: herwin
Is CHS 2.0 compatible?
Has anyone developed the cluster and clusterbase files for the 15x series of scenarios?
I'd like files for s157 - I can't get mine to work [:(]
EDIT: downloaded original clusters-example CSV file and renamed it - now works like a dream[&o] - except the missing last cluster [;)]
RE: Why using a DB with integrity constraints is usefull
Posted: Fri Dec 08, 2006 6:00 pm
by Woos
ORIGINAL: Feurer Krieg
Does this mean that if you adjust your clusters mid-game (say by clearing the China rail line and connecting Manchuria to Indo-China in one big cluster) that you will lose all the data you have read in up to that point, since you would need to erase the witp.* files?
Well, I never said editing the cluserbases.csv file mid-games was supported.
But actually it is [;)]
If you start a new database without clusters.csv and clusterbases.csv available, any file you add later will be ignored. In that case you have to reinitialize the database to get the Industry tab to work.
If you started the database with the files available, you can edit them afterwards (while witpdecoder is NOT running) and the changes should be used from then on. Note that this feature is completely untested.
BTW, another known bug: Resource display in the Storage tab is broken.
BTW2, V0.3 will probably be released this weekend which will include a more easy setup mechanism (at least if I get the jiglo SWT GUI editor to work more reliably).
RE: Why using a DB with integrity constraints is usefull
Posted: Fri Dec 08, 2006 6:19 pm
by RAM
woos, any idea on what is happening with the SYS_FK_104 table error I quoted above?
I simply can't get the utility to load my saved games

...
RE: Why using a DB with integrity constraints is usefull
Posted: Fri Dec 08, 2006 6:27 pm
by herwin
Are you enjoying eclipse? I teach a final year class using it.
RE: Why using a DB with integrity constraints is usefull
Posted: Fri Dec 08, 2006 7:22 pm
by saj42
Where is link to the 2b version?
The link on post 141 only gives me the 'de' and 'META-INF' folders no replacement witpDecoder2.jar file (so i've no ship classes tab and last cluster is missing). Reloaded from link in first post and this gives me a witpDecoder.jar file with 19/11/06 date stamp.[&:][&:][&:]
RE: New tool: WitpDecoder; No more spreadsheets!
Posted: Sat Dec 09, 2006 6:55 pm
by shangrila
Hi everyone perhaps a person that got the Allied to work could help?
I have extracted the WITP files. I am using 2b and when running it I am getting an error. Been working on this for an hour or so.
Some DB problem during Storage Tab initialization. Nothing will be shown!
java.sql.SQLException: Column not found : appearingFuel in Statement [SELECT SUM("appearingFuel"), SUM .... then continues through the SQL DB call...
Any help greatly appreciated!
Thank you in advance.
RE: New tool: WitpDecoder; No more spreadsheets!
Posted: Sat Dec 09, 2006 7:30 pm
by shangrila
Now I'm getting
C:\Matrix Games\War in the Pacific\SAVE\Ana>echo off
WitP-Decoder V0.2b (C) 2006 by M.Baumeister. Please wait!
Couldn't set up a working DB template. Exiting.
Press any key to continue . . .
All files are in the directory listed. All files have been reinstalled in this directory. (Application, WITP, Save games(not that I can get there yet [:)] etc)
Any help would be cool, again thanks in advance!
RE: Why using a DB with integrity constraints is usefull
Posted: Sat Dec 09, 2006 7:34 pm
by VSWG
ORIGINAL: Tallyho!
Where is link to the 2b version?
The link on post 141 only gives me the 'de' and 'META-INF' folders no replacement witpDecoder2.jar file (so i've no ship classes tab and last cluster is missing). Reloaded from link in first post and this gives me a witpDecoder.jar file with 19/11/06 date stamp.[&:][&:][&:]
The link works for me...
Anyway, check your PMs, I've sent you the file which I'm using for my Allies PBEM.
RE: Why using a DB with integrity constraints is usefull
Posted: Sat Dec 09, 2006 7:36 pm
by VSWG
shangrila,
are you deleting all witp.* files before every try to initialize the DB again?
RE: Why using a DB with integrity constraints is usefull
Posted: Sat Dec 09, 2006 8:55 pm
by shangrila
Thank you, I had missed a file!
All is working.
Nice tool.
V0.3 released
Posted: Sun Dec 10, 2006 11:48 pm
by Woos
OK, everyone's patience has finally paid (you were patient, weren't you?): The V0.3 release is ready. Find it in the first post.
Everyone complaining about complicated set up can rejoice and frolic (no, I don't mean you should start eating the dog food), V0.3 does most of the things automatically (hopefully). You will
all come to love the highly sophisticated (*cough*) automatic setup routine since V0.3 does change the database schema and you thus need to re-setup the database. V0.4 will do again.
Everyone having problems with inconsistent save games can join all the frolicing. While playing around with V0.3 to test it for the Allies I found quite a bit of inconsistencies (the game really likes to corrupt Allied TF records). That's actually the reason for the late release. But also Allied save games should now read into witpDecoder without an exception every other time.
Everyone hoping for new functionality probably has to wait for merrier days to do the rejoicing, the above ate quite a bit of time. So the only new functionality over 0.2b (which is no longer available) is the resource history tab (which also took quite a bit of time). See below.
And since now christmas is nearing, cookies need to be baked, presents to be made, etc. you are expected to find no more bugs and live happyly with the current functionality for the rest of the year.
RE: V0.3 released
Posted: Mon Dec 11, 2006 1:05 am
by ctangus
Outstanding! I
tried to be patient, at least... [:)]
I did found a minor bug. I'll mention it now, only because I might forget to later. If you never fix it your tool is still fantastic.
On your LCU targets tab, every unit is listed as being on ship, when mostly they're not. This is with two different games - both as Allied PBEM. Here's a screenshot. It would be hard to load that many Chinese units onto ships:
Get to this if & when you can & enjoy your holidays! [:)]
RE: V0.3 released
Posted: Mon Dec 11, 2006 12:34 pm
by RAM
....still gives me error when I try to load a savegame...
Still haven't been able to use this magnific tool in my PBEM

RE: WitpDecoder; Now also for allies
Posted: Mon Dec 11, 2006 12:43 pm
by m10bob
ORIGINAL: Woos
As discussed
elsewhere I was a bit displeased with the GUI of WitP which doesn't deliver lots of necessary information at all or only after several clicks (and thus hint at Mr. Grisby being a quite bad UI designer).
Solution a first: Maintain several spread sheets by hand. Bad. Why am I doing work a computer is much better at.
Solution now: WitpDecoder!
WitpDecoder will read your savegame file, extract information into an SQL-Database, collect it over several turns and display it in a (hopefully) easily accessible way to you. Currently it provides:
- Overview of stocks, production, usage, ... of all 'strategic resources' like engines.
- List of units moving and/or preparing for a certain base (basically impossible to get that in-game since all units on ships vanish from the in-game lists)
- List of leaders with all attributes shown and custom rating formulas defineable
- List of ships to be updated at a date (and their current location)
- List of ship classes to select the best ones for a TF.
- List of leaders assigned to more than one unit/TFs and other inconsistencies (Yeah, you finally can see the leaderbug

And all that for not 10, not 7, not 5, no only 2.6 MB download from
http://extweb.retsiemuab.de/witp/witpdecoder.zip (most of it used up by the SWT and HSQLDB jar files and libraries). More instructions in the
witpDecoder-docs.pdf file (also in the .zip file).
Now updated to V0.3 which is the first "full release" (including docs & Co) supporting also Allied players. Has an easier setup (no work on the command line should be necessary anymore), a resource history and a ship classes tab. Just download the above zip file.
Previously V0.2 brought better handling of CHS and dot bases as well as a working Industry&Spoilage tab. Also removed the need to copy error reports from the console, they are written to witpdecoder.log.
Below some screenshots to wet your appetite.
Oh, before I forget. Some restrictions.
- You need Java 1.5.
- This is an early release. Expect bugs. And expect database changes in future versions to come without an automatic upgrade mechanism (so keep your safe files).
- Do use the "Quit" menu to leave (and not the "Close Window" X-button). Otherwise the database will never clean up and things will quickly become awfully slow.
- Reading in a save file is slow with only minimal feedback. Don't despair. It does not hang. Really. Remember, you need a fast computer for WitP anyway

Known bugs:
- Coral Sea Scenario does not work with witpDecoder (and probably never will). It uses the Truk base as Headquarter for Truk Base Force, which can not easily modeled within witpDecoder.
Thank you Markus..I would like to send you a big box of Quark, but we don't have it in the stores over here![8|][:)]
RE: WitpDecoder; Now also for allies
Posted: Mon Dec 11, 2006 1:37 pm
by JamesM
Markus,
I am still getting errors,

RE: WitpDecoder; Now also for allies
Posted: Mon Dec 11, 2006 3:17 pm
by Toddr22_slith
Marcus I am getting the following errors.

RE: WitpDecoder; Now also for allies
Posted: Mon Dec 11, 2006 6:37 pm
by Oliver Heindorf
works now !

one little thingy : I load one of my pbems and I get a zillion leader error messages...but alot of them are from not-yet-received ships

and some of them are from LCUs I never heard of
RE: V0.3 released
Posted: Mon Dec 11, 2006 7:32 pm
by Woos
ORIGINAL: ctangus
On your LCU targets tab, every unit is listed as being on ship, when mostly they're not. This is with two different games - both as Allied PBEM. Here's a screenshot. It would be hard to load that many Chinese units onto ships:
Strange, the only reasons I can see for that in the code is either the units having a non-existing suffix (which doesn't seem to be the case guessing from the screenshot) or walking to a non-existing base. Can you send me savegame, .csv files and password, you should have my e-mail already.
@RAM: looks like an unkown save game inconsistency, can you please sent me the files mentioned above, e-mail adress is on its way.
@m10bob: Well, I like ice-cream better than quark anyway. Although there might be an even worse transport problem with that
@jamesm You are obviously lacking the ships4history.csv file. It's in the witpdecoder.zip file.
@toddr22 Never seen that but I very much suspect that you are using a java version before 1.5. Get 1.5 from the URL mentioned in the docs (note that in an attempt to pass through version numbers quicker Sun actually calls java 1.5 "Java 5"). The latest version (1.6 resp. 6) should also work, but I didn't test it.
@Oliver Sorry, all your ships are read in and all your ships have leaders assigned in the save games (even those in the build queue). I would suspect that if a leader dies, he is not removed by the game as commander of the ships in the build queue and thus generates an error by witpdecoder. Would be interesting to see, if some existing leader is assigned to a ship when it is finished or if it stays with an empty leader.
In principle the DB schema already contains a special table for shpis in the buildqueue (on which much less information is required by witpdecoder), but it is currently not used and all ships are in the main ship table. Will not be changed any time soon, your best bet is to use the "Cancle" button to get rid of the pop-up.
Same problem probably with the LCU. Dead leader assigned to a replacement LCU.
RE: V0.3 released
Posted: Mon Dec 11, 2006 9:14 pm
by JamesM
Markus,
It is saying it is a leadership bug issue.
RE: V0.3 released
Posted: Mon Dec 11, 2006 9:29 pm
by treespider
I have the same LCU on ships issue....only from a Japanese perspective.
In addition -
when I first ran v0.3 I initialised as stated in the user guide. Then when I loaded my first save I clicked 'Cancel' on the first inconsistancy pop-up and the programmed CTD. Then when I re-opened the program again I found the the save was already loaded. When I loaded my second save I decided not to click 'Cancel' as I figured that was the source of the CTD. So I clicked on 'Yes' on the first inconsistancy popup and it CTD again. However when I re-opened the program I found the second save had been loaded.