GrEaSeLiTeNiN

Would this be right for the latest open beta as of today? CMS Switch FWD: Dispense selected Prog 1-4 LEFT: Dispense Prog 6 AFT: Enable AUTO, ECM to Active (No "Consent SEMI" here since you need to manually dispense (FWD or LEFT) after audio prompt in SEMI) RIGHT: Disable AUTO, ECM to Standby Dispense Button Dispense Prog 5

Thanks! I'll just paste it here for quick reference on this thread:

Thanks. So XMIT 1 allows some (60%) radar usage. Does that mean AMRAAMs fired in 1 will not be as reliable in terms of locking and tracking till impact?

Spudkocker explains FRM and SPL at the 6min mark in his video here - FRM (Formation) - combined jamming strength with wingmen’s pods in close formation SPL (Special) - a special type of jamming algorithm for specific emissions encountered Both are not implemented yet.

So is “silenced” the same as “reduced by 40%” and when Aim120s are selected is Rdr and HTS reduced by 40% or silenced? Thanks

These vid tutorials will help. Undesignate and SCS to AttkRdr (AACQ) may be faster ways to designate.

The official one that comes with the purchased module is Thunder Strike but it’s in the early access stage. I don’t think it’s been updated much. I haven’t tried it though. Desert Thunder is a user-made campaign for download in DCS User Files. You will need the JF17 module to play it. I use Liberation 5.0. It has ‘dynamic’ campaigns with the JF17 as one of the flyables.

Yeah, JF17 weapon/MFD procedures are more simple, logical and streamlined, yet effective. The one I find increasingly HUD/MFD cluttered and complex is the F18. Sweet spot is the F16.

Speaking only from my own experience, from TFlight HotasX to a Warthog, I tried AAR a couple of times for the first time and couldn't do it properly. Warthog may not be a good example as the stick is quite stiff. Not sure about VKBs and Virpils. It's probably more a skills thing. From what I read, VR gives the best advantage due to better depth perception.

I have been having this same problem in the f16 with CBU97. What makes the CBU97 so different that it needs such drastic dive angles in order for the delay cue to move down to the pipper?

Thanks for the info and correction on the BORE/SLAVE that it is from the permanent setting. Enable depress does not seem to work for Aim-120 (BORE/SLAVE) at the moment. As for HARM, yeah I thought it should cycle HAS/POS but it does not at the moment. (Comparing all this with that other sim.)

What it does at the moment (latest Open Beta as of 15 Dec): A-A Depress (Hold): AIM-9 -> BORE (if SLAVE) / SLAVE (if BORE) Depress or Depress (Hold): AIM-120 -> Does not cycle BORE/SLAVE (Is this correct?) A-G Depress: MAV WPN Page (must be SOI) -> Cycle VIS/BORE/PRE Depress: HARM -> Does not cycle POS/HAS/DL (WIP?) a) Is the above correct for the AIM-120? b) Is this all the Enable button can do or is there more? Thanks!

From what I've tested, say you have Link16 on and see 3 full red triangles (correlated hostiles) on the FCR. You bug one and want to bug cycle the others with TMS right. If it does not happen it is because the other 2 are actually not system files (hollow squares) yet but track files (full squares). You can't tell because the full red triangles have covered these squares. But you can verify this by turning MIDS (Link16) off and look at the squares. You can only cycle bug system files (hollow squares). What you need to do (if Link16 is still on with those full red triangles covering the squares) is: 1. TMS down to unbug 2. TMS down again to set all to track files 3. TMS right to set all to system files 4. Bug one and then you can cycle bug You do the above without seeing the squares but understanding what's actually going on 'hidden beneath' the full triangles. I think the problem is that full or hollow triangles in the FCR have to do with correlation, not track/system file status. It's symbology brought over from the HSD where full or hollow are about correlated/uncorrelated. But in the FCR (MIDS off), full or hollow squares are about track/system file status. Do correct me if I am wrong. Cheers

When the CM802AKG first came out, I remember it was very difficult to steer, like it kept veering off. Seems a lot easier now, more ‘ground stabilised’.

I've only added my own flight mission to avoid "your plane is delayed". Have you tried GitHub forums? I think it can only be done in mission editor/planner.

