Here are a few quick questions for anyone who has this QW 757. Can I select my own wingview by going to "virtual cockpit" mode and walking back to pick my seat vie Active Camera, the way I can with most models. Or am I limited to the wing views that come with the airplane. And most importantly, would I be able to use the sounds in another model? Or are they limited to this aircraft. From what I have heard the sounds alone would be worth the money

No The format is individual exc Model_VC / Model_WVI know how you feel about that though. It was kind of my main blast to them.They stated it would be a hard hit on the Sim....being the VC is Complex enoughNow I don't own active camera but with DBS Walk & Follow you can set a wing view setting from external.Go Outside the cabin:Then walk into your desired point of view:Then turn around and set:Once in the VC model with one keystroke to initiate again the Walk & Follow, It will be showing the wings(last pic).If active camera has this function, then yes you can still enjoy your.Downside to it, Info display will always be there.

Benz, how bout the sound. Is it a folder you could use on another plane, and do you know if you can open the folder and replace certain sounds with others.

Benz, how bout the sound. Is it a folder you could use on another plane, and do you know if you can open the folder and replace certain sounds with others.

I use it for my CLSB767. Just to hear the Magnificient soundset.I'm Not a spokesperson for QWs, Heck I seldom fly it. I just wanted to clear things up with TORKERMAX with his post. There are bugs but not to that extreme.Sorry for the pics up top Googles server error issue. =(T. Headlam

Are you insinuating I falsely fabricated the list? For what reason i would not know. I have no interest what soever. I shall assure you it is from their support website! Mind you not the GENERAL PUBLIC. IMO were it should be.

He simply meant that one shouldn't take the list you posted that seriously, for the reason that one user will unlikely see even half of these bugs (He won't see all of them, as in "the extreme"). Or at least, that's what I make of the post...

He simply meant that one shouldn't take the list you posted that seriously, for the reason that one user will unlikely see even half of these bugs (He won't see all of them, as in "the extreme"). Or at least, that's what I make of the post...

Jeeze guys don't shoot the messenger!SEVENTEEN (17) of the issues state that QW is aware of the issue and / or it will be addressed in SP1. QW said that THEY ARE AWARE OF THE ISSUE, so obviously this is not being made up. But you guys are advising readers to IGNORE issues of which QW is aware or simply that QWs own list can't be true or is some sought of fabrication? Seriously?I APPLAUD QW for posting the list of known issues, besides, who can point to any add-on release that is bug free and quite frankly this list is not that long or severe compared to others. But what I see is an attempt to ignore the obvious facts for fear of making QW look bad and shoot the messenger for daring to provide such facts. Instead of trying to explain away known bugs being addressed by the developer in an upcoming patch, why not instead admit the obvious and simply point out that its being fixed? Other products have faired FAR WORSE than QWs first attempt.So why should a reader NOT take QWs post so seriously when it is a list of bugs 99% are being addressed in SP1? The responses to the posters list are really simply outlandish and quite frankly smacks of "Fanboyism". How can developers IMPROVE their products when people say things like "this must be an old list" or "don't take it so seriously" when the DEVELOPER THEMSELVES have said they are aware of the problem and are fixing it. If all of these issues don't exist in one form or another why are they being fixed in SP1???Luckily it appears that at least QW IS taking it seriously and fixing the issues even if you guys refuse to believe such issues could possible exist despite what the developer themselves acknowledge. :(

I won't be as diplomatic as Mike nor as thorough as tokermax. My advice is simple, stay away from the QW 757 until the SP is released and then wait for the reviews. For the time being, it is a bug-ridden late-beta-grade product. Rarely has a new release disappointed me as much as this one (and I'm not talking about complexity - I knew it was going to be a lite type of a product before purchasing it).

Jeeze guys don't shoot the messenger!SEVENTEEN (17) of the issues state that QW is aware of the issue and / or it will be addressed in SP1. QW said that THEY ARE AWARE OF THE ISSUE, so obviously this is not being made up. But you guys are advising readers to IGNORE issues of which QW is aware or simply that QWs own list can't be true or is some sought of fabrication? Seriously?

