June Release: WitPTracker now at 1.6!
Moderators: Joel Billings, wdolson, Don Bowen, mogami
RE: WitPTracker 1.3.1
yes, exactly. Thanks!
RE: WitPTracker 1.3.1
Saw a post on the Matrix tech forum ... I hope this helps ...


- Attachments
-
- Trackersetup.jpg (158.68 KiB) Viewed 267 times
- khyberbill
- Posts: 1941
- Joined: Tue Sep 11, 2007 6:29 pm
- Location: new milford, ct
RE: WitPTracker now at 1.3.1
How can one print out a file. I am interested in the disposition of LCU's. What is the best way to print this file out for each command?
"Its a dog eat dog world Sammy and I am wearing Milkbone underwear" -Norm.
RE: WitPTracker now at 1.3.1
ORIGINAL: khyberbill
How can one print out a file. I am interested in the disposition of LCU's. What is the best way to print this file out for each command?
We don't support printing (yet).
We're focusing on adding basic functions first (and we're almost done with that, I suspect) and then adding additional "nice-to-have" stuff later.
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.
-
- Posts: 1756
- Joined: Fri Jan 11, 2008 5:15 pm
- Location: Brussels, Belgium
RE: WitPTracker now at 1.3.1
Copy/pasting into excel files works well enough, for now at least, and you can easily delete the lines and/or columns you don't need, or move them to group as you see fit.
The only panel where it's a bit difficult, is the summary panel, but that may be pasted to word files.
The only panel where it's a bit difficult, is the summary panel, but that may be pasted to word files.
-
- Posts: 7485
- Joined: Thu Jan 17, 2002 10:00 am
- Location: Cottesmore, Rutland
RE: WitPTracker now at 1.3.1
Can you add HI to the Regioanl Fct/Resources screen.
- khyberbill
- Posts: 1941
- Joined: Tue Sep 11, 2007 6:29 pm
- Location: new milford, ct
RE: WitPTracker now at 1.3.1
Copy/pasting into excel files works well enough, for now at least, and you can easily delete the lines and/or columns you don't need, or move them to group as you see fit.
The only panel where it's a bit difficult, is the summary panel, but that may be pasted to word files.
I tried to copy and paste to an excel file and could not copy. What am I missing?
"Its a dog eat dog world Sammy and I am wearing Milkbone underwear" -Norm.
RE: WitPTracker now at 1.3.1
Yes I have wanted to do this for a while ... I'll try to remember next time ...ORIGINAL: Chris H
Can you add HI to the Regioanl Fct/Resources screen.
-
- Posts: 1756
- Joined: Fri Jan 11, 2008 5:15 pm
- Location: Brussels, Belgium
RE: WitPTracker now at 1.3.1
You first need to highlight what you want to copy, then use the CTRL-C/V shortkeys. If you don't highlight, it doesn't work.ORIGINAL: khyberbill
Copy/pasting into excel files works well enough, for now at least, and you can easily delete the lines and/or columns you don't need, or move them to group as you see fit.
The only panel where it's a bit difficult, is the summary panel, but that may be pasted to word files.
I tried to copy and paste to an excel file and could not copy. What am I missing?
-
- Posts: 1756
- Joined: Fri Jan 11, 2008 5:15 pm
- Location: Brussels, Belgium
RE: WitPTracker now at 1.3.1
Sorry, after checking, it doesn't work for every panel. Alerts, Devices, Victory points (and related air losses & ships sunk) are ok with that, but LCUs, airgroups and ships are not : only one line at a time may be copied/pasted, albeit I don't know what's different there (I never tried to copy those previously).
RE: WitPTracker now at 1.3.1
Floyd, if I remember correctly you are also using hsqldb. It is surprisingly easy to dump to .csv with it. You can quite simply tell it to dump every table (maybe even works on views). That might help people even more than printing.ORIGINAL: floydgWe don't support printing (yet).ORIGINAL: khyberbill
How can one print out a file. I am interested in the disposition of LCU's. What is the best way to print this file out for each command?
We're focusing on adding basic functions first (and we're almost done with that, I suspect) and then adding additional "nice-to-have" stuff later.
(Just looking around

RE: WitPTracker now at 1.3.1
I really hope you huys get this going with AE.
This program is awsome!!![:D]
This program is awsome!!![:D]
RE: WitPTracker now at 1.3.1
Hello [:)]
Still fighting mistakes here and there! [:D]
1. I found something strange in the Air Production screens. Sorry if already mentioned before.
In the Upgrades Tab, the LB-30 Liberator shows no upgradable plane group (109 in pool) but the 7th BG equipped with B17E can upgrade to LB-30.