Deka's current guide still says - "In DIR mode, missile fly to SPI directly. In COO mode missile will attack PP point (choose from No. 36-39)." This can create confusion. Chuck's latest guide is now clearer (just reread it) as it says "fly towards" the SPI/PP and mentions "the missile will enter MITL mode" 20km out. Seems I missed the update - "28/05/2021: CM-802AKG missile logic & procedures revised; Datalink pod is required for DIR, COO and MAN, which all require MITL guidance." (Though I can't seem to use the optional RP for DIR or COO modes as described in the guide.) Anyhow, looks like the CM-802AKG is more akin to the Israeli Delilah missile, not the SLAM-ER or Walleye.

Yeah, it's the same with COO. Maybe it's a bug or misrepresentation of the missile. I couldn't find real world info on it. Or perhaps "DIR" and "COO" are inaccurate translations from Mandarin to English, that the Chinese manufacturer's meant something else. There isn't a Western equivalent to a locked target SPI or PP coords where the missile just flies over it. The other question is why the UFCP DST page COO/PP Alt setting (I tried zero) made no difference, and why the ME does not permit you to enter elevation for the PPs. Hopefully it's WIP.

If we look at the SLAM-ER or Walleye (Wags' Hornet tutorials), they both have the fire-and-forget option of not requiring the use of the datalink pod and MITL steering, and will still hit their targets (PP/TOO for SLAM-ER, locked target for Walleye). If you fly Western aircraft like the F18/F16, you are used to the idea that the weapon will hit a locked target or target coordinates. But not so with the CM-802AKG in DCS. It sees a locked target (DIR) or pre-planned coordinates (COO) as just 'waypoints'. It would be unusual if Deka's CM-802AKG in DIR and COO modes are true to real life. Anyway, I found this old thread discussing this confusion. Manuals and choice of words used to describe the first two modes ("DIR" and "COO") can be misleading.

Just did some testing. Yep, in DIR and COO modes, the missile just flies over the SPI and PP targets. You must do MITL final steering to the target. Kind of strange for an SPI. For PPs, I noticed there is no option for elevation setting in ME. In flight using the UFCP DST page, I tried setting ALT for the PPs to 0 but the missile still flies over the PPs. MAN mode goes without saying. So the CM-802AKG is a MITL weapon in all 3 modes.

I'm currently doing a refresher in the JF-17 after having been away from it for a while. I have some questions on the CM-802AKG missile: a) If I recall, the CM-802AKG missile REQUIRES MITL steering at terminal phase for ALL 3 modes (DIR, COO, MAN) to hit its target. In MAN mode, it's understood MITL steering is required. But in DIR (SPI) and COO (PP) modes, it's not always apparent that MITL steering is ALSO REQUIRED despite having an SPI or PP (which act more like "waypoints" for this missile). Is this correct? I could run some tests but thought I'd check with the forum first. b) What's with the "5NM" range indicator next to the RP indicator (top left DLPOD display) whenever the last RP is reached? For example, "3/3 2NM" means 2NM remaining to RP3. But once RP3 is reached, it stays fixed at "3/3 5NM". It's always "5NM" regardless of number of RPs or distance from last RP to target. Thanks!

Hi, when I open liberation_nextturn in the ME, I see dozens of blue plane icons and flight lines all over the place. Is there a button or command I can use in ME to get the player mission/plane that I have selected from Liberation to automatically show up (in white) so I can do my edits to my flight like change the loadout, skin, etc? Otherwise, I have to click on many of those blue lines and plane icons to figure out which one is my mission/plane. UPDATE: 'C' key in ME centers player's plane icon in screen and highlights it in white.

If I recall right, I did a mission to strike 4 offshore oil rigs placed adjacent to each other. The 4 waypoints were acccurate.

Thanks. I just got into Liberation and this is the one thing newcomers need to understand about Lib esp if they were expecting a dynamic campaign similar to BMS. Other thing is that the generated missions you get to pick in Lib comprise a mix of different aircraft, unlike in BMS where you belong to say an F16 squadron and fly F16 missions. So if you are focused on flying say the F18, you'll have to filter through the list to find an F18 mission to fly.

Hi, just wanted to check if the countermeasures behavior described below is correct. Thanks! SEMI-AUTO Mode (Switch-Fwd consents release of chaff/flares and also stops it, as per current implementation): If I stop the dispensing halfway (Switch-Fwd), re-consent to dispense (Switch-Fwd again) does nothing so long as the RWR warning sound present at the previous consent is still beeping. I have to wait for the beeping to end then re-consent when a new RWR warning sound starts, in order to dispense again. AUTO Mode (Consent/dispense is automatic and Switch-Fwd will stop release of chaff/flares, as per current implementation): Similarly, it will not auto resume after I stop it halfway, so long as the RWR warning sound (that started the previous auto dispense) is still beeping. It will only auto dispense again after the beeping ends and a new RWR sound starts. Is the pilot suppose to use Switch-Aft to dispense the selected program in such situations?

Sorry, just to clarify, the test mission had AWACS and friendlies too. Friendly or Unknown - I see that now with the chart from Tholozor which was helpful. But my issue is that with RWS/LTWS on, the same contact in SA (the TUC in RWS) would update to a thick staple (ambiguous) as opposed to remaining as the default thin staple when SCS IFF is commanded in the RWS page with LTWS off. But perhaps as Harker has explained, it's just the way it is currently implemented.