Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

9 Neutral

About bert.laverman

  • Rank
  • Birthday 02/27/1964

Profile Information

  • Gender
  • Location
    Almere, the Netherlands

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

1,270 profile views
  1. I wonder, anyone suggested the Woodpigeon route already? A totally new line: GA!
  2. Just in case anybody missed it: This is new "Standard" behavour. The intent was to allow people to just shutdown their PC, and continue where they were after the next start. For some applications (like (flight) simulators and games) that's just weerd, but there you are: "Works as designed."
  3. If this is "Boxed" FSX, then a possible crash when you end a flight is (unfortunately) a fact of life. There are nowadays so many addons which are 20 years younger than FSX, written with a different generation of development tools and for a different generation of hardware, combined with numerous known-but-never-fixed-because-MS-dumped-FSX bugs, that we are stretching the poor thing way beyond its design limits. Windows 10 is also 5 versions beyond FSX's intended platform. Dovetail did fix a number of the most serious bugs with FSX-SE, but not all. Prepar3D v3, being targeted at the professional market, is way more stable and makes better use of modern graphics hardware. The new Dovetail FlightSimWorld and Lockheed Prepar3D v4 finally address many of the the hardware advancements we've seen since FSX came out, most notably the larger address space (the famous "64-bit" thing) and up-to-date graphics support. With FSX and FSX-SE I tend to be happy if I can complete a flight, and completely ignore how I get back to the desktop. Having to manually kill off Saitek Instrument Panel drivers and Linda have become a second nature. When I build a new PC I'll go for Prepar3D v4 and then I'll start to be picky... Cheers, Bert PS If you still feel this is a PMDG 737 NGX specific thing, please do not hesitate to open a support ticket at the precisionmanuals.com site. They will try to help you as well as they can. They cannot fix FSX for you though...
  4. Eh... this is a pinned thread, started by rsr himself. Doesn't that count as an "official topic from PMDG"?
  5. Sorry, I don't read every day. What I did was twofold: make sure the switches that are hard to match on the big airliners are aircraft-specific, and (sigh) start each flight with 'twiddling' a button just to make sure the initial synchronisation has been done. Actually I use Linda for my buttons, but the Saitek Drivers do some things with key-mappings even if you don't use their dumb 'Smart Software'.
  6. Just a wild hunch, but are you using a Saitek button pannel and did you just raise the gear? I had that happen to me once and it turned out that was the first thing I did with the panel that flight... The panel's driver only then woke up and started setting all FSX switches to match the physical ones, which happened to be on off mostly.
  7. How about this all concerns something physical rather than a new virtual plane? Apart from that, everybody flocks over to this thread and all usual chatter about the impending release has reduced considerably. Well played, Kyle...
  8. This has been discussed to death. Problem is FSX, not the addon. These effects are possible, but form an absolute performance killer.
  9. AFAIK this is specific for the RR engines also, so standard ops rather than risky. I remember reading about this somewhere way back.
  10. Are you using e.g. the NL-2000 scenery for EHAM? That one has extreme detailed textures and gives me OOMs with the NGX, guaranteed.
  11. Nope, this is a completely new development, not a (small) update on the existing code.
  12. Do you have the PMDG Operations Center software installed? It will update the product for you, with no need of going to the site's download area. If you bought the CDROM version, then Aerosoft should provide the update.
  13. I have experimented with this a while back and noted that the 777 needs to be "triggered" to start the generation. For this you need to go to the LEGS page and then use LSR6 to go to a data page. This tells the 777 code that weather data is wanted. I believe the instructions in the manual actually state that you have to open this page, although the reason for it is not explained. Once you have done this, any change in the plan will trigger a regeneration of the FSX flight plan and the corresponding WX.PLN file from the current state of the plan in the FMS. Note that if you use a tool like FSTramp or Plan-G to produce a live view the FSX flightplan, you will see that any waypoints you've passed are removed, so your aircraft will not always be perfectly "on the line". The current segment is shown as a line from your departure airport straight to your next waypoint.
  14. That isn't so bad. I remember seeing a comparable discussion in the Aerosoft Airbus 320 forums with even stranger route misbehaviours, where real-life pilots responded that they actually had such things occurring. Just like with the Tesla, never blindly trust the autopilot.
  • Create New...