Come on, people....a few observations. Some of these points essentially repeat:
1. Developers can and do make mistakes and/or release things when they feel they are "close enough". This can be proven through such things as the issuance of patches, whether initiated through the developer, or though a wide amount of constructive criticism.
2. I'm sure we all appreciate new aircraft releases, whether or not they're payware or freeware. On that note, I don't care if something is freeware, payware, or if the dev has an "outstanding" reputation either way. If something is wrong, they should be told about it, and the developer (and their supporters) should not act indignant when the facts are presented. This also relates to this strange mindset on various forums that "freeware (and some payware) developers can do no wrong or do not make mistakes!". (I have actually heard the argument used in one case that developer XYZ does not make mistakes in their addons..when a realism issue popped up.)
3. Let those who know, help those who don't. Sometimes, those who know didn't make the aircraft, or have the opportunity to test for those who don't. As people have said, we are here to help each other, and developers of aircraft should be open to that help if a flaw is pointed out!
The following is really what I have issue with lately:
4. Related to the quality of work of any/all addons: We absolutely must not rest on our laurels! I've seen posters here and elsewhere say, when confronted with criticism, that the end-user should simply be happy that the product was made, and that because someone put effort into it, that's all that counts. If we didn't continue to push ourselves for ever higher standards of excellence, we would still be using a sim and addons with the capabilities of a decade ago, if not more so. Yes, there is a line of critique that may not be appropriate for the time...this includes rivet counting in the *literal* sense.
However, if some are pushing for accurate systems, sounds, or a flight model, which should be well within the capabilities of a developer willing to put in effort (unless the info is classified or something) why is that an argument to be rejected? Every addon maker out there...freeware/payware...whatever is capable of producing products to the highest standards of today's "known companies with high standards", such as one that recently created a 737.
5. Criticism must be tactful. Unfortunately, some seem to think that any criticism is uncalled for.
What I look for if I voice a complaint is the following: 1. What the problem is. 2. What the real world aircraft/scenery location/whatever is like in reality, with examples to support that. 3. Advice on how to accomplish this goal, or compromise to get closer to that goal of realism or a fix in general.
6. Developers should do their best to push themselves to make the most realistic adaptations of aircraft/scenery possible! If something comes up leading to the lack of implementation of a feature, especially if it is wanted or expected, then maybe a note saying "this is what we aimed for and accomplished, this is what could not be accomplished for x, y, z reasons. Maybe someone can help?"
Regarding this Sukhoi specifically, I have yet to purchase due to the facts presented. These are:
1. It apparently does not sound accurate at all. (Allegedly not even a radial engine sound)
2. The flight model is not nearly close enough. Now, we know that the FS engine can't do much with aerobatic physics anyway, but this issue sounds like it goes beyond that.
3. It *does* look good. Exterior modelling seems to be fine.
4. Summary...nice picture with no substance.
Issue 1 can be fixed with proper research and implementation.
Issue 2 can be addressed to a closer extent. We all know it can't be perfect due to the aerobatic nature, but it sounds like it can closer.
Non-issue 3...haven't heard a bad thing about the looks!
All in all....
Criticism of any product, freeware or payware, should be allowed. The key here is presenting it with evidence, and not simply saying, "X aspect of this addon sucks!". Instead "X aspect is inaccurate and could be better...here's why".
No developer is so good that they are beyond needing help, making mistakes, etc.
No end-user is entitled to get everything that they ask for in an addon, BUT, the developer should be willing to push themselves to the best of their abilities, rather than relying on the "if it ain't broke, don't fix it" development mentality. If it can't be done/implemented, it can't...but bringing up a neat aspect that *may* be able to be isn't a bad thing.
Yes, expectations are high, but developers should be willing to work with that and raise the bar. "OK, we can't put in dynamically moving fuzzy-dice, but we'll put in X for you instead, how about that?"
I don't think anyone here is expecting an aircraft to be the end-all, be-all of simulator addons. We're looking for realism that's practical and able to be implemented, not the ability to run our virtual fingers across individual modeled fibers in a cloth seat or something.
Developers: It's not what you can do, it's what you could do. Push yourselves to try new things. Lead the pack with the quality of your addons. Put realism at the forefront!
End-Users: Be tactful when addressing issues. Push, but don't bully developers into excelling further and outputting their very best!