Leaderboard

I thought the beta patch period is over, and we will get more stable versions? With each new patch we get a new "behavior" of one of the F16 systems, but no instructions on how to use them properly. We are supposed to submit a "bug report" without knowing if it is a bug or a new "feature". How are we supposed to do that if we have to guess whether the current behavior of the F16 is the right one? I don't know right now, is this the right way I'm learning to get the F16 to work, or is this the next new of "1000" workarounds. The last few weeks I have the feeling that with every patch a lot of things become new, and hardly anything works like before. With each patch we have to wait longer for the next fix, and with the fix we get a new "feature" that doesn't always work right, and we have to wait again until the next patch "fixes" it (or adds a new problem/new behavior). I feel like the F16 has a lot of new issues right now (INS, scope, laser code, weapon systems, datalink, etc), and with each patch there are coming more. Actually, I just want to have fun, but ED, you make it really difficult for me to have any fun at all. Fun is currently being replaced by frustration and that really sucks. It's ok if the F16 systems finally work as they should, but do they? I don't know. How so without any actual manual? When will we get the newly revised F16 manual? This manual is the basis for learning things and knowing what is right or wrong. Since the last 4 updates, I have the feeling that changes and how they affect the game are decided by a dice roll (I hope I am wrong). I no longer recognize any system behind all the changes. I'm also beginning to lack the imagination to think that there is still a plan for why things happen the way they do. So what's going on, ED? What is the right doing, to have fun with the F16 again? How long do I have to wait, the F16 is in a good state again? And please, don't ask me what's wrong with the F16 right now. If you want to tell me, there is no big problem with the F16 right now, I will give up in believing in you. Yes, I am frustrated, really frustrated.

Hello Bignewy, thank you for your very detailed reply. I am well aware that you all (the ED team) are working hard to make sure everything runs as smoothly as possible. Unfortunately, lately I have the feeling that some things are going wrong with the planning. For me, the F16 module has never been in such a bad state without major features being added. And in my opinion, there have never been so many different problems at the same time. I can't remember for a long time that the F16 was ever in such a bad state. It's frustrating when what's added or improved isn't even noticeable as an improvement, but makes the F16 much more unplayable. Waypoints drift as soon as I set markpoints and turn them into STPTs. Boresighting no longer works at all. HARMs suddenly fly around wildly. GBUs no longer find their target. Confusing altitude information for cluster munitions. TGP need and "rearm" to work after a rearm, and many more. And what's worse, I don't even know whether this is a bug or whether I'm simply operating the system incorrectly now (because I learned it wrong, since it wasn't implemented correctly before). I just don't know anymore, is it me or is it the game. Please, if at all possible, stop putting in half-finished things into the game that break more than it adds in functionality. That's all I wish.

I wholeheartedly agree with you. We do appreciate all the work going into the F-16. But the current state of the F-16 forced me to park it in the hangar for some time. I am a Viper guy from the very beginning but at this time frustration keeps me from using it which is truly sad. I hope we will see an improvement in the very near future. Be it a quicker rollout of bugfixes between major patches or whatever. The current situation is not okay, though.

Sadly have to agree with OP, The viper is imho the most FUN module to fly in dcs but since last patch ive stopped using my fave all time airframe due to it not being fun anymore, Cmon devs, You guys had the F16 in a very stable and almost finished state before the unified patches came out? For the love of god please stop adding and changing whats not broke... Very frustrating as half of her systems are not fun to use anymore.

Hey @spidierox and repliers. So, with the INS update, you are not required to have GPS right away, so I am not sure where you read you needed GPS Time to be available for that, but now you know. INS can perfectly align itself on it's own if GPS isn't available right away or at all. Now, concerning the GPS initialization, It now takes only 1 minute to perform. When it is available it is then used by the Kalman filter for the proper corrections in aircraft positioning. But one system is independent from the other. Concerning MIDS, the correct procedure is still to turn it on after, and only after, you the "GPS" symbology on the TIME DED page. If you do it before that, the system will not be able to update Datalink information, since it's using incorrect data. I think you are mixing this procedure with INS alignment. Please consider that now we also have a GPS satellite and antenna obscuring simulation. So, if you are, for example, inside an hangar, it is perfectly possible to not have "GPS" on the TIME DED page right away. It's even possible you have no satellites over the horizon, even with the hangar door open, so you'll not be able to get proper GPS Time. That is why it is advisable to only turn on the GPS switch (and later MIDS) when you exit the hangar. Finally, regarding the IFA item, that was a small velocity error being introduced when it was performed, the SPI position was rapidly degrading after it was done. Now it is fixed. In the near future, we plan to release some more information regarding the new INS procedure that will make this all a bit more "interactive". For now, the correct procedures can be found here:

