deadpool

Flip this switch: https://i.imgur.com/8U1lsKy.png

Ok, than threads can be merged with for example: https://forums.eagle.ru/showthread.php?t=253449 (October 2019)

And the mirage is the only modern jet out of Early Access. Go figure.

I am really really REALLY bored of this early access argument. The only modern jet fighter in the game that is *NOT* early access is the M2000. If you just declare everything early access and never finish it loses it's value due to inflation. That said, the F-16 was promised to have a seperate team and be finished in 2020, now it most likely won't be on much at all during 2020. Early access or not, I can understand his frustration. But you just have to suck it up and live with it sadly. Or play one of the alternative F-16 sims if you don't mind missing out on all the rest that DCS has to offer. --- Just to clarify: I don't count in the FC3 planes as they lack the simulation depth.

I refuse to press TMS UP short as that is not necessary and a defect that has been reported seperately for many times. Kind of like in the hornet once you are in helmet aquisition mode it is enough to slew the oval over the target and the radar will lock anything inside the oval at a certain maximum distance. If you need to press additional buttons it is a defect, and since I get a lock after what feels like ages still, it is not required!

I recently also learnt that there are coded hard limits, if you are racing with mach 1+ behind another F-16 at mach 1+ you will only be able to see it on radar exactly when it's within 20nm ..

Mavericks might come shortly and ED has said that some things will trickle in throughout 2020 for the Viper, too. But just don't expect it or get your hopes up. See if that what you get works and learn to love it.

I bound it to a knob and I can tell you that trimming this plane is still worse than any other Gen3 or Gen4 plane I have flown. You have more success trimming a F-14, MiG-29 or Su-27. Look down to write down a nine liner and you will start rolling. It's really tedious and I am just waiting for someone to find the LUA settings on how to make the TRIM button things about 0.20x as potent as they are now. So that you can trim the plane like you can trim any other plane in DCS or how you can trim it in any other sim.

Reported earlier here: https://forums.eagle.ru/showthread.php?t=265398&highlight=nav

Additionally the snapshot of the TacView as seen by the RED plane. He also had the missile turn back into me, but also there you can clearly see that his plane was outside 120x120° so the RWR indications were completely wrong and actually misleading: Sadly I will not be able to provide the track file for this and I don't have the time to recreate it cleanly. :-/

Wait a moment? In other threads you are defending broken modules because they are EA and because you got what's on the packaging. And here you are not defending people for expecting the clock speeds that were mentioned on the packaging? Make up your mind, DerHirte.

Sorry, I didn't find any other title for this defect. 2 BLUE vs. 1 RED situation. Here is the sequence of events: Timecode 1) Tacview: Situation: OPFOR locks Deadpool in STT and fires a missile. Then breaks look to lock the second blue plane "Buddy". RWR of Deadpool: This seems to be correct. Timecode 2) Tacview: Situation: Deadpool is notching and missile is not guiding. RWR of Deadpool: This seems to be correct. Now as for things starting to go weird: Maybe 2 seconds after Timecode 2 my RWR starts showing the OPFOR F-16 again, even though I am 180-200 degrees of his axis, effectively meaning his radar can't directly look at me (120x120°). But I am willing to settle for maybe sidelobes here? Timecode 3) Tacview: Situation: After Deadpool turned back in, well outside the 120x120° of OPFOR's F-16 the first RED AIM-120C goes active and turns for him. This is not visible on the server TacView (I have yet to receive the TacView of the red player) but on Deadpool's (mine). Inside Deadpool's plane the RWR now indicated a launch coming from the F-16 off my 12 o'clock (which can't even see me on it's radar physically). RWR: I expected an "M" symbol at my 10 o'clock maybe, or none at all if outside RWR coverage. The spiking and firing 16 symbology is plain out wrong and actually led me to believe that the red F-16 turned back into me. (the barely visible direction indicator on the FCR does help confuse more). So two defects are visible here: Defect 1) Tacview on server and my computer have significant differentes in missile flight paths or even target aquisition. I will follow up with RED OPFOR's side of things as well as soon as I have it. Defect 2) I did not get any indication on the RWR for the active seeker in the missile, but absolutely wrongfully for the launching platform (the OPFOR F-16) that doesn't even physically have the option to do what it supposedly does.

Apologies, yes. Level flight, looking straight ahead of course

The plane is supposed to be trimmed for 1g, yet it noticably pitches up when accelerating.

This is just about radar locks, and the videos in the FA18 weren't from me. I was only interested in the time it took to lock radar, not anything IR related.

No chaff involved. Also an info: Chaff in DCS supposedly does nothing against locking attempts and won't work against aircraft or SAM radar at all. It only has an impact on missiles guiding on you (which is mindboggling and surreal as well)

Thank you for the insight! I have added a bit more material to the post.

Dogfight ACM modes taking a long time to lock I am going to leave a youtube video of DCS footage here and just need a verdict on how realistic the times for the radar to lock up are. 1m11s to 1m46s in this video with other ACM modes: (he was not notching me and distance was 7-8nm) I sadly couldn't find any real world examples of how long it takes, but with the FA18 in DCS it looks like it's going a lot quicker: see at: - 2m00s - 2m18s - 2m39s - 2m43s That guy is locking targets in the FA-18 quicker than it takes me to lock even one in the F-16.

Switching to A3 from A6 with the OSB-Left Button works as expected: - You have a smaller scanning azimuth - You lock a target - Target notches - Lock drops - Azimuth setting stays at A3 Now if you switch from A6 to A3 using the TDC that you slew outside right or left side of the FCR. - You have a smaller scanning azimuth - You lock a target - Target notches - Lock drops - Azimuth setting resets to A6 Will trade track file for when going into and out of DGFT mode doesn't drop lock anymore :D

The earlier F-16s had a data modem installed to exchange information between F-16s. You could see your peer's positions, their targets and assign them stuff / push out AG coords, etc. And the best of it all was that every few seconds you had a nice chirp in your ear. It's symbols looked like what was pasted above.

What's not to be forgotten is the huge gap in between messages: You bought the plane when it was said that the F-16 (and the FA-18 ) were to be out of EA at the end of 2020. Now the narrative is: This holds true for FA-18 but F-16 will only get minor fixes (that I also sadly don't perceive), but more importantly: F-16 features will be started 2021 essentially. That's a year worth of gap that developed "overnight". And I know that my perception of what's going on behind the scenes isn't catching it all and that I am sure some things will trickle down into the F-16 as well over the course of the year. For a plane where loadout and feature decisions were very strongly influenced by the bold statement that it should be the best F-16 simulation on the market (hinting at that other flight sim) I feel very drained. Still, you have to play with the cards you're dealt, so I feel happy for all FA-18 guys and all the others and will just see what the Wednesdays bring for us F-16 pilots. My trust is gone, and you won't get it back. ED can only make it worse by introducing more defects into the F-16 or communicating promises only to break them then. So imho, best would be to not get any more news on the F-16 except for bugfixes. But only once they are done and guaranteed to be in the Wednesday patch. I don't want to get my hopes up every Wednesday and feel that sting over and over again.

I try to see both sides here, obviously something didn't turn out as planned ressource wise or progress wise. I hope everyone learns from that. ED, and those that have some sort of expectations when they buy EA stuff. My main struggle with the F-16 isn't even the long term development and what it gets when and whatnot. It's more the small things about basic usability and the care that goes into how ED deals with this model and updates it, for example that the datalink hasn't been working since what feels like ages - for varying reasons - and that hasn't been fixed adequatly. Instead it breaks in newer ways, which leads me to suspect not much attention / care or some very weird development process going on. It just feels like: "If it breaks, meh .. not that bad". Now with the most recent datalink issue (example included as image) it was said the week of the first occurance: Sorry guys, it was fixed internally already but didn't make it into this Wednesdays release. Yet the fix is also absent from next Wednesday's release. And no word was lost on it. The F-16 will be done when it's done, same with the FA-18. I am appreciating any words from ED on this and roadmaps, but the sad matter of the truth is, that while I don't have a general dislike of ED or anything, I just don't feel like trusting them on the point of schedules or priorities anymore. This isn't trash talking, I have realised that I can live with that. I don't even regret dumping some money into the F-16, but it's healthier for me to just let it slide and not even look at patch notes anymore and have hope to catch a glimpse of love. I am sorry that it came to this point, I believe ED is, too. I believe they are doing their best and that they care. Stay healthy, Deadpool

Absolutely encouraged and great. Love it if it did something good for you. Best greetings to France! Deadpool

Hi if you add .fixedtime. into the filename, it won't touch the time. Otherwise it will set the time to the current time. Though I should check if it messes up due to websites server timezone. Not sure about that one off hand. - Deadpool