February 21, 20197 yr For whatever reason, almost every time I try to fly into KSNA from LVFR in P3d (v4 through 4.4), I get a CTD on approach. This is the only airport that I have this problem with. I am able to fly out of the airport but any time I am flying in, I get a CTD. I used to think it was some sort of Pilotedge conflict with their AI traffic, but it has happened on Vatsim or offline. I would like to start using this airport more but don't want to have this ruin the flight. With that being said, does anyone else have this issue? I have the following airports installed in the area and have no problems flying into those (FSDT LAX, ORBX KPSP, Orbx KSAN). I am also using Orbx Global Base, openLC NA, and use BM Vector for that. I also have UTL for traffic. I also have some black patches near the airport that look like a square of night textures (I also seem to see these at FT CYYZ but that is unrelated) Does anyone else have this problem with KSNA? If so, is there something to fix this? Or, what can I look at to see what is causing the issue? This seems to be the only airport I can’t fly into. Thanks! Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU 32GB G.Skill Performance DDR4 SDRAM 3600MHz Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System 2TB Western Digital, NVMe M.2 Solid State Drive
February 21, 20197 yr There were previous discussions about this issue - I would suspect it an object on the airport that is not compatible. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
February 21, 20197 yr From that thread: DEACTIVATE: (by renaming from .bgl to .bgl.off) >>> in \LatinVFR\OrangeCo_KSNA\Scenery LC_1620.bgl.OFF Worked for me. Ben P3D 4.3, Windows 10/64 bit, Intel 6700k @ 4.7 air-cooled, NVidia 2080 Ti Founders Edition, ASUS Rog Maximus VIII Ranger, 16GB G.Skill Ripjaws DDR4 @3200, Phanteks Anthoo Pro Series Case, Samsung 950 Pro M.2 500GB, Sandisk 1TB SATA, Seagate 2TB Hybrid Drive, Cooler Master 700W, 40-inch Samsung 4k TV
February 21, 20197 yr Author 2 hours ago, Jim Young said: There were previous discussions about this issue - I would suspect it an object on the airport that is not compatible. 1 hour ago, bbain1187 said: From that thread: DEACTIVATE: (by renaming from .bgl to .bgl.off) >>> in \LatinVFR\OrangeCo_KSNA\Scenery LC_1620.bgl.OFF Worked for me. Ben Thanks guys! Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU 32GB G.Skill Performance DDR4 SDRAM 3600MHz Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System 2TB Western Digital, NVMe M.2 Solid State Drive
February 21, 20197 yr I have also turned off all the photo scenery files, they don't blend well with the Orbx SCA and the airport looks just fine without them. Dan Downs KCRP
Archived
This topic is now archived and is closed to further replies.