I just downloaded Update 19 and Tracker still works ... I'll do some testing soon with 100 + turns and see what I can do on my end ... as Floyd says sorry guys ... for now [;)]ORIGINAL: michaelm
Maybe it might be an idea to try using an earlier JAVA version (like 17). Update 18 broke witpstaff. Update 19 has come out recently.ORIGINAL: floydg
ORIGINAL: castor troy
Hi
had an automatic java update and now it seems I made it that tracker isn´t running anymore. [:(]
any clue what I should do?
These memory issues are starting to stump me (like I have no clue on Nomad's issue). For your case, perhaps try increasing the memory values in the .bat file by 64 or 128 until it starts working again.
Sorry...
Floyd
I think I have suggested how to run multiple copies of JRE on the same machine. You could in theory install under the tracker directory and point to it there.
WitPTracker AE News
Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition
RE: WitPTracker AE Release 1.0
RE: WitPTracker AE Release 1.0
Just in case the info helps, I got the auto Java update and my Tracker is still working fine. I am running XP 32-bit all the latest service packs, patches, etc.
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: WitPTracker AE Release 1.0
I had to restart one games tracker but my second game with a few less turns is still working. I have no idea what is happening.
RE: WitPTracker AE Release 1.0
I need to report that my problem has been solved but I am not entirely sure what happened. When I tried to load my second turn in the game shown above I again got the not enough memory error. I then copied both the bat and jar files from my second game to this game and it worked fine. [&:]
RE: WitPTracker AE Release 1.5.1 Available
This a great management tool for WITP. Thank you for sharing and keep up the good work![&o]RE: WitPTracker AE Release 1.5.1 Available
On the ship tab, when I filter to AP, APAs do not show up.
RE: WitPTracker AE Release 1.5.1 Available
ORIGINAL: Nomad
On the ship tab, when I filter to AP, APAs do not show up.
It will next release... [:D]
Delete the trackerdb.* files.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
RE: WitPTracker AE Release 1.5.1 Available
In WITP/AE Tracker, I saw several messages about allied R&D date advances for new aircraft? I thought only Japan got advances for R&D and allied got new aircraft designs on fixed dates?
RE: WitPTracker AE Release 1.5.1 Available
ORIGINAL: pad152
In WITP/AE Tracker, I saw several messages about allied R&D date advances for new aircraft? I thought only Japan got advances for R&D and allied got new aircraft designs on fixed dates?
The code generates the alert if the available date changes, regardless of side. Maybe R&D works for the Allies, too...?
Delete the trackerdb.* files.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
More Insight on Memory Issues
My problem is very similar to what Grotius reported in post #1213, and a bit similar to Castor Troy's report in post #1385. Here's the scoop:
Because I don't read the forums every day (some of us do have a life outside of WITP and AE!), I was humming along blissfully with v1.2 of AE Tracker. Saw my problem had been resolved, so upgraded to v1.5.1. Deleted the old data bases since my game was so old I might as well start over, anyway.
The initial load of Tracker took a long time, but I chalked that up to initializing the data base (although it said the files loaded in 39 seconds). Then, after one turn, I tried to open Tracker again. Took forever, so I ended up canceling via Task Manager.
Tried again the next day. First shut off the wireless, then closed down Zone Alarm. Tracker was the only application left running that I could really do anything about. Again, database files loaded in 39 seconds, but almost 10 minutes more before the application opened. I did have Task Manager open, and found that by opening Tracker my page file had soared from 165MB to 940MB, although Java was using about 24MB of RAM (with occasional spikes as high as 100MB, but generally under 50MB). This really doesn't seem normal. The large database theory shouldn't apply, since it had only one turn stored in it.
Machine specs are XP w/ SP 3, 512MB RAM, severely fragmented hard drive. I'll be doing a defrag and testing the physical memory, but wanted to supply these details in case anyone has any insight.
For the record, I do realize that with AE (and probably Tracker) 512MB of RAM is barely enough. I never open the two of them together, and close down everything else (except ZA, if I still have the wireless on) to run them. Until I can get more RAM, though, this is the way it'll have to be.
Because I don't read the forums every day (some of us do have a life outside of WITP and AE!), I was humming along blissfully with v1.2 of AE Tracker. Saw my problem had been resolved, so upgraded to v1.5.1. Deleted the old data bases since my game was so old I might as well start over, anyway.
The initial load of Tracker took a long time, but I chalked that up to initializing the data base (although it said the files loaded in 39 seconds). Then, after one turn, I tried to open Tracker again. Took forever, so I ended up canceling via Task Manager.
Tried again the next day. First shut off the wireless, then closed down Zone Alarm. Tracker was the only application left running that I could really do anything about. Again, database files loaded in 39 seconds, but almost 10 minutes more before the application opened. I did have Task Manager open, and found that by opening Tracker my page file had soared from 165MB to 940MB, although Java was using about 24MB of RAM (with occasional spikes as high as 100MB, but generally under 50MB). This really doesn't seem normal. The large database theory shouldn't apply, since it had only one turn stored in it.
Machine specs are XP w/ SP 3, 512MB RAM, severely fragmented hard drive. I'll be doing a defrag and testing the physical memory, but wanted to supply these details in case anyone has any insight.
For the record, I do realize that with AE (and probably Tracker) 512MB of RAM is barely enough. I never open the two of them together, and close down everything else (except ZA, if I still have the wireless on) to run them. Until I can get more RAM, though, this is the way it'll have to be.
Possible Bug -- But AE, or Tracker?
I haven't had a chance to go back and see what it says in the game, and won't for a while, but wanted to mention this while I remember it. I scuttled two ships at Pearl Harbor (float damage 98 -- not much hope!), but after finally getting the turn loaded into Tracker (see previous post) the Sinkings report shows them as being sunk near Samah.
Again, this could be a ridiculous FOW thing from the game (I should know where I scuttled my own ships, for crying out loud!), but just in case it isn't, I'm letting you know. If I get further information, I'll add it.
Again, this could be a ridiculous FOW thing from the game (I should know where I scuttled my own ships, for crying out loud!), but just in case it isn't, I'm letting you know. If I get further information, I'll add it.
And a Low-Priority Request...
Thanks much for fixing the display of the base damage levels; that's a big help!
At some point in the future, could this information be displayed in a tab? While I don't really mind having to move through the bases one-by-one to find those with damage, the angular spread on the sub-info screen is just too much to allow the eye to catch a change in one of the figures. Having it in a tabular form, which was made sortable, would be a great benefit! In the grand scheme of things, though, this should not be a high priority.
Thanks again for the fix, and for this product!
At some point in the future, could this information be displayed in a tab? While I don't really mind having to move through the bases one-by-one to find those with damage, the angular spread on the sub-info screen is just too much to allow the eye to catch a change in one of the figures. Having it in a tabular form, which was made sortable, would be a great benefit! In the grand scheme of things, though, this should not be a high priority.
Thanks again for the fix, and for this product!
RE: More Insight on Memory Issues
ORIGINAL: CaptDave
My problem is very similar to what Grotius reported in post #1213, and a bit similar to Castor Troy's report in post #1385. Here's the scoop:
Because I don't read the forums every day (some of us do have a life outside of WITP and AE!), I was humming along blissfully with v1.2 of AE Tracker. Saw my problem had been resolved, so upgraded to v1.5.1. Deleted the old data bases since my game was so old I might as well start over, anyway.
The initial load of Tracker took a long time, but I chalked that up to initializing the data base (although it said the files loaded in 39 seconds). Then, after one turn, I tried to open Tracker again. Took forever, so I ended up canceling via Task Manager.
Tried again the next day. First shut off the wireless, then closed down Zone Alarm. Tracker was the only application left running that I could really do anything about. Again, database files loaded in 39 seconds, but almost 10 minutes more before the application opened. I did have Task Manager open, and found that by opening Tracker my page file had soared from 165MB to 940MB, although Java was using about 24MB of RAM (with occasional spikes as high as 100MB, but generally under 50MB). This really doesn't seem normal. The large database theory shouldn't apply, since it had only one turn stored in it.
Machine specs are XP w/ SP 3, 512MB RAM, severely fragmented hard drive. I'll be doing a defrag and testing the physical memory, but wanted to supply these details in case anyone has any insight.
For the record, I do realize that with AE (and probably Tracker) 512MB of RAM is barely enough. I never open the two of them together, and close down everything else (except ZA, if I still have the wireless on) to run them. Until I can get more RAM, though, this is the way it'll have to be.
The major change is the addition of the map. This is a real memory hog, so it could be the major culprit.
Or something else could be happening... Once the tables are loaded from the database, the data is built for presentation, which requires a bit of additional processing. Maybe something is amiss there.
I'd need to do a bit more profiling of where the processing killer really is.
Delete the trackerdb.* files.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
RE: Possible Bug -- But AE, or Tracker?
ORIGINAL: CaptDave
I haven't had a chance to go back and see what it says in the game, and won't for a while, but wanted to mention this while I remember it. I scuttled two ships at Pearl Harbor (float damage 98 -- not much hope!), but after finally getting the turn loaded into Tracker (see previous post) the Sinkings report shows them as being sunk near Samah.
Again, this could be a ridiculous FOW thing from the game (I should know where I scuttled my own ships, for crying out loud!), but just in case it isn't, I'm letting you know. If I get further information, I'll add it.
Oh, that doesn't seem right. Can you send me a save with this misinformation?
Delete the trackerdb.* files.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
RE: And a Low-Priority Request...
ORIGINAL: CaptDave
Thanks much for fixing the display of the base damage levels; that's a big help!
At some point in the future, could this information be displayed in a tab? While I don't really mind having to move through the bases one-by-one to find those with damage, the angular spread on the sub-info screen is just too much to allow the eye to catch a change in one of the figures. Having it in a tabular form, which was made sortable, would be a great benefit! In the grand scheme of things, though, this should not be a high priority.
Thanks again for the fix, and for this product!
Yeah, that's probably a good idea. Maybe I could make it a switchable thing between some other data so as not to make too much use of horizontal scrolling.
Delete the trackerdb.* files.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
Copy the pwsdll.dll file from the game folder to the WitPTracker folder.
Try running the WitPTracker.bat again.
RE: More Insight on Memory Issues
ORIGINAL: floydg
ORIGINAL: CaptDave
My problem is very similar to what Grotius reported in post #1213, and a bit similar to Castor Troy's report in post #1385. Here's the scoop:
Because I don't read the forums every day (some of us do have a life outside of WITP and AE!), I was humming along blissfully with v1.2 of AE Tracker. Saw my problem had been resolved, so upgraded to v1.5.1. Deleted the old data bases since my game was so old I might as well start over, anyway.
The initial load of Tracker took a long time, but I chalked that up to initializing the data base (although it said the files loaded in 39 seconds). Then, after one turn, I tried to open Tracker again. Took forever, so I ended up canceling via Task Manager.
Tried again the next day. First shut off the wireless, then closed down Zone Alarm. Tracker was the only application left running that I could really do anything about. Again, database files loaded in 39 seconds, but almost 10 minutes more before the application opened. I did have Task Manager open, and found that by opening Tracker my page file had soared from 165MB to 940MB, although Java was using about 24MB of RAM (with occasional spikes as high as 100MB, but generally under 50MB). This really doesn't seem normal. The large database theory shouldn't apply, since it had only one turn stored in it.
Machine specs are XP w/ SP 3, 512MB RAM, severely fragmented hard drive. I'll be doing a defrag and testing the physical memory, but wanted to supply these details in case anyone has any insight.
For the record, I do realize that with AE (and probably Tracker) 512MB of RAM is barely enough. I never open the two of them together, and close down everything else (except ZA, if I still have the wireless on) to run them. Until I can get more RAM, though, this is the way it'll have to be.
The major change is the addition of the map. This is a real memory hog, so it could be the major culprit.
Or something else could be happening... Once the tables are loaded from the database, the data is built for presentation, which requires a bit of additional processing. Maybe something is amiss there.
I'd need to do a bit more profiling of where the processing killer really is.
Let me know if I can provide any more help.
RE: Possible Bug -- But AE, or Tracker?
ORIGINAL: floydg
ORIGINAL: CaptDave
I haven't had a chance to go back and see what it says in the game, and won't for a while, but wanted to mention this while I remember it. I scuttled two ships at Pearl Harbor (float damage 98 -- not much hope!), but after finally getting the turn loaded into Tracker (see previous post) the Sinkings report shows them as being sunk near Samah.
Again, this could be a ridiculous FOW thing from the game (I should know where I scuttled my own ships, for crying out loud!), but just in case it isn't, I'm letting you know. If I get further information, I'll add it.
Oh, that doesn't seem right. Can you send me a save with this misinformation?
Since I submitted this without double-checking the game, I knew it would turn out this way. Tracker is accurately reporting what is reported in the Intelligence screen within the game, so this seems to be a problem for the other programmers. Thanks, anyway!
RE: And a Low-Priority Request...
ORIGINAL: floydg
ORIGINAL: CaptDave
Thanks much for fixing the display of the base damage levels; that's a big help!
At some point in the future, could this information be displayed in a tab? While I don't really mind having to move through the bases one-by-one to find those with damage, the angular spread on the sub-info screen is just too much to allow the eye to catch a change in one of the figures. Having it in a tabular form, which was made sortable, would be a great benefit! In the grand scheme of things, though, this should not be a high priority.
Thanks again for the fix, and for this product!
Yeah, that's probably a good idea. Maybe I could make it a switchable thing between some other data so as not to make too much use of horizontal scrolling.
Yeah, I would definitely recommend a separate display, since I would guess very few people care about this. It could be dynamic (click a button to change) or a separate tab (like the various resource displays). As I said, though, not the highest importance!
RE: WitPTracker AE Release 1.0
I'm trying to export a list of reinforcement LCU's that shows delay & Port of Arrival so I can have transports etc. ready when they appear.
I can see this inside WITPTracker - LCU Production but not as an option to export to csv.
Am I missing something?
Cheers
Dave
I can see this inside WITPTracker - LCU Production but not as an option to export to csv.
Am I missing something?
Cheers
Dave
RE: WitPTracker AE Release 1.0
One of the few remaining panels which I haven't given an export to csv yet ... next release Dave ...ORIGINAL: davbaker
I'm trying to export a list of reinforcement LCU's that shows delay & Port of Arrival so I can have transports etc. ready when they appear.
I can see this inside WITPTracker - LCU Production but not as an option to export to csv.
Am I missing something?
Cheers
Dave
Cheers
Damian


