WitPTracker AE Release 1.11 Available!
Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition
-
Moss Orleni
- Posts: 201
- Joined: Mon Nov 03, 2008 8:36 am
RE: WitPTracker AE Release 1.0
Hi Floyd & Damian,
Enjoying the latest Tracker version a lot!
Question for a future release: is there a possibility to include details (and a csv export) on the pilot skill stats (eg Torpedo Attack, Strafing, ...)
Particularly handy for those feeling the urge to optimize pilot management...
Cheers,
Moss
Enjoying the latest Tracker version a lot!
Question for a future release: is there a possibility to include details (and a csv export) on the pilot skill stats (eg Torpedo Attack, Strafing, ...)
Particularly handy for those feeling the urge to optimize pilot management...
Cheers,
Moss
RE: WitPTracker AE Release 1.0
Not at present Moss, the amount of data is fairly huge and as we've been having slow response times with large amounts of turns loaded we've shelved doing that for a little bit... Never say never though [;)]ORIGINAL: Moss Orleni
Hi Floyd & Damian,
Enjoying the latest Tracker version a lot!
Question for a future release: is there a possibility to include details (and a csv export) on the pilot skill stats (eg Torpedo Attack, Strafing, ...)
Particularly handy for those feeling the urge to optimize pilot management...
Cheers,
Moss
RE: WitPTracker AE Release 1.0
I second this request but pilot details just in CSV export will be fine, in-tool screen should stay as-isORIGINAL: Moss Orleni
Hi Floyd & Damian,
Enjoying the latest Tracker version a lot!
Question for a future release: is there a possibility to include details (and a csv export) on the pilot skill stats (eg Torpedo Attack, Strafing, ...)
Particularly handy for those feeling the urge to optimize pilot management...
Cheers,
Moss