I've said it before. For every update I'm going through all the weapons and radars and updating them. For example, the SM-3 will behave differently in the upcoming USA pack update.

Just a thought experiment: What would drive you to do your work? The money you earn, the fun you get from your job, your sense of duty or rather the fact that your customers are impatient? I personally don't like it, when customers start do get impatient. When they are understanding and friendly, I usually work with more energy and passion.

For those curious on the Morse code heard in that video, it says “coming soon” Characters as I heard them (backslash as character separator) - . - . / - - - / - - / . . / - . / - - . / <pause> / . . . / - - - / - - - / - .

While I mostly agree, judging people with an air of superiority and lack of empathy is the real reason why we can't have nice things. I'm willing to bet if someone dug deep enough, they'd find something you're not so secure about - which is a normal human thing. It might be better to aid a discussion with encouragement and professional explanation rather than shame. Adults are all basically big kids who need therapy and blast it out online (myself included). Our community is tiny enough. Can we at least pretend to get along?

It's a digital plane to fly around in for fun. It's not going to ruin your lives if it releases three months from now instead of TODAY, just because you want to use it. The people like myself who paid for it already got a discount, THAT is the reason to order early.They never gave any contractual promises that you could use the product at a given date. They said "we are hoping it will be released winter '24". I think a lot of people here need to really re-evaluate how they are reacting to what is a complete non-issue, and let the developers just get on with fixing the product so you can enjoy it better when it releases. Which it will, when it's ready. I say all this as a massive fan of the aircraft, but there is honestly far more important things to worry about in the world than when a digital plane gets to be flown.

No you’re right there, they’re totally lying and making stuff up just to mess with you, it’s personal and you should ask for a refund and stop playing DCS entirely

Ein Trailer zur Orbx Kola Map, Morsecode besagt: Comming Soon

That is nonsense. They will release it when they think it's good now and not because people are screaming and crying...

…AND if you take the refund, I think I remember (but am too lazy to check) they will give you two weeks after EA release to buy it again at the same pre-purchase price.

Agreed. I think it bears repeating that HB have offered a refund ('No Questions Asked' I believe) to anyone who is dissatisfied, so if anyone is so uncomfortable with the situation that they want out all they need to do is tell Heatblur. I don't know how that could be fairer.

But doesn't that mean, that the current displayed burst altitude, which is totally wrong as compared to the previous patch, is a bug? why is this a wishlist item now? I agree that the fuzing improvements are a wishlist item. more options etc... But the displayed burst altitude being completely wrong and totally misleading should remain as a bug tbh.

Not sure if you are in the discord but this was our april update April Update Hey everyone! It has been a bit since the last update, but rounding out the first quarter of 2024 we have done quite a bit! We've also added a new member to our modeling and texturing team, @FuriousVoid, and hopefully you have gotten to talk to him a little already. Most of the work done in the last few months is under-the-hood (I know, I know, that is what everyone always says), and most of what Scooby has shown has been our cosmetic changes, but I am more than happy to share what we've developed lately. Texture and Model Work: As we introduce a new modeler to the group, we are working on standardizing all our materials and techniques to get a consistent feel to the aircraft. We have pretty good references to match what things looked like in the 40's, and not just what they look like now. On top of our work in consistency, we are slowly making a pass at all our placeholder models and textures, to put in our final/close to final high quality textures and models. We are striving for a quality of at least the attached Engineer's panel (photo courtesy of Scooby posted on the forum). Debugging: A lot has gone into making our project easier to test and debug. Creation of loggers, automation of internal debug/dev and release/test builds, etc. What this means for our eventual user is that there will be as little overhead as possible when flying. What this means for us is that we can continue to develop more advanced systems, and get accurate measures of our data to compare to the next point... FM Work: Loki has put a ton of work into the FM, like always. We are continually aiming to hit wartime numbers more closely. Importantly in dives, climbs, landings, etc. Drag has been a key issue we have been working on, as getting a realistic drag is crucial to our dives and landings. Our numbers and charts match the reference ones pretty nicely. There's also been work on our representation of the Merlin engine, its supercharger, and props. Autopilot: The meat and potatoes of the Lancaster's Autopilot Mk IV has been implemented. Awaiting are more realistic gyroscope physics, but the basis is there and the autopilot is fully functional. This will prove an important part of the Lancaster's strategic bombing missions. Other systems are of course being constantly fine tuned. Realistic pneumatics to power the brakes and autopilot were implemented, and hydraulics get a new pass every time I look at them and cringe. Fore feedback implementation is also in the near future, and I plan to support FFB in both the yoke, as well as in haptics for 3rd party/diy peripherals, like 3D printed machine gun controls. Development is going pretty great. I am hoping to put together a VR video of bombing procedures sometime in the near future. This will be similar to the bombing video that Loki put out pretty early in our group's history, but will showcase the newest state of our Lancaster. We continue to appreciate the members of the community and their interactions here and on the forum. Please continue to ask questions, post your airshow pictures and cool finds, and chat about our beloved bomber.

