SUBSIM Radio Room Forums

SUBSIM Radio Room Forums (https://www.subsim.com/radioroom/index.php)
-   Dangerous Waters (https://www.subsim.com/radioroom/forumdisplay.php?f=181)
-   -   Cant mark sonar contacts BB (https://www.subsim.com/radioroom/showthread.php?t=89878)

GunnersMate 02-23-06 01:35 PM

Cant mark sonar contacts BB
 
I have a faint contact that doesnt's show clearly on STA but is a very clear distinct path on ITA but the MARK or ASSIGN TRACKER button doesnt work!! :stare: :damn:
Can anyone help me here please ?!? :(
I'm running 1.03 and LWAMI 3.00B
I'll post a screenshot .

GunnersMate 02-23-06 01:46 PM

http://img.villagephotos.com/p/2006-...mp01519367.JPG

The contacts are at 010 and 170 thereabouts.

Bellman 02-23-06 02:07 PM

:) You show Auto control sonar - not tried it for a couple of years but did'nt think you could mark manualy
at that time.

So you have to ask yourself have you tried to mark in BB manualy and if that was not successful did you try to
mark the actual tonals in NB ?

GunnersMate 02-23-06 03:40 PM

Quote:

Originally Posted by Bellman
:) You show Auto control sonar - not tried it for a couple of years but did'nt think you could mark manualy
at that time.

umm.. What is "auto control sonar"? Do you mean Autocrew? If you did I never use Autocrew on sonar.
Well :hmm: except on active intercept :ping:

Edit - I only use Autocrew on TMA and radar sometimes. :oops:

zma 02-23-06 04:26 PM

Re: Cant mark sonar contacts BB
 
Quote:

Originally Posted by GunnersMate
I have a faint contact that doesnt's show clearly on STA but is a very clear distinct path on ITA but the MARK or ASSIGN TRACKER button doesnt work!! :stare: :damn:
Can anyone help me here please ?!? :(
I'm running 1.03 and LWAMI 3.00B
I'll post a screenshot .

I was wondering about this same thing a while back... Basically, this behaviour is caused by a fixed treshold value in the sonar interface which prevents too faint contacts being marked. The LWAMI mod increases the sensitivity of the sphere sonar, but can't do anything about the threshold value, since it's hardcoded in the interface. And that means you can see a faint contact in BB, but can't assign a tracker to it. Or, at least, that's how I've understood it. :-?

Like Bellman suggested, try to assign a tracker in narrowband. It's a good workaround, and you can assign a BB tracker once the signal is stronger.

Bellman 02-23-06 11:04 PM

Ummm ! Did you mean ''never'', or almost never , use AC sonar ? ;)

OKO 02-23-06 11:10 PM

the sonar AC shown on the screen is switched off, and not on, Bellman :roll:

Bellman 02-23-06 11:31 PM

OKO - my monitor was still in 'high gamma' diving mode.,,,,,,,,,,, his AC flag looked pallid ! :yep:

Anyways he should have been in NB.

BigBadVuk 02-23-06 11:55 PM

I have also the same problem and my autoCrew for sonar is always off!!!
And i use 1.03 full + latest LWAMI....It is same for SA and TA....i have very faint contact and i just cant mark him!...After a lot of clickings i stoped and i went to second stations ...And then suddenly :Conn. Sonar I have new contact..... :doh:
The faint contact in the meanwhile becomed more loud and he was marked...I know that i didnt have auto crew enabled so what is going on? :damn:

Bellman 02-24-06 12:50 AM

BBV - yes there is often a delay after trying to assign a tracker on BB, before it is shown and called.
But I think you will find faint tonals on that bearing in NB, and if you select one you can mark and assign a tracker.
Make sure if this contact is via TA that you justify it by eliminating the ghost first. OK you have no demon
until a BB replacement is available as you close range. You need to constantly monitor the BB bearing of this NB
contact and keep trying to assign, so that you can work demon and TMA.

You mention a delay also on marking in SA but my impression is that these,and the TA ones, are relatively short
in duration - around a minute and just a delayed response. If it is longer then it would be a cool SCS interpretation
of the senior sonar operator issuing instructions to a crewman to search with a following delay before success.
This type of 'memory' would nicely avoid the ''constant monitoring'' I doubt its a feature that is present in-game.

sonar732 02-24-06 07:50 AM

There are usually four members of the sonar crew in the shack at all times unless they are short in their division.
  • 1. Sonar Supervisor (The reporter on DW and SC...Conn, Sonar...)
    2. Sphere Operator
    3. Towed Array Operator
    4. FRAZ Operator

Either one of the 3 "lower" men have to investigate the contact, then report it to the Sonar Supervisor who's at least an E-5, if he's sharp, who then concurs and reports to the Conn.

Dr.Sid 02-24-06 08:45 AM

There is delay before marked contact is reported in audio, but no delay in log window and on map (or TMA window). At least I have never seen it.

Bellman 02-24-06 08:50 AM

:D Thanks sonar732 - interesting. Almost a five - a- side !

Bellman 02-24-06 09:16 AM

Dr S - I often see an unsuccessful attempt to assign in BB at a bearing you are monitoring (no tracker assigned) in NB and
often when you return to NB the call comes through with a small delay when the tracker has become established in BB.
Never timed it, but it just seemed to confirm that as you close range that BB bearing request for an assigned tracker
sticks, without any BB tonal/s, then kicks -in.

Reminded me of my first car an old Armstrong Siddley with a pre-selector semi-auto box and fluid flywheel.
Choose the next desired gear, kick the pedal and wait - not long, but just long enough to make you wonder whether
it was really gonna happen. :hmm:


All times are GMT -5. The time now is 04:14 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.