WitPTracker AE News

[floydg]

ORIGINAL: Deerslayer

ORIGINAL: floydg

ORIGINAL: Deerslayer

I'm enjoying this tool guys and thanks for doing it but confused about something. After I set up with the batch file everything is fine. But when I tell it to Read in a new turn later on, it just jumps out of the tool to my Desktop and does nothing. What am I missing?

It's gotta be a JVM memory issue. Are you sure you started from the witptracker.bat file?

Floyd

I ran the batch when I first installed. Do I have to run the batch ever time I want to run Tracker? When I run the batch first time the turn is there and all the data. But later turns that I try to "read" in do nothing.

You need to run the batch each time or ensure that the JVM has the needed memory allocation.
If you run from the witptracker.jar directly, you won't get the proper memory settings.

[floydg]

ORIGINAL: pad152

Japanese Base (1404) Utsonomiya is showing up as in the Soviet Union when looking at aircraft production, it's on the main island of Honshu.

Update your regions. See the Regions page on the WitPTracker website for instructions.

[floydg]

ORIGINAL: Moss Orleni

I went through all steps yesterday...
but tried a second time today and succeeded (I guess it was a typo somewhere)!

Looking at the data right now, but will take some time to decypher. Especially, as you mentioned, the delta values. Are the item explanations of the delta tables included somewhere in the DB?

I will try to summarize the data that would be interesting to have (I suspect I won't be too much in the end).

Thanks,

Moss

The deltas are all in the code and not defined externally anywhere.

All of the data in the database is displayed in WitPTracker one way or another. There is no hidden data in there...

[floydg]

Folks, the latest release of WitPTracker AE is now available.

New Features:
[*]Minefield panel shows count of ACM
[*]Export to CSV for Task Forces
[*]Display of pilot training pool
[*]Additional items related to ship classes added and displayed in Ship Class panel
[*]Filters added to Ship Class panel
[*]Ship Class upgrade delay, damage and yard size shown in Ship Upgrade panel
[*]Task force detection levels shown in Task Force panel and alerts added related
[*]Leader panel filter for unassigned/active added

Bugs Fixed:
[*]Sorting and filtering in Ship panel fixed
[*]"Custom" TOE's show up strange in formation after reading in a new turn
[*]LCU and Formation device usage when the TOE repeats devices (this was a tricky one)
[*]Aircraft for multiple nations in Aircraft Comparison, Air Group and Air Production panels (first two show the nation in <braces> in the filter choices)
[*]LCU replacement flag was not properly read
[*]Ordering of turns when using the multi-turn read function
[*]Minefield delta was off
[*]Sunk ships that had a "base near" that was not valid
[*]LCU objects with a device ID greater than 1300 now read in
[*]LCU arrival base fixed
[*]Air loss filter by side in Victory Points panel
[*]Sorting by date in Sunk Ships in VP panel and Ship Class panel
[*]Victory points for ships (approximate, but very close, algorithm used)

The distribution can be found on this page.

One important note: the database had a bunch of changes needed, so the expedient thing was to require you to restart with a fresh database. Therefore, you need to delete your current database (trackerdb files) and start from scratch.
For future releases, we'll try to incorporate a database upgrade function like we had for "classic" WitPTracker, but I think we just wanted to get this out...

We hope you enjoy it. As always suggestions, comments and bug reports welcome.

Damian and Floyd

[n01487477]

Hey Floyd,
sure you built the right thing ? Looks like 1.01 to me ???

--Damian--

[floydg]

ORIGINAL: n01487477

Hey Floyd,
sure you built the right thing ? Looks like 1.01 to me ???

--Damian--

[:@] Sorry, I picked up the wrong file. Try it now.

Early adopters of things always get shafted one way or another... [;)]

[Nomad]

Much better Floyd. Thanks guys.

[n01487477]

Just a quick note so you know what is happening with the Detection Increase alert, we made it so that the alert is triggered when the Maximum detection >= 6 and that, that turn the detection lvl > 3.

If you think this needs to be adjusted for the next build let us know ... also I'll make sure that a TF history is included for next build so you can see movement and detection levels.(and possibly a filter which will look at this change).