Hey, Today, I played with the F16 Viper on a multiplayer server with Skynet. I used the HTS/HAD to locate some targets. My first target was an SA-11, so I selected it on the HAD page. I launched a HARM missile, and the SA-11 went offline. Shortly after, the SA-11 shut down and disappeared from the HAD, along with the cursor. I pressed TMS down, and the cursor reappeared from the old SA-11 position, but I couldn't select anything anymore. Additionally, the TGP slewed to a position somewhere far away (to the coast, I think somewhere near my spawn location). On the TGP, I pressed TMS Down/CZ, and after a few seconds, it slewed back to the original location. This kept happening for the rest of the flight, and I tried to deal with it. I've attached a track; it's a little long but should be okay. I think the way the SA-11 was shut down caused the problem. I believe the HAD didn't like it when the SA-11 disappeared while I still had it selected, and the SPI was constantly resetting to a random position. I hope you can help. This isn't the first time I've run into this problem, and I've tried to explain it as best as I can, but my English skills aren't perfect. Thanks! EDIT: My track has 64 KB but it says I cant upload because 50MB is the limit? I have a drive link, but I understand that you may not be able to open it. Can I send it other ways?

My understanding is that VSN is a team and each aircraft is created by different individuals, so the A-6 has one main developer, the F-4B another, and so on. Seems to me that the vsn developer behind the Mirage has real life commitments that have delayed this project … I don’t believe that the progress reports were meant to be a joke, or to be cruel with the users. These Mods are provided for free, so I’m happy to use whichever one is released and don’t get frustrated with those that are not released yet.

@Tom P, posts that are in violation of the forum rules will get removed. Specifically, if it is in violation of Rule 1.10, meaning it is non-constructive, insulting, or condescending, it will be removed. If feedback is provided in a constructive and mature manner, it will not be removed. Simple as that, and this is nothing new. ______________________________________________ In regards to this entire thread, the flight dynamics team will continue to work on the flight model to ensure it meets the quality that is expected of DCS. We understand the frustration with the lack of progress updates, but the lack of updates is not indicative of a lack of progress or development. The complexity of any simulated flight model of a helicopter cannot be over-stated. These things take time, you will need to be patient. If anyone has anything constructive to add to this conversation, then by all means provide it. But if this thread is simply going to turn into a rage against the development process or the ED staff, it will be promptly moderated and closed.

On one hand they have no experience with DCS, but on the other hand they've been making terrain for a long time and in great quantity. I'm feeling positive about it.

Everyone has the translation wrong. If you take into account the leap year and the angle of the solar eclipse divided by the difference between traditional Morse code tones and that of the modern tempo in the message the correct translation is … “TWOWEEKS”

I agree, too. As i write in my own "CBU 97 Burst Altitude" thread.... The whole CBU 97/105 system is bugged now. Somebody has marked my thread as "solved" but it is not. It was working perfectly before. And now best part of it, they move my problem to "wish list" ...... it was not a wish it worked before, i want it back working.

Coming soon or DCS Coming Soon™ Because those are to very different meanings of coming soon

Same for me. I've been back to flight simulation after many years thanks to VR, a few years ago with Rift CV1. I thought flight simulation was a dead genre that have had its glory back in the 90s, but VR have made me change my mind. It was then that I discovered DCS and I've started to play in VR from the beginning. Since Rift CV1 and a GTX 1070 I've been through Rift S, Reverb G2 and now Quest 3 with a RTX 3080ti. Quality is vastly improved, performance can be adjusted. Now I have a 3440x1440 monitor on which I play other types of game (RPGs mainly), but I can't even think about flying in 2D. I've tried, but I'm not flying, I'm watching a flat cockpit through a tiny window (even a ultrawide screen is tiny if you want to fly). When I play DCS (or other flight simulators) I want mainly to fly, and there's no flying outside VR IMHO. On a flat screen I loose interest, I prefer to play RPGs.

