Bunny Clark

Unfortunately, no. Myself and several others have tried chasing down a fix, but everything has been a dead end. At this point I suspect it's something only ED can fix.

The monitor you are exporting to is located below your main display in the Windows layout settings?

Sure, here's mine. If you don't find anything obvious you can upload yours and I can take a look at it. Helios Touch.lua

Do you have RIGHT_MFCD and LEFT_MFCD defined in your monitor config?

No, I simply removed those files from the download in the Export Guide, as there is no need to patch them now. If you don't have backups, doing a repair install, or installing any DCS update, will restore them. Or if you need, I can upload the stock files for you.

Because the Hornet had a several year head start for mission builders, compounded by the Viper launching without enough functional systems and weapons to really build out a complex campaign with. In 4 years or so, the Viper should have about any many mission as the Hornet does right now.

Your MFD_cpg_left_init.lua, MFD_cpg_right_init.lua, MFD_plt_left_init.lua, and MFD_plt_right_init.lua files should all be restored to stock without a specific reference to a viewport. Then in your monitor config you need to define LEFT_MFCD and RIGHT_MFCD.

What viewport are you exporting to your monitor? By default, the switching view port - which will show either Pilot or CPG depending on what seat you're in - is exported to LEFT_MFCD and RIGHT_MFCD.

Yup, this is my solution as well in all DCs modules. At night I only look at the displays on my export monitor, and just leave the in-game displays blindingly bright.

My display export guide has been updated. There are still config files to download, those allow mapping the EUFDs, TEDAC, and KU, which have no viewport assigned to them by default, but the download no longer changes the MFDs.

An "S" represents a search radar, you will never get locked up and engaged by a search radar, in most cases you're looking for a number. In TOO you can set your filter to Priority threats ("PRI," in the lower right) and the screen will only show you threats that are tracking you. If you're going Wild Weasel this is a good way to quickly engage a SAM site that's trying to kill you.

It'll be announced as a new module if it happens. I wouldn't hold your breath waiting, you'd likely suffocate.

The problem usually is that when you do an in-game rearm, George tends to get confused about what type of missiles you have loaded. The only way to solve this is to jump into the CPG seat and change the selected missile type to "SAL."

Agreed. And even if there isn't, TGP Boresighting would seem to be favorable anyway, since it's likely to be the most accurate I'm not sure that's true. Range to SPI is a known value, so the boresight corrections should be able to be calculated in 3 dimensions and then extrapolated to minimize parallax errors. My impression has always been that it's not possible to boresight in BORE mode, but it's certainly not clear in the -34. Since BORE doesn't generate a SPI or have any range data associated with it, it would be a lot more difficult.

As per the real manual you can Boresight in either VIS or PRE mode. In PRE you are Boresighting to the TGP, FCR, or a predefined object that is a Steerpoint. In VIS you are Boresighting to the HUD TD Box, so IRL the reference object needs to be visible in the HUD unaided. In any of the above examples you're essentially just Boresighting to the SPI, but the F-16 separates different SPI generating sensors out by delivery mode, like it does for other weapons.

That depends entirely on the terrain. In the desert, sun-baked sand and rocks will get just as hot as sun-baked metal. There's a reason the CCD seeker H and K Mavericks exist.

The new FLIR system is definitely still being worked on and refined, but overall it should look worse. The previous FLIR system was far too clear to be realistic.

IRL, the Maverick is boresighted to the system SPI, however that happens to be generated at the time, and not a specific sensor. This works because the weapons computer knows where the different sensors all point relative to each other and can correct for those errors. The only unknown in the system is the Maverick seeker and exactly how it was loaded onto the launch rail. Once the computer knows the boresight corrections to bring the Maverick seeker in-line with the TGP, it can do it just fine with the HUD, or the FCR, too.

Boresighting should have nothing to do with Mavericks ground stabilizing. The only thing it does is align the Maverick seeker crosshairs with another sensor. Usually this is the TGP, but in VIS mode it is the HUD TD Box. Without boresighting, the missile crosshair will be slightly off from the TD Box location on the HUD, but the missile should still snap to where it thinks the TD Box is and stay there.

In theory, yes. That's basically what the HTS pod in the Viper does, and you can see a version of a top-down situational awareness page populated by real-time emitters on its HAD Page. The Hornet doesn't have an HTS pod, but its RWR system is better integrated with other aircraft systems. It doesn't take that kind of information and combine it with the SA Page though, nor does the Viper do so on its HSD Page. Integrating passive sensors, especially with other networked aircraft, and combining that information on a single unified display is a form of sensor fusion, and that is F-35 stuff.

I'll be updating mine with Helios display patching at some point. I'd like ED to at least fix TEDAC export ghosting first, but I might just implement it anyway and then manually comment out the TEDAC export.

Nope, I just didn't make further steps clear. When I built this profile DCS display exports for the Apache were a hot mess and Helios didn't natively support display patching for the Apache either, so I just did everything manually. Now DCS display exports for the Apache are less dumb, and Helios has native display export support for the Apache, so I could revisit this to add display export support to the Helios profile, but in its current state it does not exist. You can learn all you need to about setting up your display config manually, including the quirks of the Apache that persist, here: Or you can delve into adding display export patching to the Helios profile yourself, which isn't too hard, but will still require some knowledge about how the Apache display exports specifically work.

Monitor exports from DCS will switch depending on what seat you're occupying, but button presses in Helios are still bound to specific buttons in the cockpit. So you'll still need 4 MFDs, and switch back and forth hiding two of them.

I decided to take a look at Mission 4 for you. You need to destroy 4x BM-21 MLRS units in the city, generally around waypoints, and shoot down four L-39s to complete the mission. There is no score variation. You'll either get Results 0 and go back a mission, or get Results 100 and move forward.

You can fly the mission but not accept the results. Once you accept the results from the debrief screen you have completed the mission and moved on in the campaign. It also looks like you're going backwards in the campaign too. DCS campaigns can be set up so that when a mission in failed, you return to the previous mission.