Save your flights as you go along!!! I don't use FSUIPC and do it manually - never had it crash on me whilst saving. Never had a crash in the 777 too. I can't fly without saving. 

So I am not the only one who is flying the PMDG B777X with it crashing my flightsim constantly. I thought it was a one off thing. I tried flying out of Melbourne last night on Emirates and after takeoff and retracting the flaps FS X crash. So I tried again! And this time it crashed again just before I got onto Runway 16.

 

Well, I have been having problems with crashes, but I won't be too quick to blame the 777.  I have had some problems with the 737NGX, as well.

 

For a while, I was blaming Coatle with the FS Dreamteam sceneries.  But the problem persisted after I removed the FS Dreamteam products along with Coatl.  So my initial assessment on that was incorrect, I think.

 

But I am not sure that it is even a PMDG problem.  I will need to try several other aircraft.

 

But I am not even sure that it is an FSX problem.  One of my video editing programs has been doing weird stuff.  I guess I will need to play the Sims for a while to see if I have crashes there, because, that, too, is a fairly demanding 32 bit program.

 

But I have been bird dogging this problem for about a month now.

People,

 

The PMDG 777 is crashing on may people. I did open a TICKET with PMDG and they've recognised the problem:

 

---------------------- Here's what they are saying ---------------------------

 

From: "PMDG Technical Support Desk" <>
Date: 22 September 2013 18:28:55 IST
To:
Subject: [018-19D194ED-045F] PMDB 777 crashes at FL370 (EGLL- OMDB)
Reply-To: "PMDG Technical Support Desk" <>

There is a known issue with switching the EFIS to Plan mode in flight that has already been corrected for the first update coming in the next several weeks.
 

Paul Gollnick
Technical Support

PMDG Simulations, LLC

www.precisionmanuals.com

----------------------------- end -------------------------

 

So the gentlemen saying the issue could be with our rig is not correct...There seems to be some sort of incompatibility with some files...

 

In our case, we are not interested to know about them files, at $90, all I want is install and fly....

 

Thanks,

Regis