I have to disagree Mike.Doesn't seem like they were shooting the messenger at all.No-one said or implied he was making the list up. What they said was you can't judge the product solely on the list when in their opinions you likely will not even seehalf of the items listed. Therefore you can't take the list by itself that seriously.I agree with them , making a decision on a product based solely on a bug listand nothing else does seem a little unfair. You are only considering the negative. One of course can use whatever criteria they wish to make a buying decision, but thatdoesn't mean everyone else has to follow that lead. Regards.Ernie.

I have to disagree Mike.Doesn't seem like they were shooting the messenger at all.No-one said or implied he was making the list up. What they said was you can't judge the product solely on the list when in their opinions you likely will not even seehalf of the items listed. Therefore you can't take the list by itself that seriously.I agree with them , making a decision on a product based solely on a bug listand nothing else does seem a little unfair. You are only considering the negative. One of course can use whatever criteria they wish to make a buying decision, but thatdoesn't mean everyone else has to follow that lead. Regards.Ernie.

Ernie:Again. If one doesn't OWN a product how are they supposed to decidee if it is the right time to buy a product? If YOU put a list of bugs that YOU will be fixing in SP1 then what is someone supposed to judge a product on besides a list of known problems and word of mouth? ESP? Gut instinct? Tarrot cards? If you have a list of fixes in SP1, then someone has at least one problem and you can't guarantee if a purchaser will have one, two, six or eight of those issues. You can't and neither can the consumer. All the consumer has is word of mouth and issues that have been catalogued. SO far the word of mouth on the QW has been decidedly mixed at best, from hate to love...that is all subjective. What is objective is the current issues which is has to be taken into account and simply not ignored.For instance, if you are going to purchase are car, there is a list of issues and recalls that consumers have had. You can read the reviews, ask current owners (who will give you mixed reviews). You then have to decide are you willing to POSSIBLY have similar issues when you make a purchase. It doesn't mean that you will have the issue or all issues or no issues, it simply means that the issues DO exsist and that is how an educated consumer makes a purchasing decision. Of course the alternative is to pay first and then ask questions later and you have customers who did that and are not happy just like you have customers that purchased and are happy. Again subjective. ALL things are taken into consideration when a purchase is made to state otherwise is like the commercial where the used car salesman tells the potential buyer how great the used car is and when the buyer asks to see the list of issues in the CARFAX the car the salesman tells them that's not important, you don't need a CARFAX.Some say that your aircraft is 'LITE' you say that its 'MEDIUM', some say that one should not waste one's money on your aircraft and some say to buy it now. That is all subjective. The only thing objective IS your list of issues and your list of features, that is absolute and beyound dispute. Your list of features is clearly displayed on your webpage, your list of issues....well not so much. If your own list of issues is somehow inaccurate then why are you fixing them in SP1? The assumption being that if its important enough for YOU to take into consideration in a SP, then isn't it important enough to be noted by a consumer?I don't see how giving weight to your OWN list of issues can possibly be "unfair". Unfair would be to make stuff up that isn't true. If that is the case then negative opinions have to be catagorized as "unfair" too. SO if that's the case it must be fair to only take into account the good things and give no weight to bugs?It's not my fight, its yours. And if you can justify YOUR OWN buglist as unfair then that's fine too. How about Mack's comments NOT to buy your aircraft until SP1 has been released? IS that fair or unfair?

Hi Mike:

Again. If one doesn't OWN a product how are they supposed to decidee if it is the right time to buy a product? If YOU put a list of bugs that YOU will be fixing in SP1 then what is someone supposed to judge a product on besides a list of known problems and word of mouth? ESP? Gut instinct? Tarrot cards?

The big picture Mike , not a narrow view based solely on a bug list.The bug list doesn't tell you what works, does it ? Does it tell you what some people may like about theproduct ?? Does it ?Should we also post a list of everything that works as its supposed too, or as we had designed it ? That list is is going to be a lot larger than the bug list.But such a list would unfairly overstate the products positives would it not ?We put the bug/issues list up to let out customers know we had heard everything they reported.This was a way that they could confirm it, they could see it on the list.But so far what I'm hearing seems to be more an endorsement to in future not to keep such a listfor the customers.So why should another developer who see's this thread do what QW has done ?Seems like the developer would be better off keeping you in the dark as to what exactly theyare going to address in future updates as is per the norm. You won't know if they heard you are not until the first patch comes out, and unless you had followed the product very very closely, you'll pretty much only know what they chose to fix. We chose to do that process differently.

