G-YMML1

Members
  • Content count

    1,388
  • Joined

  • Last visited

Community Reputation

119 Excellent

About G-YMML1

  • Rank
    Member - 1,000+

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    KIAD
  • Interests
    Too many to mention

Recent Profile Visitors

4,882 profile views
  1. G-YMML1

    P3D 4.1 CTD near Labrador

    Most likely it's true
  2. G-YMML1

    FSL latest update

    What is OSD? David, do you lock the FPS limiter via in-sim locker of via NVI?
  3. G-YMML1

    P3D 4.1 CTD near Labrador

    Use x16, folks. It's a 100% medicine of you want to COMPLETE a flight.
  4. G-YMML1

    P3D 4.1 CTD near Labrador

    Found it! quantumleapv1.1.zip I will test it later tonight under P3Dv4.3 conditions
  5. G-YMML1

    P3D 4.1 CTD near Labrador

    Bob, Sounds like that I have been wanting all these years. Do it work with P3D v4.3? I'd like to give it a try. Thanks PS. Searching by your name returns zero results 😞
  6. G-YMML1

    P3D 4.1 CTD near Labrador

    Vector itself (and Regions especially) have made a LOT of changes to default *bgls by adding new bgls, not modifying the defaults and if this would have been a culprit for CTD, it would be uproar all over the flighsimming boards already.
  7. G-YMML1

    P3D 4.1 CTD near Labrador

    Yes, the whole sandwich - FTX Base, Vector, OLC NA and Europe.
  8. G-YMML1

    P3D 4.1 CTD near Labrador

    I do, but not on the long-hauls. Zero issues
  9. G-YMML1

    P3D 4.1 CTD near Labrador

    To my knowledge PMDG does not use default Navaids, rather those from their own database. Correct me I'm wrong
  10. G-YMML1

    P3D 4.1 CTD near Labrador

    No, please don't. What do you mean "fresh install"? Just naked P3d? Did you get your ntdll.dll error in the naked sim without GSX, FSDT sceneries? If so, then the answer might be leading to *bgl failure that only LM could fix.
  11. G-YMML1

    P3D 4.1 CTD near Labrador

    Folks, Is any of you with CTD using this DB? http://www.aero.sors.fr/navaids3.html
  12. G-YMML1

    P3D 4.1 CTD near Labrador

    I have to agree and I believe that this is something inherent to the sim or to the combination of the add-ones. Wrong NAVAID in the NavDataBase could be a trigger also or incorrect AI placement between AI sectors. The only way to test is to have a naked default P3D and fly transatlantic constantly adding add-ones progressively. Unfortunately, this method is extremely time-consuming. Here is my solution for transatlantics that has worked so far for all my instances (PDMG, both 777 and 747) and I have never had this error since them. 1. Once you're at your initial FL, kill GSX completely. 2. As soon as you leave Shanwick ARTCC fire up X16 (anyway, it's absolutely nothing to do while you're over the pond) and go back to normal once you enter Boston ARTCC. That's all, even thought VATSIM folks won't like my approach, I know that. 3. At the TOD, reactivate GSX Also, since I'm able to avoid this error while using X16 acceleration I have my own theory that incorrect AI placement between in-sim AI zones could play it's role. In case you're unaware, once you hit anything faster than x8 acceleration, P3D internal engine suppresses any AI activity. Hence, those of you who fly in a normal time tend to face an error with greater probability.
  13. G-YMML1

    FSL latest update

    David, thanks! What is you method of reinstalling - complete wipe out and clean new install or new installer over the old one?
  14. G-YMML1

    FSL latest update

    Okey, thanks. I presume that I should not reinstall FSSpotlight, shouldn't I?
  15. G-YMML1

    FSL latest update

    I see now. Okey, since I'm a freshman in this field, what is the safest way to update to the new version without touching liveries and other important stuff? Should I reinstall the old version first and then install the new one OR just install the new one over the old one? Thanks!