Echo II sonar issue?

Post bug reports and ask for game support here.

Moderator: MOD_Command

Post Reply
DMAN
Posts: 98
Joined: Fri Jan 11, 2019 3:56 am

Echo II sonar issue?

Post by DMAN »

Hi all,

The message states the contact is estimated at 13nm when you can see that it's around 1nm.

This was the same for the first contact in the messages (time compression was on and it was sunk).

And then was repeated for 2 more.

Any thoughts?
Attachments
Dockingtest.zip
(24.84 KiB) Not downloaded yet
DMAN
Posts: 98
Joined: Fri Jan 11, 2019 3:56 am

RE: Echo II sonar issue?

Post by DMAN »

The following 2 contact reports can be seen in this snip. The timestamp (not seen) is 13:03:35. Detection at 13:01:53 and 13:03:53.
Damaged ships travelling at 4kn.

God's eye view was on, and as you can see, it's around 3nm, not 13nm.

I understand the sensor has a detection range of around 4nm, so 3nm makes sense, but 4 identical messages seems odd to me.

Regarding the first post, not detecting until 1nm, and I think the very first contact was detected under 1nm, also seems odd.

Image
Attachments
Untitled.jpg
Untitled.jpg (135.57 KiB) Not viewed yet
DMAN
Posts: 98
Joined: Fri Jan 11, 2019 3:56 am

RE: Echo II sonar issue?

Post by DMAN »

I've run a few more tests with Russian/Soviet submarines, and every contact is a generic 13nm, regardless of the actual range, sensor, platform, etc.

As you can see from the attached, an Akula with TASS (range 70nm) is not detecting the Algol banging along at 32kn and cavitating at a range of about 35nm.

What do you think?
Attachments
Dockingtest.zip
(32.13 KiB) Not downloaded yet
Dimitris
Posts: 13396
Joined: Sun Jul 31, 2005 10:29 am
Contact:

RE: Echo II sonar issue?

Post by Dimitris »

ORIGINAL: DMAN
I've run a few more tests with Russian/Soviet submarines, and every contact is a generic 13nm, regardless of the actual range, sensor, platform, etc.

As you can see from the attached, an Akula with TASS (range 70nm) is not detecting the Algol banging along at 32kn and cavitating at a range of about 35nm.

What do you think?

General comment before looking at the save: 13nm as max range sounds about right for direct-path contact (9.5nm is the nominal limit, and then you get bonuses for surface ducting etc.).

What you see is probably the Algol being in the "shadow zone" between the direct-path limit and the first CZ.

If you place the Algol smack into the 1st-CZ ring, does it get detected?
DMAN
Posts: 98
Joined: Fri Jan 11, 2019 3:56 am

RE: Echo II sonar issue?

Post by DMAN »

ORIGINAL: Dimitris
ORIGINAL: DMAN
I've run a few more tests with Russian/Soviet submarines, and every contact is a generic 13nm, regardless of the actual range, sensor, platform, etc.

As you can see from the attached, an Akula with TASS (range 70nm) is not detecting the Algol banging along at 32kn and cavitating at a range of about 35nm.

What do you think?

General comment before looking at the save: 13nm as max range sounds about right for direct-path contact (9.5nm is the nominal limit, and then you get bonuses for surface ducting etc.).

What you see is probably the Algol being in the "shadow zone" between the direct-path limit and the first CZ.

If you place the Algol smack into the 1st-CZ ring, does it get detected?

Hi Dmitris,

Yes, within the first CZ ring it is detected. I had it cross the CZ at an angle and was detected at about 20nm although the message said 48nm.
Thanks for that one! And to be transparent, I forgot about CZs, sound propagation, surface ducting, etc. Doh!

How about the first and second posts here regarding the Echo II detection range? They seem awfully short.

I've also noticed that contacts are also being ID'd but there is no message indicating that. Is there a setting I'm missing?
E.g. New Contact Skunk-20....
Skunk-20 identified as SL-7 Algol (or similar message type).
Post Reply

Return to “Tech Support”