For instance, if you are going to purchase are car, there is a list of issues and recalls that consumers have had. You can read the reviews, ask current owners (who will give you mixed reviews). You then have to decide are you willing to POSSIBLY have similar issues when you make a purchase. It doesn't mean that you will have the issue or all issues or no issues, it simply means that the issues DO exsist and that is how an educated consumer makes a purchasing decision. Of course the alternative is to pay first and then ask questions later and you have customers who did that and are not happy just like you have customers that purchased and are happy. Again subjective.

As pointed out correctly other others, you can't really judge the product solely on the bug listbecause in reality the average customer will likely not see or experience the majority of the items on the list.Because obviously several of the items are related to system configurations, some others are relatedto how a customer uses the product.For example what if Microsoft posted all the bugs reported for Win Vista had, or Win7 ? , it'd be a rather huge list. I don't think it would be fair to assess whether to buy Win7 basedsolely on its bug list.

Some say that your aircraft is 'LITE' you say that its 'MEDIUM', some say that one should not waste one's money on your aircraft and some say to buy it now. That is all subjective. The only thing objective IS your list of issues and your list of features, that is absolute and beyound dispute.

But it isn't absolute, how can it be ? Even reported bugs are subjective ?For instance on the list one item says 'FMC Fonts missing', that's actually one customer, who for some reason did not have a standard windows font installed. Its on the list, but one could argue there's no bug here.Another one is 'Control Column blocking EHSI', is that really a bug ? We put it on this list because the customerwould like that removed so his view isn't blocked. Some might call that one an enhancement request.Or the 'Cold and Dark Cockpit Problems'issue. Such a feature was not designed into the product. Isn't this morean enhancement request ? People said it was a bug because it didn't work. But what is it when it never intended to work that way ?Plus don't we also have to consider the severity of the bug ?, the list does not make such a distinction.For example the 'Decision height' issue. Occurs when scrolling backwards past 0, but really who normallysets their decision height below zero ?Now don't get me wrong, there are several legit issues on the list. But the complete list a far shortof absolute.

I don't see how giving weight to your OWN list of issues can possibly be "unfair". Unfair would be to make stuff up that isn't true.

Giving weight is fine, What we are talking about here is making a decision 'solely' on the issues list and nothing else, that is the unfair part.

How about Mack's comments NOT to buy your aircraft until SP1 has been released? IS that fair or unfair?

Its his opinion, but other opinions differ, as you pointed out. But at least his opinion is based on something more than a list of reported issues.Regards.Ernie.

Hi Ernie:My esteemed friend, I think that we can both be best served if you'd stop cherry picking my posts. The argument has NEVER been that bugs should be the sole reason to purchase or not purchase your product. I've never once said or insinuated such a thing.1) In my first post concerning the matter I clearly stated that your product SHOULDN'T (e.g. should not) be judged solely on bugs and second the list of bugs is rather SHORT compared to others. You chose to totally ignore that, I suggest you read the entire context of my post.2) In my second post I clearly stated that an educated consumer takes into account positive and negative word of mouth AND known issues (aka, bug list), you again chose to ignore that as if I stated that only bug lists matter which I clearly never said. Again, I'm not sure what is being lost in translation but my argument has never been that your product should be judged solely on bugs.3) Nowhere in the list of 'bugs' being fixed in SP1 being missing fonts in the FMC or the yoke blocking the EHSI. Of course these are not bugs which is why they are not being addressed in SP1 (unless you chose to remove the yoke as a courtesy to your users, this is a design decision not a bug). I think that average person knows this.4) You state that nowhere are the positives being listed, just the negatives. Have you not seen the list of features on your webpage? The list of features are the positives of your product for the world to see, and we have come to know that the sounds are spectacular in addition the VC and 3D models look spectacular. I also know that those who like the product see great potential hence the push to make it more "medium" than it is now. Obviously, I know far more positives about your product and AGAIN, have never, NEVER said the list of bugs makes your product better or worse. A list of bugs just is. Certainly PMDG 737 and 747 had a list of bugs a mile long, both products are now must haves post fixes. LDS 767 had many bugs, much more than yours (granted a much more complex simulation) and they too set the standard. If all any of us ever went by was a list of bugs no one would ever buy a MSFS add-on. But that doesn't mean that the list of bugs don't exist, they do becuase they were found OBJECTIVELY by your customers.I think this thread has run its course, but I just want to make sure you are clear on the intent and content of my posts. Your angst is best directed at the person who posted the bug list. My only question was to those who say that you can't take the bug list too seriously...and maybe this is were we shall agree to disagree because I simply beg to differ.Regards,

