Let’s see, I think Dean has been very clear from the beginning and here there has been no attempt to deceive or cheat anyone, if someone has felt itself offended or insulted at some point it has not been our intention:
Point 1: DCDesigns does not create studio-level aircraft, it has been made very clear from the beginning and has never been implied otherwise. If at any time Dean has said that his goal was to create studio-level aircraft, you are free to rescue and post that statement here.
Point 2: This is MSFS and not DCS: That means that this is a civil aviation simulator and DCS is a military combat simulator, therefore, no weapons system can be incorporated into this simulator because it is not natively prepared for it and it is not up to third party developers to implement it. MSFS is focused on one type of audience and DCS on another. I do not believe that ASOBO’s intentions are to substitute one simulation platform for the other or to embrace the entire simulation market. I think the world is massively huge so that different things can coexist. And, honestly, I don’t see what the problem is, you have two different simulators and you can use the HealthBlur model in DCS with great detail, because that is what DCS is designed for and not MSFS. If the problem is that you cannot use the HealthBlur model in MSFS, perhaps you should make that request to the HealthBlur team and not to us (I feel frustrated by many things with life in general, but I do not discharge that frustration, attacking who it’s not their fault, or I insulting people for free if something is not how i has expected in my head). I believe that any developer is free to develop their products on the platform they want, the decision is up to them, just as you are free to consume that product or not. The streams made to date should have given you a clear idea of whether this product is for you or not and whether you should grab money to acquire it or use it in something else (my advice: if you think buying this product is going to generate such frustration into yourself because is not what you wanted it to be, honestly, don’t buy it for your health). I am not impulsive guy in what regard to consuming products, I previously inform myself of a product and think 100 times first whether to buy it or not.
Point 3: This product is called DCDesings F-14, not HealthBlur F-14. They are two different products and it was not the objective nor the scope of the project to copy, plagiarize or use as reference the awesome HealthBlur model (I am not saying this alone, Dean has stated it before if you go back in the post). They are two different products focused on different audiences, although not for that reason exclusive between them. If someone in themselves has created an expectation that they would see the HealthBlur F14 model faithfully represented in DCDesings model or even the real model, is not our fault, we have neither affirmed nor pretended it. We have simply developed the aircraft using declassified NATOPS F14 as reference. Each and every one of the nearly 1000 pages that make up each NATOPS has been reviewed researching which feature can be implemented or not. What was possible to bring to MSFS has been evaluated and implemented within the possibilities offered by MSFS, no more, no less. There are aspects that are not supported natively and with ingenuity and entire nights without sleep have been successfully implemented with precautions to not cause conflicts with the base game. Other aspects that we would have liked to implement have been discarded at first because, either it is impossible or they do not make sense in a civil simulator. And other aspects of the plane have required certain adaptations to make it compatible with MSFS and its essence, which for the moment is none other than being a civil aviation simulator. To make the panels also for example, the Natops have been taken as a reference but trying to make them functional as far as possible with what MSFS allows. With which, a 100% representation of reality is not possible, but compatibility and functionality on this platform has been sought above all. Honestly, we could have copied the garmins as others have done and yet we have not, since that would have been the easiest way.
However, we are proud of what we have done and I repeat, here nobody has tried to deceive or cheat anyone at any time. And I repeat it again: do not buy this product if you think that it will not provide what you are looking for, or if you think that your expectations or needs as a consumer will not be satisfied. Nor do I think we should regret something or apologize for anything. It has been developed with great enthusiasm and we assume that not everyone will like it (nothing in this life can be liked by 100% of people but we are convinced that the vast majority will like it). And what has been said is that features will be incorporated according to whether the simulator supports them natively. If ASOBO does not have in its scope of its project to implement military-type features for now, neither do DCDesigns. We are not going to swim against the current of a river nor can we work miracles. The SDK is very clear on what we can do and what we cannot. And that is what we have done.