HereThen

To give the guy some more credits who helped me with this:

It wasn't in the release notes though but I hoped it was fixed as well. To bad

Credits to Hollywood_315 by making, of what I can only assume, a very tough decision. Hope you are doing well!

So I did some more testing. Went back to the release version on both client and server, but wasn't it. Tested local mission and dedicated server, but wasn't it. I noted in the thread posted before that they were focussing on Tacan channels so I went with that. I deleted all my tankers from the mission created by Liberation and voila datalink was back up. After some tweaking it seems any Tacan channel from 4 up to 7 can't be used as either Y or X. The 4th tanker in my mission is the S-3B Tanker and is spawned with Tacan 4Y. Delete it or change the Tacan to at least 8Y and you should be fine.

I have the same. Used to be working for me last week but then I changed some things. (latest open beta and I changed to dedicated server instead of local mission). There is also an issue reported since last July which is under investigation. When I am close to some friendly CAP aircraft they appear on datalink, but they drop like in the video posted in that thread, although those are enemies. How do you play the mission, do you play it from missions, editor or also dedicated?

Things do change on airplanes so maybe the functionality of the china hat has changed as well in all those years and it was never actually wrong in the first place for the model we always flew.

Ordered mine today! Order #5074

ED acknowledged they messed up yesterday by pushing an update that was build the night before without testing before release (there wasn't enough time, testers are not all in house so not always available and 3rd party didn't even have this build to test their module on). If they just stop doing this and delay the patch we wouldn't be here complaining and open beta could still be the preferred platform to fly on. I understand the late night build, I understand that the internal test team is small, I understand they rely on external testers in closed beta's and that they are not always avilible. But please use them and just don't release if not ready! On the other hand (many of) the community should be more patience. Stuff happens in R&D and stuff get delayed. Deal with it. Also, stop this weekly update nonsense. It is not doing anyone any good. Release when ready.

Good to see there's an actual plan now. Let's make this happen! I would also like to see a list of reported bugs / errors that are accepted by ED (locked sticky forum post or something) and that they are being worked on and what has been finished. Looking on a forum for issues already reported (or not) is a pain in the but. Especially when bugs reported many months ago are way down the list but have yet to be resolved! Do you folks at ED have such a list available to share?

If it ain't ready by now, it shouldn't be in tomorrow. Make an internal deadline few (or more) days ahead of release. Whats ready then can be released. Items with small non game braking issues can be considered (maybe with a known issue warning in the notes if it can't be fixed fully for release, otherwise boot it to the next release window). Items that are just not ready or have a game braking features should be booted to the next release window. With such workflow you can let people know by friday in the newsletter what is to be released and you work on a more stable environment for the beta build (and later on the full release). It seems you guys are willing to do everything to deliver us those "promises". Much appreciated, really!!! but it ain't working out (in a development world).

It is becoming harder and harder to defend your way of development to be honest. Viper was released and many Hornet fans were disappointed with the Viper taking the spotlight. The state of the Viper was also questionable at release to say the least. We were told that both addons would be developed together and that both would take advantaged of using similar functions and systems so that would speed up things. Now F16 is abandoned (last few months it already showed 0 real progress) and Hornet is pushed towards (actually over) end 2020 (Viper was also announced to be pushed out of EA end 2020 remember?). At this time, the roadmap has little meaning for me as the past promises were never met. Hope you will prove me wrong this time, that would be a welcome change for once. Good luck with the development and hope to see you back in good health somewhere in 2021!

Like others have said, hard to tell their prioritization from what has been released in updates vs not yet ready to be released. On the other hand, for me, the whole INS alignment and simulation is impotent. If I am correct, a lot of systems on the F16 depend on the INS alignment, so simulating this correctly will have an impact on all those systems. At least, it should be. I know a lot of people here want to skip this whole INS alignment but for me it is an important step of the startup. At this time the plane also forces me to wait so I take the time to plan my mission, brief a wingman, make sure I'm all set before rushing to the runway.

Bring a wingman instead.

Happened to me once and it was because alt hold was set on ground. I have it mapped on the throttle and I didn’t reset it before flight.

https://forums.eagle.ru/showpost.php?p=4143427&postcount=180