WHOGX5

One month of hard work = a half dozen fixes that nobody asked for. Nevermind the bugs that actually ruin the experience and severely lowers the combat effectiveness of the F-16 in DCS. TWS is broken, SAM is broken, EXP is broken, IFF is broken, etc. And that's only avionics. We could also talk about wheel friction, NWS gain, engine performance, G-LOC, etc. But no, chaff/flare audio is what we needed fixed. Oh, woe is me!

Trust me BIGNEWY, of everyone I fly with in my community the answer is unanimous; take your time and get it working correctly from day one. For the last couple of months it has been one step forward and two steps back with each patch for us F-16 pilots. Not getting anything at all rather than something that breaks features that previously worked would be much preferred. We just want more communication. To be honest, I've been getting really fed up with the way the F-16 early access phase has been handled so far, but I will reserve judgement until the 15th and the consecutive patch after that to see if ED really are changing their ways on this issue, which it seems like they are. My hope is all I've got left. :music_whistling:

Any cargo aircraft would be much appreciated, but nothing could beat a C-2/E-2 combo. Would be awesome though to have something like the C-130 which is capable of airdropping both infantry, vehicles and supplies.

We know we'll at least have Palmyra in the east, Adana in the north and Haifa in the south. I just hope the map goes far enough west to include the airbases on Cyprus as well. Would open up for a lot more scenarios.

Minor bug fixes is all I pray for. I can live without new features, I just want the few things we have at the moment to actually work. Especially the D/L and the radar.

I don't know what you do when you fly in DCS, but good luck getting a good trim when you're number 3 in a fingertip formation or joining up with the tanker. I can take my hand of the throttle to use the ICP (which I bound to my numpad) while in formation and I could theoretically use my left hand to trim the aircraft. The issue is, I don't have any physical knobs for trim, and binding it to the keyboard doesn't give you any more precision than the trim hat does. I can't just look down behind me while in formation and drag the knobs with the mouse. It's also not feasible to break formation and go heads down every time I have to trim. The only thing this does, is that flying formation or refueling at a tanker takes a lot more energy than it should. Flying formation in the F-18 is the easiest thing in the world, because you can actually trim the aircraft and only have to make small corrections if you start drifting. In the F-16, you have to make constant corrections just to fly straight, and then you have to make corrections on top of those corrections to stay in position. Maybe it's not as big of an issue if you have a military-grade force sensing stick, but must of us don't and it's a major issue for us. There is zero logic to this statement, and I'm not sure how you came to this conclusion. The issue isn't mental capacity. The issue is turning around to look behind you and find the trim wheels with your mouse. Real pilots with real cockpits can simply use muscle memory. We can't.

I'm not angry that we don't have all the features in the F-16. I'm not angry that development is taking a long time. I'm not angry that the F-18 gets prioritized. I'm angry that the few features we have in the F-16 are broken. Everybody talks about the D/L, but I can cut some slack on that front since it's a big and complex system, even though it's essential to get a fix for it. What I can't understand however, is why all the minor issues that could be fixed in no-time don't get fixed. TMS left and right long registering on release rather than when you push the button. Ridiculous NWS gains that makes taxiing feel like you're riding a unicycle down Mt. Everest. Wheel friction that is so high it makes crosswind landings per F-16 handbook guidelines an impossibility. Target lock not being maintained when switching from A-A mode to Dogfight mode and vice versa. TWS changing radar scale when a lock is lost making a chore to reaquire. EXP mode still not being centered on the cursor, making it effectively useless since you can't see where your cursor is, and therefor can't lock targets without a shot-in-the-dark technique. All of these are quite easily fixable issues and there are more examples in addition to these. Still, they're present for months and months after they're discovered and no progress is being made at all. They can say "reported" for six months on end in the bugs thread, they still don't get fixed. I don't care about new features at this point. Just fix the ones you already have.

