Page 1 of 1

Possible "Threat Tolerance bug"

Posted: Tue Sep 01, 2009 3:35 pm
by Smeulders
Noticed something that might be wrong with the threat tolerance. I was evacuating a HDML group through the straights of Malacca and up the Malaya peninsula, when I got the 'retreating from surface threat' message in the TF information screen. Only problem is that I can't see any Japanese ships nearby, unless you count those on the other side of the peninsula in the gulf of Siam.

RE: Possible "Threat Tolerance bug"

Posted: Tue Sep 01, 2009 3:46 pm
by jhdeerslayer
ORIGINAL: Smeulders

Noticed something that might be wrong with the threat tolerance. I was evacuating a HDML group through the straights of Malacca and up the Malaya peninsula, when I got the 'retreating from surface threat' message in the TF information screen. Only problem is that I can't see any Japanese ships nearby, unless you count those on the other side of the peninsula in the gulf of Siam.

I assumed it checks air threats too? But yours says surface. Hum..

RE: Possible "Threat Tolerance bug"

Posted: Tue Sep 01, 2009 4:20 pm
by Don Bowen
ORIGINAL: Smeulders

Noticed something that might be wrong with the threat tolerance. I was evacuating a HDML group through the straights of Malacca and up the Malaya peninsula, when I got the 'retreating from surface threat' message in the TF information screen. Only problem is that I can't see any Japanese ships nearby, unless you count those on the other side of the peninsula in the gulf of Siam.

The surface threat logic uses a combination of "hex-math" and actual sea path range checks. The former is very fast but, as you say, does not account for hexes through which a TF can not pass. The latter is very accurate but, with the enlarged map and multitude of terrain types/movement options, takes longer than a politicians speach. In the interest of turn resolution efficiency, the logic uses hex-math range to disqualify TFs that are obviously too far away and then sea path range for the remainder.

But blugs have been kwonw to glappen. Post a save and I'll check it out. One just before the retreat message, please.




RE: Possible "Threat Tolerance bug"

Posted: Wed Sep 02, 2009 6:35 am
by Smeulders
How do I upload save files ? When trying to do so I get the message "wpae010.pws is not supported"

RE: Possible "Threat Tolerance bug"

Posted: Wed Sep 02, 2009 7:00 am
by TheTomDude
ORIGINAL: Smeulders

How do I upload save files ? When trying to do so I get the message "wpae010.pws is not supported"


You'll have to ZIP it.

RE: Possible "Threat Tolerance bug"

Posted: Wed Sep 02, 2009 1:15 pm
by witpqs
Don, I saw a case a while back in my game where an escort TF a couple days out of Pearl heading to Seattle starting to pick up wacky-looking routing. It turned out it was routing around an enemy carrier TF threat. Trouble is I had zero spotting of the TF except for that. While it's possible there was a 'radio transmissions from xxx,yyy' or some such message that I missed, as far as I know it was free intel!

RE: Possible "Threat Tolerance bug"

Posted: Wed Sep 02, 2009 1:45 pm
by Don Bowen
ORIGINAL: witpqs

Don, I saw a case a while back in my game where an escort TF a couple days out of Pearl heading to Seattle starting to pick up wacky-looking routing. It turned out it was routing around an enemy carrier TF threat. Trouble is I had zero spotting of the TF except for that. While it's possible there was a 'radio transmissions from xxx,yyy' or some such message that I missed, as far as I know it was free intel!

I just can not do anything without a save.

RE: Possible "Threat Tolerance bug"

Posted: Wed Sep 02, 2009 6:19 pm
by Smeulders
This should be the correct save file, hope it helps you.

RE: Possible "Threat Tolerance bug"

Posted: Thu Sep 03, 2009 2:29 am
by Don Bowen
ORIGINAL: Smeulders

This should be the correct save file, hope it helps you.

Yup, bug there - just as you thought.