Destroyers Discussion (getting rid of pin point drops)

[Redwine]

Originally Posted by caspofungin

@hemisent

(and others having issues w/ single destroyers)

consider implementing the min surface for sonars in ai_sensors -- a value of 60-80 seems to work best. allows you to evade active pinging by turning directly into or away from the escort, as was practiced irl. in combination w/ silent running, allows you to potentially get some distance and eventually break free.

Just an idea.... if you adjust a min value in anywhere, any measure under this value make the sub undetected.

I put the line "aspect = x,x" used into Sensors.cfg for own sub sensors, into the "Sim.cfg".

Not sure if it works, need more test specially on this point, but if you put a value

Aspect = 0,5

it means the aspect reduce at half the detection capability, but not totally to zero as if you use a minimun value setting.

I note i can scape from uber DDs leting them at back, it seems to be more easy than when they are at my side.

May be you want to try it.....

Originally Posted by thecaptain

Had high hopes for this one. I set sail and purposely steered for the area around Gibralter. I was looking for trouble and could be assured I'd find it there. Sure enough, it didn't take long for one destroyer to emerge out of the darkness and see me. I took to the depths and waited to see what would happen next. It wasn't long before he called in several of his friends. One after another, more destroyers answered the call. Unfortunately, that was as exciting as it ever got. I set the engines for flank just to draw their attention and not once did any of them go to active sonar - not a single ping. A couple just continued to make sweeps and depth charge runs behind me, but never came close. Don't get me wrong. I appreciate the hard work that went into this test mod, but it's going to need much more. I replaced the old files and I found that the destroyers were much more aggressive. Go flank and they've got ya.

The Captain

Hi Captain....... may be this can help you.

I think so..... only my impression...... the fact of you dont hear the pings, do not means the DDs are not pinging you.

I am not crazy, i think so, the gtame modelation of the ping sound is not linked to the Dds pinging activity.

You can verify it.

Just make a test file. Adjust visual and radar min height to a high value, to ensure you are not being detected by radar or visually.

Then reduce the active beam wide angle (min bearing) to in example 15 degrees, it is 15 degrees left, and 15 degees right.

Your beam now is 30 degrees wide.

Just go to periscope depth, to ensure you can follow the map icons.

Then put flank speed and let them to detect you, you will see they are going to your position, and turning right and left scanning for you.......

No ping sound.

Click on the map icon, then you are able to see, the dash line indicating the active sonar beam.

When you enter into about a 90 or 80 % of the active sonar beam, you will see the DDs just put bow on you, you are now centered in middle of the active sonar beam.

This means you was detected by active sonar, you are pinged.......

But no ping sound yet.......

The DDs is pinging you, you can see it at the icon on the map, the DDs stops to turn right, to left, to right to left to sacanning for you...... he put you just in middle of the active beam now, and is running just over your position......

But no ping sound......

When the DDs is more near, you start to hear the ping sound, but he is pinging you some time before.

What it means..... the range at wich you are hearing the ping, is not related with the pinging range capability.

It is a bug in my opinion, and is correctable with TT's MiniTweaker, wich can edit the range at wich a sound is audible.

I hope this can clarify and be a help for you on new ideas.

Originally Posted by Jungman

Hey, I found out how to set the Hydrophones Sensitivity from deaf to infinite. It is really easy. It was discovered based upon changing one line at a time inspired by all you guys, CB and all's work. (plus 12 hours of testing).

Sim.cfg

[Hydrophone]
;Detection time=1 ;[s] Stock one second is pretty fast.
;Sensitivity=0.03 ;(0..1) Who knows. Nothing gained here.
;Height factor=0 ;[m] Depth? harder to detect? Needs testing.
;Waves factor=0.5 ;[>=0] Rough weather makes for harder detection.
;Speed factor=15 ;[kt] Destroyer speed, higher the worst detection. Above this no detection.
Noise factor=0.1 ;[>=0] 1.0 Sensitivity for speed sub noise. Lower is higher.


Setting the Noise Factor from default 1.0 to a lower number towards zero will make the Sensitivity to your Uboats speed noise and silent running go to infinite as you aproach zero. Also going higher than 1 makes it become deaf. no other change. I made comments on what the other values seem to do.

So Noise Factor set at 0.1 you must move at below 3 knots at silent running at 4 km. Within 500m you must be SR and zero speed.

I disabled the DD active sonar for these test! Only passive at work here.

Set it at 0.5 you can move at 4 knots without silent running out to 2 km of DD.

Set for 1.0 for normal.

I commented out the other factors for now.

Yeh! There you go.

Hi Jungman...... my english is not good, but i note you discover the Sensivity value doesnt works fine..... lookt at the yellow line above you wrote.

That as a headache for us at first times of this topic, the matter is this value doesnt works, if the sensivity value at AI_Sensors.dat is not set at zero.

The game take the Sim.cfg sensivity value, only if the AI-Sensors.dat sensivity value is adjusted to zero.

This is explained into SH3Sim.act file, and discovered by .... i dont remember who was......

I think so the best way is to adjust sensivity into AI-Sensors.dat, then you can adjust a speciphied value for each determined sensor......

If you want to adjust sensivity via Sim.cfg, you must to adjust all sensivity values into AI-Sensors.dat to zero....... then you are able to use the Sim.cfg value, but.......... now you will a single sensivity value, it means, you will have the same sensivity for all sensors, disregarding model or age......

Sorry if i misunderstand that you wrote....

About your silent running settings, with my settings i attempt to found a behavior i think so was beliable.
I reach to be undetected by pasive sonars when at slow speed and silent running, except if you had the bad luck to be pinged.

I think so in real life a sub at silent running was litterally undetectable except it had been detected in the zone by periscope use visually or by radar, or use of high propeller speeds, and in the DDs seach he had the very bad luck to be pinged.

With my settings i am detected at slow speed, under 3 knots, at very near ranges, 500/1000, but when put silent running, the DDs can pass over me with no detection.

This is due to in the game, if you are not detected previously, by radar, visual or pasive sonar, they do not sails pinging.

If they had a previous advertence, and when they pass over me are pinging, i am detected.