Bunny Clark

In the Hornet, the T/O Trim button only works when on the ground (for normal flight modes). But, why would you want to reset in flight anyway? The reason for a reset button at all is to setup the aircraft in a known stable position for a safe transition between rolling and flying. Once the plane is flying, neutral trim is all relative. The in-flight equivalent to resetting the trim is just trimming the aircraft. Trimming an airplane is a normal procedure that every pilot learns very early, it's a common enough procedure to have a dedicated control on the stick in nearly every modern aircraft, though the Hornet's FCS means you need to trim it far less than some other aircraft.

Thanks to @SparrowHawk003 for pointing me in the right direction. Looks like Razbam not only stealth enabled display exporting in the last OB patch, but also has default display definitions for most of the displays in the aircraft. Like the Apache, display exports switch on and off when entering and exiting the two seats, and the seats can share viewports in your monitor config. Here's the default viewport assignments: Front Seat "LEFT_MFCD", "CENTER_MFCD", "RIGHT_MFCD", "UFC". Back Seat "OUTER_LEFT_MFCD", "LEFT_MFCD", "RIGHT_MFCD", "OUTER_RIGHT_MFCD", "UFC". If you'd like to change any of the viewport assignments, you can find the MFD files in \Mods\aircraft\F-15E\Cockpit\Bake\MFDG and the UFC files in \Mods\aircraft\F-15E\Cockpit\UFC\Indicator I've not found the file for the Engine Monitor Display.

Yes. They're an issue in DCS because of how the rendering engine handles display brightness vs ambient illumination. Dimming the in-game displays also dims the exported displays, but the displays rendered in-cockpit are also corrected for ambient light level and dynamic range. In daylight with MFDs set to max brightness the in-game and exported displays both look fine. At night, turn down the display brightness enough to be legible in-game and exported displays are basically invisible. Turn the brightness up enough for the exported displays to be legible and the in-game displays are completely blown out.

You MFD brightness issues are probably related to the in-game MFD brightness settings. In your screenshot it looks like it's a bit dark outside, so the in-game MFD brightness was probably turned down. That also makes the exported displays darker. If the instant action mission you loaded was daytime and MFD brightness was at max, that would explain the exports getting brighter.

Looks like your game is rendering a much wider area than your monitor, and the CENTER_MFCD viewport is being drawn off the edge of your second monitor. Check the resolution defined in your game settings, and that it matches the resolution in your monitor config file. Also check where CENTER_MFCD is defined in your monitor config file.

It wasn't mentioned anywhere in the patch notes, but pilot MFDs are exporting now. They are rendering to the standard LEFT_MFCD, RIGHT_MFCD, and CENTER_MFCD viewports. The F-15E is not using the standard file structure for MFD exporting, and I have not been able to find where viewports are defined in the module.

My understanding is that INST Mode is intended as an emergency reference mode for when the pilot becomes spatially disoriented and needs one-button access to orientation and navigation instruments. It's a safety feature more than something that is normally used.

Apart from the fact that weapon systems are a bit more complicated to integrate than bolting the missile to the plane, there's the whole other issue of training and TTP. Successfully performing a SEAD mission is a bit more complicated than pointing a HARM in the right direction and pressing a button. If F-15E crews never trained on the SEAD mission, and the USAF still had operational F-16C squadrons that specialize in that mission, why would they ever bother strapping a HARM to a Strike Eagle? Let the Viper drivers do what they've trained for, while the Strike Eagle pilots focus on the missions they train for. The idea that every plane and every pilot must be able to do every mission is very much a DCSism and is not how real life works, except sorta with the Hornet, as it's often the only strike fighter in a carrier group.

If you believe Dassault, that's what "omnirole" means ...

The upper CFT stations are not wired for data. They can physically carry JDAMs, but they cannot employ them. The max GBU-38 load is three per fuselage rack, one on centerline, and one on each wing pylon for nine total.

You can create a overfly mark point in the Hornet by hitting the "MK" button on the HSI or SA Page without a target designation.

The hard line between rendering and not rendering is a DCS limitation. IRL, you still won't get a useful image out of it at 40nm, but it would look like a blurry / pixilated mess rather than just cutting off entirely.

That functionality is included within the DTC functions that is on the roadmap. A few of them we sorta have already. The threat circles you see on the HSD, for example, are representative of Steerpoints 56-70, they are just auto-populated right now.