Bunny Clark

Yup, this is totally normal and expected behavior and has nothing to do with GPS. IFF systems are actually a form of radar transponder, and an IFF response can be used to locate the responding aircraft. That's how the fire control system can correlate IFF returns with radar contacts, and why IFF transmitter power is variable and the system can be setup to notify you when an IFF response is broadcast.

Nope, those are baked into the system during the planning stage of the mission in real life. They're actually stored as a form of waypoint and not tied into the EW system at all.

If you follow the link for download, there are installation instructions, though it's pretty simple: Create a "Kneeboard" folder in your {User}\Saved Games\DCS folder, from there you can create specific subfolders for different planes, though you need to name them exactly right. If you download from the User Files link I did all the folder creation for you already, and it'll include files for more than one plane too

Not all GPS systems are created equal. My phone has GPS, but it sometimes can't even tell me accurately what block I'm on, I wouldn't trust it to guide an explosive device. The AGM-84E SLAM entered service a full decade before JDAM did, I imagine they made some improvements. Also, I'm not sure GPS guided weapons should really be accurate enough to take out tanks realistically. The JDAM has a realized CEP of around 7 meters, which is good, but still not good enough to reliably hit a tank sized object. There's a reason the GBU-12 is still around (other than cost), and that the GBU-54 was developed. LGBs seem to still be the weapon of choice when extreme precision is needed.

There's never been one since release, probably because the switch has been completely nonfunctional. Hopefully we get it as an available keybind when we get functional ECM.

Do you have a resource for a full list of real HOTAS commands? I'm not aware of one. I'm not sure logic has much to do with it, but the Hornet is definitely designed with the radar on the right DDI being considered "normal"

Yah, definitely a few startup issues to solve there. Your ejection seat isn't armed either, not that it would effect your guns.

Nope, it certainly won't. The T/O Trim button does nothing in normal flight, it will neutralize trim when the aircraft is on the ground, but in the air its only function is to neutralize stick position if the aircraft is in MECH mode. The FCS Reset button will reset the flight control computers and is used in the air only to clear faults.

There's few few options. You can leave it in manual, in which case it'll center on the TDC cursor. Or you can set a scan center bias by depressing the TDC on a blank area of the scope, which essentially marks a point on the scope you want to center the scan volume on - though we don't have this capability yet.

Oh that's a good point, I didn't think of that. Still, if someone's willing to overlook other oddities with the later ships not matching for first few, they may be fine overlooking that too.

The altitude value in the mission editor uses absolute altitude above sea level. The altitude indicator in game shows barometric altitude. Increase the mission editor value by the difference and it should be where you want it in game.

Like, use a track file to basically program an AI flight? I'm certainly not aware of any simple way to do that ...

How often are those on though? I don't imagine it'd be a problem during daytime or during nighttime flight ops, which is when nearly everyone will be looking at it.

On final bearing, technically, not BRC. But yes.

Where are you looking to see the change? The name of the unit type would need to be a .lua edit, though I'm not sure how to do this, I'm pretty sure it's possible. The name of the unit itself, and it's TACAN identity, are set in the mission editor and can be anything you want. The name and ship number you see on the actual ship in game is a texture file, and should be changeable by making a livery for it, though I don't believe we have a template for that yet to make it simple.

That's actually realistic. Since the ICLS and IFLOS systems are not mounted in the exact same location on the ship, they are not coincident for the entire approach. It is realistic and expected that they should diverge as you get in close, which is why preference is always given to the ball once you're visual on it. We'll also be getting the ACLS needles at some point, which will add another HUD indicator for approach position.

They use both. Or more generally, pulse Doppler radars use frequency analyzation algorithms to solve both range and velocity ambiguity, and in both cases those algorithms are vulnerable to false return attacks by EW systems.

In addition to AvroLanc's post above, the XP / AI display on the UFC is just a menu category showing which settings you are currently viewing and editing. Switching between them does not change IFF operation at all.

All the FC3 jammers seem to be a rudimentary noise jammer or barrage jammer, and nothing more. This function in the Hornet looks to be something like a range gate pull-off attack, which is totally different. I wonder if the ASPJ has additional modes or functions that we may yet be getting in the future?

Huh, interesting. Yah, the A-10C II doesn't carry the AGM-65E in DCS, it uses the AGM-65L variant of the laser Maverick. My guess is this mission was built with an early version of the A-10C II module when ED was just using the AGM-65E from the Hornet. When the 65L was added they would have removed 65E capability.

It's drawn the way it is on the reference guide for a reason, the "empty" SCS action will only bring up certain pages on certain displays. I don't believe SCS left will ever bring up the RDR page on the left DDI in any master mode, it's exclusive to the right DDI. I also seem to recall reading some time ago that the Stores page has specific SCS interactions as well, though I can't recall exactly what they were. I think SCS Left with Stores on the Left DDI in A/G toggles between weapon video and the Stores format, or something like that. I could be misremembering. But I think the Stores page has more complex SCS interaction than what we have now.

I hope and expect that this feature will come to all aircraft that slave Mavericks to other sensors. I imagine we've seen it in the Viper first because there are clear unclassified documents that detail the procedure. But hopefully that doesn't keep it as an exclusive thing to the Viper, that would be unfortunate and definitely feel like a Viper specific restriction when it shouldn't be. It's generally recommended to not boresight on the ground. Typically, this is something that would be done during cruise to the target area.

Generally ATC doesn't care when you start the plane. It's certainly not something that's done in general aviation. I'm not a commercial pilot, but I imagine that engine starts are something that coordinated with the ground handling crew and not the tower. You don't typically call the ground controller until the aircraft is started and ready for taxi instructions. On an aircraft carrier all aircraft launching for an "event" are started on signal over the flight deck loudspeaker. After that the pilots have no communication with controllers in the tower at all. All aircraft moving and launching is communicated to the pilots by hand signals from the aircraft directors.

Nope, the radios on the Hornet won't work until at least one AMAD is running. It's weird, and "request startup" is not really a normal ATC thing anyway in the real world. I just usually skip it.

You have two options for the radar antenna elevation controls: You can bind the axis: ANT ENEV Knob. You can bind buttons: ANT ELEV Knob - CCW, and ANT ELEV Knob - CW