Quote:
Originally Posted by in_vino_vomitus
Well - I used subguru's dipping sonar doctrine file and it's working like a charm now. There's no actual report from the chopper but the sub shows up as a green symbol, and if you click on it it gives the source of the info as link [helo ID] often you'll get a positive ID from the chopper even if you haven't got one from narrowband etc - and it seems like the MAD is modelled too. My chopper flew over at 200 or so feet and instantly the sub he was searching for was ID'd. Happy days - It makes a huge difference.
|
I stil can't understand if it is a bug in the LWAMI doctrine file or not, but I'm happy you found a solution.
Out of curiosity, I downloaded the doctrine file from subguru to see for myself the difference with the relevant doctrine file of LWAMI.
I have highlithed the parts missing from the Subguru doctrine file...
HeloDipping.txt -- LWAMI
Code:
...
; Assign Dipping Tactic
IF NEWTRACK THEN {
; Sub?
IF ( TgtClass $= "SUB" ) AND ( ( TgtSource $= "MAD" ) OR ( TgtSource $= "Visual" ) ) THEN {
SETTACTIC "MadDrop"
} ELSEIF ( TgtClass $= "SUB" ) AND NOT ( ORDER $= "TRANSIT" ) THEN {
DEBUGOUT "Assigning Dipping Tactic\n"
TACTICCENTER
SETTACTIC "DippingSonar"
Enable
SensorEnable "AI Dip Active" OFF
SensorEnable "AI Dip PassiveS" OFF
SensorEnable "AI Dip PassiveD" OFF
Pinging = 0
WaypointReached = 0
DipTimer = -1
TargetCount += 1
} ENDIF
...
HeloDipping.txt -- Subguru
Code:
...
; Assign Dipping Tactic
IF NEWTRACK THEN {
; Sub?
; IF ( TgtClass $= "SUB" AND ( ORDER $= "SEARCH" ) ) THEN {
IF ( TgtClass $= "SUB" AND NOT ( ORDER $= "TRANSIT" ) ) THEN {
DEBUGOUT "Assigning Dipping Tactic\n"
TACTICCENTER
SETTACTIC "DippingSonar"
Enable
; SensorEnable "Active Sonar" OFF
Pinging = 0
WaypointReached = 0
DipTimer = -1
TargetCount += 1
} ENDIF
...
I wonder if somebody here on the DW section of the forum, that knows about the doctrine file scripts and/or the LWAMI doctrine file, could rule out if in fact the LWAMI HeloDipping.txt snippet posted above contains a bug?
It looks like that, for some reason, the Subguru version commented out the use of the "SetSensorEnable" fuction: