WHOGX5

As I said, time is not correct in cold started F-16s. As I do not use hot start I don't know if it applies to those slots as well. You can simply compare your time in the DED it to the time in the F10 view. Time will be set to zulu but it won't start counting until the aircraft is powered up so the minutes and seconds will be offset by however long it takes for you to power up your aircraft. We even have time synchronization in our community SOP as a mandatory step for all F-16 pilots as everyone's clocks will display a different time and none of them will be correct.

The new setting is perfect! It was okay for me before as I can disable friction for my scroll wheel and scroll my way through a 600 page pdf in 3 seconds. But for others it was an absolute pain to set QNH. Keep it as is please!

Also make sure you're not rearming while aligning as that will rock the aircraft and mess up the entire process.

The time starts at Zulu but the clock doesn't actually start ticking until your aircraft is powered up, that's why it's always delayed. For this reason you need to do a time hack to make sure the indicated time is correct. Afaik this is done in real life as well where wristband watches are synced during the briefing and then the aircraft time is synced when you've stepped.

If the F-16 can carry HARMs and MAVs on stations 4 and 6 in real life, then it should be able to do it in DCS too. Otherwise it's not a realistic simulation. I've never used it myself since I fly realistic missions where fuel is more of a concern, but I still want it since it's an option in real life.

Me and my pals have the same issue every now and then. I don't remember what conclusion we came to as per the cause, but the solution was to simply switch to another STPT, then switch back to the TGT STPT. Give it a try and see if it helps!

Being unable to switch between DGFT and A-A/MRM mode while maintaining lock is empirically incorrect even if you just reference the evidence in this thread. This needs to be fixed.

A good thing to keep in mind is that A-A TACAN can interfere with D/L. I don't know if you know about yardstick, but basically if you have two aircraft tune TACAN channels that are 63 channels apart you can get distance between between the two aircraft. I don't have the scientific explanation for it, but IIRC it's something about the channels doubling in frequency or something. So as you can see in the illustration below for A-A TACAN, channels 1-36 and their respective "sister" channels 63 above are unavailable. If these are tuned it will most likely interfere with D/L. So make sure that the mission you're flying have all A-A TACAN set to 37-63 and 100-126. It doesn't necessarily be the cause of the issue you're having, but it's a good thing to keep in mind.

For the love of god, I wrote an entire post, and then it only sent the pictures. Oh well, I'll recap it in short. First of all, I think you've misunderstood the issue BIGNEWY. The pictures you see above show a locked contact both in NORM and EXP mode. When EXP mode is entered, the contact moves to the center of the display instead of staying in the same location. It's not even inside the radar beam. Also, if I move my cursor over the contact in EXP mode and press TMS UP, it won't select the target. However, if I place the contact in the center of the display while my cursor is elsewhere, then I can select the contact. This is obviously inaccurate. If you need reference materials, here is a video of an early F-16C entering EXP mode (at 5:39): https://youtu.be/Aq5HXTGUHGI?t=339 As you can see, when EXP mode is selected the screen zooms in on the locked contact. If you have no contact selected, then the display will simply zoom in on your cursor. The reason the selected contact/cursor stays in the same location both in and out of EXP mode is so that you always know the contact/cursors position in relation to your radar gimbal limits. If a locked contact is 2 centimeters from the right edge of the display in NORM, then that same contact will be 2 centimeters from the right edge in EXP mode. So if you don't have a contact locked and have your cursor close to it but not on top of it, then the cursors location will be accurate relative to the radar gimbal limits, but the contact will have shifted out of position due to the zoom level.

I think you've misunderstood the DTC since you say it's great for single player but not for multiplayer. If the DTC is properly implemented you will have the same functionality as you do now with baileys times a hundred. Don't get me wrong, I use Baileys as well. But native DTC support would allow for setting pretty much everything you can think of avionics wise unlike now when we pretty much only have preset CMS. And you'd be able to have multiple preset DTC settings and just choose which one to use right before the mission.

Regarding the RWR, it's the same issue we had in the A-10C (don't know if it's fixed yet). The default position of the players view is too far forward. If you move your head backwards towards the headrest, not all the way, but a heads distance from it, you can actually see the RWR quite well. You just have to change the default head position to a more realistic one.

