WitpDecoder; Now providing some overview

[siRkid]

You know I'm really interested in this utility but reading this thread make me think you have to be an IT expert to install and run it. [:(]

[Roger Neilson II]

It sounds harder than it is..... its a bit like following a recipe for a meal, provided you do things exactly as listed it works, and the new version is easier to install... follow the readme and you should be fine. And if you are not then simply post here - I did and got the help I needed.

Roger

[Woos]

ORIGINAL: VSWG
I think everything will become clear once you open the attached example files. Use Editor, or WordPad, or MS Word, or any other program able to open text files.

I would even suggest to use your favorite spreadsheat program to open them (both Excel and OpenOffice are able to open .csv files). This saves you the problem of keeping the syntax correct. And it looks much nicer formatted as a spreadsheet. Just remember to save as .csv again. And keep a backup copy. witpdecoder will delete the "basename" column during database compaction as it is unused by it.

BTW, someone stated that the example files also work for other scenarios than 192. That may well be true but did you check if the numbers are correct? There is no error indication if a base located in Japan in your scenario is assigned to the Indochina cluster.

And if you consider editing the cluster/clusterbases.csv file by hand to difficult, you could plead e.g. Andrew Brown to write a program which creates these files automatically. It's mainly a map problem and less a save game problem. (Haehae, hot potato dropped into someone else's lap *evil grin*)

Oh, and the next version will give VSWG a taste of the problems to come with the database dump feature. I had to split the "ShipStatus" table into three ("Ships", "ShipStatus" and "ShipBuildqueue") to get the Ship History tab finally implemented. You might start to think on how to do JOINs in spreadsheets.

[eloso]

ORIGINAL: Woos
BTW, someone stated that the example files also work for other scenarios than 192. That may well be true but did you check if the numbers are correct? There is no error indication if a base located in Japan in your scenario is assigned to the Indochina cluster.

I checked and the numbers don't match for the Base IDs. [:-] I'm making one for CHS 2.08 scenario 160 at start for the allied side.

[ctangus]

Does anyone have cluster files for the Japanese for any of the CHS 2.08 scenarios? (I think the base ID #s are the same for all 6 scenarios.) I could do them myself this weekend, but I can be a lazy SOB & would rather take advantage of someone else's hard work. [:D]

Woos - it keeps getting better and better. [:)]

[jcjordan]

Just do what I did & it only took a few minutes to do - use witpload to create the csv files (or use the ones witpdecoder makes) & go into the location csv file & select the columns for the base # & name (just for ref) & then copy them over to a blank (or use Woos' file as a template) csv file. After copying it over delete the blank & area named lines seen in the file as well as base names leaving only the base #, then assign the group # to each base you want for the cluster.csv file to use. Took me about 10min as I wanted a different cluster setup than what Woos had in his. At work now w/o laptop so can't get file.

[FeurerKrieg]

I finally finished up my CHS 160 Japanese cluster files. If anyone wants them just PM me. Nothing fancy, but they do work properly at least. Using a couple Phillipines bases as the 'extra' cluster that gets dropped by the decoder.

[Woos]

