Bunny Clark

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.

On the current Open Beta and Stable builds LEFT_MFCD and RIGHT_MFCD will switch to show either the Pilot's or CPG's screens depending on which seat you are in. The TEDAC ghosting problem has not been fixed yet.

Score is simply an arbitrary number based on the number of units you destroyed. It has nothing to do with campaign progression. Result is a value from 0 to 100 and entirely dependent on the goals set by the mission designer. These should be pretty obviously based on the briefing for the mission, but for real specificity you'd need to open the mission up in the Mission Editor and see what the goals are programmed as. To make things more confusing: Results is listed as Score on the campaign screen. Looks like you've already flown all of those missions. You can only skip a mission you have not flown already in the campaign. Once you've flown through a set of campaign missions you can effetely "skip" to any point in the campaign with the "Fly Again" button.

I always fly with the map enabled on the HSI and SA Pages. But I gain it down significantly. I also have all three displays exported to a touchscreen, so glancing down at it is pretty easy, regardless of my zoom setting.

I'm not sure. I also scrolled through your file and didn't see anything that should cause an issue. DCS identifies profiles by the "name = " field inside the file, not file name. Do you maybe have a name conflict with another monitor config file on your system?

I think either should work, but the DCS World folder is intended for game files, it's where ED's default config files live. You can place your own there and I think it'll work, but they may be moved whenever you do a cleanup of your DCs folder. Placing them in Saved Games is safer.

Yup, that's exactly what I figured. Based on the monitor config you posted in the other thread, you're placing your MFD screens 45 and 800 pixels from the left edge of the rendered space - which means from the left edge of Monitor 2. Change the x values in your monitor config to 1965 and 2720 and you should see them.

Got it. I'm betting the horizontal position is incorrect in your monitor config then. How do you have the touchscreen aligned in Windows? Do you know how many pixels are in between the leftmost edge of your primary display and the leftmost edge of the touchscreen?

Do you have it saved in \Saved Games\DCS\Config\MonitorSetup\ ?

What's your monitor arrangement look like?

Have you read through this guide? To build a export .lua for you, I'd need to know the resolution of your other monitors and their arrangement.

You're defining the viewports for AH64_PLT_LEFT_MFCD and AH64_PLT_RIGHT_MFCD, have you modified the MFCD files to export to those names? If not, then you should be using LEFT_MFCD and RIGHT_MFCD now, those are the default, and since the last update they work great.

Yes, DCS only has a single export display for the KU scratchpad. Yup, unfortunately at the moment only the TEDAC display will turn off when not in the correct seat, everything else will stay on all the time. I don't use the CMWS panel in my layout, so there isn't a good place for it by default. If you want to use it in yours you'll probably want to do some rearranging or hide other panels that you don't want.

SAM and DTT aren't exactly STT locks, they're more like TWS with certain tracks given higher priority. Ultimately, we really don't know how this "should" work. How an RWR classifies and prioritizes threats is not public knowledge. There's more going on than simply analyzing dwell time too, there can be frequency sweep changes in different modes, and the RWR can tell if the threat radar is emitting in HPRF or MPRF too. Exactly how all of this information is used to determine when a pilot gets an elevated warning about a specific threat we can only guess at.

Laser guided bombs don't have a TOO mode, are you sure you're not using a GPS guided weapon? With a JDAM or JSOW in TOO mode, hitting WPDSG will send the WP to the bomb as the target point, and pressing the TDC with the FLIR pod selected will send a new target point to the bomb. Which Raven One mission are you playing?

New version, with a redesign inspired by our new switching MFD export capability. The Pilot EUFD moved to be in the same place as the CPG EUFD, since they will both always render. This is designed to have only one of the EUFDs exported into the window, so you'll only see the EUFD for one seat, regardless of which on you're in. Since the EUFDs don't toggle like the MFDs do right now, this is the only sensible solution I could come up with. Download link is the same as above: https://www.digitalcombatsimulator.com/en/files/3322990/

First post updated with new info following Open Beta Update 2.7.16.28111 in 07/28/2022. We can have MFDs that switch what they show depending on what seat you're in now! But not everything is perfect yet.