Is it because the 7th BG is divided in 3 groups?
2. Still in the Air Production screen, but in the Overview Tab, maybe I don't understand the Build status B + NotB but if it means Building + Not building planes, then it seems to be wrong. It's easy to check with the allied patrol planes and the Do 24K-2 which is not build anymore. It appears only with the Build Status set to "All". I understand it should appear also with the Status set to "B + NotB". Am I right?


3. Already said before but I don't know if you could not find the information in the database or if you simply forgot: The task force screen shows the ASW TF as Surface Combat instead.[;)]
Finally, a wish for the alert screen if you find a way to let us select the type of alerts we want:
I would like to see the pilots who come back after being WIA or MIA.
This is a request that would be interesting for the AAR authors.
Thanks again for this great job which make the witp experience even better...
Still fighting mistakes here and there! [:D]
1. I found something strange in the Air Production screens. Sorry if already mentioned before.
In the Upgrades Tab, the LB-30 Liberator shows no upgradable plane group (109 in pool) but the 7th BG equipped with B17E can upgrade to LB-30.


Is it because the 7th BG is divided in 3 groups?
2. Still in the Air Production screen, but in the Overview Tab, maybe I don't understand the Build status B + NotB but if it means Building + Not building planes, then it seems to be wrong. It's easy to check with the allied patrol planes and the Do 24K-2 which is not build anymore. It appears only with the Build Status set to "All". I understand it should appear also with the Status set to "B + NotB". Am I right?


