GrEaSeLiTeNiN

Hi, so in the OP, I get that it is correct as is. But can someone shed light on the other issue described above? That is, for Semi-Auto and Auto, I am unable to resume dispensing if I cancel dispensing halfway, so long as the current RWR warning beeps are still going on. Thanks! UPDATE: Reported as likely a bug.

No, it's two hostiles. It's actually a training mission I made. You can try it here... https://www.digitalcombatsimulator.com/en/files/3317002/ Yes, I read RWS inherently has trackfiles that are 'revealed' when LTWS is on. Hence LTWS is just a display option as you've described. So perhaps it's bugged in DCS? Regarding your last sentence, is there a form of "manual IFF" with LTWS on? My understanding of "manual IFF" is (as described earlier) having to do SCS depress to radar on an RWS TUC to see an update of the contact's HAFU in the SA page with LTWS off. With LTWS on, TUCs have automatic IFF and SCS work is not required. Did I get it right? (I am also not referring to AZ/EL auto IFF and L&S IFF, those are fine.) Thanks

Yes I understand that. But even when I do an SCS right fast enough without getting an L&S, nothing happens in SA.

Doesn't seem to work for me. Example: RWS with LTWS off - SA shows default yellow staple (at top half of HAFU) contact. At RWS TUC, I do SCS depress then SCS to Rdr -> no change to default yellow thin staple in SA. And often, that action by nature will make the RWS TUC into an L&S which then gets IFFed automatically and the yellow staple (at SA) become thick (ambiguous). What I was expecting to see (if IFF was working via the TUC SCS depress and SCS to Rdr method) was the thin staple (at SA) becoming thick without the TUC (at RWS) having to become an L&S first.

Thanks for the reply. The chart was helpful. OP updated for clarity. Just to check first: 1. Does the "T" in "TUC" refer to any contact or a locked (L&S) target? 2. SCS depress to radar means holding SCS down and towards the direction of the MFD with the radar, correct? My problem is not with the AZ/EL page - no problems with Auto IFF and L&S IFF there. It's with how and when to use SCS depress (now updated to SCS depress to radar MFD). Also with a Warthog hotas, this is a bit of a problem. I need to find a button that acts like SCS depress held down. Otherwise, if not done properly, SCS to radar just make a contact the L&S.

I'm still unclear about how SCS depress-to radar for IFF interrogation works. I mean all IFF seems automatic at the moment when the contact is under the cursor (TUC). So in order to NOT have IFF via TUC and use the SCS depress to radar to do an IFF, do I have to use only RWS with LTWS off? I actually tried that but nothing happens - was it suppose to update the HAFU in the SA only. With LTWS on (in RWS), it's automatic when you hover over the contact but often the top half of the HAFU is just a default yellow staple (not a thick ambiguous staple which I assume would have been a sign of the IFF working). With RWS/LTWS on, hovering the cursor over a default staple and doing SCS depress to radar changes nothing for me. What am I missing? Thanks. Updated for clarity.

Thanks for the tips! I get the idea of a max quick dispense when reactive (near) and a more drawn out program when proactive (far). Thanks for the tips! I get the idea of a max quick dispense when reactive (near) and a more drawn out program when proactive (far).

Hi, Against radar guided missiles, which program is more effective? (other variables being the same) 4 Chaff + 0 Flares Repeat 5x Interval 1 sec 2 Chaff + 0 Flares Repeat 10x Interval 1 sec I guess what I'd like to know is whether 4 chaff has a larger and thus better decoy radar signature than 2 chaff, and if so, whether this is modeled in the DCS. Thanks!

Thanks guys! I got it now. Part of the confusion I had (aside from the manual) was that in Semi-Auto and Auto modes, the little number below the mode name was actually the manual program which I could initiate with Aft. I had thought it was the program self-selected and dispensed by Semi-Auto and Auto modes. But while testing, I noticed something odd. I'll try to explain it... Semi-Auto: Fwd consents and stops it as intended. But if I stop the dispensing halfway, I cannot resume (re-consent to dispense) while the initial audio warning is still going on. I have to wait for the initial warning sounds to end then re-consent when a new audio warning starts, in order to dispense again. Auto: Consent is automatic and Fwd stops it as intended. But similarly, it will not auto resume after I stop it halfway, so long as the audio warning that started it is still going on. It will only auto dispense again after the initial audio warning ends and a new audio warning starts. Is this correct?

Hi, using latest Open Beta. In Create Fast Mission (Advanced mode), every time I try to generate a SEAD mission, the 'Generated' progress bar hangs at 10% or 14%. This happens in Syria, Nevada and Caucasus maps with the F18 and F16. I haven't tried other maps and planes but I suspect the same will happen. I don't have a problem generating all of the other mission types. It is only SEAD that causes this issue. Is this WIP? Thanks I did a full DCS World repair just in case but the problem is still there.

But the manual does not put it that way.

Hi, I'm using the latest open beta. In semi-auto and auto modes, forward on the countermeasure switch seems to do nothing. Should it not dispense program 5 as stated in the manual (see screenshot)? The switch works fine (fwd and aft) in Manual and Bypass modes. For example, in fwd, it will dispense Prog 5 in Manual mode. But in both Semi-Auto and Auto modes, fwd on the switch does not dispense anything. I can't figure out why. Was there an updated change? Please also see attached track file. Thanks! Hornet Countermeasures Switch Fwd Issue.trk