Yah, this update did not fix all the issues, but it is progress. My notes so far: By default LEFT_MFCD and RIGHT_MFCD will create auto-switching MFD screens. We can change the MFDs to other viewports and move then around if we want, but if you want four separate viewports all four will render all the time. The TEDAC is still doubled, but will stop rending when you're not in the CPG seat. Both EUFD screens will continue to render, even when you're not in the respective seat.

Yup, this was just fixed with the Open Beta patch yesterday! I'm working on figuring out exactly how the screens work with the new update, make changes to my patch files, and then update this guide.

This is false, there are actually a ton of official liveries in the game that are fictional. Many are even called out in the name as fictional. Just a quick and not-exhaustive list: A-10C: Algerian, Australian, Canadian, Georgian, German, Israeli, Norwegian, Russian, Spanish, Ukrainian, and Greek. F/A-18C: Israeli, Russian, English, Ukrainian. Depending on how you want to define "realistic" there are a bunch of other fictional liveries in DCs as well, such as CAF for the F/A-18C, and a number of F-16 liveries for nations that don't fly the Block 50 F-16C but do fly other versions of the F-16.

The trouble with that approach is that modern fighter aircraft are highly integrated systems. The software update that brought GBU-39 capability to the F-16C added a bunch of other features as well, and from the sounds of it ED does not have sufficient information on all those updates to model them accurately. So you potentially end up with an aircraft carrying a weapon but modeled with software that doesn't support that weapon. Or you model the aircraft with bits and pieces from various software versions and end up with an aircraft that isn't fully accurate to any time period. Neither approach is really right or wrong in a computer game, but ED has chosen to take the approach of picking one time period and modeling that as accurately as possible. I don't fault them for it, as much as I would love SDB in our Viper, their approach provides a far more clearly defined scope and limits feature creep in the project. It's just because making campaigns takes a lot of time, and for a while after launch the Viper had such a limited capability set it wasn't worth it to start writing missions. There are multiple DLC campaigns currently being worked on for the Viper. I started working on a Viper campaign around January of 2021.

Sorry it seems it took a while for people to get around to your actual question. But as we did eventually get to: no, a USAF F-16C circa 2007 does not carry any point-target standoff weapons. The USAF was originally interested in the JSOW-C, but ultimately decided to drop out of the program and only acquire the JSOW-A. It's a somewhat curious situation. It probably has something to do with the F-16C being primarily a SEAD and light strike aircraft, and the USAF preferring other platforms for the standoff precision strike role. The F-15E has carried a number of long range standoff weapons, including the AGM-130 which is closer to the SLAM in capability, and the USAF has a fleet of heavy bombers with very long range standoff cruise missiles to fill that capability. The Navy needs its strike aircraft to be more flexible, so you see the Hornet with a wider variety of available weapons because it's basically the Navy's only strike asset. This was ultimately rectified though. Within a decade of when our Viper is modeled the F-16C gained the GBU-39 SDB, a GPS guided standoff glide weapon, the AGM-158 JASSM, a powered stealthy long range cruise missile, and the AGM-53 StormBreaker, an updated GBU-39 with datalink and an IIR seeker head allowing it to better target moving vehicles.

Unfortunately the ship damage model system in DCS is too simplistic to be able to mission kill ships or take out sensors and weapons. Hopefully someday we'll get that. At 180 feet and 500 tons the Molnya isn't exactly a small ship, but it's not large either. I think it's realistic for one to take multiple Hellfire hits and stay floating, but I agree, it should probably suffer some significant loss to it's fighting capability. Hellfire in the anti-ship role is more intended for Boghammer style fast boats and not corvettes. The heavy-warhead (E, F, G) Mavericks make far better anti-ship weapons, they have a warhead that is three times the weight of the entire Hellfire missile.

I actually kinda wish it was a little more "area" than it is. I spend a lot of time drawing squiggly lines around my target with the helmet sight as I try to aim with TrackIR.

You can reset your default head position in DCS pretty easily. Just move your view to what you want to be the new default and hit RAlt+Num0 In the Hornet I always tilt the view up until the HMD cross aligns with the TVV in normal flight.