EXPENDTripwire

Pretty much given up on ever seeing my T-shirt arriving. Ordered in Nov 2023, requested they try ship again in June, but I still haven't received anything.

I admit, I haven't tested this extensively, but I too noticed that there didn't appear to be any audible difference based on lock vs launch. You mention a bug regarding the 'new guy' indication, but either I haven't understood your answer correctly, or you haven't covered off on the quoted part of MBot's question? In my case it was an SA2 that was priority and set to handoff. The RWR provided a launch indication, as it does when you don't have handoff turned on, but am I expecting something that isn't realistic - different handoff audio based on lock vs launch?

Still waiting on mine, Western Australia.

Only if using GPS guided munitions. If that is also the case for you, switch them to PP momentarily instead of TOO to clear the stored target point and you get that ability back. Only workaround I have found thus far.

Hmm, I am disappointed it didn't work for you. When you press Right Ctrl + Enter and bring up the control display, does it not line up with the after burner detent marking illustrated there on the throttle axis?

Same issue on the Winwing Orion2 with F18 handles. This has helped me fix the issues I had with mine.

Yeah, mine did exactly that.. straight down into that hole. The amount of thread holding that nut in place is minimal. Had to pull the whole thing apart to find it.

I found that I couldn't get my left throttle to engage the off button at the end of the axis until I saw that the screw attaching the fingerlift mechanism to the left throttle was too long and fouling against the center idle detent. There was only about 1-2mm of motion that it couldn't move but it was enough to not reach that switch.

I used a slight variation to the approach. Rather than try and use F2 and looking for the AB to ignite, I went into options (from the main menu) and under the special options for the FA-18 I set the AB detent setting to always on. What this did was stopped the throttles from moving into afterburner in the game. I then moved the Winwing throttles forward until I found the exact point where the cockpit throttles stopped moving (as the cockpit throttles were locked out by the AB detent). I then took the axis values and followed the remainder of the approach and maths used by others to set the AB % in SimAppPro. Once done, I went back into the main menu special settings for the FA-18 and turned the Afterburner detent back to always off. I ended up with a setting of 74% using this method.

I've just received my preorder email and about to pull the trigger - but that video posted by Paschon really looks worrying. Anyone else that has received one able to chime in - Are they all like this or is this an unlucky case because that doesn't look like a great design?

Thanks for posting up this question, and swiftwin9s for the answer - this has been bugging me for a long time.

I'm finding the carrier LSO seems to give out way too many _OK_ gradings for something that is a perfect pass and 'rarely awarded'. I've got a significant amount of room for improvement when I watch my landing?

If it's a square it's unknown. A friendly is a square with a semi circle over it. Be aware that right now this only shows on the HUD, not the JHMCS and not for any F18s that the AWACS is also updating you about (which will be the majority of the ones you encounter) which is why there are still many FF incidents. Diamond for enemy also doesn't show unless you have a second contact declare a contact enemy, which when in mountains hidden from AWACS can be problematic.

Which is exactly what I showed in that track I uploaded? There is an AWACS in the mission. I can't see how it's seen as working correctly at all? Also is the friendly HAFU not supposed to work for the JHMCS as well?

Track file attached. In the track I am using VR. At first as explained by the OP, you can see the friendly HAFU prior to the datalink comming online for the F/A-18C. Then I show that it is removed once the F/A-18C starts broadcasting. Next you can see the Friendly HAFU work for the F5, but not the F18. Finally I show that using the JHMCS, the friendly HAFU is never indicated, only once the contact is shown on the HUD. hafu bug-vr-hmd.trk

Question - Is there a reason why a second donor is required for the friendly HAFU symbol to display? Seems more logical to warn the pilot via HUD even with a single source (ownship) like successful IFF response from the plane? Is it not like that in the actual Hornet?

With the additional D/L and SA functionality now starting to come through on the F/A-18, I cant help but notice some of the settings in the HMD page relating to Nearest Friendly, Donors, Members being in the list of configurable options. Will we eventually get some of the D/L contacts displayed in the HMD (Assuming those menu options are referring to this)? I can only imagine how much of a help that would be when things get messy to have that extra information in your HMD. Is this actually a feature of the real aircraft, and is it planned to add these capabilities to the HMD?