TobiasA

The real F-16 FLCS tries to roll around the velocity vector. You can see this in some videos, but I can't find the manual right now. Think it was somewhere in NASA paper 1538, but I am not sure. This is intentional. The F-16 should roll around the FPM.

You die in like 95% of all cases unless something small like a MANPADS hits you. But historically, the pilot rather often survived.

Apart from the AP not engaging: If you have AP enabled but a stick input greater than 0, the plane will move in that direction. So zero deadzone will always drift somewhere.

A stick input on its own should not disable AP.

It is not. In the F-16, you can actually move the stick to quite some amount and even temporarily override the AP. When you let go, it will resume the AP. Conditions to disable the pitch switch (see HAF F-16 manual 1-135 and following, publically available but never than 1980 so I am not allowed to post it here): AIR REFUEL switch - OPEN. ALT FLAPS switch - EXTEND (below 400 knots). A/P FAIL PFL occurs. AOA greater than 15 degrees. DBU - Engaged. LG handle - DN. Low speed warning tone sounds. MPO switch - OVRD. STBY GAIN PFL occurs. TRIM/AP DISC switch - DISC. Additionally, it will disable the AP if you roll over 60 degrees bank angle, but the manual isn't clear there. Which is exactly the way the DCS Viper behaves if you leave the dead zones at the default values. See track attached. The paddle will temporarily disable the autopilot while held, resuming with the parameters it had when releasing it (just moving the stick will have the AP returning to the values it had before moving the stick). Even Wags is not correct in his video. But the implementation is correct, according to publically available documentation. See attached track with me moving the stick with the autopilot enabled- you will even see the stick moving if you look closely. AP stays enabled until I command a full roll, disabling the pitch switch by exceeding the bank angle. This behaviour is correct imho. Unsure about if it disables the AP when you lower the gear though. However, the criteria for disabling the autopilot without the FLCS dead zones seems to be wrong. If you leave everything at default, it works as it should. It does on my end, and I did not touch the deadzones- I am on the FLCS defaults. There is no need for special settings regarding the autopilot. PLEASE don't adapt other airframe's logic to the F-16, it is pretty unique in that point as it was one of the first airplanes with a FLCS. AP test.trk

Honestly I don't think that there are many people in the closed beta that at least cold-start the F-16 or take it on multiplayer events. Quite frequently we had bugs that multiple people in our squad discovered on the first ride after a patch. But yes, you might be right there. Good point.

Known bug, gonna be fixed in some future patch (hopefully).

There is no beta and stable version anymore, stable and beta became one some patches ago. So technically the stable version is the open beta, and vice versa. Which one is which is up to you. But imho, bug fixes > new features.

Keep in mind that the english manual is usually somewhat up-to-date while the other languages lag behind, so it might be worth a look into the english manual if your first language isn't English.

Fear not, because both Orbx and Reflected simulations deliver products in a working state. And they put a lot of effort into it, with a serious love for detail and immersion. Pretty sure there is a bigger F-16 patch incoming, since there has been quite some activity in the bug section and even the three threads about the forgotten radar modes got merged and some TWS issues got labeled as "reported". So the bugfixes might comes as a pair with the campaign.

Bug is still present in September update.

However, I won't complain any further. I criticized the things I didn't like, and it is up to you what to do with it. Overall, I appreciate DCS too much for being negative in total. There are more modules than the 16, and some day, even this one will be finished. Have a nice day everyone.

My frustration is not caused by slow progress or something. It is things like the may update (?) that would have been pretty nice if it had not broken the radar mode memory, which might be fixed in the September patch (hopefully) which is five months. And the radar worked fine before. After a few months somebody asked for a track even though this was the third time it appeared on the forum in the bug section. Why do I even write these? Otherwise, I appreciate the work going into the sandbox DCS and the progress to logistics and such. It's just the 16 that is frustrating from time to time.

The Viper is easier in terms of avionics. Almost never requires you to take your hands off the HOTAS, I mostly use the mouse to switch AG weapons if necessary and toggle the light switch. Efficient, intuitive, bubble canopy, 9G, one of the best accelerations you can imagine (especially if you unload). But: The Viper is more difficult to fly right. In terms of air refuelling it is one of the hardest planes to master, especially at night. Easy to put into PIO for unexperienced pilots. If you want to land a hornet, just keep it straight until it touches the ground. Slam it onto that tarmac like there is no tomorrow. Don't be gentle, it's rental. If you do that with a Viper, you might break the gear. You have to flare it. You also have to flare it to be able to aerobrake, especially with HTS and TGP equipped- once the nose is down, it will stay down, and it doesn't have the brakes of a Viggen. Refuelling the hornet is not as easy as the M-2000C (which is a rocket on rails) but it comes close. Landing on a boat is difficult compared to landing on an airbase, but the hornet got tons of helpers and assistance and a beep here and a warning there and if you don't hit the bridge or the aft of the ship, it should do. A crosswind landing in bad weather in the Viper can be harder than landing on a boat- not only that you have to correct for wind, flare, and then get the nose straight on the runway while holding 12° AOA, you also have to sacrifice a part of your already poor braking performance to counter the crosswind force pushing your nose into the wind while slipping around on the wet runway. Also, the Viper doesn't have the insane nose authority of a Hornet. But I'd pick the Viper any day over the Hornet, because it is extremely satisfying to fly, a joy at low altitude, and an absolute beast when it comes to SEAD / DEAD. Depends on what you like. I never really got into the hornet, because I never understood the user interface. It is fun to fly, but I got lost in MFD screens and in thousands of menus without hitting the way back to where I have been. The A-10 is logical, the F-16 is logical, the F-18 is logical for people that started with it. Who don't know the joy of popping through three different presets with 6 MFD pages each by DMS right / left and the override switch, never leaving the HOTAS between engaging a SAM with HARMs and launching a 120 on an enemy MiG-29 just seconds later.

I have locked up and shot down Kh-58 fired by a Frogfoot. So... Yes, it is possible.

Tbh there haven't been many bugfixes on the Viper recently, and annoying things as not remembering the last radar mode that was broken several updates ago remain open for quite a long time.

It seems the modeled blast damage to some amount now. Didn't have a single failed drop yet, they used to be more like 75% prior to the last few patches.

As far as I know, yes. And anyone can induce TDOA but it's best if the lead does it for the sake of avoiding chaos. The other members get the TDOA indication and everyone has PGM1 on that contact after some time if it worked.

You need to point at the same threat as the one who initiated TDOA, as the HTS pod doesn't have 360 degree coverage. Follow the arrow in the HUD next to the TDOA indication.

There are some threads about this, so I guess one doesn't need a track.

As of 2.9.6 it remembers some scan settings, but still not TWS / RWS.

It happens with any mode change.

What about selecting a threat on the HSD as a steerpoint, as those are stored as steerpoints? What about a DTC? And the option to draw lines and custom text and threats in that DTC that help you with keeping border, for example? Will these ever come then?

When you select TWS in MRM override, the radar defaults back to RWS when cycling the OVRD switch. After a mode change, it will always fall back to RWS, the current mode isn't stored. Each submode should remember its radar setting. Steps to reproduce: Select MRM with the override switch, select TWS with TMS right long, cancel override, enter MRM override again. Radar will default to RWS.

Do one in post-designate CCIP with a little crosswind. As for CCRP, it is similar. If you deviate from 1G after pickle, it will most probably miss. I am not anywhere near the computer unfortunately. But it actually happens very often.