Yes, and FeurerKrieg also mailed the basecluster files to me, so you can dowload them directly (although without any guarantee from me, since I don't even have CHS installed).

Thanks Feurer.

In other news, progress on V0.3c (aka pre-0.4) is crawling slowly. I had to play a bit of Oblivion in the mean time just to see how far technology has come since Morrowind. No longer do all Monsters have to look angular. Plus, it seems everyone (except Nemo) is happy with current witpDecoder without finding new bugs (in the tool or in the save files) so I don't want to tempt fate by releasing a new version.

Have fun

[George Patton]

I'm running since weeks witpload as japanese and I encountered any problems.
But as allied, it's not working at all.

This is the message that I got:

[Woos]

You seem to be using V0.3 and not V0.3b which catches the savegame inconsistency you have and tells you which LCU is preparing for a non-existing base. Get it either from a few pages earlier with explanation or from http://extweb.retsiemuab.de/witp/witpDecoder3b.jar without (and overwrite the old witpDecoder2.jar with it. Maybe you loose the database if you do, see some pages earlier).

BTW, let me guess, your are from Tessin. Interesting to know that HSQLDB contains localized error messages.

[rtrapasso]

How about adding your download site to the stickied "Links for WITP Sites" above (in the stickied section...)??

[Rainer]

ORIGINAL: rtrapasso

How about adding your download site to the stickied "Links for WITP Sites" above (in the stickied section...)??

Yes, please [&o]

[Oliver Heindorf]

and where is an update pleeeeaaase [:'(][:'(][:'(][:'(]

[George Patton]

ORIGINAL: Woos

You seem to be using V0.3 and not V0.3b which catches the savegame inconsistency you have and tells you which LCU is preparing for a non-existing base. Get it either from a few pages earlier with explanation or from http://extweb.retsiemuab.de/witp/witpDecoder3b.jar without (and overwrite the old witpDecoder2.jar with it. Maybe you loose the database if you do, see some pages earlier).

BTW, let me guess, your are from Tessin. Interesting to know that HSQLDB contains localized error messages.

Oh yes. This was the problem. Now it's fixed. Danke. The only strange things that I can see is japanese engines in storage area.
Yes I'm writing from Tessin. [:'(]

[Roger Neilson II]

Ok, I have this working no problem on a vanilla install. So I have now re downloaded the required files and set them up as before.

Now when I run witpupload I get the following message, the fiels are in the right places, the scenario is there....

[morphin]

Hi
I try to initialize scenario 065 RHS and i get the following error:
-------------------------------------------------------
Could not create or initialize the database

java.sql.SQLException: Integrity constraint violation - no parent ShipsUpgradeOnlyToExistingTypes table: ShipClasses
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.aW.a(Unknown Source)
at de.retsiemuab.witpDecoder.aF.a(Unknown Source)
at de.retsiemuab.witpDecoder.aW.b(Unknown Source)
at de.retsiemuab.witpDecoder.aA.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at de.retsiemuab.witpDecoder.s.c(Unknown Source)
at de.retsiemuab.witpDecoder.f.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.F.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.main(Unknown Source)

Couldn't set up a working DB template. Bad, Bad.
--------------------
Where do i have to start for checking the ShipClass data? What does "no parent ShipsUpgradeOnlyToExistingTypes table" mean?
Thank's
Morphin

[morphin]

I don't understand the import process from this utility. i had a look at the witp.log file. it is quite SQL. So i try to reproduce it on my SQL Server 2005 Database. it works with some modification quite well. So the last lines from this log is something like this:

-----------------------
INSERT INTO "ShipClasses" VALUES(1459,20,'Medium APA (USN)',18,20,35,12000,0,0,0,0,0,0,0,0,NULL,0,0,'',NULL,NULL,NULL,6,43)
DELETE FROM "ShipClasses" WHERE "shipclassID"=1459
-----------------------------------
So it tries to insert shipclasses. What's strange is that the upgradeClass column for the shipclassID=1459 is empty (''), but on the WITPcls.csv file it is not empty (it is shipclassid=1459)!. So the importprocess removes some content of the shipupgradeClass column, but why?

Morpin

[George Patton]

Here we are again. I have witpdecoder working for one game on which I play as allies but in the second game, always as allies there is no way to run it. Same installation, exactly the same, but here is what I have as messages window. (I have copied witpdecoder3b.jar in place of witpdecoder2.jar).

[Roger Neilson II]

ORIGINAL: Roger Neilson II

Ok, I have this working no problem on a vanilla install. So I have now re downloaded the required files and set them up as before.

Now when I run witpupload I get the following message, the fiels are in the right places, the scenario is there....

I sorted out the witpload issue and now I have the scenario files dumped as per requirement. So now I run the witpdecoder.bat which has exactly the same syntax as my vanilla one, except the password is different...... as so:

echo off
REM java -Djava.library.path=%CD% -jar witpdecoder2.jar PasswordHere
java -Djava.library.path=. -jar witpdecoder2.jar 3 PASSWORD
pause


it runs and I get the display. I then go to point to the file to use and it gives me the following message.... I get this whether I am trying to point to a completed file that has been sent to my opponent, or to an uncompleted file:

[Woos]

@George Are you using any non-standard scenario? CHS is known not to work with 0.3b.

@Roger I am a bit mystified at the version you are using. Somewhere around 0.3a (or was it 0.3b) the generation of the .cvs files was automated (for you among others). Also you no longer had to specify the fact that you played allied in the witpdecoder.bat file. If you are Allies and using an older version you have to specify it there, otherwise witpdecoder will try to use your password for the Japanese side, where it won't work.

Other than that I have no suggestions as there are no known password-related bugs (unless of course your password is containing special characters or a blank).