Slitherine

quote:

ORIGINAL: mikemike

Have just installed 1.1.1. It's running fine. Carry on the splendid work, guys!

And now my fresh crop of nits:

The Air Groups and Pilots data set, tab Pilots, doesn't seem to show pilots with more than five kills.

Ship Production: The numeric sort on the Delay column is, of course, really helpful. But the Accel Delay column would be even more helpful if you calculated the value as follows:
ACC_DELAY := (DELAY+1) DIV 2; (PASCAL syntax, I'm not current on JAVA)
( in BASIC this would be AD = INT((DL + 1) / 2) )
Perhaps it would be better, anyway, to scrap the Accel Delay column totally and just put the calculated delay for accelerated ships in the Delay column; this way one could instantly see which ships will arrive in which turn instead of correlating two different columns.

The running total in the Build Points column serves no real purpose and might be dispensed with, the total is displayed in the header anyway, and if you sort the data set, you'll have to hunt for the maximum value.
The What-If columns are a nice feature, but have a bug: if you change the Calc-BR value of any ship, the Calc Points value for any ship that is accelerated but has a positive value in the Start Building column is re-calculated incorrectly which throws the total off whack; this seems to be connected to their status being Building. The Calc Points column, too, might benefit if you took out the running total display and put the end sum into the header panel.

quote:

ORIGINAL: Nomad

Any idea on what happened to my Database? I have not upgraded yet.

My list of arrived ships is very long and seems to include every ship I will get someday.

quote:

ORIGINAL: Thesix

I just tested again with the Andrew's Map scenario and... it works
Great, thank you very much!

Too late now to test more, I go to bed.

quote:

ORIGINAL: mikemike

Have just installed 1.1.1. It's running fine. Carry on the splendid work, guys!

And now my fresh crop of nits:

The Air Groups and Pilots data set, tab Pilots, doesn't seem to show pilots with more than five kills.

quote:


ACC_DELAY := (DELAY+1) DIV 2; (PASCAL syntax, I'm not current on JAVA)

quote:

ORIGINAL: Local Yokel

1.1.1 installed and working, though I received the following warning:

"WARNING: Unknown keyword found in properties file."

Doesn't seem to have adversely affected anything obvious, save that where items are tracked over successive turns, the two turns prior to the current one seem to have been assigned zero values in some cases - this is so with damage to ships on ships repairs screen and first base only that is selected for display of base basic history.  Values for the two turns prior to the current one for base resource history also seem to have been zeroed throughout.  Not a big deal, but odd.

Also, I'm able to resize the height of the window in which Tracker is displayed, but its width automatically enlarges then freezes at the enlarged size - this behaviour first occurred with this version.  In prior versions I found basic window management fragile: app. would abnormally end when resizing, maximising or moving the main window.  A problem with the Java runtime I'm using, perhaps? I'm on Version 6 Update 5 (build 1.6.0_05-b13).

So much for the brickbats - far outweighed by the usefulness of the enhancements, especially proper numeric sorting; worth the update for this alone.  Thanks a lot!

quote:

ORIGINAL: floydg

quote:

ORIGINAL: Nomad

Any idea on what happened to my Database? I have not upgraded yet.

My list of arrived ships is very long and seems to include every ship I will get someday.

The only thing I can think of is that the initial DB did not contain any of the ships and then when you read in a turn, all of them showed up as "new". But I don't know why the initial DB didn't have the ships.

If you want to send the files, you can send them to witptracker@gmail.com and I'll have a look. Send the initial save, the save you read (I assume this was the second turn you read in) and the properties file.


- Floyd

quote:

ORIGINAL: Nomad

quote:

ORIGINAL: floydg

quote:

ORIGINAL: Nomad

Any idea on what happened to my Database? I have not upgraded yet.

My list of arrived ships is very long and seems to include every ship I will get someday.

The only thing I can think of is that the initial DB did not contain any of the ships and then when you read in a turn, all of them showed up as "new". But I don't know why the initial DB didn't have the ships.

If you want to send the files, you can send them to witptracker@gmail.com and I'll have a look. Send the initial save, the save you read (I assume this was the second turn you read in) and the properties file.


- Floyd

As you can see, I have read in a large number of turns.

quote:

Hakkaido is not connected tot he rest of Japan so I want it as a separte region which I've created but I can't work out how do I add, or delate bases from regions?

quote:

ORIGINAL: herwin

The first time I loaded a turn it worked fine, but the second was hosed. Has anyone else seen this?

quote:

ORIGINAL: ny59giants

quote:

Hakkaido is not connected tot he rest of Japan so I want it as a separte region which I've created but I can't work out how do I add, or delate bases from regions?

I've done the clusters for Big B's and Empire's Ablaze, so I'm kinda good at this.
Go to File. Then to the "Regions." Click on "New" and make one named "Hakkaido." Now you can go back into "Bases" and change the bases to your new Region. Voila, you are there!!

I don't remember if they take effect right away or have to wait for the next turn to be loaded.

quote:

ORIGINAL: floydg

quote:

ORIGINAL: herwin

The first time I loaded a turn it worked fine, but the second was hosed. Has anyone else seen this?

What about it wasn't working?

quote:

ORIGINAL: herwin

quote:

ORIGINAL: floydg

quote:

ORIGINAL: herwin

The first time I loaded a turn it worked fine, but the second was hosed. Has anyone else seen this?

What about it wasn't working?

My opponent tells me he saw the sync bug with that turn. It may be a hosed save file.

quote:

ORIGINAL: Chris H

Air groups showing no leader when there is.

quote:

ORIGINAL: floydg

quote:

ORIGINAL: Chris H

Air groups showing no leader when there is.

I'm sure the Air Group does have a leader. I've seen some cases where leaders are missed from the save file. Can you verify that the actual leader appears in the Leaders panel?

quote:

ORIGINAL: Chris H

OK can somebody help please. I-27 is due in three days but the Durability is 25, greater than delay. Ships are built when Dur*10>delay but the figures make no sense?

I've got ships in the queue that havn't started to be buit yet but there Dur etc is less than the delay. I'm missing somthing here and i can't spot it.

quote:

Maybe I should start a tutorial page ... on this and other things, if the *.pdf and other forum area's are not enough explanation ...

quote:

ORIGINAL: n01487477

quote:

ORIGINAL: Chris H

OK can somebody help please. I-27 is due in three days but the Durability is 25, greater than delay. Ships are built when Dur*10>delay but the figures make no sense?

I've got ships in the queue that havn't started to be buit yet but there Dur etc is less than the delay. I'm missing somthing here and i can't spot it.

OK. some thing you need to understand first
1. Ships are able to build if their durability * 10 < delay. These ships can be
accelerated, at triple the durability cost. or it means that "Start Building" is (-) numbers (how many day it has been building)

2. Ships not in the first group, but can be built at accelerated if durability * 30 < delay. The
cost to accelerate these equals durability.

3. Ships Durability * 10 = the normal number of days to build a vessel. Also adding Delay and Start Building give total build time.

4.Build Points/Aggregate - just gives a running total as you go down the list.

5.The other columns are to manually calculate ... via a drop down on the CalBr column.

6.Durability is a constant, it never changes ... for building.

OK so in your example:
1. SS I-27 25*10 = 250, so it commenced building when it's delay was 250 days. And continued building, as delay reduced one day per turn from then on. It started building -247 days ago, so it has 3 days remaining.
2. It's build points are equal to durability = 25 (disregard the aggregate for now - it's for my calculations - it shows the aggregate total for ships building)