I think that:

1. You are a an excellent tester. Seriously, hats off :yep:
   
   
2. Your conclusion that only the first SensorData controller is used for audio is in accordance with my initial guess, and looks to me fully congruent with the results of your tests.
   
   
3. We cannot "teach" the game to "see" the second and third layer, but as you are suggesting, we can try extending the range of the first layer from the minimum to the maximum depth.
   Let's say that we have 3 depth ranges, from A to B, from B to C and from C to D, where A is the shallowest depth, and D is the deepest depth. I would try the following settings:
   
   
   Quote:

   1st SensorData: maximumrange=short mindepth=A maxdepth=D 2nd SensorData: maximumrange=medium mindepth=B maxdepth=D 3rd SensorData: maximumrange=long mindepth=C maxdepth=D

4. Notice that using the above settings the human player would be able to hear ships only from the shallowest layer: at bigger depths, our operator would be better than us in detecting far contacts. If we wanted the opposite to be true, we should try inverting the previous settings, as folows:
   
   
   Quote:

   1st SensorData: maximumrange=long mindepth=A maxdepth=D 2nd SensorData: maximumrange=medium mindepth=A maxdepth=C 3rd SensorData: maximumrange=short mindepth=A maxdepth=B

   My only doubt is that with these settings, probably the second and third ranges wouldn't be applied at all, and our operator wouldn't be affected by depth changes.
   
   If you send me your files, I can tweak them in s3d and send them back to you, for you to check :up:
   
   
5. Seems that the K.D.B has a constant offset of -7 m. this probably due to the fact that the SensorData controller min and max depth settings are relative to sensor's position, whereas the depths we are measuring in game are relative to boat's keel. The G.H.G, and probably the Balkon Gerat, are fitted near the keel, whereas the K.D.B. sensors are mounted on the deck, about 7 m higher.
   
   
6. You are a good pal, and a very friendly subsim member :O: :rotfl2:

:oops:

I think you are absolutely right here, if we make these settings, the sense of mod disappears altogether..

I have already edited my file but I'm afraid that there may be errors..
Here is my original file - http://rghost.ru/43766178
Make the changes and send it to me, please and I will check both of :up:

EDIT: and Balcon Gerat too, please :yep:

I have checked this file. The AI sonarman is no longer updating the contacts when sub is surface.
However, below 30m still no sound for human.

just kidding Volodya :)

yes, I am afraid we got to live with reduced audible hydro range :-?

Okay, working on it :up:

We are trying to fix it, whiskey. Stay tuned ;)

It's my original file.. it wasn't edited yet..
here are settings of it - http://www.subsim.com/radioroom/show...8&postcount=80

I have openend your file both in Goblin and in S3d, and I have noticed that in your post you had inverted layers order. This is because Goblin shows controllers in reverse index order. In other words, the controller used for audio contacts is the last one.

That makes little difference for our purposes, indeed. I am saying it just in case someone wants to replicate our experiment with other settings. Thinking especially of our SH3/4 mod community friends who are using S3d as their main editing tool :)

About your settings, Volodya, I have a couple of remarks:

1. the GHG is set to have 3 layers: 1 for shallow depths (7-27 m), one for high depths (27-500), and one covering the whole depht range (7-500). It doesn't make much sense :hmm2: can you please specify the number of different sensitiveness layers you want, with their depth ranges (relative to sensor position) and max detecting ranges?

2. I see that, similarly to R.E.M, your file features max detecting ranges exceding 20 km which, IIRC, is the "world limit" beyond which units exist just as a set of coordinates. Is is supposed to be like this? :hmmm:

these are not my layers.. I only a bit changed values..
it all makes sense.. the layers are working correctly.. in layer (7-27) Benno heard in range about 21-22 Km.. in layer (27-500) Benno heard in range about 37-38 km for convoys and in range 35-36 km for single ships.. with KDB less at 1-2 km

In fact the "world limit" is about 40 km mostly.. one time Benno has detected a convoy in range 55 km.. it was wolfpack.. and I had seen them using external camera.. when the first unit of the convoy is entering into the sensors area (40 km) then Benno can hear whole convoy.. that's why he could heard in range 55 km..

So you are proposing a two ranges sensitiveness pattern (7-27 and 27-500)? In this case I will remove the third SensorData controller for both the GHG and the Balkon Gerat. :hmmm:

Okay, 40 km makes much more sense :up:

If you remove third SensorData for GHG and Balcon Gerat then it will be human audible only at one range - 7-27 or 27-500..

I suggest you to add one more SensorData for KDB and two SensorDatas for Balcon Gerat type9.. because I don't know exactly which one (Balcon Gerat or Balcon Gerat type9) is using in game.. all other settings I will make by myself..

I think it's not needed.. I hope when Xrundel and TheBeast did this mod they knew what they were doing..
add only one SensorData for the KDB, please.. and send me the file..

EDIT: I've tried to did it by myself but something wrong with me.. :/\\!! Goblin don't see new SensorData after my edit.. :nope:

Okay, I think we don't understand each other. I will give each sensor 3 layers with mixed settings, and then you will adjust them to your taste. :up:

P.S: Balcon Gerat type9 was planned for type IX U-boats. I will leave it alone atm :03:

OK..
Something wrong with my brain today.. still can't add one more data for KDB :/\\!!:/\\!!

I did it! Finally I did it! :Kaleun_Wink:

now I'm testing it.. a bit later will upload it for Whiskey to testing it..

Now I see :yep: silly me :oops:

I can't figure out why they added third controller for GHG and Balcon Gerat.. maybe were some reasons? :hmmm:

EDIT: now I will remove unnecessary controllers and will see how it works without them..

http://img836.imageshack.us/img836/1228/pushme.png

... just in case. :03:

I have given the 3 hydrophones exactly the same settings:

1st SendorData:
PreciseRange=25,000
Max Range=40,000
MinSesorHeight=-500
MaxSesorHeight=-80

2nd SendorData:
PreciseRange=17,000
Max Range=25,000
MinSesorHeight=-500
MaxSesorHeight=-27

3rd SendorData:
PreciseRange=0
Max Range=17,000
MinSesorHeight=-500
MaxSesorHeight=-7

fingers crossed :up:

they did it because they gave some surface detection range to GHG and Balcon Gerat. Nonetheless you removed it, making the third controller unnecessary. I have utilized it for creating a deeper sensitiveness layer (-80 to -500).

We will talk about realistic settings later. Now let's see if our fix works as supposed or not :)

:hmmm: I think the PreciseRanges should be =0.. otherwise you will not hear the target when it will come closer then this value..

EDIT: and other targets that are already closer too..

Ah.. I see..

No, PreciseRange should be the range at which the sensor will still receive full signal. From PreciseRange to MaxRange, the signal will start decreasing linearly.

I have put there some numbers just for testing. You can set them back to 0, if you want. For ease of editing I have also moved all the hydrophone sensordata controllers to the end of the file. Have you downloaded my test fix, by the way, or still testing your tweaks?

:har: :rotfl2:
Today is not my day..
I thought this "push me" button is just for decoration..

Yes, at some moment I had this doubt. This is why I decide to ask :haha: