Correct, sorry didn't do my homework well enough, thanks Nomad ... even I get it wrong occasionally [;)]ORIGINAL: Nomad
The 1417( APD ) upgrades to the 1418( APD ) as of 12/42. And then the 1418 upgrades to the 1419( E ) as of 1/43
WitPTracker AE News
Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition
RE: WitPTracker AE Release 1.0
- CapAndGown
- Posts: 3078
- Joined: Tue Mar 06, 2001 10:00 am
- Location: Virginia, USA
RE: WitPTracker AE Release 1.0
Ok, in looking at it further, it seems that I need the Mutsukis to finish their 2/42 upgrades, i.e. be returned to service, before I will see the APD conversion option.
Thanks for the help.
Thanks for the help.
RE: WitPTracker AE Release 1.0
yeah and just to clarify once those upgrades are done Tracker should then tell you it can upgrade to the E class ... it's just we don't calculate the depth of conversions (which I'd like to sometime)ORIGINAL: cap_and_gown
Ok, in looking at it further, it seems that I need the Mutsukis to finish their 2/42 upgrades, i.e. be returned to service, before I will see the APD conversion option.
Thanks for the help.
Cheers
Damian
- CapAndGown
- Posts: 3078
- Joined: Tue Mar 06, 2001 10:00 am
- Location: Virginia, USA
RE: WitPTracker AE Release 1.0
I just upgraded a unit of A6M2's to A6M3a's. According to Tracker, the "a" model should have 2x20mm Type 99-2 cannons (plus 2 7.7mm mgs). But when I check the plane data of the unit in the game, it indicates that the "a" model has not only 2x20mm Type 99-2, but 2x20mm Type 99 as well. Is there something screwy with the plane data?
- ny59giants
- Posts: 9902
- Joined: Mon Jan 10, 2005 12:02 pm
RE: WitPTracker AE Release 1.0
I've just started a 3rd PBEM, but this time as the Allies. Is there any way to filter out the Soviet ships?? If they are not active, I don't need them being displayed as being 1 day until completion.
[center]
[/center]
[/center]RE: WitPTracker AE Release 1.0
Well in the editor it has both, but the 2x20mm Type 99 is in the 11~20 slot and from the in game plane and weapon DB we have what they have. I'm unsure why there are differences except when it's extended range (but then I'm not a modder). Maybe I should ask one of them.ORIGINAL: cap_and_gown
I just upgraded a unit of A6M2's to A6M3a's. According to Tracker, the "a" model should have 2x20mm Type 99-2 cannons (plus 2 7.7mm mgs). But when I check the plane data of the unit in the game, it indicates that the "a" model has not only 2x20mm Type 99-2, but 2x20mm Type 99 as well. Is there something screwy with the plane data?
RE: WitPTracker AE Release 1.0
I'll add it for the next build ... you're a busy man ![;)]ORIGINAL: ny59giants
I've just started a 3rd PBEM, but this time as the Allies. Is there any way to filter out the Soviet ships?? If they are not active, I don't need them being displayed as being 1 day until completion.
RE: WitPTracker AE Release 1.0
ORIGINAL: cap_and_gown
I just upgraded a unit of A6M2's to A6M3a's. According to Tracker, the "a" model should have 2x20mm Type 99-2 cannons (plus 2 7.7mm mgs). But when I check the plane data of the unit in the game, it indicates that the "a" model has not only 2x20mm Type 99-2, but 2x20mm Type 99 as well. Is there something screwy with the plane data?
I haven't look at the DB, but I found a similar sounding error for a US Army plane a while back. It turns out that one weapon (MG) was different in the extended slots than in the normal range slots, so the display showed both with one over-printing some other text. So it might just be a type in the database.
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: WitPTracker AE Release 1.0
Done ... and the Japanese side looks better too [;)]ORIGINAL: n01487477I'll add it for the next build ... you're a busy man ![;)]ORIGINAL: ny59giants
I've just started a 3rd PBEM, but this time as the Allies. Is there any way to filter out the Soviet ships?? If they are not active, I don't need them being displayed as being 1 day until completion.