Quite the same for me. Trimming and power to get AoA just messes it up for me, esp with the Hornet. The basics I find that that help me in the Viper are (a) to first get it right at the approach, by coming in well below 1000ft and with a slow speed (160-170 knots for me) before the threshold (b) slightly oscillate the throttle near idle but not idle (unless fast) before touchdown, I find oscillating it helps me avoid stalling (c) watch aero brake at close to 15deg pitch for max effect without tail strike (d) pull back a little on stick as front wheel drops to avoid bounce. I only get the AoA centered (13deg) just before touchdown. It feels more natural at 11deg AoA or less during approach. I don't always have the patience for procedures. Sometime I just drop out of the sky, jink to lose speed and declare emergency to land using these basics.

Yes, can be fun making the 'perfect' personal map. For me I checked out other layouts to get an idea of what other ppl had in mind that worked (for them). Then personalised it. I tried not to make it too complex but also realised I would get use to the layout after several missions and could see what worked and what needed changing. All the best to your hotas mapping

Congrats on your new Hotas combo. I’ve read it’s a good pairing. I got the TM Warthog eventually. The stick was quite stiff initially (ex T.Flight HotasX user) but I have gotten used to it without modding the springs. I made the ‘notorious’ Warthog throttle mouse button the perfect Shift button, IMO, as opposed to the stick pinky. After a couple of mapping iterations and practice, I am quite happy now with my Hotas setup. Here’s my layout just for mapping comparison :) - https://www.digitalcombatsimulator.com/en/files/3317760/

Good point. The Maverick display has a lower zoom level and is more finicky with target locking. So it’s better to settle a good lock with it first, then correlate that lock over at the more efficient TGP. Only thing is if you are doing boresighting in the air you’ll need to get closer or choose a larger object as the Maverick FOV is low.

Haven't tried the TGP in DCS Viper for a while now. I reckon it's still in development and subject to change/errors. So what you learn today might change some time later. Unless it is already correct and stable but I am not aware of that. As a suggestion, you could try TGP and Mavs in that other sim which is mature and stable and see if you run into the same problems. Yes, operating the two can be frustrating at times. I use Snowplow to reset the TGP when things go wacky and Wide FOV for faster re-slewing. Have to watch out for Cursor Enable which puts the SOI in the HUD and forbids TGP SOI, if I recall right. But all this is in that other sim.

Yes I finally got my setup in Apr after some research. I did ask the vendor for some advice. Something about the next higher model of CPU and GPU not being worthwhile (at that time). He also said 5600X doesn’t run hot (which it doesn’t and I live in the hot tropics). Don’t wait too long, avoid analysis paralysis [emoji28] Take the plunge and enjoy DCS to its full glory! (I upgraded from an old laptop, so for me it was wow!) CPU: AMD Ryzen 5 5600X GPU: Gigabyte RTX 3070 Gaming OC 8GB MOBO: Asus B550 TUF Plus Gaming SSD: 2TB Aorus Gen4 (R: 5000 | W: 4400) RAM: 32GB Adata Spectrix D50 3600 Mhz (16x2) CPU Watercool: Aftershock Spectra Glacier 240mm PSU: 750W Superflower Legion HX 80+ Gold CASE: NZXT H510i Compact Mid-Tower FANS: NZXT Aer F120mm Fans x 2 WIFI: Intel AX Wireless (WI-Fi 6) + Bluetooth 5.0 Vendor (Singapore) - https://www.aftershockpc.com/welcome/Productinner/hypergate-new-5 Screenshots - Settings: In-game system settings - https://imgur.com/MURVtrJ Nvidia control panel settings - https://imgur.com/zErLiu6 Win10 graphics settings - Hardware-accelerated GPU scheduling ON - Variable refresh rate ON (Screenshots in Hoggit are DCS print screens without any editing.) I don't do MP but on DCS Fast Mission / Persian Gulf / Medium Red & Blue Forces / Broken 2 Clouds, I think I get about FPS 70-80 looking at the cockpit dashboard and about FPS 100+ when looking at the sky. No stuttering.

Thanks. I have the warthog throttle and its speedbrake switch is similar to what you described. I would infer then that the concept of using speedbrakes, at least for the F18 and F16, is that the pilot is able to stop/resume at any position when extending or retracting the speedbrakes.

Hi, just a quick question. I know for the speedbrake switch, it seems backwards (aft) is to deploy the speedbrake as long as the switch is engaged. Forward retracts the speedbrake but my question is - in the real aircraft, is it suppose to retract all the way or only as long as the switch stays engaged in the forward position? Is there a difference in the way this is done between the F18 and F16? In that other sim's F-16, I noticed it retracts only for as long as the switch is held (forward) based on their stock Warthog key profile. Thanks in advance!

Could I not just pull back on the stick? Or is there a difference? Thanks

Realistic TDC (Unchecked) is still not working for moving the EXP box around in A/G RDR without having to depress TDC. Elsewhere it works.

I just bought a Warthog and have experienced the above - yes, Realistic TDC (Unchecked) still does not work for EXP work (you need to hold TDC Depress down). So I mapped the finicky slew control/mouse button as a SHIFT button and have two TDC Depress options mapped. One on the stick Pinky for regular A/A RDR work and another on the throttle coolie POV2-> for TGP and A/G EXP work. Makes life easier. That said, it should be a simple fix ED could have done ages ago.

Is the T/O trim button really necessary to use or good to have? I've never used it and am able to take off just fine.