Page 1 of 5 123 ... LastLast
Results 1 to 10 of 47

Thread: Semi active CMS profile

  1. #1
    Senior Member Howie's Avatar
    United Kingdom
       United Kingdom
    Join Date
    Apr 2013
    Posts
    1,185
    Thanks Thanks Given 
    421
    Thanks Thanks Received 
    252
    Thanked in
    171 Posts

    Semi active CMS profile

    Is it possible to create an effective semi active CMS profile for DCS A-10C?

    I know the CMS system doesn't always select the most appropriate program by itself, but could we not edit the profiles that it does select to be more effective against a wider range of threats while still not wasting too much chaff/flare?

    I'm currently running Eddie's CMS mod but using manual modes B and C exclusively.

  2. #2
    No. Which programs are selected when is hard coded and can't be edited by us. That is exactly what makes auto and semi so useless.

  3. #3
    Senior Member Howie's Avatar
    United Kingdom
       United Kingdom
    Join Date
    Apr 2013
    Posts
    1,185
    Thanks Thanks Given 
    421
    Thanks Thanks Received 
    252
    Thanked in
    171 Posts
    What I mean is could we not edit the program that the system selects automatically to be more effective against a wider range of threats?

    What are the main limitations with the semi mode? In what circumstance would it pick an inappropriate program?

  4. #4
    Ok get you.

    You could, but that doesn't solve the issue presented by the sheer uselessness of the semi-auto/auto logic.

    For example last time I tested it, all MWS alerts without a corresponding RWR alert triggered program M. Most radar threats triggered program B (IIRC may be wrong), however the SA-3 (and the SA-3 alone) triggered program L.

    And that's the big issue really, even if you created mix programs etc. it still wouldn't solve the fact the the whole implementation of the system is just flat out unfit for purpose.

  5. The Following 2 Users Say Thank You to Eddie For This Useful Post:

    El_Roto (16Dec14), Howie (16Dec14)

  6. #5
    Senior Member Howie's Avatar
    United Kingdom
       United Kingdom
    Join Date
    Apr 2013
    Posts
    1,185
    Thanks Thanks Given 
    421
    Thanks Thanks Received 
    252
    Thanked in
    171 Posts
    It's a real shame there isn't a setting in the .lua that could change which threat triggers which program. That would be awesome.

  7. #6
    Member JayPee's Avatar
    Netherlands
       Netherlands
    Join Date
    Jan 2013
    Posts
    490
    Thanks Thanks Given 
    144
    Thanks Thanks Received 
    78
    Thanked in
    60 Posts
    Howie, this might be of interest to you:

    Located here: DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\CMSC\device\CMSC_param.LUA

    Code:
    dofile(LockOn_Options.common_script_path..'wsTypes_SAM.lua')
    
    device_timer_dt	= 0.5
    
    JAMMER_SAM1 = 1
    JAMMER_SAM2 = 2
    JAMMER_AAA 	= 3
    
    -- a sequence below in an Alphabet order
    DEF_PROG_A		= 0
    DEF_PROG_B		= 1
    -- C .... K
    DEF_PROG_L		= 11
    -- M ....
    
    JammersProgramsForSAM =
    {					
    	--Program SAM 1
    	{ JAMMER_SAM1,
    		{ Kub_STR_9S91, Osa_9A33, Roland_ADS, Roland_rdr, S125_SR_P_19, S125_TR_SNR, Hawk_SR_ANMPQ_50, Hawk_TR_ANMPQ_46}
    	},
    	--Program SAM 2
    	{ JAMMER_SAM2, 
    		{ S300PS_TR_30N6, Buk_SR_9S18M1, Buk_LN_9A310M1, Tor_9A331, Tunguska_2S6, Patriot_STR_ANMPQ_53 }
    	},
    	--Program AAA
    	{ JAMMER_AAA, 
    		{ Gepard, Vulcan_M163, ZSU_23_4_Shilka, Dog_Ear }
    	}
    }
    
    ChaffFlaresProgramsForRadars =
    {
    	--Program A
    	{ DEF_PROG_A,
    		{ Kub_STR_9S91, Osa_9A33, ZSU_23_4_Shilka}
    	},
    
    	--Program B
    	{ DEF_PROG_B,
    		{ S300PS_SR_5N66M, S300PS_TR_30N6, Buk_SR_9S18M1, Buk_LN_9A310M1, Tor_9A331, Tunguska_2S6, Roland_ADS, Patriot_STR_ANMPQ_53}
    	},
    	
    	--Program L
    	{ DEF_PROG_L,
    		{S125_SR_P_19, S125_TR_SNR, Hawk_SR_ANMPQ_50, Hawk_TR_ANMPQ_46}
    	},
    }
    
    need_to_be_closed = true -- close lua state after initialization
    According to this .LUA the following programs are triggered based on the corresponding threats:

    A (RADAR - old gen.)
    SA-6
    SA-8
    ZSU-23-4

    B (RADAR - current gen.)
    SA-10
    SA-11
    SA-15
    SA-19
    Roland
    Patriot

    L
    SA-3
    Hawk

    I have a wild idea I can't test it for you right now so you'd have to do that yourself if you want. What if you could define more than just A, B, and L? Now it says:
    Code:
    -- a sequence below in an Alphabet order
    DEF_PROG_A		= 0
    DEF_PROG_B		= 1
    -- C .... K
    DEF_PROG_L		= 11
    -- M ....
    I was thinking if you change it to this:
    Code:
    -- a sequence below in an Alphabet order
    DEF_PROG_A		= 0
    DEF_PROG_B		= 1
    DEF_PROG_B		= 2
    DEF_PROG_B		= 3
    DEF_PROG_B		= 4
    DEF_PROG_B		= 5
    DEF_PROG_B		= 6
    DEF_PROG_B		= 7
    DEF_PROG_B		= 8
    DEF_PROG_L		= 9
    etc..
    etc..
    -- M ....
    you can perhaps 'map' a program to every single known (at least known to the DCS CMS logic) threat under this section:
    Code:
    ChaffFlaresProgramsForRadars =
    Maybe you can even map more threats than currently present in the .LUA but for that you'd need to know the exact name of the threat used in the programming.

    If I'm not making any sense, be sure to let me know!

  8. The Following 2 Users Say Thank You to JayPee For This Useful Post:

    Eddie (18Dec14), Howie (18Dec14)

  9. #7
    Hmm, haven't seen that file before. Will have to take a look and see what can be done with it.

  10. #8
    Senior Member Howie's Avatar
    United Kingdom
       United Kingdom
    Join Date
    Apr 2013
    Posts
    1,185
    Thanks Thanks Given 
    421
    Thanks Thanks Received 
    252
    Thanked in
    171 Posts
    Thanks JayPee!

    If that script and your idea both work, this might just be the greatest discovery ever.

    Work your dark magic Eddie!

  11. #9
    Member JayPee's Avatar
    Netherlands
       Netherlands
    Join Date
    Jan 2013
    Posts
    490
    Thanks Thanks Given 
    144
    Thanks Thanks Received 
    78
    Thanked in
    60 Posts
    Eddie, how did you come to the conclusion that every threat which does not have a corresponding RWR threat present at that time automatically triggers program M? Solely from testing it yourself or did you also come across a LUA file which suggests the purpose of program M?

    What I'm currently wondering is what would happen if you start to define program M. My logic would be that given the default CMSC_param.LUA DCS uses the first program in sequence after which no other program is defined as the 'other' program. However, I'm not sure if ED's logic and mine are perfectly in line.

    Quote Originally Posted by Howie View Post
    Work your dark magic Eddie!
    Like I said, if it works in the first place, you'd need a comprehensive library of all threats present within DCS World and their exact name. For starters you can see that ED used the Russian naming, not the NATO naming. E.g. an SA-3 is known within the LUA programming as an S-125.

    EDIT1:

    PS: I think that we now have evidence (in case it was still uncertain) that the ECM pods don't act upon A2A threats as only 3 ECM programs are defined:

    SAM1: Old gen. RADAR
    SAM2: Current gen. RADAR
    AAA: AAA
    Last edited by JayPee; 18Dec14 at 09:34.

  12. #10
    Senior Member Howie's Avatar
    United Kingdom
       United Kingdom
    Join Date
    Apr 2013
    Posts
    1,185
    Thanks Thanks Given 
    421
    Thanks Thanks Received 
    252
    Thanked in
    171 Posts
    Is there one of these somewhere for air to air threats as well? I think the program M thing was just discovered through testing.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Like our website?

You can help us by donating to cover our costs.

Many sincere thanks!


Search

Follow us

Twitter Twitter youtube iTunes Subscribe to our Podcast