- Attachments
-
- capture.jpg (154.28 KiB) Viewed 232 times
RE: WitPTracker AE Release 1.0
ORIGINAL: RUDOLF
What am I doing wrong ?
I assume you have Java installed, so what OS are you using?
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.0
ORIGINAL: RUDOLF
What am I doing wrong ?
![]()
See error message 2
Good luck and I hope Floyd will add this to the web site sometime ... I've even re-written it to make it friendlier ... [;)]
ORIGINAL: n01487477
Error Msg:
1. Can't load IA 32-bit .dll on a AMD 64-bit platform
Vista 64 and Intel / AMD
This error message is usually because you haven’t installed the Microsoft C++ libraries. But if you have then it can also be because you’ve not got Java 32 installed and configured properly.
Solutions.
Step 1. Check C++ Libraries.
Check you have the C++ Libraries installed, if not, install the 32 bit version (even if you have a 64 bit OS.)
[*]I'm unsure if you can have both the 32 and 64 bit C++ libraries available and still get Tracker to run, or how to configure it ... so it’s best for now just to have 32 bit for either 32 or 64 bit OS.
Check here for installation:
http://sites.google.com/site/witptracker/installation
Step 2. Check 32 bit Java
Check you have 32 bit Java installed. If you are working on a 64 bit OS, then you can have both installed.
Step 2. Option 1. Change your witptracker.bat file to point to the 32 bit Java executable (you need the ""'s cause of the space) - this varies on different machines so you'll need to check the path:Code: Select all
C:\"Program Files"\Java\jre6\bin\java -Xms384m -Xmx512m -jar "WitPTracker.jar" pause
NB** you must run WitpTracker from the batch file !!
(See link for executing the batch file in Win64 bit if it won’t run http://sites.google.com/site/witptracker/support )
Step 2. Option 2.
Copy NOT Move your 32 bit java.exe into the Tracker folder (I'm hoping it will pick this up rather than the 64 bit)
Windows 7 and AMD
No solution found or confirmed, try above using Intel 32 bit C++ Libraries.
Other solutions:
I have a Tracker executable file made with a 3rd party Java executable ... PM me with your email address. It seems to have a great deal of success.
Error Msg
2. Java is not recognized as an internal or external command
Java is either not installed, or there is a pathing problem.
Solution 1. Check you have Java JRE installed.
Solution 2. Move Tracker folder to the Desktop or c:\
Solution 3. Copy java.exe from your C:\Program Files\Java\jre6\bin to the WitpTracker folder (remember copy not move)
Solution 4. Change your witptracker.bat file to point to the 32 bit Java executable (you need the ""'s cause of the space) - this varies on different machines so you'll need to check the path:Code: Select all
C:\"Program Files"\Java\jre6\bin\java -Xms384m -Xmx512m -jar "WitPTracker.jar" pause
Solution 5. (The best but most difficult)
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer so check where it's installed
6. Make Sure to add a semicolon after the word bin in the path to separate it from the other important paths
7. If this doesn't work then you may have to reinstall Java and Try Again
Source(s):
http://www.java.com/en/download/help/path.xml
Setting Path on Windows
For Windows XP: (additional notes)
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.
3. # A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d901afd, pid=4924, tid=6864
Batch file Set Up
This is caused by not using the batch file to run Tracker, there are memory configurations inside the batch file.
Solution 1. This information was provided by BigJ62:- http://sites.google.com/site/witptracker/support
Solutions 2:
I have a Tracker executable file made with a 3rd party Java executable ... PM me with your email address. It seems to have a great deal of success.
Other errors.
Generally speaking, uninstalling and reinstalling the C++ redist usually works. I've found some people having to go back to the original C++ package 95/98 and then patching up ... The x64 patch, seems to cause many problems and I'd recommend for now just trying the 32bit (x86) patch, before the 64Bit.
RE: WitPTracker AE Release 1.0
For Win7 x64 the witptracker.bat file should point to the 32Bit version of java. If you haven't changed the default installation path for java 32Bit version during installation, the java.exe resides in C:\Program Files (x86)\Java\jre6\bin
That path is true for all language versions of Win7 x64.
"C:\Program Files (x86)\Java\jre6\bin\java.exe" -Xms384m -Xmx512m -jar "WitPTracker.jar"
pause
That path is true for all language versions of Win7 x64.
"C:\Program Files (x86)\Java\jre6\bin\java.exe" -Xms384m -Xmx512m -jar "WitPTracker.jar"
pause
RE: WitPTracker AE Release 1.0
ORIGINAL: n01487477
See error message 2
Ok, then I got this:

RE: WitPTracker AE Release 1.0
After some more troubleshooting I ended up with: 'java' is not recognized as an internal or external command, operable program or batch file
If I get it right, it is suppose to work on Vista64, I must be doing something wrong.
If I get it right, it is suppose to work on Vista64, I must be doing something wrong.
RE: WitPTracker AE Release 1.0
ORIGINAL: RUDOLF
After some more troubleshooting I ended up with: 'java' is not recognized as an internal or external command, operable program or batch file
If I get it right, it is suppose to work on Vista64, I must be doing something wrong.
Go back to where you got the long string of error messages, since in that case it was finding Java.
Delete the trackerdb.* files (usually there are four of them) and start it up again.
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.0
k, now I'm back here at the start line and now got this:


RE: WitPTracker AE Release 1.0
Did you delete all of the [font="Courier New"]trackerdb [/font]files before starting the [font="Courier New"]witptracker.bat[/font] file?
When you first start, you should see an "Initializing WitPTracker AE database" message, which it doesn't look like you're seeing.
Also, check your [font="Courier New"]witptracker.properties[/font] file. See the instructions on the WitPTracker AE web site for an explanation of the file contents.
Floyd
When you first start, you should see an "Initializing WitPTracker AE database" message, which it doesn't look like you're seeing.
Also, check your [font="Courier New"]witptracker.properties[/font] file. See the instructions on the WitPTracker AE web site for an explanation of the file contents.
Floyd
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.0
properties file is correct, also I did delete the db's and the "Initializing WitPTracker AE database" is visible in the screanshoot above your post.
RE: WitPTracker AE Release 1.0
I now menage to start the program successfully, thanks for the help.





