|
Bullwinkle58 -> RE: Search arc statistical test (9/18/2010 9:05:10 PM)
|
Since we're spit-balling here, waiting for some word from the devs (or not), I wonder if the results relate to what happens in the code after the first detection is accomplished under each type of search? Does a search arc mission stay on that "slice" for more time than it would if it hadn't detected anything, raising DL maybe, and thus doesn't accomplish all of the ordered arcs and misses the randomized chance to get the last one or two targets in the test array?? While a non-arc search just pings the detection and keeps on looking until it's out of time/ops points/whatever?
Do we know exactly what the courses and ranges the planes are actually covering in the code in both a detection and non-detection slice? Or are we assuming that, weather and ops loss permitting, the arced mission flies all of the ordered arcs? If this has been covered in the thread I apologize. But it seems as if, in the other times complex game mechanics have been questioned by players using set-up testing like this (naval gunfire penetration, pre-CAP flak, IJN ASW, high-altitude sweeps, etc.), even when there was a bug or two the actual under-the-hood calculations have always been far more complex than many players assumed from the test regime.
Which maybe raises a question for the historical-truth players in here--what "should" the code do with a naval search mission when a TF is detected? Stick on it or keep searching? A search mission that finds the KB should just push over to the next slice to look for sampans? In RL that plane would stick as long as it could, refine the base course and speed reports, and try to firm up ship IDs. Do we as players want an arc search to complete the ordered arc range come hell or high water, or not? I don't know which it does now, but I know which I'd like it to do.
|
|
|
|