AirGroups and Pilots - (apart from the filters wrapping to the next line), Floyd has kindly changed the drop down so that all the variants of Allied planes are available ... this was needed so the UpgradeTo special filter works for the Allies now. Pilot training pool looks good.

Anyway, hopefully next build we can get away from the tedium of bug fixes and give you guys some more new features.[;)]

[Nomad]

In Airgroups and Pilots, the HQ selection filter is missing a number of HQs.

[n01487477]

In Airgroups and Pilots, the HQ selection filter is missing a number of HQs.

Yeah, the sub HQ's need to be linked to the Parent HQ, eg. 12th Air Fleet -> 5th Air ... sorry we'll do that next time [:(]

--Damian--

[Nomad]

Not a problem, just making sure you know and it is on the fixit list. [8D]

[jhdeerslayer]

ORIGINAL: floydg

ORIGINAL: Deerslayer

ORIGINAL: floydg




It's gotta be a JVM memory issue. Are you sure you started from the witptracker.bat file?

Floyd

I ran the batch when I first installed. Do I have to run the batch ever time I want to run Tracker? When I run the batch first time the turn is there and all the data. But later turns that I try to "read" in do nothing.

You need to run the batch each time or ensure that the JVM has the needed memory allocation.
If you run from the witptracker.jar directly, you won't get the proper memory settings.

OK gotcha as running the .jar was what I was doing. So what is the purpose of Reading in Turns (or multiple ones) if you have to run the Bat? I checked the Java Control Panel but didn't find any memory options. Sorry to be a pest but curious about all this.

[floydg]

The .bat script only starts the program.

The program detects if there is a database or not. If not, it creates a new one. But once one is created, it won't be created again.

Once the program is running, you can load new turns, check histories of the loaded turns, etc.

[floydg]

ORIGINAL: Nomad

Not a problem, just making sure you know and it is on the fixit list. [8D]

Fixed (for next release).

I populated the drop-down based on which HQ had Air groups assigned. This way the list doesn't contain loads of HQ with no groups. Sound good?

[Nomad]

ORIGINAL: floydg

ORIGINAL: Nomad

Not a problem, just making sure you know and it is on the fixit list. [8D]

Fixed (for next release).

I populated the drop-down based on which HQ had Air groups assigned. This way the list doesn't contain loads of HQ with no groups. Sound good?

Perfect. [&o]

[Bullwinkle58]

I'm not to the point I can ask all these cool questions about Java and such. I'm still stuck on the install directions.[:)]

I have a post-patch, AI game. I set the switches on December 10, 1941 to auto-save every day. I'm now in mid-March 1942, so I have a big Autosave sub-folder of saves. I manually save in slot six.

So, when I edit WITPtracker.properties, do I point it at slot six, or do I point it at the first autosave? If slot six, does the manual save "get bigger" each time it saves so it has the day-by-day history, or is it a snap-shot of March 15th only? If I do the AUtosave pointer, does the program "step-through" the sequentially-named autosaves to generate the day-by-day history? (Like WITPStaff does.)

This may be apparent once the program is fired up, but I never used WITPTracker the first time. Just a suggestion, but uyou might want to edit the Set-Up instrucitons to cover the Autosave switches.

I'll put this aside for now unitl I get an answer. From what I see, this looks like a great tool, and believe me, I need the [8D]help.

[floydg]

ORIGINAL: Bullwinkle58

I'm not to the point I can ask all these cool questions about Java and such. I'm still stuck on the install directions.[:)]

I have a post-patch, AI game. I set the switches on December 10, 1941 to auto-save every day. I'm now in mid-March 1942, so I have a big Autosave sub-folder of saves. I manually save in slot six.

So, when I edit WITPtracker.properties, do I point it at slot six, or do I point it at the first autosave? If slot six, does the manual save "get bigger" each time it saves so it has the day-by-day history, or is it a snap-shot of March 15th only? If I do the AUtosave pointer, does the program "step-through" the sequentially-named autosaves to generate the day-by-day history? (Like WITPStaff does.)

This may be apparent once the program is fired up, but I never used WITPTracker the first time. Just a suggestion, but uyou might want to edit the Set-Up instrucitons to cover the Autosave switches.

