December 9, 20196 yr 12 minutes ago, Benjamin J said: That was exactly my plan 😉 I have used the FSJ Hawaii for a long time with much pleasure, even though I must say I'm not a fan of the coloring of the FSJ photoscenery, which I feel is a little too 'white', and it lacks autogen for the most part. So, my plan was to combine FSJ's scenery with OrbX Honolulu, but if this combination causes CTDs, that's gonna be difficult 🙃 The freeware looks great with my PTA preset. I have a feeling that your CTDs are related to a .bgl that need to be disabled. MSFS
December 9, 20196 yr 9 minutes ago, Bigt said: Ben, I forgot to mention this in my original response but your CTD's are probably not uncommon, although I don't know the source. Since installing the ORBX scenery when it released, I have had several (I think 4?) CTD's related to Kernellbase which I never had there before. This struck me as odd as well because I thought kernellbase errors were related to graphic settings? The only airport that I'm getting the kernellbase error on P3D exit is payware NZCH and I have a feeling that it's related to AI and not the graphic settings. AT NZCH there was no AI and after I added my AIG AI fleet, I began to see the error. MSFS
December 14, 20196 yr Author So I've attempted to get to the bottom of this, but regrettably I still have absolutely no idea what's going on. Still only halfway the tests though. A few days ago I saved a standard scenario with the default flight conditions, but moving the start position to PHNL rather than Eglin. After an initial mishap where, apparently, leaving 'use system time for default flight' checked will cause your saved scenarios to revert to your current time rather than what was saved in the scenario, I have not seen any crashes. I rebooted the computer a number of times to ensure a 'fresh' P3D load. I finally installed OrbX Honolulu, and using my saved file everything is still okay. The next step would be to experiment with different dates and times and see if I can isolate a crash situation. But for now, at seems as though it works... Benjamin van Soldt Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case
December 14, 20196 yr I’ve gotten the kernelbase crash after installing fsdt Hawaiian airports. Not sure exactly what’s doing it. On approach at PHOG is where I had it. I was/still am using FSJ Hawaii scenery and never had an issue before. Edited December 14, 20196 yr by JasonPC
December 14, 20196 yr 1 hour ago, JasonPC said: I’ve gotten the kernelbase crash after installing fsdt Hawaiian airports. Not sure exactly what’s doing it. On approach at PHOG is where I had it. I was/still am using FSJ Hawaii scenery and never had an issue before. May be best to ask over on the FSDT forums... Chris Camp
December 14, 20196 yr Author 30 minutes ago, Kilo60 said: May be best to ask over on the FSDT forums... The problem is I’m not even sure whether it really relates to the airport in my case. Kernelbase errors are notoriously hard to track down. Besides, reading similar threads at the FSDT forum the most common response “we started up the sim but had no crash, so it’s probably not due to our airport”. Which is fundamentally unhelpful, but I can’t blame them entirely, given that kernelbase errors sometimes seem to be generated by almost anything. In P3Dv4, these localized kernelbase errors can however relate to problematic AI, so that’s essentially what I’m trying to figure out. Benjamin van Soldt Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case
Archived
This topic is now archived and is closed to further replies.