Tholozor

I think he means like this:

@Pribs86 From what I can see in the first post, you have a slew delta in your steerpoint system (evidenced by the 'CZ' option for Cursor Zero on the HSD). Press the CZ option to zero the slew delta.

Depressing the SCS, then bumping it towards the ATTK format within a second (or 0.8s, can't remember which) will command manual IFF interrogation. Alternatively you can enable automatic interrogation from the AZ/EL page with the AUTO INT option in the lower left corner.

Is it similar as to what's been described here?

Also keep your landing gross weight in mind. The maximum field landing weight should be no more than 39,000 pounds.

The texture layout has been changed to the new model, and the entries in the description.lua have also changed.

AFAIK still not planned:

I don't know if the P3D procedures would be any different (also considering it's a Super Hornet v. Legacy Hornet), but you can always check the manual and see if the procedures differ.

I have a thread for part of this over here marked as "investigating":

Waypoint sequences in the Hornet can only hold 15 waypoints. If you add 14, that totals to 15 since the Hornet has a "Waypoint 0" at its starting position.

Since we're on the subject of navaid corrections: Dubai International: - Missing VOR/DME (as far as I can tell it's 108.4 MHz, 21X, callsign either DUB or DXB). Historical satellite imagery shows a VOR/DME station existing as far back as 2007 (should be off the foot of RWY 30R). Al Bateen: - VOR, incorrect NAVAID type. Should be VOR/DME according to charts. Also incorrect DME channel (119), should be 87X (paired to 114.0 MHz). Abu Dhabi: - VOR and DME stations should be co-located at the current DME location (VOR frequency, DME channel, and callsign are correct as far as I can tell). Historical satellite imagery shows no VOR station at its current location where the new control tower was under construction throughout the general time period the Persian Gulf map represents. Ras al Khaimah: - VOR/DME, incorrect callsign. Currently uses the ICAO code ("OMRK"), should be "RAV" according to charts. Lar: - NDB, incorrect callsign. Currently uses the ICAO code ("OISL"), should be "LAR" according to charts. - VOR/DME, missing DME channel. Should be 126X (paired to 117.90 MHz). Sirri Island: - VOR/DME, missing DME channel. Should be 84Y (paired to 113.75 MHz). Qeshm Island: - VOR/DME, missing DME channel. Should be 118X (paired to 117.10 MHz). Shiraz: - TACAN, incorrect callsign. Currently listed as "SYZ1," should be "SYZ" according to charts. Bandar-e-Jask: - VOR/DME, callsign uses the same as Qeshm ("KHM"). Not sure what the correct callsign should be as the charts and the Iranian AIP doesn't list Jask as having a VOR/DME station, and it conflicts with the nearby TACAN on 110X.

The developers have purposefully coded the tankers to use ground-type TACAN instead of aerial TACAN:

AFAIK, the seeker on the P5 has some of the all-aspect capability from the 9L and some of the IRCCM capability from the 9M, so imo it's kind of a half'n'half between those two. That aside, you should be testing the same missile against the same aircraft to test if the AI have something benefitting them under the hood, because this looks normal to me considering the 14's much larger heat signature over the F-5.

If you still have a trackfile designated as L&S, press RSET on the lower-right side of the ATTK format to remove it.

There's a reported topic regarding flare effectiveness/flare rejection of air-to-air IR-guided missiles:

I wouldn't recommend putting custom liveries into the core installation. Saved Games is better for file management.

No worries, the report didn't have anything to do with the fact that the right DDI is primary for the ATTK page. I just checked it again now and the erroneous behavior I was trying to report appears to have already been resolved at some point (I believe it had something to do with the initial implementation of Bump Acquisition), so it can be considered fixed.

Did you try Cursor Zero?

Already reported:

Which terrain? Some maps don't have the proper charts set for certain scales. No map should be displayed above the 40nmi scale, so that part is correct.

Pre-Programmed missions would be part of the data cartridge functionality (MUMI).

The A-10 and F-16 both use a similar SPI logic, the Hornet does not. In the 18, the FLIR pod must be the driving source of the TGT designation (denoted by a 'FLIR' mnemonic in the HUD), primarily through SCENE or AUTO tracking modes.

The Maverick can slave to the SPI in the system, but it can't move the SPI unless you're using VIS mode where you have a "pseudo-SPI" to slave the seeker based on where the aircraft is pointed. In PRE mode, the Maverick slaves to the SPI (which is basically the same location as the steerpoint, provided the slew deltas are Cursor Zeroed). If you're starting the aircraft cold and dark, the Maverick seekers needs to be boresighted as well so that they're aligned properly (not required for a hot start).

According to ↓this↓ thread, the 9E has all the coding in place, and they're just waiting for the 3D model for it to be implemented.