deadpool

The video you linked is one of the reasons why they went on to put AIM120s on the wings to reduce the wing flutter at the expense or wear on the wings superstructure. What we have is: a) what looks like a too slow PID in the FLCS not correcting for oscillations. b) something very weird with the speed instruments on HUD and steam gauge.

I reported the same thing for different effects. ( https://forums.eagle.ru/showthread.php?t=279944 ) You were at 560 kts in reality and that's when this effect is going to happen. you can produce it in level flight when flying wings level AB on clean at sea level even. What is interesting though, is how the speed readouts on both your HUD are wrong as well as your steam gauge .. in the second video it's not responding at all anymore. That's I think the real issue and something I'd like explained. In your case even the analog altimeter gave out .. the HUD one is still working though .. The altimeter later recovered about the time you went from DGFT to NAV mode again. I couldn't see you getting any FLCS error that would indicate problems with the Airprobe either.

the external fuel would quickly be pumped into the internal tanks anyhow.

A viper is supposed to be landed crabbed, NOT like you said decrabbed. Landing decrabbed is only necessary in DCS because they haven't fixed the wheel friction, yet. The fix was essentially posted by a user together with the defect, but it never found its way into the code. Not in over half a year anyways. Please don't learn to fly the plane in a way that it is not supposed to be flown in. The Viper is rated for crosswinds up to 25kts if I remember correctly, and landing in that kind of crosswind with reallife procedures will cause you to lose stabs, parts of the wing, or just die.

Please don't take our words for it, just have a look at the miniupdates thread and look what ED has published for the Viper since it's release. You will reach the conclusion that suspension has already happened october last year. Especially if you look at some very nasty bugs that prevent it from being useful, or have been teacher people wrong behaviour in both A/A and A/G ever since the release. Now as I said if you look at how much was done for the F-16 you will find that 2020 is halfway through and in the first half of the year we got a broken datalink that took months to fix, but no update to targeting pod, maybe some HUD updates for launch zone indications which are guessed anyhow. No idea about HSD. The huge benefit of steerpointcreation and .. no new weapons. So still much to do even for that going easy on the f-16 plan.

My best experience with the f16 radar was a tanker turning from hot to cold. Suddenly the hardlimit of 20nm for cold targets applied for the tanker even though I could see it at 50 or 60 earlier when it was hot.

All good. I was in DGFT for sure. Vertical worked (after taking about 8 seconds of me flying within a distance where I could shoot guns and hit) TMS right didn't work at all. TMS up worked when ridiculously pressing it repeatedly.

Speed HUD: ~ 320 falling to 280kts Speed Steamgauge: ~440kts falling Speed ACMI: ~ 560kts Pitch: -15° Altitude 18000ft Of course got the oscillations .. but I also noticed the discrepancy in shown airspeed. Airspeed / mach indicator is entirely pneumatically (and rated for IFR) and shows indicated airspeed. HUD might have been set to calibrated instead of indicated. Gotta check that. So I thought it might be me being at around mach 1 at this speed, maybe they use different pitot tubes and there is some air pressure drop behind the front wave of air (stabilizer vs. stabilator, etc.) that's just hitting the static port or something .. But it makes no sense .. it should then display higher numbers. And also static port and total pressure are on the same probe assembly in the F-16. Also while the F-16 has two air probes, nose and forward right, afaik speed for both HUD and gauge come from the nose, side is used for sideslip, aoa, etc. Steam speed is slowly dropping and HUD speed is 100kts lower and also drops at a different frequency. Real speed according to Tacview (and otherwise observed aerodynamical behaviour) is close to 580kts where the plane just goes bonkers. Then i thought .. was it icing? It is known to cause wrong low reads on the frontal probe in particular, but I did have the probe heat on and we haven't hit the clouds or anything where I'd expect sudden icing. No FAULT lights were on for the FLCS. The mission is over 2 hours long and it happened at the end, so I will save you guys the track file sadly. What I can provide is tacview on request (or even track file). I did upload this to youtube under this URL: Watch the first few seconds to see HUD and pneumatic steamgauge differ in speed and decelleration behaviour. ---------- If you look at another thread you will see this video: where (according to external view the jet is at 1050km/h ~= 566 kts) and steam gauge and HUD are just showing wrong speed numbers. BR, Deadpool - F-16 Testpilot -

I don't have the feeling that the TMS right mode works at all. Have been flying behind a plane for half a minute in dogfight range and didn't get a lock. The ACM modes are utterly broken. And nobody cares.

At the moment max endurance is above 25000ft at about M0.6 You'll have a fuel flow of 3500 and you will stay up for 3 hours if need be. But how about using aar?

I am sure I read it in Vipers in the Storm: Diary of a Gulf War Fighter Pilot Book by Keith Rosenkranz as well.

In TWS there should be no automatic scale change. Muscle memory tells me to try the range knob on the HOTAS as well. But unsure and can't test right now.

I reported this 8-9 months ago.

Give the joystick a snack to the side and see if the reaction comes instantaneously or not. I feel like there's a 200ms lag in it. Could be some weird PID parameters in the flcs

I agree, but I have to laugh, because there's not really much the F-16 can do really well right now. I think this is the one time where it's actually handy that the bird is so incomplete :-D If you go by that then there should be some kind of signaling on the scoreboard who wrecked their plane while flying it. I'm talking about the Tomcats wrecking their flaps and whatnot and the Hornet guys just binding tape around their g limiter override. Welcome to Airquake where consequences and state of airframe don't matter. I would love it if Moose had something like that. Present you the bill of armaments spent after a sortie as well as tell those guys: "tell you what, that airframe is now unusable for your faction. You wrecked it." All optional of course. But it's the mentality that matters here.

Also the air isn't perfectly homogeneous, yet unless you hit the turbulence of a tanker you will just lay calmly in the air .. always . even though you have tons of crosswind .. gusting .. it's very lifeless at the moment :-(

Not on the open servers then. Good choice! :-)

*smiles out of the F-16 cockpit and slowly shakes his head*

Thank you, AssafB!

It would be good for mainly two things: - Selecting a STPT (ok .. ) - Getting the Bullseye coords of a place Since the whole Bullseye system isn't in .. not for FCR .. not for HSD .. I am not sold, unless it's a combo-deal :-)

While I feel your pain, I hope they don't spend time on this, as it would be pallative care anyways. I hope the current "Tpod" just gets torn off and scrapped quickly and replaced for the real thing. With all that steerpoint changing magic gone for good.

Check your procedures, you might want to run the external tanks empty and keep them as cushions depending on what's sour. Belly landing the F-16 comes to mind.. It does, but the maximum takeoff mass doesn't exceed it. So colloquially: What goes up, you can take down. Immediatly if need be.

I hope this is accepted humor :D

JF17 hast no datalink with any planes other than JF17. The one that's build in is fictional anyhow. According to what I read on the JF17 it is supposed to communicate with an AWACS and that could than do conversion to L16. I'd say wrong forum?

Moose Missile Trainer