To be honest guys, I will agree with some of you here on the fact that product and updates are coming too slowly for my liking.

 

 

 

Do you think PMDG might be working as fast as they can?

 

 

 

Another question is that of planned product timelines, and I still cannot understand why this information is under lock and key that keeps getting sidelined. What is happening with the:

 

777-200er

 

777-200/A/B

 

737 NGX Update

 

 

What product timelines? What makes you think there are any meaningful timelines? How do you decide a meaningful timeline for the development and release of a patch? You don't, you can't. Did you expect... we will code aspect "A" of the patch commencing on X date, we will finish aspect "A" on X date, at 11:45 pm, we will then re code aspect "B" and finish on X date. Patch will be released on precisely 18th February 2014. :smile:

 

 

Fix one thing and you break another. Promise one release date and it invariably slips. I've lost count of the number of times this simple logic has been spelled out.

 

Under lock and key you say? So is this some kind of insidious conspiracy?

 

You know what's' happening with the ER, did you not read the  first post in this thread? You have been given an update, likewise for SP1.

 

Likewise, Kyle has already pointed all of us in the direction of the information relating to the NGX patch.

 

 

Is it plausible idea to hire more staff to complete this process quicker?

 

Which costs money, they have to be paid? What makes you think PMDG can afford the overheads.

 

 

I don't mean to be over assetrtive, but this stuff is very silly. The only slight niggle I have is regarding the trim fix. I would like to know if it is "definitely" to be included in SP1, I don't want to know badly enough to hassle PMDG with a ticket, but as  say, I am curious.

 

We have a pretty good idea that the service pack for the 777 is close, it should be entering final testing any time now, so why not all go away and play battlefield 4, mowing virtual soldiers down with a hail of bullets will take our minds of flight sim for a while. That's got be very therapeutic.

[...]

 

To be honest Martin, I think you have slightly exaggerated and perhaps playing a little devils advocate.

 

With a PMDG office and the amount of revenue they take in, wondering if they would take more staff is not a silly question. Also, the 200er hasn't been mentioned since the intro manual.

 

Alex

 

(what's with the Battlefield 4 remark?)

RSR plays BF4. I would also, if I attended these forums here regularly.  

I would say it is silly really. I'm very sure PMDG are sensible enough, pofessional enough to employ more staff if they could afford to and it would make an appreciable difference in terms of alacrity.

 

As for future 777 variants, give them a chance, they have enough to worry about. How do you expect them to give you meaningful updates re additional variants when they have no idea how lng it will take with whats on their plate now.

 

Re BF4, thats obvious.

As a customer sitting on the edge of his seat waiting for the new updates for the 777 and 747 and NGX, with the money that was paid for these products, I want a STABLE release. As far as how long it takes to put on out...Does it really matter how long it takes as long as they give you one where you don't have to have 24/7 contact trying to fix bugs and other things that went wrong with a rushed release????

Silence shows progress....

Hmmmm I wonder whee the update is on releasing it to the beta team.

 

Tony

So... I was doing a flight today from EHAM Amsterdam to FACT Cape Town, 11 hours in total. On approach, I was changing the ND mode, and I accidentally set it to plan. 

 

FSX CRASHED! I know everyone is aware of this issue, but I just can't believe it's been 3+ months without a single, seemingly easy fix for this minimal issue. It seems easy to me, obviously I don't know if that's true.

 

C'mon PMDG!

Jetflier I'm right there with you on that one. 6 months is a little too long for a patch.

 

Tony

My opinion, a patch had more problems. as earlier 777 himself reduced speed and much more, and now you are doing everything himself. About the descent I do not say anything.

 

 

Hmmmm I wonder whee the update is on releasing it to the beta team.

 

There's no update to make because it hasn't been released to the beta team, and he said "about 2 weeks" and not "exactly two weeks."

 

Half the reason they don't post very much here is that everyone parses the information to death instead of just trying to pull the main details:

• Things are progressing
• The beta team will get it soon enough
• More work is being done on the 747, too

And if everything is good, how many time will take the beta phase?

And if everything is good, how many time will take the beta phase?

 

Who knows...

 

Even if everything looks okay, sometimes that means you just haven't seen something yet.  How else would some of the stuff in the issue tracking thread have shown up?  So, it could be several days, or a couple weeks.  You don't want to cut it so short that you miss out on something you might not have seen, but you don't want to wait too long, either.

Experienced software houses have something like expected number of bugs to be found.

 

Means that as soon as betatesting starts, they expect a certain number of bugs in bugtracker. If the minimum goal is not met, it does not mean the software is good, rather than testing is bad.

 

Now, since there is SP1, 300ER and SDK coming in one package, I expect betatesting to be about the same timeframe as the prerelease one, meaning, we could reasonably expect at this point a March release, unless deviations happen (which is quite likely).

 

 

I was changing the ND mode, and I accidentally set it to plan. 
 
FSX CRASHED!

 

Never experienced such bug. Half of the time FSX crash is because of FSX itself. I change ND settings like 20 times during preflight when I am entering my route in FMC.