I'll put this aside for now unitl I get an answer. From what I see, this looks like a great tool, and believe me, I need the [8D]help.

Right now, the autosave aspect isn't dealt with. So you'll need to set a specific file name in the witptracker.properties, such as wpae003.pws, and then you'll need to rename the saves to something like that name each time you want to read a turn (e.g., wpae003.pws.123, wpae003.123.pws, etc).

Hope that helps.

Floyd

[Bullwinkle58]

ORIGINAL: floydg

ORIGINAL: Bullwinkle58

I'm not to the point I can ask all these cool questions about Java and such. I'm still stuck on the install directions.[:)]

I have a post-patch, AI game. I set the switches on December 10, 1941 to auto-save every day. I'm now in mid-March 1942, so I have a big Autosave sub-folder of saves. I manually save in slot six.

So, when I edit WITPtracker.properties, do I point it at slot six, or do I point it at the first autosave? If slot six, does the manual save "get bigger" each time it saves so it has the day-by-day history, or is it a snap-shot of March 15th only? If I do the AUtosave pointer, does the program "step-through" the sequentially-named autosaves to generate the day-by-day history? (Like WITPStaff does.)

This may be apparent once the program is fired up, but I never used WITPTracker the first time. Just a suggestion, but uyou might want to edit the Set-Up instrucitons to cover the Autosave switches.

I'll put this aside for now unitl I get an answer. From what I see, this looks like a great tool, and believe me, I need the [8D]help.

Right now, the autosave aspect isn't dealt with. So you'll need to set a specific file name in the witptracker.properties, such as wpae003.pws, and then you'll need to rename the saves to something like that name each time you want to read a turn (e.g., wpae003.pws.123, wpae003.123.pws, etc).

Hope that helps.

Floyd

Well, it helps a little.[:)]

I got it to run (neded curent Java, but I did that.)
I got it to load my current save from Slot 7, which is March 10, 1942. All the data was there, everything was stable. But I wanted the history, so I erase all the DB files, re-edited the properties to point at autosave\wpae011.pws, which is December 8, 1941. That loaded fine, program stable.
then I tried to load multiple turns, and I don't get any .pws files displayed at any level in the file tree. Not at SAVE\ or at SAVE\autosave. No files names of any kind.

So, from your note above, if I want the day-by-day autosaves, do I need to hand edit all 100+ .pws files in the autosave folder to have a ".xxx" suffix, or do I have to drag them out to the \SAVE level of the tree, or what? I guess I'm not understanding why I get no file names to display when Properties are set OK to load the first turn, and the program's directions say the multi-turn function will fetch .pws files from anywhere on the HD. The autosaves are all in sequential order as wpae012.pws, etc.

I understand that you're being bombarded with quesitons (this thread gre by three pages just as I was reading from the start this morning to see if my questions had been addressed), but I think dealing with the Autosave switches would be a good use of update time for AI-players who, like me, decide to jump in after playing months of an AI-game. I guess PBEM players just drag the save into the Tracker folder and play slowly that way, but AI players usually play multiple turns per day. I'd hate to lose the first four months of my war.

[Bullwinkle58]

I played around some more, and I think I answered my own question. Obviously, Tracker sees Save\apae011.pws as different than Save\autosave\apae011.pws. Maybe an unfortunate design decision by the the original team to make two 011.pws files possible, one auto- and one manual.

The only way I see to catch up to March 10, 1942 when all I have is autosave files, is to move all 100+ up to the Save\ level in the tree, set program Properties to read Save\apae011.pws to load December 8, 1941, then HAND EDIT each formerly autosaved file to be "apae011.pws.123", "apae011.pws.124", etc, then load them into the DB, THEN go back to Properties and change the target save to "apae007.pws" (my current, March 10, 1942 \Save-level manual save), and then remember to load data on every turn thereafter manually from apae007.pws.

Whew. Today is my birthday, so I don't think I'm going to do that. I'll probably just punt, start from March, 1942, and live without the history.

But I think adding code to make autosaves loadable natively would be a huge advance for the program and us AI-players.

[invernomuto]

Thanks for the update!