WitPTracker AE Release 1.11 Available!

[Historiker]

I reinstalled it, and there are new problems.

[floydg]

ORIGINAL: Historiker

I reinstalled it, and there are new problems.

Make sure you copy the latest pwsdll.dll file from the game folder to the WitPTracker folder, remove the trackerdb.* files and try again.

That was my sig at some point... [;)]

[BigDuke66]

ORIGINAL: floydg
Okay, I understand your point. I could check if an LCU has no destination but changed location to catch that case, but I think it will add in other cases as well, such as when an LCU unloads from a ship and when an LCU is moved by air transport. If those additional cases are undesireable, then you're out of luck on these "same turn moved" cases.

Sounds great and that these additional cases are covered too is also very helpful.

BTW will there be a beta for the new tracker version or will you release a final 1.9 right away?

[Historiker]

awesome, its finally running!

I doubt it is even possible to play the Jap side without the tracker. Matrix should buy you in [:)]

[witpqs]

ORIGINAL: floydg

ORIGINAL: BigDuke66

ORIGINAL: floydg

I'm looking at the code and it doesn't care about strategic or non-strategic move. It checks the last turn's destination and then compares it with the new turn's location. If the same and it wasn't there before, the alert is generated. If it's not happening, I'd need a specific example.

The suggested alert is possible, but currently we don't read the pack/unpack time from the save. I'll see what can be done.

Floyd

I think that's the point.
I always load the autosave, now(after the Tracker read the autosave) if a unit is sitting in strategic mode at the start of the turn and then a location is set to move to it will not be recognize before the next autosave is read by the tracker but when the unit already arrives next turn then there is nothing to compare in the autosave as the location it was ordered to move to is already reached and that info was deleted.
So basically in one autosave no destination is set and in the next autosave there is also no destination set but the unit is at a different location than before.
I hope I explained it understandable.

All this usually doesn't happen because the player changes the unit to strategic mod & sets a destination the same turn and this will be read out of the next autosave before then unit even started to move.

Okay, I understand your point. I could check if an LCU has no destination but changed location to catch that case, but I think it will add in other cases as well, such as when an LCU unloads from a ship and when an LCU is moved by air transport. If those additional cases are undesireable, then you're out of luck on these "same turn moved" cases.

I think those two cases you point out are desirable.

[floydg]

ORIGINAL: BigDuke66

ORIGINAL: floydg
Okay, I understand your point. I could check if an LCU has no destination but changed location to catch that case, but I think it will add in other cases as well, such as when an LCU unloads from a ship and when an LCU is moved by air transport. If those additional cases are undesireable, then you're out of luck on these "same turn moved" cases.

Sounds great and that these additional cases are covered too is also very helpful.

BTW will there be a beta for the new tracker version or will you release a final 1.9 right away?

I'll see what I can do.

No beta - it is what it is. If something is badly broken, we'll fix it quickly.

[BigDuke66]

Thanks.

Now I have to come back to the sunk ship list.
Seems to me that some additional fog of war is laid on the sunk ship list that causes the tracker to display strange results:
84 Ship CS Chitose Enemy ship falsely reported sunk Originally reported sunk on turn 37
85 Ship CS Chitose Enemy ship sunk Sunk by 500 lb GP Bomb at Legaspi

Now what is interesting is that in both turns the game keep displaying it as sunk on 18th December 41, also there was no "Falsely reported" entry in the OpsReport for turn 84 and the turn 37 that is mentioned isn't the turn it was reported sunk it's the turn this message was in the allied OpsReport:
CS Chitose is reported to have been sunk near Legaspi on Dec 18, 1941

Also strange that the CS Chitose wasn't reported as sunk before so how can the tracker come up with a "Enemy ship falsely reported sunk" message?


I can provide the autosave files for this and the last turn, need something else?

[BigDuke66]

Another thing you might want to look at are the TOE upgrade alerts:
This seem to be the usual:
83 LCU 6th Medium Regiment TOE of LCU upgraded Located at Madras

But what about this one, the alert name is different, no unit is listed and also no base:
85 LCU 41 Armoured Tank Regiment TOE upgraded
This alert was for the 2/4th Armored Regiment, an Australien unit.

