Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

142 Excellent

About Noble.

  • Rank

Profile Information

  • Gender
  • Location
    Oxford, UK

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Come on Kyle, you're not expecting people to read things properly now are you? :lol:
  2. No, I'm not really. Obviously there's a lower bound on what you would sell a product for and rather complex market models are used frequently to determine the price in order to maximise sales. You get to a certain point where reducing the cost only increases sales by a negligible amount - I didn't really think I had to explain I understand that in my post as it's rather obvious. You have a point in regards to the workload for support, but isn't part of the point of this product to try and encourage more people to move over to DX10, and to get developers to support DX10 properly even though it's a niche market within an already niche market? $34 doesn't help in that aspect, and nor will it encourage developers to properly support DX10, because why waste time supporting it if sales are only going to increase marginally and you overall make a loss? At $34 you've priced out the people using DX9 who have no interest in using DX10 (majority of the market) and so DX10 will just remain a niche within a niche.
  3. Chances are, if he sold it for $17 instead of $34 he'd have made a lot more money, so "devalue the man's skills and time" - not really.
  4. Whether a product is worth the price and whether or not it should be that price are two different things.
  5. Not to mention developers won't get on board and support DX10 properly if people have to spend an additional $34 to get it to work properly.
  6. I agree. At $34 people aren't going to just 'try it out' - which is what is needed for DX10 to become properly supported.
  7. There's a line in the EULA which says something along the lines of "No modifications can be made with the exception of liveries" - I'm not on my FS PC at the moment so can't give you the exact wording.
  8. Even if PMDG finished the 747 V2 in the next couple of months, it wouldn't really make much business sense releasing it so soon after the 777.
  9. I wasn't arguing that 10% is insignificant, I was just arguing that these HD textures will affect a small minority of simmers who now won't purchase V2. Obviously it difficult to quantitatively say - it could be 1%, 5%, 10%, who knows? Ultimately though it will lose PMDG money (even at the 1% level they're going to lose thousands of dollars) which is entirely why they stop this kind of activity in the EULA.
  10. PMDG employs 20 full-time people and have their own offices - not really something you can maintain for the two years of 777 production if $50,000 isn't at at most 10% of sales.
  11. You're not allowed to modify the 747 in any way other than making liveries (as stipulated in the EULA) - also Tabs has already confirmed on the forum that he told the guy who uploaded it that he isn't allowed (one week prior to it being uploaded) - see here http://forum.avsim.net/topic/403257-a-new-ngx-version-of-the-wonderful-md-11/?p=2798499
  12. As I said, it won't affect the vast majority. However, it would only have to affect a small minority for PMDG to see a $50,000 difference in sales.
  13. Firstly, PMDG do not allow it (you agree to their terms when you buy the product). Secondly, business wise, it is actually bad for PMDG as they are making a V2 and less people will buy their V2 if people are upgrading V1 (they will have already lost some sales because of this HD texture pack) - the more and more people upgrade V1, the less and less likely they will want to buy V2. It won't dissaude the vast majority from buying V2, but it will some. This is where the EULA is a bit silly, for the MD-11, as the MD-11 is a completely dead project over at PMDG so letting someone release nicer VC textures isn't going to harm their business.
  14. Have you guys managed to fix the incredibly annoying issue of flickering clouds when they intersect with terrain? :smile:
  15. *finally*? I've never disabled turbulence and never had an issue using any PMDG products with AS2012/FSGRW using turbulence.
  • Create New...