Jump to content

michael179

Commercial Member
  • Content Count

    32
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by michael179

  1. Ok, I guess since it wasn't a CAT III ILS approach the ILS wasn't that precise. I will try the ILS 06L at CYYZ again in the A320 to see if I land on the grass again or on the runway. Mike
  2. Hi Adam, Is this the hotfix you're speaking of? http://forum.avsim.net/topic/439263-hot-fix-for-flightplanner-v22/ If so, yes I have it installed. Also, I do have TESSELLATION ticked. I figured my graphics card and computer could handle it, since they're both pretty strong. EVGA GTX 760 4GB for the GFX. Thx, Mike I've tested with and without Tessellation, both times it crashes the simulator, same error.
  3. No I wan't attempting to autoland, I would flare the plane and bring it down the last 100ft or so. But I was expecting a proper glide path and LOC course at least.
  4. Hi all, I've been getting this error for the past few weeks (not due to any new addons) whenever the aircraft crashes into an object. In this situation, I believe it would normally open a menu asking what I want to do next, new flight, etc... but when clicking OK on this error, P3D crashes completely and quits. Here is the screenshot of the error in P3d: http://imgur.com/hXG57NF Event viewer information: Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53468776 Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e Exception code: 0x40000015 Fault offset: 0x0008d6fd Faulting process id: 0x1644 Faulting application start time: 0x01cf9232a09a26fa Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\system32\MSVCR100.dll Report Id: 2cb23f10-fe29-11e3-b0dd-0c8bfd5f56c1 Any idea how to fix this? Thanks! Mike
  5. Ok thanks for the replies. I guess I will just fly manually then when about 300ft AGL for the Q400. Mike
  6. Hi all, A few months ago I got into Prepar3D and this issue has been more and more predominant lately. When flying the Majestic Q400, the Airbus Extended 320/321, or really any other aircraft, there are lots of problems when landing an ILS. For example, yesterday on final with the Q400, established on the ILS 06L at CYYZ (Toronto Pearson), I actually ended up landing on the green grade between 06L and taxiway C. This is a big difference since I didn't actually land on the runway and can cause damage to the plane. Another example, the Q400 on the ILS 08 at CYTZ (City Centre at TORONTO), the glide slope and LOC are messed up. I landed to the right of that runway and almost in the water, before the runway, thus proving the g/s wasn't working properly. I've tested to make sure it's not the winds by setting the winds to calm or 000/00. The Airbus 320/321 does a better job of landing properly, but still is sometimes off course. Both the A320/321 and the Q400 have the latest Navigraph cycle installed, or second latest. 1405 or 1406. Please let me know how I can fix this, if there's an easy fix or if it's something I need to change for each airport's runways. And while I haven't tested every airport, it happens at almost every airport that I fly to, especially in the Q400. Thanks! Mike
×
×
  • Create New...