• Content Count

  • Joined

  • Last visited

Community Reputation

178 Excellent

About molleh

  • Rank
    Member - 1,000+

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

3,430 profile views
  1. molleh

    MD-11/FSX Crash to Desktop.

    Check this (it applies to boxed FSX as well, not just Steam Edition:)
  2. Mitch is right. Sometime's it's not about "who's is better." it's about having something different.
  3. molleh

    Any Solution to ATC Menu Problem??

    What is the issue you're referring to?
  4. In my experience it seems to be tied directly to loading scenery objects. A good example of this is taking of from KSEA in OrbX's PNW region. A few seconds after takeoff, the sim will load in all of the many custom scenery objects in the downtown Seattle area. I always see a fairly long pause there. Other ultra-dense scenery areas have the same behavior. OrbX SoCal is the worst I've experienced yet - when I am approaching Los Angeles, and the sim loads the many custom buildings/objects in the city, I get pauses for up to 3 or 4 full seconds.
  5. molleh

    Looking for a printed 737 QRH

    That's true, but IMO nothing beats flipping open an actual manual, checking the table of contents or index and flipping through beautiful pages of data and information yourself. :)
  6. I would echo Adrian's recommendation for the Majestic Q400. Or the A2A propliners for a totally different vintage experience.
  7. I know everyone's just trying to help and has the best of intentions, but I'm still seeing the "well it works on my end, so the problem must be with your software/hardware" getting thrown around after months of this error being posted about across various forums and social media. I personally have done a completely fresh install of Win 10 Pro from brand new 1709 installation media and still get the "child window" and/or "unsupported operation" errors. There is a compatibility problem with build 1709 and certain 32bit applications. For crying out loud, there is even a post on LM's official forums about it (because it affects P3D v3 which is still a 32bit application.) Please stop insinuating improper usage. Thank you :) -it only affects FSX and P3D v3 (or earlier) NOT P3D v4 -it usually crops up with complex add ons like A2A, PMDG, FSDT GSX, etc. So "I have a totally default install of FSX and it works great, I don't see the problem, it must be you!" is probably true. It's the combination of multiple add ons + 32bit sim + 1709 that is the problem
  8. So it's running good with PMDG etc?
  9. What you will find if you load FSX and a complex aircraft (PMDG etc) repeatedly is that some of the time it will work fine, some of the time it won't. You might be able to load a dozen times in a row without the "child window" error, or you might get the error the next dozen times in a row. Molly Norris
  10. Can you access FSX screens like date/time or options without error message also? 75% of the time or so my PMDG aircraft will load properly in FSX and everything basically works normally, except if I attempt to access one of those screens, I'll get an "unsupported operation attempted" error. And it's fairly random in that I can load/fly something from PMDG a dozen times in a row with no apparent issues, only for either the "child window" error to show again or the "unsupported operation attempted" to show up on the 13th time.
  11. The issue being talked about in this thread is about FSX and P3D v3 because they're 32 bit apps.
  12. Nice to see DTG acknowledging this issue and hopefully can work with MS towards an actual resolution.
  13. Can confirm no fix here as well with KB4048955, which by the way has nothing in the release notes about this issue with 32bit applications.
  14. I have no problems with any of the effects in P3D v4.1. They all work as they should.