Bunny Clark

At the moment, it's not possible for DCS to switch which screens are displayed for you based on which seat you are in. Unfortunately, you need to pick if you want to display the Pilot or CPG screens.

Sure, but you can say that about anything, at some point you need to start making priorities. Diverting dev resources away from other projects to make a mod-quality low-fidelity J-11 may not be worth it. Especially if there's a chance for a full-fidelity J-11 in the future.

You don't even need to lock the TGP onto anything. The Maverick IRL will boresight to a SPI generated by any other sensor, and since there's always a SPI somewhere in the Viper, in DCS all you need to do to boresight is point the Maverick, lock something, and hit boresight.

Honestly, the addition of the J-11 by Deka is the most development that's happened to any of the FC3 modules in a decade. These are old modules that are largely abandoned, ED isn't going to do anything with them, and I suspect that Deka has some fairly severe limitations with what the FC3 framework can handle. Some new avionics may be possible, the F-22 mod added MFDs with custom UI and the J-11 is basically a mod. But I suspect that at some point it just isn't worth it trying to work with code that is older than DCS World itself.

Yah, this has always bugged me too. With a hose and drogue system the tanker can't disconnect you, you need to back out yourself when complete.

You're definitely shooting at the very edge of the maximum possible range. The Maverick is not designed to be used at those ranges, and I am highly skeptical that IRL they would be even remotely accurate in Force Correlate mode at that range. DCS doesn't seem to really simulate boresighting with any complexity. So long as you lock anything with the Maverick an hit the Boresight button it'll work, it doesn't even need to be the same object as any other sensor is locked on to.

The US Army didn't begin integrating APKWS on the Apache until 2015, well over a decade after the timeframe of the DCS Apache module.

I am skeptical that the issue is with DCS, when you seem to be the only one having a problem with it... There should be no long presses needed for normal Hellfire engagement. Just a short tap is all you need for each command.

Here's a simple track of the MFDs not turning off following a shutdown. This was done in a hot start mission, but it also happens for me on cold start missions. Exported displays do turn off once the power is off, but the in-cockpit displays stay on. ApacheShutdown.trk

Unfortunately, it's not that simple. Even if you change those lines, the Apache still exports displays to LEFT_MFCD and RIGHT_MFCD in addition to the newly configured viewports. It'll work so long as you don't define LEFT_MFCD and RIGHT_MFCD anywhere in your config, but if you use those viewports for other modules, it'll break the Apache. See: And:

Is it? 742-100 is a pretty dense document, but I can't find anything that details manual scan centering in RWS. Section 011 03 details both manual and bias scan centering for TWS, but is pretty explicit that it is for TWS only. Am I missing something?

To expand a bit on what BN is saying - what you're measuring isn't actually axis deflection, it's control surface deflection. In the F-16, as with other DFCS "fly by wire" aircraft, pilot inputs do not translate directly to control surface movement. The DFCS takes pilot inputs, analyzes them relative to the aircraft's current state - airspeed and AoA in particular - and then commands control surface movements based on a number of different factors. In a DFCS aircraft pulling back on the stick doesn't simply command "elevator up" but rather commands "pitch up" and may result in movement of the stabilators, ailerons, and flaps depending on what state the aircraft is in. This is also why roll commands will move the stabilators, ailerons, flaps, and rudder. So what you're really seeing is just how far back on the stick you need to pull for the DFCS to max deflect the stabilators while parked on the ground. This is also why other people have come up with different numbers - do the same test in the air at different speeds and you'll get different results every time.

You don't technically need to make the edits again. All user-modified files that get cleaned up with the update are moved into a backup folder in your DCS install folder. Just find the files you want to restore and copy them back into your DCS install. (One caution with this, if something in the file was actually changed with the update, restoring the old file will undo that update).

For what it's worth it was also stated on the Fighter Pilot Podcast (forget which episode) that the KC-135 can only provide TACAN yardstick functionality, while the KC-10 and KC-46 can provide bearing and range. It was also mentioned that it's common practice to use radar and D/L to effect the join up, and that TACAN is not normally utilized.

There are more regulations, both American and international, than simply classification. Just because something isn't classified doesn't mean it isn't restricted. And just because something isn't restricted doesn't mean it isn't export controlled. There are documents that are illegal to posses without a security clearance. There are documents that are illegal to possess without the proper authorization. There are documents that are entirely legal to posses in the US but illegal to give to someone outside of the US. Because most of these laws were written when the internet was in its infancy, posting a document online usually counts as exporting it. The different laws and regulations are fairly complex, especially when they involve multiple nations. Because the repercussions can be severe, especially for a non-American company that works with a lot of export-restricted documents, it's understandable that they would want to take a cautious approach to moderation.

"Center" is the viewport that the main game renders in, it is defined in your monitor config file. Assuming you're still using the same monitor config file you posted over in the display export thread, your center viewport appears to be set up correctly. It looks like you have a fairly similar setup to me, other than my upper monitor is 1440x2560, but that shouldn't make a huge difference. Here's my AI config file, try dropping this in \Mods\aircraft\AH-64D\Cockpit\Scripts\AI and see if it works. PrestonAI_page_common.lua

Have you followed the instructions from this post from the 25th? With a vertical monitor setup you don't want to use the method from the first post, it will only work for people with horizontal multi-monitor setups. But the later solution worked for me.

The aircraft also spawns with the master volume at 0, so you shouldn't get blasted by static right away. Be sure to only turn up the volume after the radios are squelched.

Here's an update to this, which now has it's own User Files entry since apparently the max attachment file size limit got reduced here at some point since I last published an update. Changes include: Updated the squelch switches to reflect the new spring-to-center behavior, New MSTR IGN knob with the key in it, Better looking button guard artwork. This includes a new Interface file, as the new squelch switch behavior changed things on the backend. Download everything here: https://www.digitalcombatsimulator.com/en/files/3322990/

Perfect, looks like something made it change back to the default viewport names. This will happen every time DCS updates. You'll need to either manually copy the files back (the Updater will move them to a backup folder in your install directory), or use a mod manager. The post you want for the George AI window is here, if you haven't found it already:

@16th Widowmakr To confirm, if you open \Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\MFD\indicator\MFD_plt_right_init.lua do you see the following at the bottom: try_find_assigned_viewport("AH64_PLT_RIGHT_MFCD")

Well, a repair fixed it. Wonder what I did to screw that up ...

Huh, alright, I'll try a repair and see if I can figure out what's going on.

The TD Box is a square with a dot in the middle. It represents the location of your current target designation - hence "TD Box.” A diamond represents your current steerpoint. Its not uncommon that these are in the same place, and then you'll see both symbols combined.

Cool, I did not know that.