EDIT:
This is strange I now had a tracker alert for 2/4th Armored Regiment and that it upgraded it's TOE.
Can it be that the former alert was a general alert that a new TOE is available for a formation?

[JocMeister]

I´ve started having huge problems loading tracker. I get no error messages at all. I have to try several times before I get it to start properly. I click the bat file as usual and it pops up normally but then just stays there. I have tried letting it stay that way for a hour and still no luck. I then close the window and try again several times and suddenly it works. Any ideas what could be causing this?


Loading takes between 80-200 seconds when I does work.

[floydg]

ORIGINAL: JocMeister

I´ve started having huge problems loading tracker. I get no error messages at all. I have to try several times before I get it to start properly. I click the bat file as usual and it pops up normally but then just stays there. I have tried letting it stay that way for a hour and still no luck. I then close the window and try again several times and suddenly it works. Any ideas what could be causing this?


Loading takes between 80-200 seconds when I does work.

Not really sure. Could be a slow PC... how does it perform if you reboot the PC and run just WitPTracker?

[JocMeister]

ORIGINAL: floydg

ORIGINAL: JocMeister

I´ve started having huge problems loading tracker. I get no error messages at all. I have to try several times before I get it to start properly. I click the bat file as usual and it pops up normally but then just stays there. I have tried letting it stay that way for a hour and still no luck. I then close the window and try again several times and suddenly it works. Any ideas what could be causing this?


Loading takes between 80-200 seconds when I does work.

Not really sure. Could be a slow PC... how does it perform if you reboot the PC and run just WitPTracker?

Well I have a 3,4GHz quad core with 8GB DDR3 so I doubt its that.
Any ideas on what I could try?

[floydg]

ORIGINAL: JocMeister

ORIGINAL: floydg

ORIGINAL: JocMeister

I´ve started having huge problems loading tracker. I get no error messages at all. I have to try several times before I get it to start properly. I click the bat file as usual and it pops up normally but then just stays there. I have tried letting it stay that way for a hour and still no luck. I then close the window and try again several times and suddenly it works. Any ideas what could be causing this?


Loading takes between 80-200 seconds when I does work.

Not really sure. Could be a slow PC... how does it perform if you reboot the PC and run just WitPTracker?

Well I have a 3,4GHz quad core with 8GB DDR3 so I doubt its that.
Any ideas on what I could try?

WitPTracker takes longer to start up as you load more turns. It is completely deterministic -- with the same saved database, the start-up is exactly the same.

If you have the same number of turns loaded and the start-up time varies, it has to be the PC itself -- other programs running/accessing the hard drive, etc. Even the best PC can get bogged down.

Please try running WitPTracker on a freshly rebooted PC with nothing else running and see if the start-up time changes.

Floyd

[JocMeister]

Same thing. Fails to start a few times and then suddenly it works. I just rememberd that I had some problems with tracker before. Not enoght memory or something like that. I can´t remember were I read it but I did change the numbers in witptracker.bat to -Xms512m -Xmx768m and that solved it.

Could it be related?

[BigDuke66]

What Windows do you use? Maybe a 64-Bit version would help.
Also try to defrag the tracker database.

[Crimguy]

I give up. Cannot get it to run under Windows 7 x64. Keep getting the java out of memory error. I tried all the workarounds listed on the site.

[JocMeister]

BigDuke66, I have Win 7 64bit so that doesn´t help

[dorjun driver]

ORIGINAL: JocMeister

BigDuke66, I have Win 7 64bit so that doesn´t help

How much memory? I've got 8 gig and use -Xms512m -Xmx768m. The thing runs like a champ.

[JocMeister]

ORIGINAL: dorjun driver

How much memory? I've got 8 gig and use -Xms512m -Xmx768m. The thing runs like a champ.

So do I. Still fails to load without message most of the times. What kind of loadingtimes to you get?

[dorjun driver]

About 19" for scenario #1. Right now I'm only 10 turns in so there's that. On the other hand, I'm using a three year old processor (AMD Phenom II X2 550).

[JocMeister]

I´m getting around 80s but we are on turn 127 so thats probably to be expected. Today it started on the 3rd try. New record I think :p