Exaggerate much? Different people have different limits if they have to wait for something, esp. after they paid for it. It's normal and it doesn't matter if it's a digital toy or something really important in life. You'd think different if the delay was 1 year or 2 years. It'd finally get to you too. I appreciate that there are people with less patience - they're the ones that actually push the developers

Just came back to the 16 after a few months long hiatus and i have to agree with all of the above, what on earth happened how did the 16 go from perfectly workable and fun to this......I have a squad mate who just dropped a ton of $ on some new sim stuff and he's planning to return after a long break, i fear once he see's the state of the 16 he's just going to uninstall and go play the other 16 simulator...sad

@Teeps many thanks for the kind words, I'm happy you enjoyed it. Bio wanted to make absolutely sure we do not disclose anything confidential, so we made sure the setups, procedures and the syllabus are as realistic as possible, but left it up to the player to come up with a solution to each problem. However, now I'm working on MIG Killers, an F-4 campaign recreating the first class of Topgun in March 1969. I found many sources about the lessons taught there, and tactics, so I'm sure you'll find it very informative. Oh, and believe it or not, back then, there was an A2G part of the syllabus too Oh, an if you haven't checked my latest video, an improvement is coming re the checklists in the campaign.

Да и волну по шлангу от контакта с разгону пускать было бы здорово. Со всеми вытекающими)

One thing i would add to this discussion, whilst the map has many great features, and the additional high detail buildings will be good for chopper missions, they are lost at 500 knots and altitude. The thing that strikes me most about the map is the repeated tiles for factory units and hotels complex's, and even to the fields for that matter. Would like to see an increase in the variation of these and additional efforts made. often the same tile is next to each other repeatedly. Appreciate early EA, hence why asking if this is something you could factor in. Also as highlighted by another user - the red sea has loads of coral and is visible from the air, esp the Sinai coast and be great if the water textures around the coast could be heavily updated. Tabuk Airfield In Saudi would be really useful for MP missions also.

By definition, "Phantom pain" refers to painful sensation perceived in a part that is not present.

"It's a digital plane to fly around in for fun. It's not going to ruin your lives if it releases three months from now instead of TODAY, just because you want to use it. The people like myself who paid for it already got a discount, THAT is the reason to order early.They never gave any contractual promises that you could use the product at a given date. They said "we are hoping it will be released winter '24". I think a lot of people here need to really re-evaluate how they are reacting to what is a complete non-issue, and let the developers just get on with fixing the product so you can enjoy it better when it releases. Which it will, when it's ready. I say all this as a massive fan of the aircraft, but there is honestly far more important things to worry about in the world than when a digital plane gets to be flown." LOL!! Exactly!!! I still enjoy coming to this thread and seeing how everyone fidgets over it, contemplates it, argues over it's release, complains about it, panics over it, and vents frustration over it like a bunch of teenagers. Sorry guys, but hey....If the shoe fits....... It really floors me when people get so worked up over something that's not (for all intents and purposes) real. It's a genuine testament to the state of our species. Absolutely no ill feelings intended fellas.

While I agree with the Forrestal comment completely I would also welcome a populated deck as a choice. As I am not a developer I can say with impunity that it shouldn't be too difficult to have a standard populated or unpopulated carrier of choice

I'm so excited to announce the complete revamp of my Big Show DCS Spitfire IX Campaign to version 2.0. With the recent updates of the DCS Normandy map, the campaign can finally use historically accurate bases and routes in all of the missions. On top of this, more voice overs were added and the visuals completely redone to bring it up to current standards. All clear? Switches on!

The best option would be a checkbox in the special settings menu to require bore sighting or simple automagic boresight like we have for the cursor on the hornet or ins alignment on the harrier.