Please add the ability to set MP client aircraft to uncontrolled spawn in the mission editor, just like you can with AI aircraft. With this feature we could populate the carrier deck with uncontrolled client aircraft and when a player spawns in he takes control of an already existing aircraft instead of popping into existence out of thin air. This would be a great feature for DCS as a whole, but it'd be especially nice on the new Supercarrier! :thumbup:

To be honest I don't really care anymore about these inaccuracies in regards to thrust, flight model, etc. There are so many avionics issues that just make the day to day flying a PITA and inhibits our ability to effectively perform combat missions. As an example, I reported the fact that long TMS Left activates IFF LOS, not when you press the button, but when you release it. Sounds small, but it makes you have to hold it for a long time just to make sure you hold it long enough. I reported that on November 1st 2019. That's one simple variable that has to be changed, press instead of release. Five months later, still reported, still borked. https://forums.eagle.ru/showthread.php?t=254225 Or that fact that EXP mode zooms and centers the cursor on the screen, instead of centering the screen on the cursor making it effectively useless. That was 28th of November 2019. Four months later, still reported, still borked. https://forums.eagle.ru/showthread.php?t=256177 Both of these issues would probably take ten minutes combined to fix for an experienced programmer. Yet here we are, almost half a year later. No progress whatsoever. It feels like ED prefers a larger amount of broken features rather than a few but really solid ones. Personally I'd do things the other way around.

The letters above the track is the callsign of the locking aircraft, using the first and last letters. So in this case, PC31, SD12 & SD14 would be Pontiac 3-1 as well as Springfield 1-2 and 1-4. These letters and numbers can be changed via the ICP through the D-Link page. As I've mentioned previously in this thread, friendly contacts turn red when they're locked by friendlies. So when someone locks a friend for a rejoin or similar, that friendly will be red until the lock is dropped.

If a friendly soft/hard locks another friendly, the locked friendly will turn hostile on link for everyone, or at least everyone in F-16s. It hasn't been resolved. IFF has always worked however. It's only link that's borked.

I brought this up in a previous thread and it has been reported. https://forums.eagle.ru/showthread.php?t=255434

One thing that wasn't working last time I checked is when you're transmitting while mirroring the DED on the HUD. When you do that the UHF/VHF should increase increase in size when transmitting. AFAIK it doesn't ATM.

IMO the issue isn't how it doesn't track straight, but rather how extremely sensitive the NWS is. Even when taxiing at 15 knots it feels like your going 200 kph down the autobahn on a unicycle. There is no way that's how sensitive it is in real life. Who would design something like that? In it's current state the most difficult part of any takeoff in the F-16 is when you're between 0 and 50 knots when the nosewheel is too sensitive to be of any use at all and the tail fin doesn't have enough airflow to be effective.

Out of all the H-60 variants, I'd choose the HH-60G every time! There's nothing I'd rather do than fly CSAR in crappy weather at night with FLIR and TFR. Yum! :thumbup:

I flew with a friend yesterday, and when he locked the tanker with his radar, it turned hostile on D/L for me. As soon as he broke lock, the tanker HAFU turned friendly again. Seems like it's some issue with the D/L donor stuff. I tried a Mode 4 interrogation while we had the tanker locked and I got the green Mode 4 response, but the HAFU still showed hostile. ¯\_(ツ)_/¯

Remember that the RWR has pretty spotty coverage, and doesn't have any receivers on the top or bottom of the aircraft. So if you're in a bank, you will not get a warning until you start leveling out, or until the enemy is either in front of you or behind you. Also, it depends on how close the launching platform is. If an F-14 is within 5nm it will only take a few seconds for it to launch and subsequently kill you. So without a track where we can see the specifics of the situation, it's hard to determine what could be the cause of this behaviour.

I am unable to record a trackfile at the moment, so I'll explain the issue and hopefully someone can help me by uploading a track, it should only need to be a few seconds long. If I have a target under my cursor on the FCR and zoom in by pressing EXP, the target ends up in the center of the display, rather than under my cursor. Then when I press EXP again it zooms out and the target is under my cursor again. This is incorrect behaviour. When I zoom in, whatever I have under my cursor should still be there, it shouldn't move to the center of my display.

