RE: WitPTracker 1.0.2

RE: WitPTracker 1.0.2 (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> War In The Pacific - Struggle Against Japan 1941 - 1945

Message

floydg -> RE: WitPTracker 1.0.2 (4/24/2008 4:11:03 AM)
quote: ORIGINAL: ny59giants It would be nice to know the aircraft ranges (normal and extended) of the newer planes. Just sent Damian an updated cluster file that I did for RHAEEO, more for an Allied player familar with non-RHS games. It may be helpful. Under the LCUs, can we get their Assault Value added to the list?? It will help when planning attacks/defenses. More "wish list" items to follow. [:D] I agree about the ranges, but I'm not sure it will be correct for all mods, so I prefer to omit rather than get it wrong. I suppose I could compute it differently based on the mod... As for AV, I can't seem to find it in the save file. If someone knows how to calculate it, I'll add that in. Thanks for the RHS mapping file - Damian is checking it now.

Nomad -> RE: WitPTracker 1.0.2 (4/24/2008 4:41:51 AM)
ignore - wrong

Mistmatz -> RE: WitPTracker 1.0.2 (4/24/2008 11:22:20 AM)
quote: ORIGINAL: Nomad aircraft Ranges: max range in hexes = duration * cruise speed / 3600 ( round down ) normal range in hexes = max range / 4 ( round down ) extended range in hexes = max range / 3 ( round down ) The mod is immaterial. IIRC in RHS range is increased by use of fuel tanks (in weapon/device slots). WitPTracker shows therefore wrong range information for example for the P-39D and some others. But those who play RHS will know that so adding this into the formula is probably not a high priority.

floydg -> RE: WitPTracker 1.0.2 (4/24/2008 2:06:48 PM)
quote: ORIGINAL: Mistmatz quote: ORIGINAL: Nomad aircraft Ranges: max range in hexes = duration * cruise speed / 3600 ( round down ) normal range in hexes = max range / 4 ( round down ) extended range in hexes = max range / 3 ( round down ) The mod is immaterial. IIRC in RHS range is increased by use of fuel tanks (in weapon/device slots). WitPTracker shows therefore wrong range information for example for the P-39D and some others. But those who play RHS will know that so adding this into the formula is probably not a high priority. If the drop tanks are specific equipment on the aircraft model, I can get that. But I'd need to know how much it extends the range (I suppose it adds endurance).

mikemike -> RE: WitPTracker 1.0.2 (4/24/2008 8:23:31 PM)
quote: ORIGINAL: n01487477 OK I've reworked it, taking account for: 1. accelerated ships with delay > durability * 10 && durability < 35 (as you can see in the red -- you said <30 but actually it's 35) 2. These ships just use durability points NOT durability * 3 3. Navy & Merchant Points Used are now correct. 4. I also found that ML are also Naval ... I have tested looking at points used and Global Points turn for turn, so I hope this will almost close the issue (the only thing I haven't done is change "Start Building") ... So this reworked version will be included next build...thanks for teaching me, I certainly don't know everything ... Hmm - you can only Accelerate a ship if the delay is <= 30 times durability, can't see how you came up with 35 times. Also, ships that have a delay of exactly ten times durability are Building and should be counted as such. I think it would be best if ships with (30 times durability) >= delay > (10 times durability) should stay as Queued even if they are Accelerated. Invested a few hours testing where the building points of the several types are counted. Result: you are right, type ML is built by Naval yards, but so is Type PC! No doubt about that. WitPDecoder got that wrong, too. Sorry about the stream of nits, but this should conclude the issue. Oh, just another one: do you think it might be possible to mark the ships in the building queue (name in red, perhaps) that haven't advanced since the last turn?

n01487477 -> RE: WitPTracker 1.0.2 (4/25/2008 5:46:19 AM)
Mike, I concede that PC's are infact Naval & durability exactly 10 times can build (which in my new build I had)... quote: [edit]I think we have our lines crossed, you are talking about what can be accelerated in game, I'm talking about ships that are not building (in the normal <=dur10), but can be accelerated and are counted in the Build points ... I now see what you're trying to say and will do further testing. So it is possible to accelerate ships with durability 33 (such as many of the SS class) & CVE shinyo (35) & just tested SS HA class with 36 and CV Unryu (70)... and these do infact build, which are not in the <= durability 10. So now we're at durability <= 70 I will also look at others ... so the struggle to get this correct, continues ... I have tested this again & again and it is correct. So if your testing is different, I'm at a loss. quote: ORIGINAL: mikemike Oh, just another one: do you think it might be possible to mark the ships in the building queue (name in red, perhaps) that haven't advanced since the last turn? Will see if we keep that information in the DB, if so, yes... Thanks for your help again, I will get it done accurately, sorry for the delay! ------Damian --------

Mistmatz -> RE: WitPTracker 1.0.2 (4/25/2008 11:47:07 AM)
quote: ORIGINAL: floydg quote: ORIGINAL: Mistmatz quote: ORIGINAL: Nomad aircraft Ranges: max range in hexes = duration * cruise speed / 3600 ( round down ) normal range in hexes = max range / 4 ( round down ) extended range in hexes = max range / 3 ( round down ) The mod is immaterial. IIRC in RHS range is increased by use of fuel tanks (in weapon/device slots). WitPTracker shows therefore wrong range information for example for the P-39D and some others. But those who play RHS will know that so adding this into the formula is probably not a high priority. If the drop tanks are specific equipment on the aircraft model, I can get that. But I'd need to know how much it extends the range (I suppose it adds endurance). As I'm just a player of RHS and not involved in the mod making its probably best if you PM el cid. He'll surely know and be able to explain the mechanism behind.

LargeSlowTarget -> RE: WitPTracker 1.0.2 (4/25/2008 12:57:14 PM)
Sorry to bother you, but this tools does not work in my case. I get the following error messages: [image]local://upfiles/1313/5AF2B41F85564BBFB9201598492718E2.jpg[/image]

n01487477 -> RE: WitPTracker 1.0.2 (4/25/2008 2:27:26 PM)
I think I see the error straight away, it comes from the scenario name using Brackets () around Andrew's Standard Map ... 1.06 is fairly old isn't it ? The new CHS scenarios, don't have this ... I'll put it on our list to do ... Sorry for now ... ----Damian----

Mistmatz -> RE: WitPTracker 1.0.2 (4/25/2008 3:05:33 PM)
I'm thinking about reading in all previous turns (~70) I've played in my current game so far. Obviously this is a cumbersome process and I'd like to avoid doing it too often. So, are there currently any foreseeable compatibility issues of the 1.0.2 database with eventual newer versions?

LargeSlowTarget -> RE: WitPTracker 1.0.2 (4/25/2008 3:25:24 PM)
quote: ORIGINAL: n01487477 I think I see the error straight away, it comes from the scenario name using Brackets () around Andrew's Standard Map ... 1.06 is fairly old isn't it ? The new CHS scenarios, don't have this ... I'll put it on our list to do ... Sorry for now ... ----Damian---- Yes, I have started that PBEM over two years ago, and manage only about 4 turns a week. The game had progressed too far when a new version of CHS came out and the situation was too interesting to start over. I have sunk seven CVs while losing none (I'm Japan) plus a CVL, at least five old and two modern BBs and about 30 subs (KB hit Manila instead Pearl), while the land war is heavily in favor of my opponent (Bangkok threatended, Hanoi lost, Kuriles lost, Russia activated...) - so we have decided to continue. But now in April 43 I could really need some WitP-Tracker help in order to optimize production - fighter pools are nearly empty [X(]. Would be nice if you could make the Tracker compatible with older games. [sm=innocent0001.gif]

floydg -> RE: WitPTracker 1.0.2 (4/25/2008 4:25:56 PM)
quote: ORIGINAL: Mistmatz I'm thinking about reading in all previous turns (~70) I've played in my current game so far. Obviously this is a cumbersome process and I'd like to avoid doing it too often. So, are there currently any foreseeable compatibility issues of the 1.0.2 database with eventual newer versions? Good question and something Damian and I have recently been discussing. Yes, the new version we're working on (1.1, tentatively) will introduce some database changes. That will mean you'd need to reload from the beginning. Or I can add a DB upgrade function, but that would take a bit more time. Floyd

floydg -> RE: WitPTracker 1.0.2 (4/25/2008 4:28:22 PM)
quote: ORIGINAL: n01487477 I think I see the error straight away, it comes from the scenario name using Brackets () around Andrew's Standard Map ... 1.06 is fairly old isn't it ? The new CHS scenarios, don't have this ... I'll put it on our list to do ... Sorry for now ... ----Damian---- That's not it, it's the quote (') in Andrew's. I fixed it for the comment in 1.0.1, but not the scenario name... [:(] Floyd

mikemike -> RE: WitPTracker 1.0.2 (4/25/2008 7:22:16 PM)
quote: ORIGINAL: n01487477 So it is possible to accelerate ships with durability 33 (such as many of the SS class) & CVE shinyo (35) & just tested SS HA class with 36 and CV Unryu (70)... and these do infact build, which are not in the <= durability * 10. So now we're at durability <= 70 I understand now where our lines have crossed. I think I'll give you an example to clarify the issue: Take an AK with a durability of 20. This ship will start consuming shipyard points as soon as its delay falls below 201 (ten times durability), it is then building. It will consume 20 merchant yard points each day, or 60 (three times durability) if it is accelerated. So far so easy. The ship will consume no points if it is still queued (delay in this example > 200). But if the delay is between 201 and 600 ( ten to thirty times durability) you can Accelerate it, the delay will reduce by two each day, and the ship will consume 20 building points (= durability) per day. You can accelerate any ship, regardless of size, if its delay is equal to or smaller than its durability multiplied by thirty.

floydg -> RE: WitPTracker 1.0.2 (4/26/2008 12:02:27 AM)
quote: ORIGINAL: Nomad aircraft Ranges: max range in hexes = duration * cruise speed / 3600 ( round down ) normal range in hexes = max range / 4 ( round down ) extended range in hexes = max range / 3 ( round down ) The mod is immaterial. See http://www.matrixgames.com/forums/tm.asp?m=1672762 Floyd

Knavey -> RE: WitPTracker now at 1.0.2 (4/28/2008 5:01:02 AM)
Getting this set of errors when I try to run this: [image]local://upfiles/7595/30CB953FF50C434F8C0A520C81553EA6.jpg[/image]

Feinder -> RE: WitPTracker now at 1.0.2 (4/28/2008 6:04:15 AM)
This is where I've got mine... [image]local://upfiles/7554/A492FBD1B2FE4820879A8905FC5CC890.jpg[/image]

Feinder -> RE: WitPTracker now at 1.0.2 (4/28/2008 6:04:45 AM)
And file list... [image]local://upfiles/7554/09E7BF013ABD4D9E81B25973678DEF48.jpg[/image]

Knavey -> RE: WitPTracker now at 1.0.2 (4/28/2008 6:18:18 AM)
Might be because my Java may not be up to date. Having problems uploading the latest Java crap. It keeps cutting me off. Will have to wait until tomorrow.

Feinder -> RE: WitPTracker now at 1.0.2 (4/28/2008 6:39:13 AM)
This will test your current version of Java, and it'll tell you if it's current. Test your Java version

n01487477 -> RE: WitPTracker now at 1.0.2 (4/28/2008 6:46:43 AM)
Hi, yes please test your java version, we built this using the latest Java release V6, so if you are running a JVM less than that, you may encounter difficulties. The latest JVM is 6.5. http://java.com/en/download/index.jsp If you are up to date, and still having difficulties, please let us know... ---Damian---

Reg -> RE: WitPTracker now at 1.0.2 (4/28/2008 12:10:56 PM)
quote: ORIGINAL: n01487477 Hi, yes please test your java version, we built this using the latest Java release V6, so if you are running a JVM less than that, you may encounter difficulties. The latest JVM is 6.5. Which is a real nuisance if you are running Win98!!! [8\|] Oh well.... another item on the justification list for an upgrade....[:D])

treespider -> RE: WitPTracker 1.0.2 (4/28/2008 2:55:25 PM)
quote: ORIGINAL: Mistmatz quote: ORIGINAL: floydg quote: ORIGINAL: Mistmatz quote: ORIGINAL: Nomad aircraft Ranges: max range in hexes = duration * cruise speed / 3600 ( round down ) normal range in hexes = max range / 4 ( round down ) extended range in hexes = max range / 3 ( round down ) The mod is immaterial. IIRC in RHS range is increased by use of fuel tanks (in weapon/device slots). WitPTracker shows therefore wrong range information for example for the P-39D and some others. But those who play RHS will know that so adding this into the formula is probably not a high priority. If the drop tanks are specific equipment on the aircraft model, I can get that. But I'd need to know how much it extends the range (I suppose it adds endurance). As I'm just a player of RHS and not involved in the mod making its probably best if you PM el cid. He'll surely know and be able to explain the mechanism behind. IIRC DropTanks add their load cost to the Endurance value of the aircraft.

Knavey -> RE: WitPTracker 1.0.2 (4/29/2008 10:55:08 PM)
My issue was a Java problem...had the desktop up to date but not the laptop. Working now.

n01487477 -> RE: WitPTracker 1.0.2 (4/30/2008 6:32:14 PM)
See below for the update ...

n01487477 -> RE: WitPTracker 1.0.2 (5/10/2008 7:05:10 AM)
Hi all, just finalising the LCU production screen, the next build will hopefully include this and an update to the ShipProduction screen (which had some errors), plus things Floyd has been toiling with ... We'll have this out to you as soon as we've tested a bit more and ironed out some more kinks...and made some DB changes. ------Damian ----------- [image]local://upfiles/19798/32F4455136794390A7A30E50C1C17B79.jpg[/image]

Mistmatz -> RE: WitPTracker 1.0.2 (5/10/2008 12:56:27 PM)
Nice new sheet. [:)] Maybe you can add a column for the TOE of the selected unit in the lower part of the screen so we can easily see if there is a lack of devices or if a unit can be ordered to the front directly. Thinking about it, if there would be a TOE column why not adding a column with the difference between TOE and Amount for the lazy people. [;)]

Local Yokel -> RE: WitPTracker 1.0.2 (5/10/2008 3:51:23 PM)
I've added WitPTracker to my range of indispensable utilities - thank you both for all the work you've put into this.[&o] Particularly useful is the detail of what the effect of a ship's 'upgrade' will be. I was going to allow the upgrade of my high capacity auxiliary minelayers. Then I saw the effect in WitPTracker: mine rails removed and ships converted to AP's [X(] - No thank you, I think I'll keep the minelaying capability!

n01487477 -> RE: WitPTracker 1.0.2 (5/11/2008 9:09:09 AM)
quote: ORIGINAL: Mistmatz Nice new sheet. [:)] Maybe you can add a column for the TOE of the selected unit in the lower part of the screen so we can easily see if there is a lack of devices or if a unit can be ordered to the front directly. Thinking about it, if there would be a TOE column why not adding a column with the difference between TOE and Amount for the lazy people. [;)] Yes, my intention is to implement something like what you say, but this is the first iteration, so it is a little "dumb" at present, but in the future I intend to include this, plus tracking of devices, maybe distance to HQ, supply etc ...

Thesix -> RE: WitPTracker 1.0.2 (5/11/2008 2:30:48 PM)
quote: ORIGINAL: floydg quote: ORIGINAL: n01487477 I think I see the error straight away, it comes from the scenario name using Brackets () around Andrew's Standard Map ... 1.06 is fairly old isn't it ? The new CHS scenarios, don't have this ... I'll put it on our list to do ... Sorry for now ... ----Damian---- That's not it, it's the quote (') in Andrew's. I fixed it for the comment in 1.0.1, but not the scenario name... [:(] Floyd Nothing we can change by ourselves? Looks to be a great work! [:)]

Page: << < prev 2 3 [4] 5 6 next > >>

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

2.078125