Jump to content


Commercial Member
  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2,790 Excellent


About Tabs

  • Rank
    PMDG Support
  • Birthday 10/06/1981

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Interests
    Music/Guitar, Computers, Aviation

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That was the Craig Button incident - the plane was out of Davis-Monthan AFB in Tucson, AZ (I was in high school there when it happened). He peeled off from the back of his flight's formation and flew all the way up to Colorado and crashed into a mountain near the Vail ski resort. There was speculation he'd dropped his ordinance in various places along the flight path too - the bombs were never located and weren't at the crash site. https://en.wikipedia.org/wiki/Craig_D._Button
  2. 1. There's a simulation option for doing exactly that - check the intro manual. 2. Limitation of the sim's built-in pushback mechanisms unfortunately.
  3. It's come to our attention since the release of the latest Windows 10 update (dubbed the "Fall Creators Update" by Microsoft) last Tuesday that a subset of users are experiencing a strange "error creating child window" message when running any of the PMDG aircraft in FSX/FSX:SE/P3D. We've confirmed that this is wholly a Microsoft/Windows issue - they've been in contact with the P3D team at Lockheed Martin and have told them that they anticipate a fix for the issue to be released some time in November. For this reason we highly suggest that you do not upgrade to the Fall Creators Update until this issue is confirmed fixed. You can stop the update from automatically installing by going into the Update advanced options (located in Settings/Updates and Security) and selecting the option to pause or defer updates. This will allow you to block the install for at least a month, by which point the issue should be fixed. UPDATE 30NOV17. According to LM Microsoft will release a fix for the child window error in an update on December 12th. This problem was introduced in the Windows 10 Fall Creators Update (version 1709). UPDATE 13NOV17. KB4054517 Released on 12th of November fixes the issues.
  4. Because the latest version disabled it already via an ini entry (in fact, it goes one better and uses the FO popup in place of it so that you still have the general functionality) and we don't want customers mucking around with the files and then writing into support when they mess something up there.
  5. Frank, You did not purchase a P3Dv4 version of the 600/700, you purchased a P3Dv3 version - there is no such thing as the v4 version until it's actually released. Robert's pinned post in the general forum very clearly states that these dates we gave are estimates that can and will change as the actual situation changes. You've been a customer for a long time and honestly you should know how this works by now after all our releases over the years - software development is inherently variable and we don't like giving hard dates for exactly the reason that you're witnessing right now. Trust me, we want things released more than you do - we don't hold something back just to upset customers.
  6. We're working through it with Aerosoft's developers now - I figured out why I wasn't seeing the issue (due to an installer issue, the Bronco's add-on.xml wasn't getting installed to the correct place on my machine because I have my Documents folder moved to a non-standard location to get it off my smaller SSD). With the add-on.xml in proper place I get the issue and the 747 and 777 are dead. Simply pulling the "Aerosoft - Bronco X" folder out of your Documents\Prepar3D v4 Addons folder will allow the 777 and 747 to work - you don't have to fully uninstall the Bronco. We'll get it tracked down.
  7. I only knew about it because another customer's ticket tipped me off to the fact that he'd gotten it working by uninstalling the Bronco. Absolutely no way I would have figured it out without that honestly. We still have no idea what's going on here - I bought the Bronco today and cannot reproduce the problem - both it and the 777/747 work fine for me. We think it must be the Bronco *and* something else now.
  8. Michael, Please submit a support ticket and include your debug logs from the 777 and 747 folders under <P3Dv4 root folder>\PMDG\
  9. The OC will handle this for you automatically if you run it prior to uninstalling the old version, and then again after installing the new one. Doing it your way is not advised because there are sometimes changes to the aircraft.cfg file that you'd be overwriting with an old version. If you really want to do this manually for some reason, you would need to copy just the [fltsim.x] sections of the old cfg (excluding the PMDG House liveries) and then paste these entries into the new aircraft.cfg after installing the new version.
  10. Just replied to your ticket Joe, putting it here as well for the benefit of the discussion - that Chromate Green livery is a 700WL, you'll have to buy the 600/700 addon to get it, we never did an 800/900 version. Perhaps someone in the community did one though - check the Avsim file library.
  11. Liveries are the same between all FSX and P3D versions. This *may* change in the distant future with new products if we start to take advantage of v4+'s higher texture resolution limits where we don't have to worry about VAS and stuff like that, but for now they're staying the same because there's so many different sims we're supporting. Breaking livery compatibility would be a nightmare currently though. I wouldn't anticipate changes like that until the 64-bit sims have become the total standard for everyone and we stop developing for the 32-bit ones.
  12. Allen, We appreciate seeing positive stuff like this - thanks a ton!
  13. Hey everyone, We'd like to collect some data to help try to narrow this down more - we're having trouble finding a reproduction case here. A bunch of us have tried and we're not seeing it. 1. Post a screenshot of your P3Dv4 graphics settings, including the Lighting page. 2. Are you forcing AA/AF or any other graphics settings on via Nvidia Inspector? If so, please post a screenshot of the profile. 3. Lockheed Martin recommends deleting or renaming both the Prepar3D.cfg file and the Shaders folder after an update to the simulator, such as the recent hotfix. Can you try doing these things and let me know if they make any difference with the issue? The Prepar3D.cfg is located at C:\Users\<your account name>\AppData\Roaming\Lockheed Martin\Prepar3D v4 The Shaders folder is located at C:\Users\<your account name>\AppData\Local\Lockheed Martin\Prepar3D v4) Thanks!
  14. Thorsten, There' s a separate thread about that already - the OC downloads its files from Amazon AWS's global CloudFront distribution network. This issue is specific to German CloudFront edge servers somehow and we're going to have to get in touch with Amazon's support to figure out what's going on most likely. Every report we have of it is from Germany.
  15. Yes, those issues are fixed. The cockpit/airframe shaking feature is new to the 747v3 - we haven't backported it to the 777 or NGX yet - it's on the list for the future. The point of these updates happening right now is mainly the P3Dv4 compatibility and performance, not adding new features to the products.
  • Create New...