Slitherine

quote:

ORIGINAL: Roger Neilson II

trying to find where to put the nomap command, can't see!

Have tried in separate line on the .bat file in various places, not doing anything.

Roger

quote:

ORIGINAL: n01487477

quote:

ORIGINAL: vonTirpitz

Hello folks.

After upgrading to 1.6 (and reloading all of my earlier turns - ~160 or so) I noticed that the load time had dramatically increased.

I am running Windows 7 (x64) and 64-bit Java ver.6 update 21 with the following command line: c:\Java\jre6\bin\java -Xms512m -Xmx768m -jar "WitPTracker.jar" nomap

Once loaded everything seems to run fine but the load time went from about ~100 seconds to over 1100 seconds. I haven't been successful running 32 bit java on my 64 bit OS and I have increased the memory allocation with no noticeable differences. Any thoughts? Thanks in advance.

Marc

Marc,
I think you are using Java 32 bit as V6.update 21 is a 32 bit build... 64 bit Java doesn't work with Tracker as far as I know.

So you are saying that with 1.5.1 with 160 turns loaded it is faster to start even with the map removed ? That is a mystery ... Floyd and I are looking into optimisation but it will probably take us a while to get it right. Java is not quite the "killer" app builder, but it has come a long way in 10 yrs.

So I guess you'll have to look at optimising your computer's programs on start up ... can I ask for your machine specs please.

To the spectators ... Has Java 6 update 21 slowed down Tracker or have you seen any differences from 20 ?

quote:

ORIGINAL: jetjockey

Bug report:

I've noticed some oddities WRT Tracker's (Excellent program BTW, thanks) "Ships sunk" tab on the Victory Points page.

1) I like to add notes to the page, but the notes will disappear when I read a new turn. If I close tracker and then restart, the notes will reappear.

quote:


2) Sinking reporting: I had a running battle with the HMS Royal Sovereign, first hitting her with two torpedoes on 7/9/42, generating the first sinking report. The 10th and 11th saw more air attacks on her and more sinking reports, but no false sinking report. I finally ran her down with a surface TF and sank her on the 13th. Now here is the really odd part, when I first load tracker the sinking date is listed as the 9th, but when I read a turn the date reverts to the 13th. I'm now to the 17th. BTW: AE lists the sinking date as the 13th.

quote:

ORIGINAL: Rainer79

Hi,
I get a couple of error messages now everytime Tracker starts though I did not notice any oddities in the program itself (yet).

at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Pilots.InsertSmallDelta(Pilots.java:175)
at witptracker.Pilots.InsertInTable(Pilots.java:162)
at witptracker.InMemoryDB.ComparePilotLists(InMemoryDB.java:3003)
at witptracker.ReadTurnTask.doInBackground(ReadTurnTask.java:194)
at witptracker.ReadTurnTask.doInBackground(ReadTurnTask.java:1)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Insert Error code = -65
Table=PilotSmallDelta Values=(32969,520,1,0)
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 witptracker.Database.InsertRow(Database.java:54)
at witptracker.Pilots.InsertSmallDelta(Pilots.java:175)
at witptracker.Pilots.InsertInTable(Pilots.java:163)
at witptracker.InMemoryDB.ComparePilotLists(InMemoryDB.java:3003)
at witptracker.ReadTurnTask.doInBackground(ReadTurnTask.java:194)
at witptracker.ReadTurnTask.doInBackground(ReadTurnTask.java:1)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Insert Error code = -65
Table=PilotSmallDelta Values=(32969,520,3,0)

[...]

quote:

ORIGINAL: KMCCARTHY

V1.6 stopped working after a few successful runs. How can I export the error messages so I can post them here?

quote:

ORIGINAL: Nomad

I have Java 6 level 20 and it seems to be taking a very long time to load the db. the turn loads fine. I had one where after about 6 minutes I just stopped it, I didn't think it would ever finish. I did notice that task manager was showing Java as using about 6-11% of the CPU, and idle using the rest.

quote:

ORIGINAL: KMCCARTHY


See below. I had 1.6 run a few times after the upgrade from 1.51 with no problem. Any ideas?