First of all, thank you for taking the time for a detailed reply. The thing is not that we do not appreciate the work going into the F-16. It is... It happened in a lot of the recent patches that saw relevant changes for the F-16 that you take the F-16 for a spin after a bigger patch, and something big is broken. You literally do one single ramp start, and something is off. We went for a quick training like we always do, just a short trip to the range, checking if everything works or if things have changed. I usually take LGB, but this time we went with mavs, LGB and JDAM and out of these, only the JDAM worked. After getting the TGP to work, which took quite some time. And that is getting really frustrating, especially since it is no longer called Open Beta. I am not raging and ranting, but in some of the patches, it makes me wondering about how such problems can pass the internal beta test. And I would really appreciate it if we could get a more reliable platform, and things that already work don't get broken two updates later. That being said, I know that the 16 is still early access. But I would appreciate it if there would be more bugfixing (like fixing post- designate CCIP) and less new bugs, especially on features that didn't even see a change. It's not some new feature, or that something behaves different. It is that things completely stop working. And that's just sad.

The DCS: Viper Early Access Manual will be revised in the near future to include a lot of items that have been refined over time. This is a very extensive work to do, that's why it's taking a bit longer than expected. It's also more logical to wait until all major changes are done. Until then, please visit the Viper Mini Updates section linked above for the latest and most accurate procedures.

I understood it as: "govorit radio Moskva". Great effort btw.

thank you for your support, with great pleasure, you right last update there was no changes on FM, TEAM work hard to improve and master the EFM code and numbers to offer better experience and this take time, since we all work on free time Have Fun

Sorry to hear you are frustrated, DCS is complex and there will be issues from time to time, the DCS F-16C is having a lot of work done to it at the moment regarding its systems, like with the INS, we did post some details in the change logs, and we also had a newsletter about the INS changes. Wags will also be adding a video soon to show what has changed in even more detail. Some of the recent changes to the DCS: F-16C are below G effect improvements. Loss of colour, tunnel vision, and black out have been adjusted and all happen over a greater time period. This is most useful AFTER performing a G warmup (4 to 5 G for 90-degrees, and then the same manoeuvre back in the other direction). At 9.3 G and after a G warmup, blackout now occurs at approximately 30 seconds instead of 9.5 seconds. - work in progress. Sound effects will be done later. Added embedded INS+GPS logic based on Kalman filter. - work in progress. F-16C INS+GPS System Overview The navigation system on the DCS: F-16C Viper is a complicated mixture of technical solutions that are intended to supply the avionics with coordinates, velocity, and angles, that are characterised by precision, availability, integrity and autonomy. This is achieved by the cooperative work of the Inertial Navigation System (INS) and Global Positioning System (GPS) whose navigation inputs are processed through a Kalman filter in the Modular Mission Computer (MMC). Let’s discuss each of the components in detail. INS The Inertial Navigation System is an autonomous device that performs dead reckoning of aircraft coordinates by measuring the accelerations and then integrating them twice whilst taking into account the aircraft’s orientation in space. The latter is obtained from the F-16 ring-laser gyros. This type of INS is termed “strapdown” as there are no rotating parts. Basically, INS consists of three accelerometers, each for one orthogonal axis, and three gyros. The main features of INS improvements are: Autonomy, as it doesn’t require any external signals to do dead reckoning. Stability in a short period of time (5-10 minutes). Noticeable error accumulation over longer periods of time based on the physics of dead reckoning. Together with the integration of accelerations (to update speed) and integration of position (to update coordinates), the small errors at the level of accelerations that are introduced by accelerometer noises and imperfect alignment are integrated twice as well. Furthermore, the larger those errors are, the faster they accumulate due to the so-called integral correction of INS, which updates the local Earth gravitational force vector with the coordinates and adds them into the relative angles of the G vector. Another distinctive feature of INS is the Schuler Oscillation with a period of 84.4 minutes. Due to the integral correction algorithm mentioned above, the INS behaves like a pendulum. In ideal circumstances, it stays in equilibrium while the aircraft moves along the Earth. When coordinate errors appear, it displaces the pendulum from the resting point and it starts oscillating. The larger the errors are, the larger the amplitude of the introduced oscillations. That’s why one may notice that INS errors get smaller at a rate of 84.4 minutes once airborne. GPS Global positioning system measures the aircraft position by measuring the signal propagation delay from GPS satellites to the receiver. Satellite orbits are precisely known, the exact positions of the satellites are computed according to an almanack that is transmitted in the same GPS radio signals. That’s why GPS needs a couple of minutes after the cold to start obtaining the almanack. The moments of the signal transmission are also known and are defined by a very precise atomic clock on board the satellite. Thus, in an ideal case, if the GPS signals are propagated through space with the constant speed of light, as they do in a vacuum, the receiver could precisely determine its position by intersecting the surfaces of equidistant radio signal delays from the satellites. You may think of it as spheres with centres located at the satellite’s positions, although it’s a bit more complicated in real life. However, there are two significant factors that prevent us from obtaining the ideal point of the surface intersections; the ionospheric delay and multipath. Both add unknown time to the actual signal propagation time. Multipath happens when the receiver is placed relatively near the ground and the signal may be reflected from ground objects that results in the signal's edges degrading; this is similar to an echo in the mountains where it’s too hard to tell one word from another. When such delays are unexpectedly added by the receiver, the precise navigation solution gets lost and the output coordinate gets noisy. That’s where military GPS signals help to get a better signal resolution by the use of so-called P-codes, and the usage of dual frequency helps to eliminate the unknown ionospheric delay. Integrated solution. Kalman filtering To summarise the above: we have two navigation systems, both of which have flaws: INS accumulates errors over time, GPS is noisy and prone to interference due to natural factors like multipath and ionospheric delay and to enemy jamming and spoofing. Here is the good news! There is a way to avoid these flaws with the Kalman filter. It takes GPS and INS coordinates together with speeds as its input. The Kalman filter is a great algorithm that is able to get the maximum precision even out of measurements far from ideal, and it takes the best aspects from both systems: the stability and autonomy of INS and the precision of GPS to obtain an integrated navigation solution that is both stable and precise. Furthermore, the Kalman filter knows, in terms of mathematical equations, the dynamic properties of the aircraft that is moving through space. If the aircraft is moving, it predicts where the aircraft will be on the next filter step. That’s why it is called recursive and the filter won’t let erroneous GPS signals decrease the precision of the output navigation solution. Moreover, it is able to dynamically change its measurements vs. prediction weights to adjust to a degraded navigation precision of any input. data link: When starting or restarting the aircraft, the MIDS switch must first be set to OFF. Only set to ON after the GPS switch has been set to ON for 60 seconds and the DED TIME page displays GPS SYSTEM. The laser code issue you mention was fixed in a hotfix with some more INS tweaks. DCS 2.9.4.53627 DCS: F-16C Viper by Eagle Dynamics INS loses data if engine shuts down and EPU is triggered laser code set in ME not working Tuning the IFA alignment - IFA with GPS velocity update fix As you can see we are working hard and apologise if these changes, tweaks and updates have felt disruptive. The new patch cycle and one public version was a system that was asked for by many in the public, it is a better system although it may not seem it to some. Open beta users were used to quicker patch cycles, but stable users who used to go months without a patch now get patches much quicker, and everyone gets to play on the same servers, and get all the new additions to DCS at the same time. I do hope once things have settled down with all the changes you feel better about it all, again apologies if the new changes, tweaks, issues and updates have felt disruptive for you.

