• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. And, knowing full well there would not be enough fuel to do it, I tried the same route, with the same SID/STAR in the 737NGX. No issues at all - except for the insufficient fuel warning. It must be something I am missing with the 777 but I have no idea what it is. Dave Robinette NBL1936
  2. Here is a link to a video I just shot, showing what is happening. https://photos.app.goo.gl/0jN5YioppIgv1Uvr1 Dave Robinette NBL1936
  3. Sorry...should have said SimBrief. The route was: BSTER2 VALLY WOLFO AR18 ETECK M202 UKOKA M202 KINER 41N060W 44N050W 48N040W 51N030W 51N020W DINIM ELSOX EVRIN UL607 NUMPO UP2 BEDEK OCK2F I selected the correct SID/STAR from the FMC, and used the proper runways for each 26L for KMIA and 27R for EGLL. Thanks Dave Robinette NBL1936
  4. I have just run into this issue. I loaded a flight plan, prepared via SimFlight, into the PMDG 777-300. I went through all the necessary steps in the FMC regarding the INT, SID/STAR, TO speeds, Approach speeds, etc. I hit ACTIVATE/EXECUTE as necessary. I did all the same steps as I have done before with no issues. This time, when I look at the legs page(s), the airspeed/altitude shows, then flashes to "---/------" then flashes to the airspeed/altitude, then back to the dashes and stays there. I tried loading all into ROUTE 2, but that did not make any difference. I can't figure out what caused the issue as it has not happened to me before. One other thing I noticed was that parts of the legs in the moving maps section of the cockpit (all stock PMDG items) were flashing in 'coordination' with the FMC legs page. Anyone have any suggestions? I have a feeling I am forgetting something, but not sure what it might be. Thanks. Dave Robinette NBL1936
  5. nbl1936

    Unable to load PMDG Aircraft - P3Dv4 Crashes

    I will add my frustration to this thread. I had done a flight on P3Dv4 both before and after the Windows update. I only had the CTD with the ntdll.dll issue two days ago, towards the end of an EDDF-KJFK flight, with about an hour to go. Ever since then it has occurred. I have tried all options listed on LM's site and elsewhere, to no avail. One thing I can say is that the system runs JUST FINE when it is one of the STOCK P3D aircraft, even with ORBX, FSDT and other scenery loaded. However, when I change to a PMDG AIRCRAFT, I immediately get the CTD error. I have ensured that all push updates, via PMDG OPS CENTER, have been installed. I know LM is planning to issue a fix on/about Oct 10th, but not sure if that fixes this issue. David Robinette NBL1936
  6. On Aug 20th, I checked and there was an OPS CTR update showing on OPS in the notifications. I clicked on the update and it froze part way through. I have since un-installed the 777-200 and re-installed it, figuring it would repair/replace my OPS CENTER. No changes to OC were done by the re-install. However, when I go into PLEASE SELECT A PRODUCT, the 777-200 is MISSING from P3Dv4, when it was there on Friday the 18th. I have both the 737NGX for P3Dv3 & P3Dv4, but only the v4 for the 777. Anyone else with similar problems? Any ideas? Dave Robinette NBL1936
  7. nbl1936

    T7 FMS Error

    Thanks for the suggestions. Got it fixed. NAVIGRAPH was pointed to the wrong folder, and was updating things, but putting it in the PMDG folder, and not the data folder. Great thing about the Forum - someone always has theanswer! Dave Robinette
  8. nbl1936

    T7 FMS Error

    I updated my Navigraph files in both PMDG and AS16. I planned my route via SimBrief, using the updated data. Setting up the flightplan in the T7 FMS, I get an error stating "KORD ERR: 10 RWY NA" and I have NO SIDS/STARS showing for KORD in the FMS. Any ideas? Thanks. Dave Robinette NBL1936
  9. nbl1936

    Latest update causes my FS2Crew not to work

    Realize that this is PMDG and not FS2Crew, but since it was here....I did the PMDG update - no issues. Ran FS2Crew and it would not start. Discovered that you have to re-enable FS2Crew AND re-select the keystroke(s) you want to use to make it work. Remember to use the AUTOFEATHER ON/OFF for FS2Crew! (I spent the last hour trying to rundown an issue, only to discover I was not using the correct command.) Hope this helps. Dave Robinette
  10. nbl1936

    "Activation" Issue with 777 AFTER Push Update

    I want to give a HUGE SHOUT OUT to Paul Gollnick, Technical Support, PMDG Simulations, LLC for working on this issue. He sent me the corrected files and things work just fine. Thanks to all! Dave Robinette
  11. nbl1936

    "Activation" Issue with 777 AFTER Push Update

    If there are any PMDG support individuals on this thread, I would appreciate someone looking into my support ticket I put in a week ago. I received two replies - the last being on the 25th, saying I would hear back by the 26th. As we are now at the 29th, I am getting a bit frustrated. Dave Robinette
  12. nbl1936

    Update 1.10.8383.0

    Update issue also with P3D v3. Can't say anything about FSX. Dave Robinette
  13. nbl1936

    "Activation" Issue with 777 AFTER Push Update

    Checked all. Using McAfee, as I have been for several years. I just turned off McAfee, loaded P3D, selected the House Color 777-200, got the activation notice, entered the number I copied from the email and again get the "Activation Library handle creation failed" error and P3D shut down. Dave Robinette
  14. nbl1936

    "Activation" Issue with 777 AFTER Push Update

    The hosts file contents: # Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # rhino.acme.com # source server # x.acme.com # x client host # localhost name resolution is handled within DNS itself. # localhost # ::1 localhost Dave Robinette
  15. nbl1936

    "Activation" Issue with 777 AFTER Push Update

    I have the following in the host file: Hosts file last modified 7-16-16 Hosts.20160724-172442.backup last modified 10-30-15 Hosts.20160724-172500.backup last modified 10-30-15 Hosts.bak last modified 7-24-16 lmhosts.sam last modified 3-18-17 networks last modified 10-30-15 protocol last modified 10-30-15 services last modified 10-30-15 I did no modifications to my computer between when the T7 worked on Tuesday evening - Wednesday afternoon (long flight) to when I tried to load a flight on Thursday morning. The absolutely only thing that was changed was the push update from the Ops Center. Thanks. Dave Robinette