Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2 Neutral

Profile Information

  • Gender
  • Location

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

About Me

  • About Me
    Real World Private Pilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Since v5, I have been able to take advantage of the wonderful Nvidia control panel feature of Adaptive 1/2 refresh rate Vsync (my monitor is locked to 60hz only). Doing so effectively locks the fps at 30, and motion outside the aircraft is smooth as butter. Panning using the middle mouse button in chaseplane is butter. However, using the hat switch on my joystick, pressing the view reset button/key, or the keys assigned on my numpad, panning is very jittery/ghosty. I can make a video of this if this is unclear. Let me put it this way. If I don't move the camera at all and I'm looking at the markings on the ground surfaces as I move along, smooth as glass--no tearing/jitter/ghosting. If I pan holding the middle mouse button, also smooth as glass. But using any other method to pan/reset my view ghosts and tears very badly. I've been told that this might have to do with how chaseplane handles panning with joysticks/keys. As you know, instead of a pan axis, it behaves more like a "control to be repeated while held" keypress. If this isn't sending inputs at a high enough rate to the sim, as the view sweeps across, it will appear as if it start/stops panning hundreds of times per second, instead one fluid motion. Is this something that can be fixed with chaseplane, is it just my monitor model, or something else? PS: If I lock my frame rate to any value (30,60, etc), in P3D or Nvidia, then everything is jittery. Motion outside and mouse panning included.
  2. A couple of us figured this out a while back. I've talked extensively with TFDi about it. Yes, VSync does have an effect on it, but the fact remains that I cannot initiate a DXGI device hung if TrueGlass is disabled with any settings. This is true for everybody I've talked to. I've spend countless hours of my life on this but there is only one common denominator--disabling TrueGlass works. And the fact that TFDi cannot fathom how it is related doesn't bode well for it being fixed anytime soon. Which is a shame, because it used to work so well in v4. TFDi said they would talk to Lockheed about it. Obviously they didn't, or Lockheed didn't do anything about it. BTW--if disabling Vsync truly worked for you, I'm happy for you. I found that I was able to complete some flights like this--I thought I had my solution. But then on other flights, I would get it again as long as TrueGlass was active. Very disheartening several hours into a long haul. I understand that they don't understand the issue, but the way they vehemently deny their product has anything to do with it is frustrating when disabling it solves the problem. Recently, somebody asked on their forum when TrueGlass will become compatible with v5. They said something to the effect of, 'It is already compatible, but not as stable as we'd like. Hopefully Lockheed can work on this with 5.1'. 5.1 is here, and this DXGI crash is here to stay...
  3. I've been speaking with a certain TFDI developer about this for almost 2 weeks. He's convinced it can't be TrueGlass but P3D itself. Turning Vsync off in P3D helps for a little, but just delays the crash. The only way for no crash is to disable the TrueGlass.dll in the gauges folder. This issue has driven me crazy. I've tried just about everything I can think of. The way I'm able to trigger it the fastest is at ORBX ESKS at the gate with the Maddog. Here's the real bizarre part. It doesn't crash at dusk or at night, even when the dynamic lights are taking my gpu down to it's knees at 15 FPS. No, the crash only happens in the day when I'm running 60+ FPS. Another strange thing I noticed is that turning ON Enhanced Atmospherics helped. I don't usually use this feature, but when it's on, I don't get the crash. Very very strange phenomenon and absolutely frustrating.
  4. I will have much much more testing to do, but I believe I may have run into a solution. The problem file was indeed the model.IAE of the FAIB A320 included with FLAI. I downloaded the standalone FAIB A320 from their website, and simply replaced the FLAI FAIB A320 model.IAE folder with the one from FAIB directly. Before, i was able to get a 100% reproducible CTD (ntdll.dll) by pressing Cntl-Shift-T at EGLL (or surrounding London airports). Now, no crash. Hopefully this can help some people.
  5. I'm so happy to have found this thread, if not to find a solution, but to see that I'm not crazy or alone. Last summer, I spent hours on trying to figure out why I could not make a successful flight into or out of EGLL without P3D crashing due to NTDLL.dll. In my testing, I indeed narrowed it down to AI2UTL injecting FLAI traffic and using UTL. If I've read carefully, that makes 3 of us in this thread that have crashes at EGLL using AI2UTL to inject FLAI into UTL. Perhaps this suggests it's a corrupt model OR a specific livery/flight plan of a specific model that consistently generates at Heathrow.
  6. With this option selected, instead of both A pumps being shut off before pushback, Engine 1 A and Electric 1 B are shutoff.
  7. Make that 5 Maybe something in these links can help people. This latest thread seems to narrow in on FTX Vector; some people have had success disabling it.
  8. EGLL-KBOS crashed today at 4x speed approaching Labrador with the new GSX 😞 I appreciate the efforts though It's so strange that nobody has been able to pinpoint it yet. There are 4+ decent sized threads besides this one describing exactly this: westbound trans-atlantic flights crashing near the east coast. https://www.avsim.com/forums/topic/521091-ntdll-error-in-p3d-v4-near-canada/ https://www.avsim.com/forums/topic/477563-memory-leak-over-canada/ https://www.avsim.com/forums/topic/531004-p3d-crashing-over-northern-canada/ http://www.fsdreamteam.com/forum/index.php?topic=16936.0
  9. I believe I may have jumped the gun when I said the new GSX fix didn't work. That was the July 11th update. I see now today that the July 13th update is available which explicitly states in the changelog it disables above 10,000 and 250kts. I will test this evening on a transatlantic. Thank you Umberto for helping us, whether it works or not. If it should fix the problem, I will edit my previous posts to point people just finding this thread in the right direction.
  10. I am very interested in these four .bgl's that were identified as duplicates between vector and default. CYJT CYQM CYYT CYSJ I think I will try to disable the vector ones (use default bgls for those airports) and try to recreate this.
  11. Okay I find this very interesting. I run the aero.sors.fr update, but before I do, I use the "check conflicts" function. It spits out a long txt file containing existing conflicts between the scenery.cfg and addon bgl files that contain navdata aka FTX vector. There are a whole lot of American airport on the list, but the last few dozen entries are Canadian. Several of which are on the eastern coast. ZJT (NDB) Freq: 340.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYJT.bgl] ZMN (NDB) Freq: 366.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYQM.bgl] ZNF (NDB) Freq: 270.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYYT.bgl] ZQM (NDB) Freq: 304.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYQM.bgl] ZSM (NDB) Freq: 286.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYAM.bgl] ZST (NDB) Freq: 397.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYSJ.bgl] ZXJ (NDB) Freq: 246.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYXJ.bgl] ZXY (NDB) Freq: 353.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYXY.bgl] ZYB (NDB) Freq: 404.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYYB.bgl] ZYT (NDB) Freq: 246.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYYT.bgl] ZZD (NDB) Freq: 308.0 [Path: C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_CYEG.bgl]
  12. Is anybody getting this crash running Pointsoft's Pro ATC X?
  13. Fresh install meaning no default nav database update. I've been getting this crash for a long time now. Always with Gsx installed, but clearly that doesn't seem to be the culprit for me as it crashed even with the latest version that disables it in cruise. I'm not really inclined to start disabling add-ons that I paid lots of money for just to be able to fly routes that I can easily avoid.
  14. Currently on a fresh p3d install that does not have it. I'm going to try it.
  • Create New...