Tholozor

George aiming is still WIP:

Only had a brief moment to test it earlier today, but the usual mission I use to check this seems to be fine on MT now.

Already reported: Possible workarounds: - Advance just the power lever of the first engine to FLY by itself, then attempt start of the second engine, or: - Hold the ignition override for the second engine until Ng reaches 52%, then bump the power lever for that engine slightly above IDLE, or: - Start right engine first.

A track replay would help us see what's going on. Did you happen to take off with flaps set to AUTO?

How far away is the object you're using to boresight?

The single-rail launcher was there on release in error. It should have never released with it in the first place.

You can't clear individual threat rings. Only alternative I know of would be to use the REJ modes to declutter the display, but it'll hide all of the rings.

AFAIK Control Measures do not move dynamically, but can be sent/received between 64s over their internal network.

BFT is not planned.

You paid for a U.S. Hornet circa 2005.

The AWACS will make imperial/metric calls depending on their aircraft type. E-3s and E-2s will make calls imperial, A-50s will make calls in metric. Ideally you could appeal to the admins of the server(s) you play on to have one of each type for metric aircraft.

The BIT advisory will display any time a BIT has failed. Open the BIT page and you can see the failed BIT (will be flashing). Press the OSB labeled 'STOP' to acknowledge all failed BITs, and the advisory will be removed. The FPAS advisory will display any time the FPAS cannot calculate the HOME FUEL caution. Fuel calculations become invalid at Mach 0.9 and above, which is the most common cause that trips the advisory. The HOME FUEL caution (not an advisory) will trigger when the calculated fuel remaining at the selected home waypoint is at or below 2000 lbs (this is a separate logic to BINGO). The default home waypoint is always set as waypoint 0. You can set the home waypoint to a closer waypoint to clear the caution (provided the calculated remaining fuel is above 2000 lbs). The HOME FUEL caution should reset with the probe extended, weight on wheels, landing gear cycled up-down-up, or the home waypoint changed (for about 5 seconds until the logic kicks back in to recalculate).

Can confirm, I kept an installer of that specific version just for this.

PPLI and HAFU trackfile indicators are automatically present in the HMD, but the HUD doesn't provide these cues. Flight members will have an alpha character (A, B, C, D), but can only be currently grouped in the editor. On the HMD page, you can change the range and priority of displayed contacts from the MIDS submenu (defaults to 35nmi).

AFAIK the only thing the REL ANG setting does is change the timing of the toss anticipation cue, it shouldn't affect actual release.

Sounds like your download got corrupted, but anyway: The livery you linked is older, and missing some arguments that control how the numbers are displayed (probably made before it was set up that way). Add this to the description to turn off all dynamic numbers: custom_args = { [1000] = 1.0, [1001] = 1.0, [1002] = 1.0, [1003] = 1.0, }

Not implemented.

Are you referring to these? https://www.digitalcombatsimulator.com/en/files/3319542/

That's correct, the Hornet (in U.S. service) is not equipped with a land-based ILS.

If the TADS status is SLAVED on the Helper menu, the front-seat AI will continuously press SLAVE on the right handgrip when the aircraft is shut down. CPG_SLAVE_shutdown.trk

@JZF That video is 4 years old, a lot has changed since then.

You don't need to hold the TDC down when moving the cursor to select a grid square. Just put the cursor over the grid square and depress the TDC once (just make sure the cursor doesn't move afterwards, or it'll remove the selection).

6650 XT user here, the 'Show Models' trick partially worked for me on 23.2.2 on W10. Depending on the complexity of the scenario, it'll either be fine or crash immediately, but it doesn't feel as 'guaranteed' to happen.

That's how it's supposed to work with TrackIR; it doesn't work like you're describing in a multi-monitor setup. The HMD is always locked to the center of your entire FOV. The scenario you're describing would be the equivalent of the HMD following your virtual eyes looking to the right while the head stays center. Moving your head to the right should be moving your entire viewpoint with the HMD at the center. If you have your TIR set to 1:1 head movement, you may want to consider adjusting your TIR curves so that less head movement translates to greater virtual movement.

When you did the NORM alignment, did you ensure to verify the starting Lat/Lon coordinates on the DED with the ENT key on the ICP?