TEOMOOSE

A-G > HUD soi > ICP 7 > TMS up long > designate area of interest > press 0, this make it the active SPI From here you can switch to ccrp and use the tgp look for targets.

I've watched the video of Spudkockers, and it's interesting. We have learned from Wags that a sensor soi needed before entering markpoint on the icp. If the HUD is soi it would automatically select the HUD option in the DED page. It was not the case in he's video. So what's the workaround ? A tip: press 0 on the icp after you have created the markpoint. This will make it the active steerpoint, SPI.

The F16 is like a dragster. It's built for speed, and agility, it's old school with an upgrade to use modern avionics. Love it.

There's no confusion here from my end. If you have watched the video or read the original post. Im aware of ils frequency's at Kobuleti the question was not how to ils rather the tacan function does not work in pls modes. If I set the ehsi to tcn via the m button it's working as intended. The video is a simple example of the systems that I have questions about. You're missing the point if you start "criticizing" video, it's not a tutorial. Navtrack.trk is the same flight I have posted in the link above. The crs might be off but is irrelevant for this conversation, it could be anything for this matter. The point is pls/nav does not care about a tacan station. CRS cannot be changed via the t-ils DED page in tcn mode but it has to be manually set on the ehsi. Therefore it considered to be as a backup option.

you dont have to press and hold Cursor enable. Press it once and put the thing on the thing and when is OK press 0 on the ICP (M-select) without moving your head. After that the process will continue using the cursor. Same thing except you slew the cursor over the thing "middle" line it up and press 0 on the ICP (M-select).

PLS/TCN: ( Precision Landing System (PLS) Setting the course via the ICP will automatically changes the course in the EHSI (as it should) when PLS/TCN selected but the bars are not moving at all. The only way to get the bars working if you tune in to a ILS station. Therefore TCN becomes useless and can be turned off. PLS/NAV: Using a the waypoint to runway via the selected course in the T-ILS ded page. Except if you dont have ils tuned in it will not work. Track included and a video of the same flight. I have also tried to follow the command steering cues on the HUD which should guide to intercept course to the localizer and when intercepted it will help to stay on it. But it never uncaged from the horizon on the HUD until the flag showed up over the "cicrle" command steering cue. The flag indicates when the aircraft is on glideslope. navtrack.trk command_steering_cue.trk

The challenge is that you want to fly the blue line but you see the red line because the placement of the vor station

Posting charts here allowed ? In short for the ILS approach to ruway 03, set course 030 heading, and for the VOR DME approach to runway 03, set course 029 heading.

Does it looks like this ?

Hey @BIGNEWYCould you confirm tacan operation. Currently we are using the backup tacan, and when switched to PLS/TCN nothing works, only if you have a ILS station tuned in which is very weird and it should not work that way. TACAN Normal Operating Procedures: 1. Turn MIDS on. 2. Depress T-ILS pushbutton on the ICP. 3. SEQ to select the appropriate mode. 4. Enter the desired channel number. 5. Select the desired band. 6. Depress the mode (M) button on the EHSI to select TACAN (TCN) or Precision Landing System / TACAN (PLS/ TCN) Backup TACAN Operation: Its pretty much the same thing except you select TCN on the EHSI. Important to note that the course can be entered via the ICP through the T-ILS page and is stored in the EHSI as well in all PLS modes, but not TCN mode. In TCN mode you have to change it manually on the EHSI.

Technically you wan to search in RWS modes first, and built a track file of the different contacts that are on the scope. The spotlight is utilized in rws since it gives you a high chance to reacquire a "lost" contact since it goes to A1 4bar. Than STT if you are after a single target, this gives you the best chance to support the missile without "loosing" the contact. If there are multiple contacts and used rws to gather enough information and identified hostile, you could enter in to tws which uses "less" energy to track it. This means if a contact start maneuvering in to the notch you will most likely to loose track or "lost lock", but you can target and shoot multiple target all at once. TWS also dose not warn contacts of a incoming missile until it goes active "pitbull".

I think this is what you are after as far as tgp box/hmd. The TGP will not display bullseye information as far as i know. It is available on the HSD page, and also the tgp position is marked on the HSD with a "larger" crosshair. That way you can make bullseye calls of detected targets.

Well, currently INS 6 has been "disabled" because of lack of information, so INS 10 in either modes.

it picks the strongest signals so you dont have to mess with it all, unless theres is a system failure.

The UHF antenna selector (ANT SEL) switch, located outboard of the Avionics Power Panel, allows the pilot to optimize UHF signal transmission and reception. The UPPER position selects the upper antenna, the LOWER position the lower antenna, and the NORM position automatically selects the antenna that is receiving the strongest signal. NORM is the most commonly used position. The IFF Antenna Select switch, used to select the upper or lower IFF transponder antenna. When the antenna select switch is in the NORM position, the IFF system automatically selects the antenna receiving the strongest interrogation signals

that would be correct. HSD SOI and TMS Right to designate a non-correlated D/L contact. After a PDLT has been made you can do "stepping" between other D/L contacts, or TMS aft to drop it.

Other modules do share similar systems and capabilities, while I understand it's totally different on each and every modules, but some D/L functions do exist in other modules and it's getting more in depth. Perhaps, if not all but adding some D/L elements to the TAD would be a great start.

Helmet Designation Cue

I should have guessed it that the subject was already mentioned. I posted the "same thing" here,

Yes, the TAD has a similar Threat Database: Pre-Planned, Data Link, Donor Threat, ALQ-213 Threats and Azimuth Threats.

I think you miss understood what i said. Perhaps a tacview if you have any to look at.

This is has to do with the Field of View. At a greater distance you the radar will see more within the Field of View depending on the mode it was fired. So its hard to test it, because you will have to be either close to a target sam, or try flying way off axis where you are outside of that FOV. Im very interested to see the results of your test.

and i have also noticed that the values for MIL power and A/B power are off in the F-16C.lua, here: CoreMods\aircraft\F-16C. So the values are in KGs, thrust_sum_max: 8054 kg or 17756 lbs "MIL power", and thrust_sum_ab: 13160 kg or 29012 lbs. The F110-GE-129 should produce 17,155 lbs in mil power and 29,500 lbs in Full afterburner.

What do you mean ?

You can "lock on" bug a Data Link contact (only one at the time) on on the fcr, before your own sensor sees it. which gives you a symbology on the hud, fcr, hsd, and on the hmcs.