3. Already said before but I don't know if you could not find the information in the database or if you simply forgot: The task force screen shows the ASW TF as Surface Combat instead.[;)]
Finally, a wish for the alert screen if you find a way to let us select the type of alerts we want:
I would like to see the pilots who come back after being WIA or MIA.
This is a request that would be interesting for the AAR authors.
Thanks again for this great job which make the witp experience even better...
RE: WitPTracker now at 1.3.1
Thesix,
glad you are still alive and kicking ... hope all is good on the French Witp site.[;)]
As to your problems:-
1. The Upgrade screen really needs an overhaul, it was never very good, and was configured for a stock game, playing as the japanese. I have some time coming up (another holiday), where I might sit down and figure out what is going on...
2. The build + not build ... The Not building is for planes that can be built (their date) & their factory has factories NOT building. This is not to show planes which have NO factories. I did it because I switch on/off my production for planes, so I could check which are off.
3. Still working on that, the TF names are different to the numerous buttons on screen(Replenishment/Tanker/etc). But I am still looking and there must be a way to determine the difference...it is something that has mystified me for months now... Floyd can testify to that ...
4. I have alerts for Aces coming back to action, but as yet have never seen it occur. Maybe I should have set the Alert for any pilots, but I might do some testing on this as I don't want too many Alerts ... (but we are thinking about filtering here anyway)
(I bet if Nemo was using tracker in our game he would be sick of all his pilots becoming aces everyday).
Thanks for your thoughts and complements ... It is good when people are polite about their requests ...
glad you are still alive and kicking ... hope all is good on the French Witp site.[;)]
As to your problems:-
1. The Upgrade screen really needs an overhaul, it was never very good, and was configured for a stock game, playing as the japanese. I have some time coming up (another holiday), where I might sit down and figure out what is going on...
2. The build + not build ... The Not building is for planes that can be built (their date) & their factory has factories NOT building. This is not to show planes which have NO factories. I did it because I switch on/off my production for planes, so I could check which are off.
3. Still working on that, the TF names are different to the numerous buttons on screen(Replenishment/Tanker/etc). But I am still looking and there must be a way to determine the difference...it is something that has mystified me for months now... Floyd can testify to that ...
4. I have alerts for Aces coming back to action, but as yet have never seen it occur. Maybe I should have set the Alert for any pilots, but I might do some testing on this as I don't want too many Alerts ... (but we are thinking about filtering here anyway)
(I bet if Nemo was using tracker in our game he would be sick of all his pilots becoming aces everyday).
Thanks for your thoughts and complements ... It is good when people are polite about their requests ...
RE: WitPTracker now at 1.3.1
Ah ok, it's clear.ORIGINAL: n01487477
2. The build + not build ... The Not building is for planes that can be built (their date) & their factory has factories NOT building. This is not to show planes which have NO factories. I did it because I switch on/off my production for planes, so I could check which are off.
Yes, you are right, Aces coming back is enough. I have an example in my game of an Ace coming back after 12 days WIA. The alert appeared when he became WIA but not when he came back. But on the other hand, and I will check that again later today, I think I see him in witptracker as being alive (no status WIA or MIA or KIA) but I can't see him in game anymore, then i don't know if it's a good example [:D]ORIGINAL: n01487477
4. I have alerts for Aces coming back to action, but as yet have never seen it occur. Maybe I should have set the Alert for any pilots, but I might do some testing on this as I don't want too many Alerts ... (but we are thinking about filtering here anyway)
(I bet if Nemo was using tracker in our game he would be sick of all his pilots becoming aces everyday).
RE: WitPTracker now at 1.3.1
ORIGINAL: Woos
Floyd, if I remember correctly you are also using hsqldb. It is surprisingly easy to dump to .csv with it. You can quite simply tell it to dump every table (maybe even works on views). That might help people even more than printing.ORIGINAL: floydgWe don't support printing (yet).ORIGINAL: khyberbill
How can one print out a file. I am interested in the disposition of LCU's. What is the best way to print this file out for each command?
We're focusing on adding basic functions first (and we're almost done with that, I suspect) and then adding additional "nice-to-have" stuff later.
(Just looking around![]()
To more efficiently store the per-turn information, I made up a bunch of auxiliary tables, so a straight table dump could be a nightmare for most people to have to piece together information from bases, for example, from four different tables.
But we will probably come up with some table dump function so that people can import to Excel/etc and then re-arrange or print as needed.
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.
Device History
I've now added in reading and displaying of the device pools.
This is a history of the pool for a selected device:

Any suggestions on things to add or a different way to show it?
Thanks!
This is a history of the pool for a selected device:

Any suggestions on things to add or a different way to show it?
Thanks!
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: Device History
Yes it will be certainly useful to have this information for each LCU. But also a very interesting information could be to have a summary table in a specific screen, showing for a particular turn where, how and in which unit the different replacement (manpower, vehicles, armement) have been used. At the moment it's not obvious to find this information very quickly. I don't know if it's difficult or feasible for you to develop such a screen.
But your proposal will bring already very interesting information.
But your proposal will bring already very interesting information.
-
- Posts: 1756
- Joined: Fri Jan 11, 2008 5:15 pm
- Location: Brussels, Belgium
RE: Device History
Well, as you ask for it, I have a suggestion (already given, in fact) : listing the LCUs who have that device in their TOE, how many of them they should have, how many they have (possibly, active/disabled, but this is not very important), but especially how many they need to be filled, in order to properly plan the replacements of existing units. And of course, a column indicating whether the requesting LCU is allowed replacements or not would be the cherry on top of the cake.ORIGINAL: floydg
I've now added in reading and displaying of the device pools.
This is a history of the pool for a selected device:
Any suggestions on things to add or a different way to show it?
Thanks!
Or at least a column showing the total number of devices needed.
RE: Device History
Let me point my thinking from a scenario builder viewpoint:
I think for scenario editors proposes it would most important to know how many devices by type there are at start of a scenario since we can have that information number for most armies at war start.
If we know how many 75mm Howitzers Japanese had at war start and if the tracker can load a scenario and find the scenario quantity of that gun we can tweak the scenario until reaching the real value. With witp tracker would be easier to do and less prone to mistakes than with paper and pencil of adding 100's different values from all units that have them to find how many AT guns there are and if that number respects war start availability.
I think for scenario editors proposes it would most important to know how many devices by type there are at start of a scenario since we can have that information number for most armies at war start.
If we know how many 75mm Howitzers Japanese had at war start and if the tracker can load a scenario and find the scenario quantity of that gun we can tweak the scenario until reaching the real value. With witp tracker would be easier to do and less prone to mistakes than with paper and pencil of adding 100's different values from all units that have them to find how many AT guns there are and if that number respects war start availability.