|
floydg -> RE: WitPTracker AE Release 1.1 (10/4/2009 8:41:47 PM)
|
quote:
ORIGINAL: Kull
quote:
ORIGINAL: floydg
Folks, the latest release of WitPTracker AE is now available.
<snip>
We hope you enjoy it. As always suggestions, comments and bug reports welcome.
Damian and Floyd
Thanks guys. Works like a charm on both the 32 & 64 bit Vista's. Nice to see the addition of "Task Forces" as a csv Export. I probably should have mentioned that "Ships" would also be a very useful CSV (Duh on me for forgetting). Under the category of "suggestions", let me lay out what I'm working on and tell me if it's something you might be able to support in a future version:
As everyone knows, the opening turn (Day 2) of WitP was a mammoth affair, and under AE it's oders of magnitude worse - almost beyond the capabilities of a human being to manage without a master plan. So what I'm trying to do is develop a template that has every location on the map, along with everything based there, so that players can go through and sequentially "check off" everything they are doing, one location at a time. Part of that includes a large "comment field" where players can write down specifically what they are doing. So in location "x" you would begin by doing "base things" (expanding forts or airfields), if there's industry then change settings if desired, then move on to aircraft (search settings, mission types, upgrades, movement to another location, etc), then to the land units (some stay, some go, etc), and finally ships (which ones go into which task forces, what are they carrying, where are they going, etc). It's a mammoth undertaking, but worth it insofar as the player only has to do it once, and can then refer back anythime they start a new game or decide to tweak their approach over time.
The problem here is that "location" is really the "key field", and although WitP Tracker is a GODSEND in gathering most of the starting position information, the various csv files use different formats for the location field. As an example, let's look at Pearl Harbor:
Bases: 180,107
Air Groups: Pearl Harbor
LCUs: Pearl Harbor (180,107)
TFs: 180,107 (Pearl Harbor) [7]
Industry: Pearl Harbor
There are others, but you get the point. Now I can kludge something that will tie them all together but it would be really nice if all reports/outputs had two different location fields. The first would be the physical hex location, while the second would be the location name (if applicable). That would standardize the handling of locations and easily enable folks to link the reports together using the hex location (which, by definition, is unique to every hex on the map), while still including the "name", which is a much more "human friendly" way to spot a location for those using individual reports.
Yeah, I think I got the gist of this. I'd like to do something similar (and had some basic ideas formulating). But for now, our priority is to add AE-specific data that we're missing you can further immerse yourselves in numbers, settings and options.
|
|
|
|
