DimSim

Could be, but I don't think it was that one. Partly because I don't see that file in my downloaded set. Partly because I thought there were comments about the particular mission segment we're discussing, and no related comments are present. I don't think the mission was a re-creation of Black Hawk down, just had elements from it.

I played a mission or mini campaign a few months ago that had a section inspired by the Black Hawk down car immobilize scene. I can't remember if it was for Huey or Gazelle, but might easily be modified for the Kiowa. That part of the mission was scripted, such that after locating the vehicle, you had to fly along side it until your copilot took the shot, which had some audio effects etc. Was fun, but I can't find the mission right now, perhaps someone else can.

I just noticed this, flew a few Instant Action flights and later checked log book to find zero time logged.

Same here, would be nice to know what happened and if we can rename something to restore them without re-configuring.

I reported this issue in shared Mirror Issue thread. It seems to occur in Multi Threaded (MT) build. Several issues reported around May 2023!

If anyone is handy with the mission editor and likes to make 'living words', with some ships, aircraft, populated airfields, and other activity preferably without heavy use of mods, that would be a great resource to share.

I'm amazed what they fit into the tiny 145GB footprint. The terrain elevation map alone could consume more than that. Yet we need finer elevations for mountain peaks, better valleys and roads cut into mountain sides. We also could use more textures and variety. It's important to understand large land maps that are not flat require large color and elevation imagery data to back them.

At 20 sec into the Flaming Cliffs 2024 announcement video, we see the F5E cockpit. Experts may compare with the present to identify changes.

If not already linked, this video tutorial explains how to enter MGRS coords on the Viper. It is a bit more fiddly than other aircraft, but can be done... DCS F-16C Viper - MGRS Coordinate Tutorial | Never Deal With LAT/LONG AGAIN! | 4K 60 FPS VR! (7 mins) One thing I believe is either incorrect or obsolete is the requirement to pad out the Northing and Easting digits to 10 (5+5). Those are designed to represent precision based on supplied count. As long as they are an even count you should be able to enter 8 (4+4) or 10 (5+5) digits without appending zeros to each part.

There are about 3 different ways to emulate toe brakes with the VKB pedals. I find my method adequate and simple. I think the most common way is with VKBs software and a single modifier button on another device. Then you can switch between analog rudder and analog differential brake behavior with that modifier. But each to their own, if the full independent analog rudder & brake is critical, that is the one major down side of this device. Otherwise, they feel great for choppers, which was my main purpose, and to fit easily under a shared work desk.

I'm trying to follow along with Chuck's guide section 2.6.2, Missile Boresighting for the Maverick. I was under the impression that the goal of BSGT was to align the TGP with the MAV WPN display so pilot was certain the missile was targeting the correct target/location. However it appears to have no effect... I can move the TGP to one location, switch to MAV WPN and lock a target. Pressing BSGT appears to have no effect other than cause the MAV circle indicator on HUD to jump slightly. The TGP box indicator is still not aligned with the circle, nor is the TGP pointing at the same location or moved at all since I moved it. I'm at a loss as to what the exact purpose of bore sighting is and the expected pilot work flow. Perhaps I'm mis reading the display and BSGT is some kind of check, eg. stays highlighted if HUD/TGP target matches MAV target? Or maybe the purpose is to apply the missile target, then switch stations so the goal is to pre-target multiple MAV stations for rapid launches? After playing with bore sighting some more, it does not appear to move the TGP to point toward MAV WPN target, instead usually adjusts the MAV target indicator on HUD to match the TGP tracked location. So it appears to be a calibration type effect. Once the pilot has manually located the same location on both TPG and MAV, and boresighted, moving the TGP points the MAV to the same location. If I intentionally mis-align the two sensors and press BSGT, the MAV will not point to the same location as TGP when panning around.

I just the VKB rudder pedals. I just configured them to produce a button press of 'full left' and 'full right' for differential braking and use joystick paddle (Virple stick) as analog wheel brake. While the digital brakes are not as good as analog, they really do work well enough for WW2 planes and modern jets when needed.

I was thinking of making a similar post... bought F16 years ago on pre-order, hadn't flown it until a some weeks ago. Had been flying F-18, A-10, AV-8B. Initially thought learning the new aircraft was going to be real difficult with heavy text based MFDs and that weird DED panel. Turns out I was wrong. I think this may be the easiest plane to fly and fight in (think ground attack, not win dog fights). Everything pretty much makes sense, with quick and low error access to everything needed. I even like the way each mode retains its last configuration, so AG -> AA -> AG shows what you need without re-configuring. The biggest challenge is landing softly. After slamming planes down on a carrier, it did at first seem like the under carriage was made of glass. Now I'm starting to land gently, think air-force, not navy! Great plane.