Don't quote me on this, but IIRC the reason the TWS doesn't change scale is that it's not meant to be used until you're committed and melded to a group. It's usually set to 40 miles due to this reason you simply don't need a range longer than 40 miles for regular engagements. If you need to scan wide swathes of airspace further away you should be using RWS. Due to minimum abort ranges you probably will never get closer than 15 miles to a target in a realistic combat scenario so lowering the scale is also not needed. And since you have the EXP mode (even though it's current implementation in DCS is far from perfect) you don't need to reduce the range to see individual targets more clearly. And building on the previous point about the Block 25, back in those days the F-16 only carried sidewinders so having this kind of functionality that is optimized for long range engagements simply wasn't needed.

Had the same earlier today. Very strange behaviour.

The only palpable difference in performance between a Block 40 and Block 50 is that the block 40 has a less powerful F110-GE-100 (125 kN) engine compared to the Block 50's F110-GE-129 (131 kN). Anyone who claims that the Block 40 and Block 50 "isn't nearly the same aircraft" obviously hasn't done too much reading into the different F-16C variants because it is an absolutely ridiculous statement. Do you honestly think every single decision made by ED is correct? They're only human, errors are bound to happen. If everything is correct as is, why even have a bug section? I fully agree. In my opinion it obviously isn't the most pressing issue regarding the DCS F-16 in it's current state, but I think it is one of those small things that defines an in-depth simulator. Having a tonne of these minor features is what makes actually following real life procedures and regulations a worthwhile endeavor. If mistakes don't have consequences, why even bother avoiding them? And like you mention, it wouldn't be too hard to implement, but I agree it's also not a priority.

I just tried this with the SA-2 and I can confirm that RUK doesn't work. HARMs impact the ground exactly where the selected steerpoint is and never acquires the emitter even though it's locked on to me and firing missiles.

No worries. I don't have good source information on what the actual update rate is in the variant that's modeled in DCS. In other commercial F-16 simulations that I've tried though the update rate is arguably worse than it is in DCS. It's not a live feed of information but is rather updated at intervals of a few seconds. It's not meant to be used in stuff like ACM as it's simply not quick nor precise enough. You'll be better off trying to maintain visual instead (even though that's easier said than done in DCS).

This particular issue is not FM related and it has been here since day one. When the FPM goes outside of the HUD it will give incorrect information vertically and this gets exacerbated when banking. Normally how it should work is that if the FPM is outside the HUD and you're in a 5 degree climb, it should be displayed at the edge of the HUD along the 5 degree pitch line which it currently does not. Caging the FPM with the DRIFT C/O switch will center it on your HUD, but indicated pitch angle will still be incorrect and it will display the same faulty pitch angle as it does in the uncaged mode.

What do you mean by refresh rate? The FPS of the display itself or the update rate for data link contacts?

No, that's not how it's supposed to work. It's a bug that was introduced a good few patches back and hasn't been rectified. It only happens if you spawn at night. Every time you change page it will revert the brightness to the default night setting which is way too dim. I don't know why it says a track replay is needed? You literally only have to spawn at night, change brightness, switch page and the brightness will revert back to what you spawned with.

I mean, there should be a good couple of tens of thousand F-16 mechanics worldwide that could answer this question. I don't understand why the burden of proof is always on us when ED has access to proper documentation and SME's? And does anyone here honestly think that a little yellow brick that's not even fixed to the ground can restrain an aircraft capable of producing 131 kN of thrust? It's basic physics; the answer is no. http://www.f-16.net/g3/f-16-photos/album30/aad Here is #90-0718 which is an F-16C block 40 (so at least the same amount of thrust as the F-16 that's modeled in DCS).: "Jumped the chocks during a hot oil servicing run at Eielson AFB, Alaska and slid 400ft sideways across the ramp on hard packed snow. The aircraft ended up in a balancing act on its nose and starboard wing on the ground and port landing gear in the air. The aircraft was fixed, although there was extensive damage. A ground crew member in the cockpit was fine. A few years later, the aircraft ended up in the exact same position after being tipped over by the engine exhaust of a taxiing B-1B."

My most used radio call in the F-16: "Ehhh.... Magic, Viper 2-1, could you ehh.... give us that in BRAA?"

1. Korea 2. Korea 3. Korea If you'd make Korea with a low detail Shandong peninsula, Liaoning peninsula and MCAS Iwakuni I'd be set for life.

Learn the F/A-18C. The F-16 is my favorite fighter jet but in it's current state in DCS it's just not worth it. The F/A-18C has tonnes of more features, receives regular updates and is steadily making its way out of early access. The same cannot be said for the Viper unfortunately.

Yes, this is true for mode for mode 4. There is also Mode 1/2/3 which will reply to whether it has the correct answer or not and will appear on the FCR as a yellow box. This is why mode 1/2/3 is always disabled when nearing hostile airspace. Can be good to know when it gets implemented in the future. Also, in regards to OP's question, currently in the DCS F-16 the only way to get red HAFU's is if you recieve a hostile contact via link from AWACS or something similar.