demarr55

Members
  • Content count

    80
  • Joined

  • Last visited

About demarr55

  • Rank
    Member
  • Birthday 03/08/1948

Flight Sim Profile

  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Contact Methods

  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Knoxville, Tennessee
  • Interests
    Flight Sim, Photography

About Me

  • About Me
    Retired from Teradata and now enjoying all my free time.
  1. Having similar problem, can't load PMDG 747 from scenario screen, P3D will just show black screen then close, nothing in event log. I have updated all 3 components to V4.2 and I do not have FSUIPC installed. I can load the piper cub then switch to PMDG 747 and everything works just fine, also have no problems loading either the 737 or 777.
  2. Luis: What are you using for ATC?
  3. I went ahead and installed all 3 components individually, that way the version numbers on all 3 match. Did not have any problems with any of my addons, either scenery or aircraft.
  4. Kyle, An update, ran the flight again today, same plan as yesterday, no third party scenery or weather programs. Did not use any popup of ND, PFD, FMC, during the entire flight and flight completed without any problems. Does this shed any more light on the problem? Will verify again in the morning and run it again.
  5. Kyle, I am running the latest Nvidia graphics driver, 385.28 but could go back to previous one and see if that helps. As for unstable overclock, I have my doubts, been using this PC for the past couple years running all PMDG products in FSX with no problems what so ever, but there is the possibility that some component has degraded over the years to make it unstable. Have to keep in mind the PMDG 737 works like a charm with no problems.
  6. After purchase of PMDG 747 QOTSII, attempt flight from KSEA to RKSI, About 4 hours into the flight I get the error message that Prepar3d not responding and only option is to quit the program. Tried a second flight using the same flight plan and get same result. Setup a test flight from KFLL to KSEA using the PMDG 737-800, not using any third party scenery or weather program and flight completes successfully. Same flight plan, only now using the PMDG 747-400, again no third party scenery or weather program, and about 3 hours into the flight get the dreaded message Prepar3d not responding. Being the stubborn person that I am, tried the flight a second time with the same end result. Have searched the forum and found one case where the user mentioned a similar problem if using popups of ND and PFD. Will certainly give this a try, but that is not a solution. Also note, I was monitoring my temps during the flights and have no over heating problems. Two of the flights did not show any faulting module, however one did show ntdll.dll as faulting module. Anybody else having this problem? My sysem Windows 10 home 64 bit Asrock Z87 Professional Intel i7 4770k overclocked to 4.2 GHZ 16 GB dual channel memory GTX 770 graphics adapter Any help would be appreciated Bob Demarest demarestrobert@gmail.com
  7. Thank You Lars, going now to update my system.
  8. Just tried and had no problem, working fine
  9. My system: Jetline I7 4770K at 4.2 GHZ, windows 10 home, 64 bit. Problem started last week and so far have not found any solution. FSX does not recognize any of the buttons on the joystick, however windows sees the joystick just fine with all the buttons functional. Have looked at the Standard.xml and found it was kind of messed up so I've edited it to the way I want the buttons to be. Starting FSX and looking at the controls they do not match the Standard.xml file. I have removed the joystick and restart PC to let windows add it back, but still no help, moved my edited Standard.xml file to the controls folder in \username\appdata\roaming\microsoft\fsx\controls, restart PC, check this file and everything looks right, start FSX and again looking at the controls settings they don't match the xml file. Is there another location or some other file that FSX looks at to setup the controls functions?
  10. FSX-SE

    I have the same problem and have searched the web for a solution. For right now have left .rar file and the free standing BGL file in a temp folder until I figure it out, so you're not alone.
  11. FSX-MS

    Aaron: Keeping up with all the software updates is indeed problematic. I do setup reminders in my calendar to check for updates on most of my addons every two months. So far this has worked well for me. My biggest problem is with Aerosoft Airbus series. Since the release of version 1.30 of both the A318/319 & A320/321 they have come out with four hotfixes. Following their instructions to install, I find some files in the hotfixes are actually older then the files they are supposed to replace. Always ask myself if I'm reading too much into the install and just go ahead and do the update and hope for the best or is it just sloppy work on their part to include older files. Anyway, I can only suggest you find a way that is most comfortable for you as a reminder to check the web sites for any addons you have. Good luck Bob Demarest Knoxville, Tn.
  12. I have 3 systems and all three have their own UPS. Typically I plug the monitor, PC, external backup drive and the cable modem into the UPS and don't worry about the speakers. All three are Cyberpower 1350 units and all three have served me well, especially during those nasty thunderstorms, they give me plenty of time to do orderly shutdown.
  13. Stephen: I was in the same boat, had a problem with my system, also built by Jetline and they have replaced the ASUS MB. I always make sure I keep copies of the installers on a external USB drive and along with a spreadsheet of all the license files. Using those two items to reinstall all my FSX stuff. Have had no problem with any of the PMDG aircraft or any of the other addons I've purchased, just time consuming. And I can say actually made the tutorial flight with the PMDG 777 with no problems, that makes me happy.
  14. cavcpt: Had similar issue only with PMDG 777 and NGX. Problem turned out to be the ASUS motherboard, some problem with the clock. If you have the ASUS board you might want to check their web site for more info.
  15. Kyle: Yes, it's an ASUS MB, system was actually built by Jetline. This past incident was not the first time it's happened and I've made this same trip on my Alienware when PMDG first released the T7 and don't recall this problem. But why do you ask if it's ASUS? Hardware issue? Regards Bob Demarest