Ah, so there is no limit on the altitude for AI radar then. Yeah, ducimus, that was my suggestion earlier. the AI vs AI combat is pretty crappy as it is, the best solution would be to just NULL the Type 13 radar out.

tater

BTW, regarding the visual "sensor" does that work within the parameters deterministically, or is there a random element? Ie: You COULD be detected at such and such a range, but you might not, vs get inside X range going Y speed in Z seas, and you are detected 100% of the time.

I ask because while AI with radar when they shouldn't might be a problem, so is pulling up next to a DD and having them ignore you 100% of the time.

OTOH, I am with you on the "the heck with reality in the specifics, it's the outcome that matters" side of things. So while one such solution is to eliminate the air search radar, another similar technique might be to change the minimum surface area detected at max range to a LARGE number, like a huge warship cross section. I say this because the later radar models are identical in the tweak file except each has the max range increase by 4000m. So if the 13 detects you decks awash in the fog now at 7km, so will the 22, even if in RL it would see a DD at 7000m, but not a sub until 2000m (surfaced).

So tweaking that for a realistic outcome using the cross sectional area might make sense---all attention to its functionality for anythign other than detectign subs would be ignored, just try to get THAT part in the ballpark. If that makes any sense.

Visual detection:
varies on:
- enviormental variables (light, sea wave height, fog)
- How much surface area of your sub is being presented
- how fast your going.


Radar:
Id stick to a simplistic solution because its really not that improtant. At the most, id take the nonclamture an a 1944 surface radar, make the type 13 match it, and then shorten the range.

Minitweaker creates a backup copy of the file you are editing "Copy of ...." , you must remove it from the directory for the changes to take effect.

Ref

Thanks for the help, ref.

Changing the max range value of type 13 radar to 1 (in the AI_Sensors file) solves the problem.

I have a solution for this that allows the radar to remain enabled and operational as intended, but I need to test a bit further first. I also have to create a special visual sensor to do the testing. If I get it working tonight, and can verify the results, I'll post the modified AI_Sensors.dat.