Sn0wMan4

After flying the F-16 for 6 months and getting pretty good at it, I tried the 2 week trial of the F-18 and I can say without a doubt the F-16 is simply easier with less steps to do what you want to. The DOGFIGHT switch saves your previous mode setup, meaning you could've been lining up for some bombing runs with TGP/WPN pages up, switch to A/A mode, kill the threat, then when you exit DOGFIGHT, your bombing run pages come back the way you left them. Targets of Opportunity are ridiculously easy. Push MARKPOINT, TMS UP long to get your helmet tracking a target, TMS UP twice and you've just created a Sensor Point of Interest. The flight models are also very different. The F-18 will not let you exceed 6G's at high speeds. The F-16 will let you pull as hard as your pilot will take. The F-16 will also not allow you to stall the plane as long as you have throttle. And the visibility! I love the F-16's glass bubble. It's visually a pleasure to fly with to actually see your surroundings. F-16 all the way.

I've been flying the F-16 for about a year and have all HOTAS controls mapped to the point where I don't have to look at much. I have the Winwing F16 stick, F15EX throttle, F16 ICP, and two MFDs. I want to start flying the F-18, but I don't want to spend an hour mapping all the buttons. Does anyone have a key bindings profile for this kind of hardware? Thanks!

I am vindicated. Hallelujah. Except now CCRP misses by 300m every drop. Ridiculous. CCRP can't hit.trk

Are we back to this again?

Random question but are you having the problem using old mission saves? I've had the boresight go completely wonky mid-flight from a hot start. I can't determine how to reproduce it but it shows up.

Does this help?

Both launchers are supposed to support it but only the single one actually does. However, you're not supposed to do this in practice because you can't verify the 2nd target when you launch. You should just lock both and use missile step between shots.

I found the document they used for this change and their change log is almost verbatim to it. It's the student manual for the deployment of AGMs. Except they didn't realize it pertained only to FCR. TGP does not hand over SOI to WPN when you TMS forward, because it's a handoff of targeting data. So when they changed FCR to work correctly, they made it apply to the TGP as well.

I agree on the accuracy that the TMS-Forward when FCR is SOI indeed changes SOI to WPN, but this is not the behavior when using TGP in AUTO. Edit; and this is the last thing I'll say, Wags shows what RIGHT looks like. I'd double check with him on this one.

Except the AGM-65D isn't EO, it's infrared. The AGM-65D should not behave in this way.

Eh, I looked it up. It's not how it works. ED made a change to the FCR "When the FCR is SOI and set to GM, GMT, or SEA sub-modes, entering FTT or MTT will also transition the SOI to WPN and the AGM-65 seeker will enter SLEW mode" and the change was copied to the TGP. It was working correctly before this patch, now ED broke it, and are saying it's "correct as is."

I just tried twice and it's working fine (dropped on a moving target). My guess is that you're masking your TGP when you fly over the target.

Okay, I'll retract "correct" behavior. I don't know how a real F-16 TGP hands off to a WPN, but this change is not an improvement. Locking anything in the TPG causes the SOI to move, so if you TMS forward with TGP SOI and you missed, you have to switch SOI back every single time to reacquire a target. All this has made me do is never have WPN active on my right MFD, which is a real shame. Edit: a workaround to this is to target with the TGP, switch the SOI back, then use TMS-RIGHT to get the AGM to lock on to new targets without having to go back and forth between SOI.

TGP to MAV handoff now moves SOI to WPN, which I can't comprehend how that makes anything easier or better since you can launch mavs while TGP is SOI and the WPN window is trash for finding targets (terrible zoom). This was a huge downgrade and complicates what used to be a trivial procedure.

I provided a YouTube video tutorial showing that it is previous behavior so I'm not sure why you keep saying it wasn't. Did you watch the video? It's quite clear that setting the target in the TGP does not shift the SOI to WPN. Second, the procedure now is ridiculous with the SOI switch mandatory because if the target doesn't acquire, you're stuck in the WPN as SOI with an inferior magnification, and then you have to SOI back to TGP to reacquire the target. This makes rapid fire AGMs painfully complicated, since in the previous version, you could just slew the TGP over another target and the AGM would get the handoff again automatically. The only bypass to this is to not enable WPN on your other MFD, that way it can never change SOI. Why this is intentional is beyond me.

This is not intentional. This is the previous and correct behavior. Note time stamp 2:14. (also want to point out this was posted 1 year ago, so that's 4 years after your update reference) Why is this being posted 'correct as is' when there's evidence that this is not the previous behavior nor is it mentioned as a change?

DTOS designation does not properly create an SPI (area/point track) for the TGP. Steps to recreate: Set A-G. Set MFD left to TGP Select bombs Set DTOS Set HMCS to SOI TMS UP for 0.5 seconds to enable TARGET DESIGNATE (TD) TMS UP to designate ground target - TGP will stabilize on target, but it is not smooth (tracking glitches every second) Set TGP SOI - TGP is no longer ground stabilized and is caged to the last perspective from the aircraft to the designated target.

Steps to replicate: Set A-G SMS select AG-65D. Set to PRE. Set right MFD to WPN Set left MFD to TGP. Set TGP to SOI. Set TGP to AUTO. Locate target Target designate SOI will change to WPN during handover. Additionally, TGP SNOWPLOW gets fixed to the horizontal plane and not at an angle to the ground when in TGP/AGM-65D. TGP Loses SOI When Targeting and WPN Active.trk