Not to sound like a conspiracy theorist but I am guessing that the gentleman is on PMDG`s pay role to discredit any negative comments about PMDG products. Not the first time any one has resorted to this.

 

Regards,

Darren

People,

 

The PMDG 777 is crashing on may people. I did open a TICKET with PMDG and they've recognised the problem:

 

---------------------- Here's what they are saying ---------------------------

 

From: "PMDG Technical Support Desk" <>
Date: 22 September 2013 18:28:55 IST
To:
Subject: [018-19D194ED-045F] PMDB 777 crashes at FL370 (EGLL- OMDB)
Reply-To: "PMDG Technical Support Desk" <>

There is a known issue with switching the EFIS to Plan mode in flight that has already been corrected for the first update coming in the next several weeks.
 

Paul Gollnick
Technical Support

PMDG Simulations, LLC

www.precisionmanuals.com

----------------------------- end -------------------------

 

So the gentlemen saying the issue could be with our rig is not correct...There seems to be some sort of incompatibility with some files...

 

In our case, we are not interested to know about them files, at $90, all I want is install and fly....

 

Thanks,

Regis

Hi DarrenLiewWY,

 

At least we know that PMDG support acknowledged the problem which is already fixed...All we have to do is wait for the service pack to come out.

 

 

Thanks,

Regis

Hi DarrenLiewWY,

 

Can you please try to download "Microsoft .NET Framework 3.5 Service Pack 1"  and retry the PMDG 777 crash situation ?

 

http://www.microsoft.com/en-us/download/confirmation.aspx?id=22

 

I have tried mine and it seems ok....I might need more tests

 

Thanks,

Regis

OMG!

First it was "where's the airplane?" and now "where's the service pack?"  Really??

 

First of all, the 777 itself has several new and important features (most significant among which is the Time Compression Feature.  We all take this as "a given" and assume that with all the different hardware out there, poorly-maintained and non-optimized FSX platforms, assorted freeware and payware scenery and airports, nothing could possibly go wrong.  If it does, it MUST be PMDG's fault!

 

Sure it could be a part of the problem, but it could also be a myriad number of other things, not least of which include memory leaks, system overheating, poor cleaning/dirt, failing motherboard and/or Ram Chips, wrong Video drivers, and on and on.  It could even be FILE PERMISSIONS.  

 

Sadly, none of us WANTS to be a computer engineer, yet those of use who crave the bleeding edge in frames rates and stunning graphics - it is unfortunately part and parcel of the flight simulation hobby.

 

Like a new high-end sports car, there may be undocumented issues that arise during flights - particularly long ones.  If you're using FSInn or Squawkbox, a 3rd party Weather program, an electronic flight bag, a moving map display, a virtual CDU, 3rd party MCP panels... all of this dancing while moving all those objects onscreen in 'real time' or 'accelerated/compressed time', plus doing the calculations to put all those pixels up AND maintain the highest possible frames rate, and we are AMAZED when suddenly, with no warning, things don't go as expected?

 

Ever drive on a highly congested freeway at rush hour?  Stunned to see cars crashing into each other?  Imagine limitless lines of code (how about 4.7 BILLION instructions per second on my PC) executing, traveling across the the motherboard back and forth to the output (screens/ headphones/ speakers / printers / joysticks, rudders, throttle quads, etc) to the Pilot in Command.  You KNOW sometimes WORLDS COLLIDE.  Hence, a system crash.

 

Ever pop your PC case open and hit the innards with a can of compressed AIR?  Ever run real time Heat Monitoring Utilities and check your under-hood temps?

 

HEAT and DIRT alone can rock your world and crash your flight.  Poorly written video drivers may not manifest until a flight is well underway.

 

Wrong file permissions can make even the highest-quality software perform unexpectedly.

 

Then, there's problems caused by the inevitable overclocker, whose system might be stable for a couple hours, but finds out that after 4 or 5 hours, things are suddenly less stable?  Usually a feature of HEAT and/or poor cooling.  The greater the clock speed the higher the temps.  Dirt gets on your CPU or GPU cooler and suddenly - kaplowee!  A crash!

 

We haven't even talked about sporadic memory chip failures, or capacitors going bad on the motherboard - or VIRUSES, corrupted hard disk files, well, you get the idea.  I know!  Let's blame the AIRPLANE!

 

And yes, Virginia, this is the hobby YOU chose!  Perhaps SLOT CAR racing might have been more apropos?  Thankfully, there's always bowling, golf, and lawn darts.  Something low-tech.  Ahh... now there's a thought!

 

Or you could go fly a REAL airplane and experience REAL sudden failures,  In that case, you are permitted to unequivocally blame the airplane.  Don't pay any attention to what the NTSB says about it later on.  You won't be around to hear things like "Wind Shear", "Pilot Error" or "Poor Maintenance."

Folks, if you have the paid version of FSUIPC, make sure to turn on the autosave feature.  You can never eliminate all crashes, even with all the knowledge I have acquired over the years that have helped me avoid the most common crashes, I still get the occasional glitch that messes up my flight.  But having a save point to resume the flight from makes things much more tolerable.  If you don't own the registered version, it's worth buying just for this one feature alone.   The peace of mind is priceless.

How does this work differently than the default save flight in FSX that doesn't work very well.  Also, if you're running Radar Contact for example, you won't be able to return to it after loading a saved flight from FSUIPC.  Is this true?  Trying to justify buying FSUIPC registered but after a year haven't bought it yet.

Funny,I have the 6.0.6001.18000 version,and just completed a 8 hour plus VHHH-YSSY flight with a SID/Runway change ,using plan mode,and had no issues.The version Jim said,was the correct one gave me CTD's.

 

 

Funny,I have the 6.0.6001.18000 version,and just completed a 8 hour plus VHHH-YSSY flight with a SID/Runway change ,using plan mode,and had no issues.The version Jim said,was the correct one gave me CTD's.

I've been running that (wrong) version since Jan 2010 on two different rigs with FSX and never had an issue either. Frankly since my "wrong" version is working fine, I dont really want to mess with it and test the "correct" one and mess up some long flights. Not that I cant put the wrong (right) one back in, but if it ain't broke then I dont need to try and fix it.

 

Sean Campbell

Regis and Daren

 

From the Issue Tracking thread - - CTD after selecting PLAN mode while the ND is on the lower EICAS.

 

From Ticket submitted by Regis to PMDG - There is a known issue with switching the EFIS to Plan mode in flight

 

These might or might not be the same issue. I think one of you need to verify that these two items are the same thing and will fix your issues.

 

Michael Cubine
 

Dear All,

 

Im am not by any means a tweak expert or anything like that. Im a aviation enthusiast who likes to fly complicated aircrafts. PMDG has been by far the best developer in the market and still is. I too faced some OOM / CTD's while flying the T7, but hardly ever, flying the NGX.

 

Well, what I did is to search the forums, do some tweaking (as per the guide) and try flying again. Yes, I was flying EFHKOMDB and had a OOM on finals... Crap! luckily I saved my flight before TOD. So load up the flight and start again. After reading some more forums, found out that FSUIPC can do it automatially:) bravo, something new learned.

 

Yes, there can be some bugs, but then again, the FSX itself is a complete bug! Its an old platform whichs development has ended already... I agree that with a paying customer, you should get a product which is flyable and enjoyable. It is if you are willing to do some research. It has plenty of new systems and tricks and thus you cant ever eliminate bugs, never. Even i realize that. If there are 100 million simmers out there, there is 100 million different setups. I bet none of the setups are the same.

 

If you need to save your flight, then save it and stop complaining. Im sure PMDG is working behind the scenes to correct some of the bugs.

 

If it is too much for you, then you just have to wait for the update, fly the NGX or MD11 etc meanwhile if you are not willing to do some tricks. We all know what FSX is and that there is hardly a way to keep it without any CTD/OOM. It is not reality. For some reason, people are experimenting more these issues with this addon (me included) - too bad but im sure we will get correction to that in the future.

 

What Im more interested, did any of the beta tester experienced any of these issues? if not I quess their rig is tweaked according to all the guides available....

 

The plane itself is marvelous, best ive seen. It has some teething problem, but hey, so did the 787 had some after the release.... and in reality, there are people lives at stake, you have only 90 bucks and a computer simulation...... and youre crying for that?

 

perspective....

 

Cheers

Hi Seme,

 

thanks.

 

we are not crying we just want to flight buddy....I know PMDG are working behind the scene to improve it.

 

The fustration grows when we hear other pilots enjoying their T7 on polar routes or over the middle east to Dubai....And we cannot !!?

 

So if there are many subjects on this if that we want to hear others experiences and maybe try their suggestions as you've said 100 millions pilots using T7...

 

Thanks

 

Slan.

Regis

I use Plan mode to verify Route building, and all mods,both at the gate ,and in flight,with no issues

Not sure what you are talking about. The PMDG 777 is freaking stable on my system, and so is with most users. Why don't you take some time to figure what is wrong with your rig that could have caused CTD? Indeed the T7 places a high work load on your system, but for a correctly setup system that should be able to handle.

Yep I flew a few legs to and from ORD, DOH, NRT, and FCO without a single issue beside one flight where I had the left electrical bus shed its load (which I traced back to user error on my part regarding the gpu)