My esteemed friend, I think that we can both be best served if you'd stop cherry picking my posts. The argument has NEVER been that bugs should be the sole reason to purchase or not purchase your product. I've never once said or insinuated such a thing.

Hi Mike,I think you misunderstood points.I was responding to your point about the 'other' posters (implicitly Ben,and T.Headlam) shooting the 'messenger'.I merely stated that I disagreed with your conclusion and agreed with their positions on the implication of posting thebug list and making a judgement solely on that list. That is indeed what the original poster implied he based hisdecision not to buy it on. Any reference to that from me was staying on that point.

4) You state that nowhere are the positives being listed, just the negatives. Have you not seen the list of features on your webpage?

I think you misunderstood my point again.It was worded in the form of a question.IOW 'what if' we listed all of working features as well to judge it by ? As such that list would assuredly exceed the bug list.And unfairly overstate the products positives.

I think this thread has run its course, but I just want to make sure you are clear on the intent and content of my posts. Your angst is best directed at the person who posted the bug list. My only question was to those who say that you can't take the bug list too seriously...and maybe this is were we shall agree to disagree because I simply beg to differ.

There was no angst here Mike, it Was just an intellectual discussion that's the way I saw it. Sorry if it came across differently.Regards.Ernie.

Mike,I'm not sure where your trying to go with the whole, only listing the positives thing on the website.How would it make sense to bring down something we are selling? I mean, putting up a bug list for the whole world to see or a not included features list doesn't make much sense to me.We're doing our best, this was never meant to be full systems simulation. I get the feeling that everyday that goes by we seem to be getting closer to that though.

...For example the 'Decision height' issue. Occurs when scrolling backwards past 0, but really who normallysets their decision height below zero ?...

Hi Ernie,I just would like to add some info about this item as this is where the point of view of programmers and pilots start to be different... :)It's actually fairly common to set the DH to -20 to suppress the 'approaching minimums' and 'minimums' callouts based on the radio altimeter when doing CAT I and non-precision approaches.For this type of approaches the minimums are all based on the barometric altimeter set on QNH (for DA & MDA) or QFE (for DH & MDH). Using the radio altimeter could give you nuisance callouts at wrong altitudes when the terrain in front of the runway is not perfectly flat and level.This different use of the same instrument/device probably led to the fact the DH problem below 0 wasn't noticed during beta testing.For CAT I and non-precision approaches minimums are set with the amber reference altitude marker on the barometric altimeter (not yet simulated in the QW 757 but put on suggestion list).For what it's worth, I'm happy I purchased the QW757 the day after release. It is very stable, showstoppers have been identified and acknowledged (!) by the developers. (Nice to see some devs that can admit something went wrong... I can sum up a lot of companies not willing to do that)Buying it also allowed me to make some suggestions in the QW forum that will maybe/hopefully be implemented at some stage.Most important bugs will probably be fixed with SP1...I believe this add-on will be the perfect transition plane from the default ones to the hardcore simulations in the future.Regards,Sylvain

Hi Ernie,I just would like to add some info about this item as this is where the point of view of programmers and pilots start to be different... :)It's actually fairly common to set the DH to -20 to suppress the 'approaching minimums' and 'minimums' callouts based on the radio altimeter when doing CAT I and non-precision approaches.

Thanks Sylvain,Learned something new today.Regards.Ernie.