Matrix Games Forums

I cannot seem to actually find ships when I set search arcs. Has anyone actually tested to see if they work?

I am running version 1 dot 7 dot 11 dot 24 and whenever I set search arcs for planes, I detect nothing in the search area. If I instead set the same air groups to random arcs, I tend to find ships. In particular, I have set arcs to cover the area around Singapore using multiple Naval Search air groups searching for Force Z on 12/7/41. I can clearly see at least 4 arcs that cover the hexes occupied by Force Z, but do not detect it. If I turn even one group to random, it gets detected. I've tried different arc settings to make arcs turn green, blue, and black in dozens of tests, but as long as I enter search arcs, I find nothing.

I've run the game through December playing the Japanese side several times - and cannot locate American CV's that launched air strikes from 4 hexes away the previous turn. (CV's raiding Marshall Islands post 12/7) I'm searching with at least 3 groups of Float planes and Flying boats including the Yokohoma KuT-1&-2 air groups flying K6K4 Mavis

No, they do work. Simply bad luck.

ORIGINAL: Harald Velemans

No, they do work. Simply bad luck.

Or possibly bad settings - e.g. searching too far out dilutes the search too much. The developers have hinted that beyond 12 hexes the width of the 10º arc is too great for the plane to see across in good weather. If the weather is less than clear, the gaps between visibility start much sooner.

Then there is the issue of NavSearch training levels for the pilots - not all good at game start.

Basically you need saturation coverage and reasonable weather to be sure of spotting something.

Also consider that high-altitude searches have a better chance at finding big TFs, low-alt at finding smaller ones.

+ pilot experience and skills (Naval Search in particular). In the early game these are often lacking. Overlapping searches from different groups at different bases helps, too.

Do be advised that even the best search configurations with the best pilots, best aircraft, radar, etc. are still subject to weather and to random performance modifiers. Search (and everything else in this game) is designed to be not perfect.

As witpqs has said above even under the best conditions/circumstances things can go awry. For the most part I've not had much trouble when 'all the bases are covered' and I use arcs all the time.

Is 4 hexes and under search range 100% effective, so there's no need for arcs or is it an urban legend? I think I've read about it somewhere.

ORIGINAL: szmike

Is 4 hexes and under search range 100% effective, so there's no need for arcs or is it an urban legend? I think I've read about it somewhere.

IIRC, what the developers have said is that regardless of the search are set, all hexes within 4 hexes are searched. I don't recall them saying that it is 100% effective.

The Manual has some good tips and important search points on page 151

Naval Search – The aircraft will search for enemy Task Forces (subs or
surface) in all directions out to their extended range. They will carry an
extended range bomb load in case they spot a sub or surface ship, in which
case they will attempt to attack unless driven off by CAP or Flak. Individual
planes searching for enemy Task Forces conduct naval search. The search
continues until a TF is detected or the plane exceeds its range. Once a
TF is detected, the plane may terminate its flight depending on range to
target; the nearer the TF is to the plane’s base, more likely that the plane
may continue to fly searches. Searches within 5 hexes of the base are
more likely to detect TFs as there will be a number of planes transiting to
and from the search areas. Setting the max range to a lower range than
the full extended range will improve the chance to detect, as this can
translate to more flights by the same plane. Because the search can be
terminated due to detecting a TF, it possible better targets may be missed.

Search missions can be given an arc of 10-degree sectors to be searched. Planes in a group
are assigned to a search one at a time from the start sector to the end sector. If there are more
planes than sectors, then the process is repeated. For example, 10 planes on search over arc
of 3 sectors end up as 4 to first, 3 to second and 3 to third. The benefit of this is that only TF’s
within this arc are looked at, thus concentrating assets on a particular threat. The chance of
sighting the enemy is increased with the number of planes searching. When a unit has a Nav
Search Level set greater than zero, then the set percentage of the unit will automatically fly this
Mission, with the remainder of the planes either flying the Mission set for the unit or resting (if
the Mission is Naval Search).

You are all missing the point.

Same airgroups searching, smae percentages, same pilots, same altitiudes, same planes, etc.

THE ONLY DIFFERENCE:

Search arcs set to specific arcs (verified using 'Z' hot key and show arcs button on air group screen) - VERY LOW DETECTION FREQUENCY

Search arcs set to random arcs - VERY HIGH DETECTION FREQUENCY.

The ONLY variable here is the use of specific search arcs.

I see what you're saying, and I've observed that phenomenon at times, however my search arcs do just fine. I've been running them for months in particular areas in each of my games and I always detect stuff. In fact, in one game I don't think I have ANY groups on random and all are manually set. If they didn't work, I'd never see anything, would I? And yet I do...

ORIGINAL: Lokasenna

I see what you're saying, and I've observed that phenomenon at times, however my search arcs do just fine. I've been running them for months in particular areas in each of my games and I always detect stuff. In fact, in one game I don't think I have ANY groups on random and all are manually set. If they didn't work, I'd never see anything, would I? And yet I do...

I understand. I've done more controlled tests and detected stuff with specific search arcs. I went so far as to create a scenario that placed a couple search squadrons and support/supply on Marcus Island, then placed Allied TF's containing 1 ship in all 36 hexes around the island at range 6. I was able to detect some TF's. I also stood down every air group other than two searching from Marcus Island to make sure the detections were coming from the search arcs. All I am saying is that I completely miss detecting many more TF's using specific arcs than I do with random. And it happens all over - The Marshalls, Babeldaob, on Ships, from Takao, and Saigon. The only common thread is search arcs. I even when to verify the compass headings and clockwise/wounteclockwise settings, varied arcs slightly, Pressed Z and show arcs to verify the arcs, etc.

I know, I know, there is supposed to be degradation at long range. I got that. The degradation for search arcs should be LESS than random arcs though - and random arcs work with uncanny efficiency and specific arcs do not work for shit sometimes, even though the hexes that contain TF's should have more planes searching the hex - and the difference is not even close.

I literally set EVERY search plane I had to specific arcs representing the Threat axis for the base/ship they were on - and when I did, that is when the problem appeared. (and I do mean EVERY search group -Glens on subs, AV, CS, carrier groups, CL/CA/BB groups included). I think the groups that are placed on random arcs somewhat mask the issue. Players see the TF's get detected therefore they think the specific arcs work better than they do.

Within 4 hexes, you'll get good results. I think it's outside of 4 hexes where it starts to break down, and people have said that at 15+ it's really a crapshoot. I've detected things that far out, but it must just be luck at that point because the 10' arc is so wide.

ORIGINAL: Lokasenna

Within 4 hexes, you'll get good results. I think it's outside of 4 hexes where it starts to break down, and people have said that at 15+ it's really a crapshoot. I've detected things that far out, but it must just be luck at that point because the 10' arc is so wide.

Loka - you can get the º symbol by holding down the ALT key and typing 167. When you release the ALT key it will appear.

ORIGINAL: BBfanboy

ORIGINAL: Lokasenna

Within 4 hexes, you'll get good results. I think it's outside of 4 hexes where it starts to break down, and people have said that at 15+ it's really a crapshoot. I've detected things that far out, but it must just be luck at that point because the 10' arc is so wide.

Loka - you can get the º symbol by holding down the ALT key and typing 167. When you release the ALT key it will appear.

176 gives °. 167 gives º.

ORIGINAL: witpqs

ORIGINAL: BBfanboy

ORIGINAL: Lokasenna

Within 4 hexes, you'll get good results. I think it's outside of 4 hexes where it starts to break down, and people have said that at 15+ it's really a crapshoot. I've detected things that far out, but it must just be luck at that point because the 10' arc is so wide.

Loka - you can get the º symbol by holding down the ALT key and typing 167. When you release the ALT key it will appear.

176 gives °. 167 gives º.

Well we use Celsius scale up here so our degrees are bigger!

ORIGINAL: witpqs

176 gives °. 167 gives º.

176 gives ░ 167 gives ž

ooops

ORIGINAL: szmike

ORIGINAL: witpqs

176 gives °. 167 gives º.

176 gives ░ 167 gives ž

ooops

It depends on the font set that you are using. If you are not using the US English keyboard setting, you will have a different font which means a different character set.
Windows used to allow you to see the character set by going to the "Character Map" item in one of the properties menus. I have not been able to find it in recent versions of Windows but I know I could create one by starting a document and then going through the numbers 1 to 256 using the ALT key to print the character in the document. Somewhere in your character set you will have a º symbol - in with all the mathematics and scientific symbols most likely.

Thank you. I've already known that, I'm not using US keyboard settings obviously, I could switch to get the symbol without looking at character map, which is readily available in Win7. I won't change to win10 as long as I can.

ORIGINAL: BBfanboy

ORIGINAL: Lokasenna

Within 4 hexes, you'll get good results. I think it's outside of 4 hexes where it starts to break down, and people have said that at 15+ it's really a crapshoot. I've detected things that far out, but it must just be luck at that point because the 10' arc is so wide.

Loka - you can get the º symbol by holding down the ALT key and typing 167. When you release the ALT key it will appear.

It depends on what text editor/web browser you are using, therefore I just always use the apostrophe [:)].