WitPTracker AE Release 1.11 Available!
Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition
RE: WitPTracker AE Release 1.6.1 Available!
Thank you both!
[&o][&o][&o]
[&o][&o][&o]
RE: WitPTracker AE Release 1.6.1 Available!
No Problems ... one thing to keep in mind is that using the UpgradeTo(path) may make you think there are more options available ... For instance many of the A6M2's will have to upgrade to the A7M3-J Sam before they can be downgraded ... obviously not an ideal situation. This is because all the A6M2's are carrier capable and the first option to change to non capable is the A7M3-J Sam... then this allows to downgrade. So actually there are very few groups that can upgrade in a timely fashion ... I'm on the fence about PDU ON being this restrictive ... but it's what we've got to work with.ORIGINAL: pompack
Thank you both!
[&o][&o][&o]
Also there seems to be a bug (or WAD) that I'm going to talk to MichaelM about.
[edit] Also you may find that you have to follow the DB upgrade path fairly closely to get the option to upgrade to the plane model you require. Especially make sure that you upgrade to the plane model directly above the one (DB editor) you want (if you can't see it in the upgrade window) ... the bug I saw was sometimes you need to go two slots (DB editor) above the plane required and follow the path until reached ... Hope you understand [;)]
PLEASE ... Use "UpgradeTo(path)" with caution ~ I'll try to improve this soon . "UpgradeTo" is working fine as far as I can tell.
RE: WitPTracker AE Release 1.6.1 Available!
ORIGINAL: n01487477
No Problems ... one thing to keep in mind is that using the UpgradeTo(path) may make you think there are more options available ... For instance many of the A6M2's will have to upgrade to the A7M3-J Sam before they can be downgraded ... obviously not an ideal situation. This is because all the A6M2's are carrier capable and the first option to change to non capable is the A7M3-J Sam... then this allows to downgrade. So actually there are very few groups that can upgrade in a timely fashion ... I'm on the fence about PDU ON being this restrictive ... but it's what we've got to work with.ORIGINAL: pompack
Thank you both!
[&o][&o][&o]
Also there seems to be a bug (or WAD) that I'm going to talk to MichaelM about.
[edit] Also you may find that you have to follow the DB upgrade path fairly closely to get the option to upgrade to the plane model you require. Especially make sure that you upgrade to the plane model directly above the one (DB editor) you want (if you can't see it in the upgrade window) ... the bug I saw was sometimes you need to go two slots (DB editor) above the plane required and follow the path until reached ... Hope you understand [;)]
PLEASE ... Use "UpgradeTo(path)" with caution ~ I'll try to improve this soon . "UpgradeTo" is working fine as far as I can tell.
This is quite useful as it is, but just a suggestion for a "minor" change ([8|]): If the "UpgradeTo(path)" included an additional column labled "via" indicating which upgrade in the root opened the new path to the target it would be most useful [:D]
RE: WitPTracker AE Release 1.6.1 Available!
Can a new feature be added in the supply/fuel chart, a column that "Daily/Monthly Supply Consumption by LCUs"
So we can check what it`s the net exportable supply in each region daily/monthly
So we can check what it`s the net exportable supply in each region daily/monthly

RE: WitPTracker AE Release 1.0.1 Available
Gents: I love Tracker. But I have a problem.
I accidently erased tracker, but upon re-install, I only seem to have one "Region"; Japan. All Bases are tagged to JAPAN. I seem to have lost my regions. Is there a fix for this?

I accidently erased tracker, but upon re-install, I only seem to have one "Region"; Japan. All Bases are tagged to JAPAN. I seem to have lost my regions. Is there a fix for this?

- Attachments
-
- 120BroadwayLobby.jpg (131.11 KiB) Viewed 341 times
RE: WitPTracker AE Release 1.0.1 Available
Yeah, the new version doesn't have the regions set ... you need to go File -> Import base region Definitions and then inside the Region-Mapping folder pick either Kull or Nomad_5.ORIGINAL: Q-Ball
Gents: I love Tracker. But I have a problem.
I accidently erased tracker, but upon re-install, I only seem to have one "Region"; Japan. All Bases are tagged to JAPAN. I seem to have lost my regions. Is there a fix for this?
...
Look here under Import method for more info ...
http://sites.google.com/site/witptracker/regions-1
RE: WitPTracker AE Release 1.0.1 Available
Just like to thank you both again for the latest update. Making the traking of reserve pilots sooooooo much easier
1966 was a great year for English Football...Eric was born
RE: WitPTracker AE Release 1.6.1 Available!
Yeah ... I had been planning on doing something like that ... here is my first pass at it. Mouse over tells the upgrade pathORIGINAL: pompack
ORIGINAL: n01487477
No Problems ... one thing to keep in mind is that using the UpgradeTo(path) may make you think there are more options available ... For instance many of the A6M2's will have to upgrade to the A7M3-J Sam before they can be downgraded ... obviously not an ideal situation. This is because all the A6M2's are carrier capable and the first option to change to non capable is the A7M3-J Sam... then this allows to downgrade. So actually there are very few groups that can upgrade in a timely fashion ... I'm on the fence about PDU ON being this restrictive ... but it's what we've got to work with.ORIGINAL: pompack
Thank you both!
[&o][&o][&o]
Also there seems to be a bug (or WAD) that I'm going to talk to MichaelM about.
[edit] Also you may find that you have to follow the DB upgrade path fairly closely to get the option to upgrade to the plane model you require. Especially make sure that you upgrade to the plane model directly above the one (DB editor) you want (if you can't see it in the upgrade window) ... the bug I saw was sometimes you need to go two slots (DB editor) above the plane required and follow the path until reached ... Hope you understand [;)]
PLEASE ... Use "UpgradeTo(path)" with caution ~ I'll try to improve this soon . "UpgradeTo" is working fine as far as I can tell.
This is quite useful as it is, but just a suggestion for a "minor" change ([8|]): If the "UpgradeTo(path)" included an additional column labled "via" indicating which upgrade in the root opened the new path to the target it would be most useful [:D]

- Attachments
-
- capture.jpg (166.23 KiB) Viewed 341 times
RE: WitPTracker AE Release 1.6.1 Available!
Heya,
Anyone have any ideas on this problem I'm having. I was running 1.6 but just upgraded to 1.6.1 to see if it resolved it, but no joy. I've run 53 turns with tracker until it stopped working. Tracker launches fine (I tweaked the memory usage up until tracker failed to start at 2048). But when I try to "Read Turn" nothing happens, and in the launcher window I see this error:
C:\Matrix Games\War in the Pacific Admiral's Edition\tools\witptracker>"C:\Progr
am Files (x86)\Java\jre6\bin\java.exe" -Xms1536m -Xmx1536m -jar "WitPTracker.jar"
WitP Tracker AE tables loaded in 57 seconds
Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: C:\Matrix
Games\War in the Pacific Admiral's Edition\tools\witptracker\pwsdll.dll: Not en
ough storage is available to process this command
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at JNIpws.JNIpws.<clinit>(JNIpws.java:19)
at witptracker.SaveFileReader.ReadScenarioTurnNumber(SaveFileReader.java
:327)
at witptracker.GUIMain.ReadNewTurn(GUIMain.java:144)
at witptracker.GUIMain.actionPerformed(GUIMain.java:511)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown
Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(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)
I have 8 gigs of RAM, on a fresh boot, and plenty of disk space. I searched back thru this thread and couldn't find anything about this particular problem - on turn read. On the google tracker page it talks about this error happening when it starts, and by running the jar directly, but I am using the batch file. Anyone have any ideas?
Anyone have any ideas on this problem I'm having. I was running 1.6 but just upgraded to 1.6.1 to see if it resolved it, but no joy. I've run 53 turns with tracker until it stopped working. Tracker launches fine (I tweaked the memory usage up until tracker failed to start at 2048). But when I try to "Read Turn" nothing happens, and in the launcher window I see this error:
C:\Matrix Games\War in the Pacific Admiral's Edition\tools\witptracker>"C:\Progr
am Files (x86)\Java\jre6\bin\java.exe" -Xms1536m -Xmx1536m -jar "WitPTracker.jar"
WitP Tracker AE tables loaded in 57 seconds
Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: C:\Matrix
Games\War in the Pacific Admiral's Edition\tools\witptracker\pwsdll.dll: Not en
ough storage is available to process this command
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at JNIpws.JNIpws.<clinit>(JNIpws.java:19)
at witptracker.SaveFileReader.ReadScenarioTurnNumber(SaveFileReader.java
:327)
at witptracker.GUIMain.ReadNewTurn(GUIMain.java:144)
at witptracker.GUIMain.actionPerformed(GUIMain.java:511)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown
Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(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)
I have 8 gigs of RAM, on a fresh boot, and plenty of disk space. I searched back thru this thread and couldn't find anything about this particular problem - on turn read. On the google tracker page it talks about this error happening when it starts, and by running the jar directly, but I am using the batch file. Anyone have any ideas?
RE: WitPTracker AE Release 1.6.1 Available!
When I tried using very large memory numbers I had that error. I have found that this is the sizes that work best for me.
java -Xms512m -Xmx768m -jar "WitPTracker.jar" nomap
pause
When I tried -Xms768m -Xmx1024m I received the not enough memory error.
java -Xms512m -Xmx768m -jar "WitPTracker.jar" nomap
pause
When I tried -Xms768m -Xmx1024m I received the not enough memory error.
RE: WitPTracker AE Release 1.6.1 Available!
ORIGINAL: Nomad
When I tried using very large memory numbers I had that error. I have found that this is the sizes that work best for me.
java -Xms512m -Xmx768m -jar "WitPTracker.jar" nomap
pause
When I tried -Xms768m -Xmx1024m I received the not enough memory error.
Thanks Nomad! That did the trick! When I first ran into this problem I was running -Xms1024 -Xmx1024 and decided the only way to go was up, whops!
RE: WitPTracker AE Release 1.6.1 Available!
Thanks so much!!! One more way to enjoy this wonderful game!
JF
JF
RE: WitPTracker AE Release 1.6.1 Available!
ORIGINAL: Lomri
ORIGINAL: Nomad
When I tried using very large memory numbers I had that error. I have found that this is the sizes that work best for me.
java -Xms512m -Xmx768m -jar "WitPTracker.jar" nomap
pause
When I tried -Xms768m -Xmx1024m I received the not enough memory error.
Thanks Nomad! That did the trick! When I first ran into this problem I was running -Xms1024 -Xmx1024 and decided the only way to go was up, whops!
It seems an increasing number of people run into this error (see also page 57 of this thread):
Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: C:\Matrix
Games\War in the Pacific Admiral's Edition\tools\witptracker\pwsdll.dll: Not enough storage is available to process this command
The cause seems to be that calling the pwsdll.dll results in an increased memory demand in addition to the memory allocated with the Xms and Xmx parameters. If the Xmx value is too high, the command to read in a turn cannot get enough memory and fails. This has nothing to do with how much physical memory there is. Java.exe as a 32Bit application can use a maximum of 2GByte and that seems to be the limiter.
It seems with current knowledge only the -Xms512m -Xmx768m parameters are safe. Higher Xmx values seem guaranteed to fail. The nomap parameter may help only in that regard, as the -Xmx parameter can be set lower or when set to 768m will allow to read in more turns into the database.
Perhaps the "solution": -Xms512m -Xmx768m should also be mentioned on the support page of the Tracker-Homepage. Maybe my suggestion in post 1698 could also be of value.
RE: WitPTracker AE Release 1.6.1 Available!
Support page updated with the (digested) information above.
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.6.1 Available!
ORIGINAL: n01487477
No Problems ... one thing to keep in mind is that using the UpgradeTo(path) may make you think there are more options available ... For instance many of the A6M2's will have to upgrade to the A7M3-J Sam before they can be downgraded ... obviously not an ideal situation. This is because all the A6M2's are carrier capable and the first option to change to non capable is the A7M3-J Sam... then this allows to downgrade. So actually there are very few groups that can upgrade in a timely fashion ... I'm on the fence about PDU ON being this restrictive ... but it's what we've got to work with.
Also there seems to be a bug (or WAD) that I'm going to talk to MichaelM about.
Good point, Damian.
What do you mean when saying about "a bug" (or WAD) here?
Talking about the general concept of PDU? IMHO it should be rather "SPDU" as "Some player defined upgrade"... [;)] I was talking about the single squadron for patrol version of Jude the other day.. uprades are in fact kind of much limited... [:(]
Przy lackim orle, przy koniu Kiejstuta Archanioł Rusi na proporcach błysł
RE: WitPTracker AE Release 1.0.1 Available
ORIGINAL: n01487477
Yeah, the new version doesn't have the regions set ... you need to go File -> Import base region Definitions and then inside the Region-Mapping folder pick either Kull or Nomad_5.
Look here under Import method for more info ...
http://sites.google.com/site/witptracker/regions-1
Are there any other region mappings available?
Maybe it could be possible to place there some user created separated for download mappings?
I find that after some linking created of conquered areas... Thailand, Malaya, China, Korea... the resources fly somehow more freely without penalties... i think that say fuel unloaded in Singapore can be transfered by the game engine to the bigger port in Hong-Kong or even Port Arthur. And it can be misleading to look at needs of separated regions. I know the regions can be merged by user etc. but maybe some more "general" mappings can be of use here?
Przy lackim orle, przy koniu Kiejstuta Archanioł Rusi na proporcach błysł
RE: WitPTracker AE Release 1.0.1 Available
ORIGINAL: viberpol
ORIGINAL: n01487477
Yeah, the new version doesn't have the regions set ... you need to go File -> Import base region Definitions and then inside the Region-Mapping folder pick either Kull or Nomad_5.
Look here under Import method for more info ...
http://sites.google.com/site/witptracker/regions-1
Are there any other region mappings available?
Maybe it could be possible to place there some user created separated for download mappings?
I find that after some linking created of conquered areas... Thailand, Malaya, China, Korea... the resources fly somehow more freely without penalties... i think that say fuel unloaded in Singapore can be transfered by the game engine to the bigger port in Hong-Kong or even Port Arthur. And it can be misleading to look at needs of separated regions. I know the regions can be merged by user etc. but maybe some more "general" mappings can be of use here?
Feel free to make your own. Just use excel, load one of the existing region files and change it to how you want and save it. Open tracker and load your region file.
RE: WitPTracker AE Release 1.6.1 Available!
ORIGINAL: viberpol
ORIGINAL: n01487477
No Problems ... one thing to keep in mind is that using the UpgradeTo(path) may make you think there are more options available ... For instance many of the A6M2's will have to upgrade to the A7M3-J Sam before they can be downgraded ... obviously not an ideal situation. This is because all the A6M2's are carrier capable and the first option to change to non capable is the A7M3-J Sam... then this allows to downgrade. So actually there are very few groups that can upgrade in a timely fashion ... I'm on the fence about PDU ON being this restrictive ... but it's what we've got to work with.
Also there seems to be a bug (or WAD) that I'm going to talk to MichaelM about.
Good point, Damian.
What do you mean when saying about "a bug" (or WAD) here?
Talking about the general concept of PDU? IMHO it should be rather "SPDU" as "Some player defined upgrade"... [;)] I was talking about the single squadron for patrol version of Jude the other day.. uprades are in fact kind of much limited... [:(]
[edit] Also you may find that you have to follow the DB upgrade path fairly closely to get the option to upgrade to the plane model you require. Especially make sure that you upgrade to the plane model directly above the one (DB editor) you want (if you can't see it in the upgrade window) ... the bug I saw was sometimes you need to go two slots (DB editor) above the plane required and follow the path until reached ... Hope you understand
[edit] ... the bug I saw was sometimes you need to go two slots (DB editor) above the plane required and follow the path until reached ...
For example sometimes if you want to see the A7M3-J as an option, the DB says that upgrading to the A6M8 should open the option for the A7 as the next option from the DB upgrade list; well sometimes it does and sometimes you need to go M5c-> M8 -> A7...
As Nomad stated you can make them yourself ... but IF you want to make one and send it to Floyd then I'm sure it could be included in the next release.ORIGINAL: viberpol
Are there any other region mappings available?
Maybe it could be possible to place there some user created separated for download mappings?
....
RE: WitPTracker AE Release 1.6.1 Available!
Hi, using tracker 1.6.1, I'm getting a hang up again on "compare task forces". I'm about 200 turns in now and tracker takes so long to start up (probably a good 10 minutes) and process turns that I was willing to delete the database and start over. So I made a fresh install of tracker, skipped a turn in case the particular one was the problem, loaded up the next turn and the problem persists. Maybe it's a lost cause.
RE: WitPTracker AE Release 1.6.1 Available!
Problems like this do crop up from time-to-time ... please help us debug the problem by sending some saves with properties file to Floyd at witptracker@gmail.comORIGINAL: dalejr33
Hi, using tracker 1.6.1, I'm getting a hang up again on "compare task forces". I'm about 200 turns in now and tracker takes so long to start up (probably a good 10 minutes) and process turns that I was willing to delete the database and start over. So I made a fresh install of tracker, skipped a turn in case the particular one was the problem, loaded up the next turn and the problem persists. Maybe it's a lost cause.
We can look at it and improve Tracker [8D] (Floyd send them to me if you're too busy)