GrEaSeLiTeNiN

I get that spotlight focuses the radar. In the video, Wags releases the hold on TMS Up in order to lock up the target. Unless a regular TMS Up would have been unable to lock that contact, the procedure is pointless. I’ll have to try the new spotlight when it comes out against far away contacts that can’t be locked up with a regular TMS Up to see if it makes a difference.

I watched Wag's recent (19 Aug) upcoming updates video which included Spotlight Scan Radar Mode here. But I am not sure how it is to be used exactly or whether it is useful to have the cursor over the target with TMS forward for > 1 sec, because the target will lock up anyway upon immediately TMS release without having to wait 1 sec, ie. a regular TMS Up would have done the job. Or do you do this only when the target, although detected, isn't locking up (is there such a possibility?) and having the cursor over and holding TMS up (> 1sec for Spotlight) will focus the radar on it in so it becomes 'lockable'? Also, spotlight scan radar mode is already available in OpenBeta. So what is the change? Thanks in advance

Hi, the manuals say... ED: Scan - Press TMS Left short (1 second or less) to interrogate all contacts in the radar scan volume. Line of Sight (LOS) - Press TMS Left long (more than 1 second) to interrogate the locked target or immediate area around the radar cursor. Chuck's: SCAN interrogates a locked target or immediate area around the radar cursor. LOS (Line of Sight) interrogates all contacts in the radar scan volume. 6. With Radar Cursor/Enable Switch, slew the Acquisition Cursor over the contact you want to interrogate 7. If desired, you can bug the target by using TMS UP, but this step is not necessary 8. Press TMS LEFT LONG (more than 1 second) to interrogate the locked target or immediate area around the radar cursor So it's a bit confusing but in doing some tests (latest OB), I find IFF LOS simply interrogates whatever is in the current FCR scan azimuth. So locking a target or having the radar cursor near a contact (let alone a contact under the cursor) is kind of pointless? because it does not interrogate only the locked target or the contact(s) 'near' the cursor (whatever distance that means is not clear). As such, IFF LOS with a scan azimuth of 60deg would also yield the same results as IFF SCAN (interrogates all contacts regardless of radar scan azimuth). Did I miss something? Is this WIP or should IFF LOS be more correctly defined as "interrogates only contacts in current radar scan volume". TIA

Isn't the IR Pointer no longer available in DCS F-16 TGP (see thread below). I'll just be in Area track with TMS Right x 2.

Have a look at these two videos: Although they are for the hornet, they teach some good A2A radar detection concepts.

When in AUTO and XMIT1, I can have FCR when the ECM is transmitting (Ts are lit). If I move the switch to XMIT2 (ECM is still transmitting), I lose FCR which is correct I gather. But when I move the switch back to XMIT1 (ECM is still transmitting), I cannot get back FCR even if I switch ECM to STBY (all Ss lit) unless I switch ECM off. Seems I have to wait for ECM transmitting to end first, then flip the switch from XMIT1 to XMIT2 to get back FCR, then back to XMIT1 (I want to remain in XMIT1). It's as if the logic got stuck in XMIT2. Is this intended or a bug/WIP? Thanks

Actually, would 'she' not know since it is already programmed (PRGM 1-6) and pilot-selected? Furthermore, for SEMI and AUTO modes, CMS Aft (in this F16) will only ever dispense chaff, never any flares. But I guess "chaff flare" is an easy generalisation, just that it sounds a bit odd when you know you aren't dispensing both types. Would have been nice to know (like a confirmation) if you are dispensing one (CH) or the other (FL), or both.

Sounds like a switch logic oversight? On a related note, in all my testings, CMS Aft in SEMI/AUTO will ONLY dispense chaff (as it sees fit) and never any flares, and it never uses any of the selected PRGMs (1-4). I understand this is because the onboard systems do not detect IR missiles and MWS is also not equipped in this F16 block. However, Betty will still say "Chaff! Flares!" and also in some tutorials "flares" are still mentioned with CMS Aft. I also wonder how the chaff program is determined by the system in DCS, or perhaps it is just a basic chaff program that is always the same (I did not count them).