+1

If you look at modern A-A tactics employed by western countries this decision makes sense. According to certain documents the TWS mode should be set before the mission to a certain range and azimuth, so once you commit to engaging a certain group you already have everything setup the way it should be for an engagement. If you're not committing, then you should stick to RWS. This is especially true in the F-16 since we have EXP mode which negates the need to reduce range to distinguish between radar contacts, and also SAM mode which let's us see the same information we would in TWS, even though we're in RWS.

When you press the pinky switch for FOV EXP mode on the FCR, all datalink tracks will disappear off of the FCR for as long as your zoomed in. If you press it again to zoom out, they will all reappear.

If I hover my cursor over a target on the FCR and press the pinky switch for FOV EXP, my cursor will be way off the target. When I press it again to zoom out my cursor will be over the target again.

I've tried to find a single condemning sentence in all my handbooks but there is nothing that explains it beyond the shadow of a doubt. Everything seems to point towards it, but I don't have definite proof. The closest sentence I found was the exact same that you quoted NineLine. One interesting thing though is that in my handbooks I can't find a single picture of the DED in COM Override Mode that has an empty scratchpad, and there is not a single illustration where the scratchpad frequency is the same as the selected frequency. I also found this illustration through google images but I can't for the life of me find it's source, and therefore I can't claim it as definite truth. The illustration does however show the exact behaviour that I tried to explain, which Frederf explained more eloquently than I ever could.

Where my J-35 Draken boys at? We need the AJS-37's brother in arms! Imagine having either the J-35F2 from '67 or the later J-35J from '87. Either of these two options would make me a very happy man! :D

I understand what you mean, but I think you misunderstood what I meant in relation to the quote you posted. In it's current implementation it doesn't select your previous freq/channel you had in the scratchpad. Instead it displays the current freq/channel which makes no sense. Why would I press ENTER to see the freq I'm already on? I have no IRL F-16 experience, but the way it works in other sims I've played this feature allows me to quickly return to my previous channel without having to input anything; just press COM1/COM2 followed by ENTER and you'll be back on your previous frequency. Do the same thing again and it will return to the freq/channel you were originally on. In its current implementation in DCS this isn't possible, as it instead tries to enter my current freq/channel and I just stay on the same freq/channel as before. EDIT: ̶T̶o̶ ̶c̶l̶a̶r̶i̶f̶y̶,̶ ̶w̶h̶e̶n̶ ̶y̶o̶u̶ ̶p̶r̶e̶s̶s̶ ̶C̶O̶M̶1̶/̶C̶O̶M̶2̶ ̶i̶t̶ ̶w̶i̶l̶l̶ ̶a̶l̶r̶e̶a̶d̶y̶ ̶d̶i̶s̶p̶l̶a̶y̶ ̶y̶o̶u̶r̶ ̶c̶u̶r̶r̶e̶n̶t̶ ̶f̶r̶e̶q̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶c̶r̶a̶t̶c̶h̶p̶a̶d̶.̶ ̶P̶r̶e̶s̶s̶i̶n̶g̶ ̶E̶N̶T̶E̶R̶ ̶w̶i̶l̶l̶ ̶r̶e̶p̶l̶a̶c̶e̶ ̶y̶o̶u̶r̶ ̶c̶u̶r̶r̶e̶n̶t̶ ̶f̶r̶e̶q̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ ̶f̶r̶e̶q̶.̶ EDIT 2: I checked again just to be sure I wasn't talking out of my ass, and there was an slight inaccuracy on my part. Actually, when you press COM1/COM2 your scratchpad will show your previous freq by default, not the one you're currently on. So if I switch from 251.0 to 255.0, then the next time I press COM1 my scratchpad will display 251.0 even though I'm on 255.0. If I then press ENTER, the next time I press COM1 I will be on 251.0 and the scratchpad will display 255.0. I'm tired and possibly retarded. I'll be back tomorrow to triple check my claims lol. :music_whistling: