Quote:
|
Originally Posted by Dr.Sid
Hm .. I did some checks .. and really .. I don't see how to do it. HF is not even a sensor in database, it is just a different 3D view. 
I think reasonable ranges would be 1-2 miles for detection, 5 miles counter detection .. or something like that .. you whould know when it is safe to use. You should be pretty sure with your 5nm vicinity.
But let's discuss the possibility of doing it first. |
Ok.
My 1st attempt would be:
Test case:
Two playable submarines, SUB A and SUB B, SUB A detects SUB B HF sonar at 5nm or less
Trigger:
Event / auto / refire time: 1 second
Duration: 5 seconds
Doctrine:
If detect SUB A by SUB B with HF sonar AND
Range from SUB A to SUB B < 5.25 nm THEN (to cover range at 5nm or less)
Trigger fire
Script:
Send report to ownship “sub A detected sub B HF sonar” (at least, to know if trigger fired or not)
Enter bearing for SUB B
Notes:
Run a script to report bearing of the HF source, in the case a bearing on SUB B while the conditions are met. IIRC this could work in SP, but in MP we ran into problems of it ‘half working’. It would work for the host, but not for clients. The bearing report is sent to NAV and could make up for the act int.
I’m thinking that the moment SUB B turns on his HF sonar from 5 nm, that would force the trigger to fire, then spit out a bearing report on SUB A nav screen, revealing the bearing of the HF source. However, I’m not sure if toggling the HF sonar(on, off, then on again) itself would effectively enable or disable the trigger. I am also not sure if actual detection of HF has to be made for the trigger to fire either.