DW Mod question

banryu79 · 06-09-14, 08:34 AM

Quote:

Originally Posted by in_vino_vomitus

Yeah - Have read the manual - but missed that line - good point - as for the dipping sonar issue - although the helo *looks* like it's using it's dipping sonar, it doesn't seem to be detecting subs that are as little as 1000m away - It's certainly not reporting them.

Well, I'm not familiar with the dipping sonar capabilities in active mod in Vanilla DW, go figure in LWAMI!

But before thinking the behaviour you are experiencing is a bug, consider the possibilty it is in fact a feature!
I can give you two possibe reasons for why your active dipping sonar is not acquiring an enemy sub at 1000 meters.

First:

An second, as you already have read:

If you put in the equation the two reasons above and add in the changes LWAMI put in general in the acoustical model for the game, chances are that what you are experiencing is in fact exactly correct. Or maybe not, go figure

FPSchazly · 06-09-14, 10:47 AM

Quote:

Originally Posted by banryu79

Well, I'm not familiar with the dipping sonar capabilities in active mod in Vanilla DW, go figure in LWAMI!

But before thinking the behaviour you are experiencing is a bug, consider the possibilty it is in fact a feature!
I can give you two possibe reasons for why your active dipping sonar is not acquiring an enemy sub at 1000 meters.

First:

An second, as you already have read:

If you put in the equation the two reasons above and add in the changes LWAMI put in general in the acoustical model for the game, chances are that what you are experiencing is in fact exactly correct. Or maybe not, go figure

1000m is pretty close for a big chunk of metal, even if it's bow/stern on haha I would definitely expect a sub that close that's getting pinged to be detected for sure. But, who knows?

in_vino_vomitus · 06-09-14, 05:57 PM

Quote:

Originally Posted by banryu79

Well, I'm not familiar with the dipping sonar capabilities in active mod in Vanilla DW, go figure in LWAMI!

But before thinking the behaviour you are experiencing is a bug, consider the possibilty it is in fact a feature!
I can give you two possibe reasons for why your active dipping sonar is not acquiring an enemy sub at 1000 meters.

First:

An second, as you already have read:

If you put in the equation the two reasons above and add in the changes LWAMI put in general in the acoustical model for the game, chances are that what you are experiencing is in fact exactly correct. Or maybe not, go figure

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.

Also the towed arrays on the 688i are definitely different, despite the platform info saying they're not. The Starboard array washes out at about 14 kts and the Port at about 18, so it seems that it's just the in-game info that's behind the times, which I can live with

banryu79 · 06-10-14, 04:19 AM

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:

in_vino_vomitus · 06-10-14, 06:29 AM

Quote:

Originally Posted by banryu79

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:

Answering that is beyond me, but even at my level of inexperience I can tell it's made the FFG a lot more effective. Now I guess I need to learn how to use it to best effect.