Meekg

Members
  • Content count

    60
  • Joined

  • Last visited

About Meekg

  • Rank
    Member

Flight Sim Profile

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

Profile Information

  • Gender
    Male

About Me

  • About Me
    A320/A330 Captain/TRI

Recent Profile Visitors

330 profile views
  1. There is a big improvement on that side also. You will be impressed. The Maddog X flies exactly as per the real aircraft manual in all aspects (pitch, power, fuel consumption, climb and descent rates all the way to the taxi dynamics). Do not miss it. ;-)
  2. I use the following settings with a pretty realistic result. Occasionally on the 737 I experience some abrupt pitch inputs with the AP ON but I'm convinced it is more an autopilot glitch than excessive turbulence. The same does not occur with the 777 or 747. Cloud options: - Maximum Cloud Turb 70% Wind options: - Maximum Wind Turbulence 60% - Turbulence effect scale 55% - Maximum windshear 30% - Enhanced Turbulence: OFF Maximum updraft AND downdraft rates at 500fpm Random light chops turb percentage: 30% Let me know what you think.
  3. ;-) I wanted to fly the same route but I'm currently stuck with recurrent CTD. That link is very good for vintage flight schedules. Have fun
  4. They were flying through Prestwick EGPK http://www.timetableimages.com/ttimages/complete/kl57/kl57-30.jpg
  5. Thanks Gunter, I tried ABORT after before landing flow only, I will try to abort after each phase.
  6. I get the crash 99% of the time right after touchdown.... let's say 1 second after nosewheel touches the ground. I've tried to uninstall and reinstall. no luck. I only had it once during taxi out, but then again, I rarely perform long taxi during this test flights. Has any of you open a support ticket?
  7. I get the crash from NON SODE default airports too. I'm giving up.
  8. Somehow a CTD event was finally triggered upon touchdown. Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: api.dll, version: 4.0.28.21686, time stamp: 0x594a7300 Exception code: 0xc0000005 Fault offset: 0x00000000000155d1 Faulting process ID: 0x2600 Faulting application start time: 0x01d30bc39967c588 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\api.dll Report ID: 8aa7e2db-df61-4209-bda4-736a4d414422 Faulting package full name: Faulting package-relative application ID: Hope this helps.
  9. Another CTD on touchdown... So far these are the different conditions I've been using: - Scenery default/add on - Weather - AS ON/OFF - AFE ON/OFF - USB headset (connected but not used as default speakers) - FSUIPC registered version, no brake or flight controls axis other than "steering set" - no GSX installed I have to be honest I'm very frustrated after 20 years of PMDG without a flaw.
  10. SLOP 1 or 2 NM right is normal procedure also in the Indian Ocean airway system (e.g. Mumbai oceanic area and Chennai oceanic). In China it is not exactly SLOP per se (Strategic Lateral Offset Procedure), but most of FIRs despite radar available, ask ALL traffic to offset (generally 3nm RIGHT of track, but they occasionally vary).
  11. Disregard, the problem presented itself again.
  12. AFE YES, FSUIPC YES, ORBX GLOBAL, TREES (no vector), sound device? My motherboard inbuilt one (realtek chipset I believe). Useful information: I completed a couple of successful landings after adding the AlwaysFullLoad=1 in Prepar3d.cfg file main section. Consequently I've had another CTD when trying to select the prop reversers back to normal, after normal application of reverse power. The latter, as opposed to the CTD on touchdown generated an event, I therefore believe the two events are unrelated. Here's the latest CTD log: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: menus.dll, version: 4.0.28.21686, time stamp: 0x594a71cc Exception code: 0xc0000005 Fault offset: 0x0000000000005100 Faulting process ID: 0x43c0 Faulting application start time: 0x01d30a347726a402 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\menus.dll Report ID: 94febc1e-4a65-4136-90b1-12e762f21768 Faulting package full name: Faulting package-relative application ID:
  13. CTD on touchdown every flight.
  14. Alex, you stand correct, when testing in ELLX I still experience the FPS drop. Well... I solved half the problem then; I was experiencing it everywhere, now only on selected airports. Mike
  15. Please refer to this These nvidia settings solved the FPS drop for me for now. No more FPS drop. Good luck