TobiasA

That doesn't solve my problem though.

This will change to TWS, changing to RWS is done by 2x TMS down short with no lock.

I am using DTC, you need to let the mission run in realtime until the dtc upload is finished.

When returning from TWS by double-bumping TMS down, the RWS mode will have its scanning altitude (elevation) stuck until you "bumb" the scan range by moving the cursor to the side. Returning to TWS by TMS right long will regain control over the scan altitude, bumping back to RWS will leave you unable to control elevation. This doesn't happen always, but I have been able to reproduce it in a test mission. After shooting down the last enemy plane (mission is 4 minutes in total), the altitude control is locked to what you had when you exited TWS. I am using an axis to control the elevation. You can see the altitude jumping back to -99/-99 when going back to TWS and coming back to the "old" altitude range when going back to RWS. When bumping to a 60 degree scan volume, I regain control over the radar antenna elevation and I can move the elevation around again. This has been bugging me for a while, and I finally managed to recreate it. I hope the attached track makes it possible to see why and how it happened. It may be the case that it happens when a lock is dropped because the target leaves the scan volume or is destroyed. RWS_no_altitude_control.trk

Post- designate has been buggy for a long time now. It is worse for some bombs (CBU-97) and less bad for others (Mk-84). It also gets worse if you pull out of a dive after designation. They will go anywhere along the bomb fall line. CCRP will work just fine, but CCIP is not usable right now in most cases because the post designate does not work as it should.

First of all, thank you for taking the time for a detailed reply. The thing is not that we do not appreciate the work going into the F-16. It is... It happened in a lot of the recent patches that saw relevant changes for the F-16 that you take the F-16 for a spin after a bigger patch, and something big is broken. You literally do one single ramp start, and something is off. We went for a quick training like we always do, just a short trip to the range, checking if everything works or if things have changed. I usually take LGB, but this time we went with mavs, LGB and JDAM and out of these, only the JDAM worked. After getting the TGP to work, which took quite some time. And that is getting really frustrating, especially since it is no longer called Open Beta. I am not raging and ranting, but in some of the patches, it makes me wondering about how such problems can pass the internal beta test. And I would really appreciate it if we could get a more reliable platform, and things that already work don't get broken two updates later. That being said, I know that the 16 is still early access. But I would appreciate it if there would be more bugfixing (like fixing post- designate CCIP) and less new bugs, especially on features that didn't even see a change. It's not some new feature, or that something behaves different. It is that things completely stop working. And that's just sad.

Strange, I flew several minutes and it remained dark until I enabled master arm., two times. It happened after rearming with the TGP already present and powered. I will try to recreate it.

Plus, it seems to not come back to life until you enable master arm. Which is not correct.

If you rearm with the hardpoint still powered on, the same seems to happen.

Yes, and in some cases, Master Arm has to be on to power on the TGP.

CBU-97 will fall really long in post- designate CCIP, or do not release at all. Edit: This seems to affect other weapons as well, just not as much. CBU-97.trk

Does this apply to normal startup as well?

Do not have the gun cross above 10 degrees on the pitch ladder unless your sink rate is really low. At no point should it ever exceed 13 degrees AOA, especially when carrying HTS, TGP or heavy ordnance on the inner wing hardpoints.

That is probably another bug. I never tried repairing so I haven't tested yet.

Datalink is bugged for a while now. Press LIST, ENTER (EDNLK) on ICP. You will see GPS TIME. Switch it to OFF by pressing "1". Wait a second. Switch it to ON again by pressing "1" one more time. It should work now.

The RWR button "TGT SEP" does not separate the RWR symbols on the RWR: Attached please find a short track with a simple test mission. All icons are still placed on top of each other instead of separating them a little so you can read the numbers. F-16_TgtSep_does_not_separate.trk

It says "investigating". It is fixed when it's available to the customer.

You always get a rough steerpoint from people with boots on the ground. Especially if you have a JTAC, you rarely ever find something out of the blue and decide to engage it.

2x AGM-88, 3x120, 1x9, ECM, fuel tanks, HTS, TGP. But the fuel is pretty much gone, external is empty. However, the two pods pull down the nose, which you counter with aft stick... Probably pushing down the suspension. If this is correct then the manual is wrong.

I had reported this some time ago, it was fixed, but the tail strikes too early (again?). F-16_Tailstrike_too_early.trk See attached track, picture is in the old thread (about the same right now, happens at 14 or something). The manual states >15 degrees AOA for a tailstrike risk, but I am unable to reach 15 degrees AOA while aerobraking, even when the speedbrake is on the 43 degree position (no override to 60). So, trying to aerobrake on 13 degrees AOA is pretty risky.

The problem is that you will get a tailscrape at about 13-14 degrees in DCS which is wrong, it should be 15 with the brakes in landing position.

This. Flying around and looking for targets is mostly a sim thing. DCS doesn't have a lot of OCA strikes, SEAD/DEAD packages with multiple flights and types or Deep Strikes on enemy logistics. And even CAS would have pre-planned target areas.

The F-104 worked well for us. And it is surprising how far the F-16 came, from a light weight fighter with sidewinders to a multirole fighter. Not everything was planned when they designed the plane, but here we are. Just as the 104 did back then. Not without flaws, but it is amazing what we got out of that airframe. Looking back, fitting bombs on it wasn't quite something it was good at, but it was an important step. And not a bad airframe.

It happened when doing exactly that, so that might be a reason for it. We had some people already connected and restarted the server with a different mission.

Given time, it probably does. Not all publicly available information does mention all the capabilities.