I have successfully entered MGRS coords from JTAC on the F16. However I find it more time consuming, fiddly and error prone than on other aircraft with MGRS coordinate support. I find it easier and more flexible (steerpoint limit wise) to enter in Lat, Lon DMS format, mostly due to the physical control interface. I realize our current DCS built-in JTAC only provides MGRS coords for 9 line. My question is: In real life, do JTACs typically provide coords to F16s in MGRS or DMS?

Thanks @Mollerz I haven't tried that. I typically avoid modifying the game or module files. Can that file exist in the saved game folder to override the game, or would any changes be overwritten each patch?

Reading the manual and Chuck's guide, I see there are steerpoints reserved for geographic lines. I wonder if they are ever used to assist with runway headings, or if they are always just used for things like borders and boundaries?

Thank you for the responses. I'll mark as solved. Right mouse drag and Left Shift + Mouse wheel both allow an accelerated movement. For some reason I was only trying Left mouse drag, which can be used for all the other knobs like light and volume controls. I guess it's because that knob also has a pressed state. The key/button binding still seems strange as it remains a 3 step increment, so doesn't seem to suit keys or rotary encoders well.

I'm finding the course knob frustrating to use... If I use mouse wheel, the knob always increments or decrements in single units, so turning 180 degrees or so takes a lot of scrolling and time. If I bind a button to CW, CCW knob rotation, the knob increments in 3 units, so fine tuning is not possible! What I'd expect, and I believe is implemented in other jets, is the knob scroll to accelerate with rapid mouse wheel scrolling and return to single units when scrolling slowly. (Watching someone else on YouTube from a year or more ago, it looked liked this behavior was happening for them.) The heading knob behaves the same way, but I have not been using it so far. Can I configure nice mouse scrolling behavior within DCS F-16?

I'm new to the F16, coming most recently from the AV-8B Harrier. I see the F16 has a classic EHSI down low, and a HSD page on the MFDs. My questions, which are not entirely related to each other, are: Is there any way to display the TACAN position and/or bearing on the HSD? Is there a way to display a course line at steering point on the HSD? It seems strange to have a more modern HSD without those useful bits of info, forcing head down at times. If not present, is this coming in the future or not part of this jet model / block?

Where I'm from, one might say they were reclaiming their backyard that had become overgrown with plants and weeds, nothing more implied. I'd guess same language intent here.

Thanks for the replies. I'm having no trouble with LSS/LST from other laser sources. All issues relate to self-lasing. Reading the OP's post again, his behavior matches mine: 1) Selecting MAV from stores or EHSD cancels TPOD lasing and TPOD HOTAS mode. It also restarts the 30sec count down each time. 2) Selecting TPOD from MFD button or SSS double click de-selects MAV as active weapon. So there is no way to both self lase and uncage fire the MAV. (Unrelated I think, my original issue from earlier post turned out to be that I needed to DESG before MAV can seek laser. Just designating the waypoint near target is fine, and then move the TDC to not be locked was the missing step for that issue. Chuck's guide misses this step and the official manual is almost devoid of information about weapons.) EDIT: It appears all the missions I'm having trouble with arm the player craft with AGM-65E, not the E2/L variant. I'm guessing this is the cause and those missions need to be updated to support self lase?

Having no luck with self lasing LMAVs today. I realize the MAV screen and TPOD screen can't both be visible at the same time. However every time I prepare a target on TPOD and select MAV from stores the laser turns off, TPOD HOTAS mode is canceled and MAV starts a fresh count down from STBY. Once MAV is RDY, the cycle starts again as switching to TPOD deselects MAV weapon! It is impossible to follow the instructions from the video above as the behavior is different in the game. While the TPOD and MAV pages have always conflicted, I don't recall the MAV weapon being deselected like this. Perhaps this is the bug Ramsey mentions?

Similar to the video above, but over on the mainland (Instant action - F15 take off free flight), I'm seeing 45-50fps down low but 120fps (capped 120) a few thousand feet up. I currently have a powerful system that generally performs well.

To help trouble shoot, turn on the control indicators, Ctrl + Enter by default and see what inputs are apparently being sent to the aircraft. Open control configuration and check the axis bindings. Some people have reported that after the last update some devices added new axes that were previously unmapped.

@Ramsay Thanks for your fast and detailed response. I'm not entirely sure what you meant by "You need to create a waypoint/target designation near the desired grid square, if you've already designated a TOO/waypoint you may find the ODU grid selection limited to squares near that point until you either create/designate a new waypoint/target point or erase/zero your existing target point i.e. T1" Perhaps you mean that I need to already have a nearby waypoint selected OR waypoint designated first, then create the new point? I guess it does make sense that currently selected or designated point would be used as reference for a new one rather than the aircraft's current location, to assist building a route, otherwise a pilot may need to overfly a target just to enter coordinates! In my case, the mission had 3 waypoints over a city, very close to the location I needed, however I did not have any of those 3 waypoints selected, instead I was orbiting another waypoint further out. I was using Target points instead of waypoints and repeated the process twice but did not zero or delete the first one.