C:\Program Files\Matrix Games\War in the Pacific Admiral's Edition\WitPTracker A
E Release 1.6>java -Xms384m -Xmx512m -jar "WitPTracker.jar"
WitP Tracker AE tables loaded in 62 seconds
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap spa
ce
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknow
n Source)
at java.awt.image.BufferedImage.<init>(Unknown Source)
at witptracker.MapPanel$Map.<init>(MapPanel.java:354)
at witptracker.MapPanel.<init>(MapPanel.java:193)
at witptracker.GUIMain.CreateAndShowGUI(GUIMain.java:883)
at witptracker.GUIMain$5.run(GUIMain.java:997)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

C:\Program Files\Matrix Games\War in the Pacific Admiral's Edition\WitPTracker A
E Release 1.6>pause
Press any key to continue . . .

quote:

ORIGINAL: floydg

quote:

ORIGINAL: Nomad

I have Java 6 level 20 and it seems to be taking a very long time to load the db. the turn loads fine. I had one where after about 6 minutes I just stopped it, I didn't think it would ever finish. I did notice that task manager was showing Java as using about 6-11% of the CPU, and idle using the rest.

Seems odd. I don't know where it's hanging up...

quote:

ORIGINAL: scalp

All worked fine with Tracker, before yesterday when this mistake suddenly appeared:

Error: problem starting the database. Exiting.
java.sql.SQLExeption: error in script file line:49 S1000 General error...

It was ok fot 180 turns, with many different AE Tracker versions.

Any advice?

quote:

ORIGINAL: scalp

Is there any way to fix it?! I need all that data. I think the problem is about trackerdb.data file.
Actually everything works fine if its just installed,but i dont see my previous turns info.

quote:

ORIGINAL: seille

Just found a little "bug".

Industry screen:
When i try to sort for "oil produced" it doesn´t sort in the right order.
For other columns like "oil stored" or "oil use" it works.

quote:

ORIGINAL: Judykator

Suddenly I can not run ....

quote:

Ran out of memory. See http://sites.google.com/site/witptracker/support in the Java Memory Issues section.

quote:

ORIGINAL: witpqs

Absolutely love the new version. The 'Base Load' calculation is priceless for figuring out island garrisons.

One little glitch. Twice now, a few turns apart, Tracker has erroneously reported that zillions of my ships upgraded. See screenshot below.

FYI, I started a new Tracker database with the new Tracker code release.

EDIT TO ADD: In case I am being unclear, the list went on for pages on end and might have included all of my ships!

quote:

ORIGINAL: n01487477

quote:

ORIGINAL: witpqs

Absolutely love the new version. The 'Base Load' calculation is priceless for figuring out island garrisons.

One little glitch. Twice now, a few turns apart, Tracker has erroneously reported that zillions of my ships upgraded. See screenshot below.

FYI, I started a new Tracker database with the new Tracker code release.

EDIT TO ADD: In case I am being unclear, the list went on for pages on end and might have included all of my ships!

Thanks witpqs,
we know about it and it will continue every 5 turns until we release an interim (soonish) ... a bit of an oversight by us ~ sorry;
The error comes from us trying to improve the start up times which we applied to the Ship set...

quote:

ORIGINAL: vonTirpitz

WitPTracker AE Release 1.6

I was wondering if you could help me figure what I am seeing here.

In the Engine/Aircraft Planning Screen I am seeing the Ki-46-II Dinah (ID 782) appear in both the Mitsubishi Ha-31 (correctly) and Ha-33 (incorrectly). The planning numbers appear to be okay but the Ueng column shows 242 and 243 respectively. There appears to be a couple of other planes that also list incorrectly on the Ha-33 screen such as the A6M5c Zero (616), A6M7 Zero (617), D4Y2 Judy (650) and Ki-61-II KAI Tony (813).

The Ha-31 screen shows the Ki45 KAIa Nick (775), Ki45 KAIb Nick (776) which use the Ha-35 engine and Ki-57-I Topsy (805) which uses the Ha-5.

The B6N1 Jill (630) and P1Y1 Frances (721) appear on the Ha-32 screen as well as their proper places under the Ha-44 and Ha-45 screens.

Does all this perhaps have something to do with the upgrade paths?

P.S. FYI the latest java patch seems to have reduced the load time problem I was having. I still notice an improved load time after the initial (i.e. closing the program and running it again) which I attribute to caching perhaps. It doesn't seem to be as bad as it was (10 minutes down to 2).

Thanks again for all the hard work and support!