8 months later.... Don't mind if I resurrect this old thread. Using latest Open Beta (14 Aug 2022). When in AUTO and XMIT1, I can have FCR when the ECM is transmitting (Ts are lit). If I move the switch to XMIT2 (ECM is still transmitting), I lose FCR which is correct I gather. But when I move the switch back to XMIT1 (ECM is still transmitting), I cannot get back FCR even if I switch ECM to STBY (all Ss lit) unless I switch ECM off. Seems I have to wait for ECM transmitting to end first, then flip the switch from XMIT1 to XMIT2 to get back FCR, then back to XMIT1 (I want to remain in XMIT1). It's as if the logic got stuck in XMIT2. Is this intended or a bug/WIP? Also, to have FCR in XMIT2 with AIM-120 "active", what are the conditions? Must the AIM-120 be in flight tracking a target BEFORE ECM transmitting starts? TIA

Yes, I figured it out finally. If I created say MPs 26, 27, 28, there is no way to correct MP26 and I cannot advance to MP30 with the rocker because there are no MPs 29 and 30. The only way to edit MP26 is to create MPs 29 and 30. Then go to MP30 to create (override) MP26. As you said, the easier way is to just edit MP27 with the corrected SPI intended for MP26 and ignore MP26. (Note-to-self: With TMS up and the MP number jumps to say 28, then MP28 was just created. That is why MP26 being the first, cannot be recreated from MP26 but from the last MP30.)

I find Markpoint (MP) 26 a little problematic. If I created MP26 (from blank/zero coords) using the TGP and then needed to correct it with a new SPI designate, I could not do it at DED MP26. I'd have to go to MP30 and start from there to change MP26. I know how to create MPs (TGP must be in point track and the new coords must show in the DED for the current MP being created). But to override or correct a particular MP in the process is confusing. I feel like the only way is to start over from MP30. Is there something I am missing? Thanks

I updated my earlier post with regard to IR missiles and SEMI/AUTO modes.

As already mentioned, if you go CMS FWD, you are in essence only using SEMI for its prompter "counter" and not its other purpose which is to dispense what it 'deems fit' (chaff only though) with CMS AFT. Doing CMS FWD always dispenses the PROG (1 to 4 only) you have selected on the knob unless in BYP mode where it is then fixed to 1C+1F. Note also that while SEMI is dispensing after going CMS AFT, doing CMS FWD will not work until the dispensing is completed, and this is the same with AUTO. Note that CMS AFT in SEMI and AUTO only dispenses chaff since the system cannot detect IR missiles as explained in another thread here. So SEMI and AUTO modes are only good for radar guided missiles, and be careful that CMS AFT while actively dispensing chaff, will prevent you from using CMS FWD/LEFT for some needed flares if an IR missile is inbound. CMS Diagram [Updated]

Yeah I know. Wait till you get in the Hornet. LoL The F16 is less complex than the F18 while the JF17 (which is a surprisingly good module) is more streamlined in weapon's deployment than either, IMO. Every time I fly something else for a couple of months and return to these modern jets, I need a refresher but it gets easier with time. But that's DCS as there are many modules to learn and fly. The helos if you are interested are actually easier to cover as they have fewer weapons and no radar (save the later Apache).

See if this helps...

I too wondered and bought it. Glad I did. I kind of prefer it over the Apache. I mean it flies really well and can outperform the Apache IMO (A2G/A2A) and that's with just one pilot. This is made possible in part because it has a great autopilot system and hovers well. Also, it isn't an EA module so you don't have to deal with bugs and wait for updates to fix them. Looking forward to BS3.

UPDATE: Did some testing today (latest open beta). It still works as per diagram as far as I can see. But to add, when tracked in SEMI, ECM will transmit automatically from Active mode but not when in Standby. Also (when tracked in SEMI) you will start dispensing (the PROG determined by SEMI) with CMS AFT and cannot halt it halfway. There isn't really a need to stop it halfway since it is going to stop on its own once the PROG is completed.

Should be able to that in SEMI. Have a look here though I am not sure if things have been updated. Haven't flown the F16 for a while.

Yeah similar frustrations but with a desktop warthog and VKB T setup which isn’t helo friendly. Anyhow, I set Apache missions with no wind, cold, low altitudes. Every bit helps. I find transition to OGE hover can work with ATT and ALT hold when done carefully and ‘it all goes smoothly’. But sometimes when things go wrong it gets crazy, yeah the helo is all over the place. It’s just so out of character to spend minutes trying to tame a rodeo helo infront of your enemy location. They must be watching with amusement. Went back to the joyful Black Shark and lately revisiting the F16. Taking a break from the Arghpache. Hope they fix the FM soon. It’s the Achilles heel of an otherwise great module.

Turkish F-16s with 192 Filo Kaplanlar Cyber Tigers tail art, Tigermeet 2014.

Time to give the Black Shark some love...