19 hours ago, Lawy said:

•  

  Is it possible for information not to be accurate?

This is the kind of question that can be argued indefinitely.  Going back to the father of information theory, Shannon, the amount of information in a message is related to the entropy of the data.  One example is that if you are expecting a message to say something then when you get the message you received very little information.  If a message is a complete surprise then there is a lot of information.  The surprise does not imply anything about truth.  There is a lot of information on the internet, but much of it is of questionable truth.

It is a good question, and one worth considering.

17 hours ago, FreightDawg said:

never has crashed once on my end, its been Flawless

I concur with FreightDawg, (hey that's my call sign, smile freight only). Hundreds of long haul hours in the -8.

 

5 hours ago, Bluestar said:

Marc,

I just checked my flight log for 2018. I flew approximately 500 hours (real time) in the PMDG B777 with 15 flight over 8 hours and 5 over 10 hours with the longest being 13.8 hours.  I haven't experienced any system crashes with the B777. 

I'm not sure what to tell you, wish I had an answer. 

Grace and Peace, 

Wilhelm,

I really see that there is no point to give any fault to PMDG or point a finger at them.. However I can't delete more than everything. I've completely nuked my P3D SSD for 4.4 and deleted everything I could find that was related to P3D in the folders and in the registry all I left was the PMDG registrations on my system. Then I installed 4.4 and my PMDG addons (all the three of them. Ne scneries, no tools, nothing. no issues. I added GSX.. no issues. I added ORBX, other sceneries, no issues... I thought that's it, everything was set up again and the 777 just worked flawlessly.. then suddenly without me installing or changing anything I had another ntdll crash. I went through the crash guide, took load off my video card, all that stuff.. ntdll every single time I do long hauls in western direction. not when flying eastwards. I surely don't blame anyone for something as wicked as this, but I can't quit thinking that there must be something in the 777 code that doesn't like that.. maybe my german date system? maybe a shared dll? maybe a ß or ü or ä.. I don't know.. I'm thinking about reactivating my old computer to install the 777 there and do tests.. This freaks me out... sigh

26 minutes ago, Ephedrin said:

This freaks me out..

We've all been there with our sims. 🙂

Grace and Peace,

56 minutes ago, Ephedrin said:

ntdll every single time I do long hauls in western direction. not when flying eastwards

Oh yeah... these happen to many and last year GSX looked like the problem.  FSDT modified GSX to "solve" the problem, which it didn't, so now LM will not do anything and FSDT says it's not their problem.

Based on your description of the problem, I'd recommend you disable or kill couatl for a session that you normally get the CTD event.  Mine usually occur in Canada or So Greenland flying Westward; although, I had one in W China in the middle of nowhere too.  This has been going on ever since P3Dv4 came out.

7 minutes ago, downscc said:

I'd recommend you disable or kill couatl for a session

That's actually what I did right today. I uninstalled every single FSDT addon, deleted the Addon manager, got rid of couatl and bglmanx as Robert told me/us in another thread. ntdll after 7h+ somewhere north of PNG. I'm not too sure as I simply can't sit in front of my computer for 7 hours to wait for a CTD.. but considering my route from Rarotonga NCRG to Hongkong VHHH, a flight of around 11h, it must have been somewhere there. Maybe there will be an update sometime by anyone that accidentally or intentionally fixes this.. But until then I think the 777 won't be a candidate for western intercontinental flights for me... 

2 minutes ago, Ephedrin said:

That's actually what I did right today. I uninstalled every single FSDT addon, deleted the Addon manager, got rid of couatl and bglmanx as Robert told me/us in another thread. ntdll after 7h+ somewhere north of PNG. I'm not too sure as I simply can't sit in front of my computer for 7 hours to wait for a CTD.. but considering my route from Rarotonga NCRG to Hongkong VHHH, a flight of around 11h, it must have been somewhere there. Maybe there will be an update sometime by anyone that accidentally or intentionally fixes this.. But until then I think the 777 won't be a candidate for western intercontinental flights for me... 

Marc, this happens with the PMDG QOTSII and also the FSL bus.  Extensive testing by others has ruled out everything but FSDT and they claim it is a corrupted data in some facility in default P3D.   Haven't found the corrupt facility data yet but again the 777 has been ruled out as the problem.  Please see the 100+ post threads in the LM forum on this problem.

LM has never contributed to the discussion by the way.  It very well might be corrupt facility data but until it's found we have to remove FSDT from triggering the problem.

1 minute ago, downscc said:

but again the 777 has been ruled out

If that's the case then I definitely can't tell what's happening on my system.. The most probable explanation would be that I have missed anything when I deleted the stuff.. 

Man, I really hope there will be another solution for a proper push back in P3D some day so GSX loses its monopoly, even if it's the super expensive AES.

Is the update out yet?

2 minutes ago, lukejw20 said:

Is the update out yet?

Probably not as there is no thread opened listing all fixes. 

We must be getting closer. Its eerily silent here 😂 Hopefully its a sign of impending release, or atleast a changelog..

6 minutes ago, lukejw20 said:

Is the update out yet?

whenever you ask yourself this question, simply open the operation center 😄

1 hour ago, lukejw20 said:

Is the update out yet?

Since the 26, I've been checking twice a day based on the X-Mas - New Years possible release. If it's delayed, no biggie. 

Slight delay.

Soon^TM

3 minutes ago, scandinavian13 said:

Slight delay.

Soon^TM

The week‘s not over yet. Take your time, I go to sleep now anyway, after that I‘ll have a salmon breakfast with my parents, then I‘ll go see my ex... and only then you will need to have released the update 😂