RE: WitPTracker AE Release 1.0
It's been some time since I used Tracker AE due to it stopped working on my savegame (the problem where savegame was started under a earlier version of AE & patched up) so I'm going to give it another try but does this problem still exist? I started this savegame under the original AE release & it's patched to the last hotfix so would it work under these conditions or would I still get an error when I tried to load savegame turn in? I could initialize the db but the error would happen when I tried to load a turn in & I think that's where the problem occurs is that due to I started my savegame under the original release & the scenario db has actually changed since then but my savegame doesn't show it.
RE: WitPTracker AE Release 1.0
I've never seen this problem, can you tell me what the error message is ? Are you sure you are starting tracker with the witptracker.bat file ? - this allows the memory settings to be definedORIGINAL: jcjordan
It's been some time since I used Tracker AE due to it stopped working on my savegame (the problem where savegame was started under a earlier version of AE & patched up) so I'm going to give it another try but does this problem still exist? I started this savegame under the original AE release & it's patched to the last hotfix so would it work under these conditions or would I still get an error when I tried to load savegame turn in? I could initialize the db but the error would happen when I tried to load a turn in & I think that's where the problem occurs is that due to I started my savegame under the original release & the scenario db has actually changed since then but my savegame doesn't show it.
RE: WitPTracker AE Release 1.0
Offhand since it's been so long ago I can't remember the exact error but will see what happens when I update it & do a new initialize over the weekend.
Also I just remembered (old timers disease you know [:'(]) that the savegame problem I mentioned was from WITP Staff but did have some problems w/ getting Tracker to work right but I just dropped using both some time ago.
Also I just remembered (old timers disease you know [:'(]) that the savegame problem I mentioned was from WITP Staff but did have some problems w/ getting Tracker to work right but I just dropped using both some time ago.
- ny59giants
- Posts: 9902
- Joined: Mon Jan 10, 2005 12:02 pm
RE: WitPTracker AE Release 1.0
This may have been addressed before, but is there a way NOT to display the changes in your opponents base expansions?? Under "Alerts" I see ALL base development regardless.
[center]
[/center]
[/center]RE: WitPTracker AE Release 1.0
When the devs stop this in the Ops report, we will too ... see this thread tm.asp?m=2482693ORIGINAL: ny59giants
This may have been addressed before, but is there a way NOT to display the changes in your opponents base expansions?? Under "Alerts" I see ALL base development regardless.
RE: WitPTracker AE Release 1.0
ORIGINAL: n01487477
When the devs stop this in the Ops report, we will too ... see this thread tm.asp?m=2482693ORIGINAL: ny59giants
This may have been addressed before, but is there a way NOT to display the changes in your opponents base expansions?? Under "Alerts" I see ALL base development regardless.
And even if it wasn't in the Ops report, it's still available on map mouse-over (which is how I derive the alert).
I could always suppress the alert for bases not owned (which is what I presently do for expanded forts) but, as stated, it's still available in-game.
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
Is there a list anywhere in Tracker that shows "Dead Commanders"? It'd be interesting to see which leaders have died in combat along with their stats, particularly ship captains and TF leaders. That way you can tell if you've lost a truly great man or not, adds to the roll playing.
I'm not sure if ground or air commanders can be killed in the game, but TF commanders and captains most certainly can be.
I'm not sure if ground or air commanders can be killed in the game, but TF commanders and captains most certainly can be.
"Cry 'Havoc,' and let slip the dogs of war" - William Shakespeare, "Julius Caesar"
RE: WitPTracker AE Release 1.0
ORIGINAL: Jones944
Is there a list anywhere in Tracker that shows "Dead Commanders"? It'd be interesting to see which leaders have died in combat along with their stats, particularly ship captains and TF leaders. That way you can tell if you've lost a truly great man or not, adds to the roll playing.
I'm not sure if ground or air commanders can be killed in the game, but TF commanders and captains most certainly can be.
No such list. In fact, once a leader is out of the game, we remove it from the database.
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
Any possibility of adding leader deaths to the Alerts? It's an event at least as significant as a stats increase which is already in there.
"Cry 'Havoc,' and let slip the dogs of war" - William Shakespeare, "Julius Caesar"
RE: WitPTracker AE Release 1.0
ORIGINAL: Jones944
Any possibility of adding leader deaths to the Alerts? It's an event at least as significant as a stats increase which is already in there.
I agree on the significance, however the alerts reference stuff in the database and when the leader is deleted, I can't refer to it.
I can look at leaving some of the leader info intact on death, but I'm concerned that if the leader slots ever get re-used, it would cause a whole slew of other problems.
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
You could copy the dead leader off to a new, separate DB table at the time you are deleting them. Then there'd effectively be no change to any other part of the program. A new screen could be written to display from the new table.ORIGINAL: floydg
ORIGINAL: Jones944
Any possibility of adding leader deaths to the Alerts? It's an event at least as significant as a stats increase which is already in there.
I agree on the significance, however the alerts reference stuff in the database and when the leader is deleted, I can't refer to it.
I can look at leaving some of the leader info intact on death, but I'm concerned that if the leader slots ever get re-used, it would cause a whole slew of other problems.
Just a few thoughts! [:)]
"Cry 'Havoc,' and let slip the dogs of war" - William Shakespeare, "Julius Caesar"
RE: WitPTracker AE Release 1.0
ORIGINAL: Jones944
You could copy the dead leader off to a new, separate DB table at the time you are deleting them. Then there'd effectively be no change to any other part of the program. A new screen could be written to display from the new table.ORIGINAL: floydg
ORIGINAL: Jones944
Any possibility of adding leader deaths to the Alerts? It's an event at least as significant as a stats increase which is already in there.
I agree on the significance, however the alerts reference stuff in the database and when the leader is deleted, I can't refer to it.
I can look at leaving some of the leader info intact on death, but I'm concerned that if the leader slots ever get re-used, it would cause a whole slew of other problems.
Just a few thoughts! [:)]
True. And that's what I do for sunk enemy ships so the alerts can reference them. I'll take a look at adding that.
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
Fun!ORIGINAL: floydg
I'll take a look at adding that.
"Cry 'Havoc,' and let slip the dogs of war" - William Shakespeare, "Julius Caesar"
RE: WitPTracker AE Release 1.0
Have a problem getting Tracker to run & not exactly sure on what to do. My version of Java is 1.6.20 & I've got the vcredist files & below is pic of what I see in the dos command box that comes up. I'm running the last hotfix but save game was started under original release so it's been run under all patches/hotfixes since. It me vs AI IJ & I've got the properties set to check both the Tracker & AE for the save game.


- Attachments
-
- WITPTracker.jpg (87.54 KiB) Viewed 219 times
RE: WitPTracker AE Release 1.0
ORIGINAL: jcjordan
Have a problem getting Tracker to run & not exactly sure on what to do. My version of Java is 1.6.20 & I've got the vcredist files & below is pic of what I see in the dos command box that comes up
The side-by-side error is usually caused by not having the Microsoft Visual C++ SP1 update install properly. What is your OS? What version of C++ did you install?
I'd look at un-installing C++ SP1 and reinstalling the x86 version (even on 64 bit), also make sure you're using 32bit java (which I think from the version no, you are ... )
RE: WitPTracker AE Release 1.0
I'm fairly sure it's 32 bit Vista that I've got as much as I hate Vista. I've got the 3 vcredist files listed in a folder in the main AE folder called redist. The files are vcredist_IA64, vcredist_x64 & vcredist_x86 & all are dated 9/9/2009 & look to be version 6.0.2900.2180. So I should get rid of all of these & just get the x86 version?
RE: WitPTracker AE Release 1.0
Stupid Question ... Did you install then or just have them in a folder ? Yeah uninstall them all, and just have the x86 version ... I've seen it conflict / have problems on different installs... Microsoft doesn't always work as intended [;)] [edit] then reinstall the x86 versionORIGINAL: jcjordan
I'm fairly sure it's 32 bit Vista that I've got as much as I hate Vista. I've got the 3 vcredist files listed in a folder in the main AE folder called redist. The files are vcredist_IA64, vcredist_x64 & vcredist_x86 & all are dated 9/9/2009 & look to be version 6.0.2900.2180. So I should get rid of all of these & just get the x86 version?
Also I've had some unfortunate users have to go back to the original C++ redistribution, then have to SP1 it... I'm hoping you won't have to do this.