And what is the point of such a headset if you then decide to lower the res anyways? You put it, as if lowering the res has no negative impact on image quality. What is your dislike of DFR based on?

I run DCS normally, non Admin. I used have it installed in Program Files but that caused an issue with not receiving all parts of an update. I've moved it to its own folder (and drive) since then.

This is gonna be buy on first day!

Можно подумать сейчас в ФАКе только то, что нужно исключительно всем. Судя по тому, что этот вопрос периодически бурно обсуждается с завидным постоянством, то это нужно многим.

Если проц понимает парковки следуй указаниям этой ссылки: https://forum.dcs.world/topic/320824-obsuzhdenie-mnogopotochnosti-mt/?do=findComment&comment=5323284 Если проц старый и парковки не понимает, следуй указаниям из этой ссылки: https://forum.dcs.world/topic/320824-obsuzhdenie-mnogopotochnosti-mt/?do=findComment&comment=5352456 Почему эти ссылки до сих пор не в ФАКе с пометкой "ВАЖНОЕ" я не знаю.

If you're referring to the HB UI issue, then I recommend to read the Delay Announcement again, because nowhere does it say that it broke on first test on most systems. It literally said that it caused a critical issue on a very small number of systems that was detected when mass testing begun: https://store.heatblur.com/blogs/news/of-delays-and-silence

Sorry, but i am understand it correct that you took a working system (which was in 2.9.3) where i can set my BA Altitude correct and also throw CBU 105, break it, and "maybe" in 4 or 6 weeks with next update i will get it back working with a new fuse system? My personal finding, thats not how updates should work guys, why not keeping a working system till the new system is ready