markom

As a suggestion, this should've gone into the known issues. I had my hopes really up for MT, but this is a show-stopper :-(.

That may be true, but 0 has mostly worked for me to get "close enough" to the area where I need to be, and then just manually adjust the actual targeting.

I think the default in mission editor is some 6000 ft for waypoints. Unless you set that to the ground level, you've made a WP in the air. In Hornet, waypoints are 3D. In the air, you can edit WPs coordinates (including altitude) from the UFC. In HSI, tap on DATA and edit there.

Apparently, the only viable solution is to find a human wingman. For those of us who dislike that as an option, there isn't much joy in DCS AI...

Ah, indeed, one could use VOR-NDB style approaches. D'oh. Even GPS ones with some careful planning of waypoints.

Silly question - how do you use ILS in Hornet? I thought it worked only with carriers, not land-based ILS?

Ooof, hit you right in the feels that one. So sorry.

Photoshop does wonders

IFA *is* the switch you want it in if GPS is available.

Toldya they'd be your friends. They are, sadly, a necessity for those of us with WW peripherals.

Oh no, that part is OK. Look at the physical device - it doesn't implement this "compression", nor does it expand to two digits. It simply skips one digit. Input: 8989898989 DCS: 8 [98] 9898989 WW: 8 89898989 Note that the "98" is not the only "compression" done on the UFC. It happens with many wide numbers. Helios solved this problem with the following mapping: https://github.com/HeliosVirtualCockpit/Helios/blob/master/Helios/Gauges/FA-18C/UFC/UFC.cs#L36-L37. They use a custom font that has special characters that map to the compressed-like glyphs. On the physical UFC, WW would either need to replace the screen, or implement a firmware change to address the compression in the 2nd leftmost alphanumeric spot. In the attached image, they'd need to implement the "compression" in the spot #1. They already knew about this for the number "20" in #2 and #3, but compression in #1 is what they seem to have missed. At least for some of the combinations. I have tried the one I was confident they've missed. Spot to the left of #1 may also need it, but I have not encountered a situation where it's used, yet.

Restart your combat and t/o panels and try again. By restart, I mean power-cycle. This will be your friend: https://www.amazon.com/gp/product/B07G8CMR18

Thanks for the cable observation. I'm glad I didn't order them, then. I currently use the setup with 3x Cougars on two 11" screens. Side cables make this possible. That said, cable from behind, as WW has done is needed for a side-by-side assembly with the UFC, so I understand their engineering decision there. It's wonderful we have multiple options to address our needs, isn't it!

Thanks. This is really not a show-stopper for me to use it. UFC is great.

Could one of you fine folks with the new UFC try and reproduce this behavior? WW wants to have remote access to my machine to help me resolve the issue, and I don't believe this is the issue with my computer or setup, rather the incomplete implementation (of otherwise phenomenal product) on their end.

This is an issue almost identical to the one I reported some time ago to Helios and their software-only UFC, here: https://github.com/HeliosVirtualCockpit/Helios/issues/605 Steps to reproduce: In F/A-18, on either one of the "MFD"s (use left or bottom, because process in the plane takes over right at one point): Select HSI Choose waypoint using up or down arrows Press DATA (top-right) Select PRECISE (bottom) Press UFC (top-left) Press GRID on the UFC On the right MFCD, select a two letter grid using TDC On the UFC, enter a long (10-digit) grid coordinate. The result is shown on the attached images. Opening this for the visibility here, but I started a support chat as well.

You do know you don't have to order the minute the orders are open, right? You could, you know... do it later?

Doing a "launch" the way they obviously wanted to do is incredibly challenging technically. The website load and the user behavior patterns are wildly different than expected... And predicted load is, as a rule, at least 10x less than observed. They'll learn for next time.

Very detailed, thank you!

That means that 40% of the functionality isn't there. Would you care enumerating those 40%? Having never flown a real Hornet, I can't really tell, but I am curious, since it appears you have insight.

Also:

It sounds to me like you are seeing this:

I finally found the will to turn off the burble and give it a try... I got _OK_ LSO score on the first try. I usually get... a lot less from the paddles. While it feels like cheating a little bit, I am also inclined to keep it off to increase the entertainment value of my gaming time.

For me that's usually a sign that I am overdue for the tanker stop. I believe this happens when you empty external tanks. You can either isolate them, or drop them if refueling is not an option. Also, pretty sure NATOPS says something about this, but... haven't read it yet.