bkthunder

I find it *very* strange that in dgft mode the hud doesn't de-clutter as seen in pretty much all variants / tapes of the F-16 throughout the years. I have personally not seen info, anywhere (manuals, videos, specialized forums) about this type of hud behavior where the hud is so cluttered. Mind you, I have never flown an F-16, I'm just passionate about it and have read, watched and listened to anything available about it for the past 25 years or so... I was sure teh current hud behavior was a bug, but I recall ED saying this is true for the very specific tape version and year. So, can we get any info about what tape it is? Thanks

It's still not possible to do a cold start following RL checklists because of bugs and incorrect things. Things that were reported two years ago. That's just the very tip of the iceberg.

So, the F-18 is a lot of fun in a dogfight, however, the DM is totally sub-par. I made a little statistic, and out of 50 times I was hit, 80% of the time somehow the bullets manage to completely destroy either the left or right elevon. The remaining 10% of the time end up in either direct head shots, loss of an entire wing, or loss of engines which instantly disables your gun. I am not talking about a healthy burst of bullets hitting you in a precise spot. I'm talking about as little as one bullet coming from ANY direction and resulting in disproportionate damage. Funny facts: - as little as one bullet can make your elevons disappear - elevons are the first thing damaged even when being hit head-on - a few bullets on the aileron/wingtip can result in total loss of the wing When dogfighting another F-18, I get a lot of kills out of sheer luck. Just spray a few shots around, if one hits, it's a nearly instant kill.

Has there been any development on this?

Aren't the tailerons pitching a bit too much when flying straight? The whole point about the F-16s relaxed stability is so that tailerons stay in a mostly neutral position most of the time, thus reducing drag. Doesn't seem the case here? Some pictures for reference, look for the painted mark on the fuselage, just fwd of the taileron's leading edge:

EDIT: Track attached and more testing EDIT 2: EXCESSIVE PYLON DRAG! All numbers below are referring to an aicraft with no payload but pylons. Tried again withotu pylons and numbers are closer to the charts. Gone is the weird behavior between 43-50k feet. Pylons have no weight (from ME loadout screen) but make a big drag difference! US standard day, 22k lbs, no external loads At 38.000 ft, the aircraft reaches a max speed of M 1.75 after several minutes of veeeery slow acceleration. At 40.000 ft, max speed is still M 1.74-1.75 At 43.000 ft, max speed is still M 1.74-1.75, but at this point a strange behavior manifests itself (see below) Keeping full AB at M 1.75 @ 38.000 feet, I start a slow climb past 40k feet, at around 43.000 feet mach number starts to pick-up quickly up to mach 2.2 as I climb through 45.000k. It holds mach 2.2 up until ~52.000 feet and then suddenly and very quickly IAS drops in the 350s kts and mach drops to 1.6. I descent again to 43.000k (the altitude at which during the climb I attained M 2.2, but the speed now tops at M 1.73-1.75. I redo the procedure and the same behavior shows: slow at 38-43k feet, then sudden acceleration past mach 2, then at 50k sudden deceleration as if the engine lost power. However, If I maintain 43.000 feet and try to accelerate there, I can never achieve more than 1.74-1.75. So it looks like there's some strange zoom-climb behavior or something. For reference: Top speed at 30k feet should be Mach 1.89 Top speed at 38k feet shoudl be just shy of Mach 2.0 Top speed at 40k feet should be Mach 2.00 At 50k feet max speed shuould still be just shy of Mach 2.0 F-16 max mach oddities.trk

Ah thanks guys, I saw "TDC slew" and it was greyed out, didn't know there were multiple commands for it.

Is it still the case and why is it so? Any work around? Thanks

Nice catch!

Ah didn't notice that

The radar search volume is there, all the rest is missing. I hope they add it. The cursor is especially useful for "bumping" the HSD range as you do on the radar page.

I don't wanna sound like an ungrateful a-hole, and I know you're busy and all, but this was "passed to the coders" when it was reported years ago... :music_whistling: Hopefully this is the time it'll actually get sorted! Thanks

So I just picked up the baguette today after a while, and noticed that fuel flow is still only taking into account altitude and not airspeed.. So at high altitude you can go Mach 2 for ages 'cause you're not burning any more fuel than if you were going slower.... This has been around for ages (two years?), and it really isn't very fair when other airplanes are burning realistic amounts... Come on Razbam, fix this stuff, it's pretty fundamental stuff you know?

Exactly my thoughts :(

No, it's because the G-tolerance across the whole sim is far from realistic, and it has been asked a number of times to update it. Everytime someone posts about it, it swiftly gets moved to the "General questions" forum. This is not a wish, it's an issue that DCS has had for a long time, and people really start to notice it thanks to the F-16, which is pretty much handicapped because of this (as is the F-15). https://forums.eagle.ru/showthread.php?t=251891

any news about this in the last update?

That's totally wrong.

You have to press the NSW button and then "find" the position at which the nose wheel was left at, with the rudder, until it re-engages. You can try to: 1. Press NSW button 2. Go full rudder on the side where the wheel is pointing, and slowly recenter the rudder. The wheel shoul dre-engage and you're good to go. But don't rush it and don't ever release the button, lol. IIRC if you let the engine RPM drop too low the NSW will get disconnected also, so keep a little power during the turns.

Any idea when the "DIS TYPE" knob on the RWR panel will become operational? It's one of those little things that I find myself wishing for, more often than not.

Was thinking the same "anti-torch" thing. F-18 depserately needs it when the sun shines on those MFCDs... Please make it happen!

That's great, thanks for the input. Anyway I was not referring to the sustained turn, but instantaneous load (fully aware this is transient and can't be sustained at 440 kts). However, I re-checked the mission file I used and the aircraft had more fuel than I had wanted to set-up (probably a slip of the mouse). Tried again at 22000 lbs GW, and it seems more in line, reaching 8.9 at 440 kts :thumbup: P.S. man, you started your post with "hi everyone" and now I can't get your voice out of my head :D

You're at M 0.76 and 462 Knots... I'll provide a track but please pay attention to the details before labeling something as CANNOT REPRODUCE. Of course you can't if you follow the wrong parameters. Thanks

CAT1 of course, no external loads.

Test conditions: Standard day, GW 20000 lb, no stores. Note: we consider a drag index of 0, because DCS doesn't simulate pylon drag and weight even though pylons are attached to the aircaft MIL POWER ACCELERATION Sea level, acceleration at MIL power, from 200 KIAS to 550 KIAS Real life: 29 seconds DCS: 35 seconds 10.000 feet, acceleration at MIL power, from 200 KIAS to 550 KIAS Real life: 48 seconds DCS: after 1 minute 30 seconds, the aicraft reaches a top speed of 543 KIAS MAX AB ACCELERATION Sea level, acceleration at MAX AB power, from 200 KIAS to 750 KIAS Real life: 25 seconds DCS: 30 seconds 10.000 feet, acceleration at MAX AB power, from 200 KIAS to 750 KIAS Real life: 34 seconds DCS: 47 seconds All tests were performed starting from a speed lower than 200 Kts to allow time for the engine to spool up, I started timing when the speed passed 200 Kts and stopped once it reached the 500, 550 or 750 markpoint according to each test. Track attached in case it's needed. F-16 level acceleration discrepancies.trk

The corner speed for the F-16 is in the range of 330 to 440 kts. At sea level on a standard day, the F-16 should reach 9g at mach 0.67 (right about 440 kts). In DCS, at M 0.67 the jet only pulls a maximum of ~8.7g with full joystick deflection. The g buildup is also pretty slow, an initial pull only reaches 8.2-8.3g before the airpseed starts to be too low to allow pulling maximum g, for this reason (not necessarily a problem/bug), in order to reach 8.7g I have to start the pull above the 440kts, at which point the peak g is 8.7 down to 440kts, where it will start to decrease. I have checked the EM charts available from various sources.