Page 12 of 29
RE: V0.3 released
Posted: Mon Dec 11, 2006 10:24 pm
by Woos
@james Huh? Your screenshot clearly says that you are missing a file and are not having leaderbug problems.
*edit* I think I found treespider's "CTD" (which is no "crash", there will be an exception backtrace in witpdecoder.log) as well as the "all units are on ships" problems of ctangus. Actually I suspect ctangus also had a "CTD". Because everyone has who created a new database with V0.3.
One of the last changes I did yesterday introduced dummy base 32767 which is located at position, you guessed it, 32767/32767. It's needed to replace the missing home harbour of some Allied TFs.
Now witpdecoder also contains a routine to generate an array of which hex is next to which base. That generation process runs once the first save game was read in (didn't do that yesterday evening) and really does not like it when a base is located far outside the pacific (like in hex 32767,32767). Fixed in the newly uploaded release. Everbody should redownload. No need to reinitialize the database, the "everyone is on ships" should fix itself once the next save game is read in.
RE: V0.3 released
Posted: Tue Dec 12, 2006 5:08 pm
by Seeadler
Woos,
I'm getting the same error message as RAM. Do you have any idea already?
ORIGINAL: 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: V0.3 released
Posted: Tue Dec 12, 2006 9:54 pm
by Oliver Heindorf
thanks Woos ! [&o]
RE: V0.3 released
Posted: Tue Dec 12, 2006 11:03 pm
by saj42
Woos
This keeps getting better, now patched to V 0.3 - but I'm still having 'a senior moment'.
I've got the 'ship classes' tab now [:)]
I'm not getting 'foreign leaders' reported anymore (and I had 5 under V 0.2) [:(]
I'm not getting the LCU prepping showing as all 'on ship' (ctangus problem) [;)]
Enjoy the holiday season and look forward to more in the new year.[&o]
RE: V0.3 released
Posted: Tue Dec 12, 2006 11:44 pm
by Woos
ORIGINAL: Seeadler
I'm getting the same error message as RAM. Do you have any idea already?
RAM's problem is that the "Portland Base Force" (LCUID 2156) is preparing for base 299. To bad, because base 299 is non-existant (located in the list between Magwe and Christobal). Now there are IMHO three explanations for this:
1) random corruption by WitP
2) bad prep Target assigned by mod in scenario definition
3) Mod has manipulated base list and the AI is prepping that unit for a fixed (and now empty) baseID.
IMHO 1) is not probable because I got an error report PMed from OSO which concerned the same LCU with the same exception. He BTW send me the ASCII output from the witpdecoder.log file which a) take less space than the screen shots and b) contains an indication which unit has a problem (so people can have a look themselves at those units in-game or in the mods .csv files)
3) is improbable because RAM is playing as the Allies and the LCU is also an allied unit.
That leaves 2) as most probable reason: we have another problem with CHS (in addition to the torpedo inflation). Can someone check the CHS scenario files what Portland Base Force is prepping for? I don't have that scenario here.
Next version will fix the problem, for now just assign a different prep target to Portland Base Force (and if that doesn't help have a look in the witpdecoder.log file, which LCU is causing the problem).
BTW, is someone reporting these errors to CHS?
RE: V0.3 released
Posted: Tue Dec 12, 2006 11:58 pm
by VSWG
ORIGINAL: Woos
That leaves 2) as most probable reason: we have another problem with CHS (in addition to the torpedo inflation). Can someone check the CHS scenario files what Portland Base Force is prepping for? I don't have that scenario here.
Portland Base Force is prepping for LocID 299, which is indeed an empty slot in CHS.
BTW, is someone reporting these errors to CHS?
AFAIK there's no new release of CHS pending, but I'll keep this thread in mind should Andrew ask for bugs. I think he's checking this thread himself, too.
RE: V0.3 released
Posted: Wed Dec 13, 2006 2:12 am
by RAM
thanks a lot Woos. Looking forward the fixed version
and, reporting the errors to CHS is a bit tricky now as I think its no longer supported as the main developer stopped working on it...
RE: V0.3 released
Posted: Wed Dec 13, 2006 3:58 am
by RAM
I manually changed portland base force's target base to Portland itself in my savegame, saved the game, and tried to open the saved game with WITPdecoder.
It worked [:D]
Thanks again, Woos...and thanks for the tool itself it will really help in my games from now onwards [&o]
RE: V0.3 released
Posted: Wed Dec 13, 2006 4:09 am
by jcjordan
Woos now getting this error on a new savegame, need me to send you anything or can you tell me where to look? I've not deleted anything this time [:-]
Could not create or initialize the database
java.sql.SQLException: Numeric value out of range
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.
RE: V0.3 released
Posted: Wed Dec 13, 2006 5:52 am
by AU Tiger_MatrixForum
I figured I would wait for an upgrade or two before I downloaded. I finally did it, and now I am perplexed. I am in December, 41 as the Allies so now I have the added PP load (stock) of removing G. Boyington from command of a DD amongst many others... Very nice work by the way. I also liked the touch in the manual about not understanding "the above paragraph." I didn't. When can I sign up for lessons? [:D]
RE: V0.3 released
Posted: Wed Dec 13, 2006 8:35 am
by Andrew Brown
ORIGINAL: VSWG
AFAIK there's no new release of CHS pending, but I'll keep this thread in mind should Andrew ask for bugs. I think he's checking this thread himself, too.
I do look in from time to time and I have seen the references to the two errors. By all means keep reporting them if any more are found.
Thanks,
Andrew
RE: V0.3 released
Posted: Wed Dec 13, 2006 11:02 pm
by eloso
ORIGINAL: Woos
ORIGINAL: Seeadler
I'm getting the same error message as RAM. Do you have any idea already?
RAM's problem is that the "Portland Base Force" (LCUID 2156) is preparing for base 299. To bad, because base 299 is non-existant (located in the list between Magwe and Christobal). Now there are IMHO three explanations for this:
1) random corruption by WitP
2) bad prep Target assigned by mod in scenario definition
3) Mod has manipulated base list and the AI is prepping that unit for a fixed (and now empty) baseID.
IMHO 1) is not probable because I got an error report PMed from OSO which concerned the same LCU with the same exception. He BTW send me the ASCII output from the witpdecoder.log file which a) take less space than the screen shots and b) contains an indication which unit has a problem (so people can have a look themselves at those units in-game or in the mods .csv files)
3) is improbable because RAM is playing as the Allies and the LCU is also an allied unit.
That leaves 2) as most probable reason: we have another problem with CHS (in addition to the torpedo inflation). Can someone check the CHS scenario files what Portland Base Force is prepping for? I don't have that scenario here.
Next version will fix the problem, for now just assign a different prep target to Portland Base Force (and if that doesn't help have a look in the witpdecoder.log file, which LCU is causing the problem).
BTW, is someone reporting these errors to CHS?
This worked. I got a few other warnings and notices but the file loaded successfully after changing the prep target for the Portland Base Force.
Note that this applies to CHS 2.08 scenario 160.
Thanks,
Oso
RE: V0.3 released
Posted: Thu Dec 14, 2006 12:43 pm
by Likendeeler
Great tool and it´s working for most of my saves. But not for my own PBEM-scen (probably my own fault) .
Got this message and couldn´t find a hint in this thread. Anything that can be fixed here?
Could not create or initialize the database
java.sql.SQLException: S1000 General error java.lang.NumberFormatException: For input string: "laude""" in statement [
SET TABLE WITPAIRCRAFT SOURCE "WITPair.csv;ignore_first=true"]
RE: V0.3 released
Posted: Thu Dec 14, 2006 5:23 pm
by VSWG
ORIGINAL: Likendeeler
Great tool and it´s working for most of my saves. But not for my own PBEM-scen (probably my own fault) .
Got this message and couldn´t find a hint in this thread. Anything that can be fixed here?
Could not create or initialize the database
java.sql.SQLException: S1000 General error java.lang.NumberFormatException: For input string: "laude""" in statement [
SET TABLE WITPAIRCRAFT SOURCE "WITPair.csv;ignore_first=true"]
Could it be that the Claude is missing the 'C' in your scenario? Just a wild guess...
RE: V0.3 released
Posted: Thu Dec 14, 2006 7:12 pm
by Rainer
Hallo Herr Baumeister,
works beautifully for the Allies against AI Japanese (Scen 15, no mods, Game Date June 4, 1943).
The
setup now is a breeze, so everyone hesitating because of the seemingly fuzzy setup of past versions should now join.
Woos has done a great job, me thinks
One minor detail. Under "Inconsistencies" three ships are listed which actually do not (yet?) exist in the game: 594K, LCI-66 and Token. The ships are listed to have "none" or "foreign" leaders because of the leader bug.
Actually, I was surprised to see only three occurrences of this.
Thanks so much for this beautiful tool (and the GREAT potential within!) and
Frohe Weihnachten
Cheers
Rainer
RE: V0.3 released
Posted: Thu Dec 14, 2006 8:47 pm
by Likendeeler
Good guess!
The C wasn´t missing but I was using quotation marks for the nicknames ("Claude") and forgot computers didn´t like them.
Never had problems with them during the game.
Thank you, I really couldn´t imagine what "laude""" meant [:)]
It´s working now.
RE: V0.3 released
Posted: Thu Dec 14, 2006 10:59 pm
by Woos
ORIGINAL: Rainer
One minor detail. Under "Inconsistencies" three ships are listed which actually do not (yet?) exist in the game: 594K, LCI-66 and Token. The ships are listed to have "none" or "foreign" leaders because of the leader bug.
Actually, I was surprised to see only three occurrences of this.
That's WAD. Since those ships might become problems when being ready, they are already in the list. Of course if the popular opinion is to not have non-ready ships in the Inconsistency list, that's just about 20 characters to add to the programm (but you will continue to have them in pop-up requesters). And you are already the second one to complain.
Likendeeler
Could not create or initialize the database
java.sql.SQLException: S1000 General error java.lang.NumberFormatException: For input string: "laude""" in statement [
SET TABLE WITPAIRCRAFT SOURCE "WITPair.csv;ignore_first=true"]
And VSWG continues to solve most support request before I even reach the computer. [:)]
As background information: That error indicates that HSQLDB is not able to parse the .csv file mentioned. As you already found out, it is a bit picky about the .csv format. Nothing I can nor intend to change. As long as you don't hand-edit the .csv files everything should be fine.
RE: V0.3 released
Posted: Thu Dec 14, 2006 11:25 pm
by VSWG
I guess it cannot hurt to earn some brownie points before we enter the 'feature request phase'. [:)]
There will be a 'feature request phase', right? Right?!
[;)]
RE: V0.3 released
Posted: Fri Dec 15, 2006 3:13 am
by FeurerKrieg
Okay, I'm still trying to get my 'main' game to load. I have been able to load my CHS 160 as well as my 3x3 PBEM. But this last is eluding me.
First it wouldn't load because the oil and resources had turned into factories producing invalid items (devices that are normally created with Armament points). So first, thank you Woos, your utility found that error. Then wonderful Matrix guys [&o] fixed my save file so that oil and resources were back at Anshan.
Now I get this error, my guess is it is something in the game that maybe I can fix, similar to RAM's preparation thing, except it has something to do with leaders maybe?
Couldn't write things to the DB due to
java.sql.SQLException: Integrity constraint violation - no parent LeadersCommandAbilityMustExist table: CommandTypes
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.at.a(Unknown Source)
at de.retsiemuab.witpDecoder.ae.a(Unknown Source)
at de.retsiemuab.witpDecoder.ba.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at de.retsiemuab.witpDecoder.s.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.F.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.a(Unknown Source)
at de.retsiemuab.witpDecoder.Main.main(Unknown Source)
RE: V0.3 released
Posted: Fri Dec 15, 2006 3:48 am
by jcjordan
Markus fixed the 5in rocket problem & program now runs but I've now got the same problem in post #165 yet if I load scenario into editor it's correct & the error shouldn't occur.
One minor thing I've also noticed is that when I change something in the WITP database editor it shows my changes but when decoder exports it the changes aren't there & it's reverted back to the old data??? I can manually export the data files with witpload & make the changes then import it back & they're fine & redo decoder. It's like for some reason the WITP DB Editor no longer has authority to change things even though I save it when done...scratching my head on that one [&:]