Hey Guys,

Have a problem that I just can't figure out, and hoping some of you might have seen this, or know what's causing this. 

I have had FSDT's PHNL for ages, all this time working fine. When I installed OrbX Honolulu, I started getting Kernelbase.dll crashes upon loading at PHNL. I load with the default F22, it always CTD'es with a kernelbase error, as per the Event Viewer. I googled to see if I could find anything about a Kernelbase.dll error specific to PHNL, both as FSDT and the OrbX forum, but came up empty-handed.

Finally couldn't figure out what was causing this, so I did a couple of things:

1) I uninstalled both FSDT PHNL and OrbX Honolulu, and then all was fine again. Honolulu loads well in a default state.

2) Installed OrbX Honolulu by itself, and this also seems to work just fine.

3) I then uninstalled OrbX Honolulu and installed FSDT PHNL instead - this also works fine. No crash.

4) here's the kicker. I now reinstall OrbX Honolulu, but don't change any settings in the configurator: everything seems to work fine. No CTD.

5) Finally, I run the FSDT LiveUpdate, and configure OrbX Honolulu to be compatible with FSDT PHNL. Now, everything was just fine.

 

So I was happy, thinking it was all fixed. in the meantime I installed a couple other OrbX addons as well as some things I bought at Black Friday, notably some UK2000 airports.

6) Now I decided to load at PHNL again to see if it still works - CTD.

7) So I removed OrbX Honolulu, and now everything works again...

 

I have not reinstalled OrbX Honolulu since, but I expect that initially it will work fine and later it will cause crashes again. It seems that there is something problematic in the interplay between these sceneries perhaps, though I'm thinking that it's more likely to relate to OrbX Honolulu, given how long I've been running FSDT PHNL without issues. The newcomer here is OrbX Honolulu, after all. But, again, I'm grasping at straws. I have no idea what the potential issue might be...

Anybody have any ideas?

One thing to add: it's easy to think that whatever I installed last is probably the culprit, but I heavily doubt that. The fact is that it started crashing at PHNL before the most recent installations, plus the only sceneries would have active at Honolulu are OrbX Honolulu and FSDT PHNL, plus OrbX's OpenLC and vector and FreeMesh. It seems highly unlikely that other sceneries would have an issue. Also, all my AI is AIG's OCI, so should certainly not contain and FS9-era models or files. The mystery to me is how specific the Kernelbase.dll is... Normally this is a somewhat vague error that's hard to track down, but here loading at PHNL crashes P3D every single time. Makes it seem like there is a very particular file that's causing the error, but I have no idea what it might be.

Hello Benjamin,

My issue(s) were a little different...

I, too, have had FSDT PHNL for ages...about 6 years. I was never able to fly into PHNL, but, I could depart without issues. Three months ago, I bought Orbx Honolulu and found the same issue...CTD on approach...every time. I thought it may have been related to using time acceleration...off/on didn't make any difference.

My CTD's on approach were occurring with both the FSLabs Airbus as well as the PMDG 747-8.

Recently, I upgraded my motherboard and CPU (8700K) and still had the same issues...departing, no problem, CTD on approach (kernelbase.dll).

After I updated my motherboard/CPU, the symptoms changed a little bit...on approach, the first thing that would happen was FSUIPC would "freeze". I could use keyboard commands but nothing operated through FSUIPC. Eventually, toggling between views would cause a CTD.

I started to look at the WEP files and Realtek was standing out as a possible contributor. (I run a SB THX sound card...don't use the internal sound for P3D.)

I disabled/removed any reference to Realtek on my SSD and my problems went away!!! I tested several times with both FSlabs and PMDG and all was good.

I re-installed my Realtek drivers (to determine if it was the cause) and my CTD's returned as well.

For my system, the Realtek drivers were an issue...I don't understand why.

I'll just have to watch after any Windows 10 updates...but this worked for me.

Rob

Well, this is most discouraging. I bought Orbx's Honolulu today and also have FSDT PHNL.  Am out of town until tomorrow, so will install once I return home. I use internal sound, so I hope the problem does not exist with Realtek drivers. Not good. Pete

2 hours ago, retnavycpo said:

Well, this is most discouraging. I bought Orbx's Honolulu today and also have FSDT PHNL.  Am out of town until tomorrow, so will install once I return home. I use internal sound, so I hope the problem does not exist with Realtek drivers. Not good. Pete

Don't be discouraged too quickly. Fact is I've not heard anybody else with this particular problem, so it might very well be specific to my setup... Lord knows right now 😛

@rmeier Yeah that does sound quite different from my issue. I think I used to have Realtek drivers but I uninstalled them long since 😉 Glad you got it sorted! I'm trying some other things again, including a thorough investigation of all my AI. I have loaded PHNL and right now it works fine at this particular day and time. I will use it as my benchmark going forward to take into account the possibility that a corrupt AI aircraft is causing this. Will report back if I find anything.

Benjamin, in your "\FSDT\Addon Manager\FsDreamTeam\PHNL\scenery" folder have you disabled the 3 following files by changing the extension to .OFF(required for ORBX Honolulu compatibility) ?

cvx_PHNL.BGL.OFF
PHNL_Elevation.bgl.OFF
PHNL_Terrain.bgl.OFF

After doing it, I added a DONTUPDATE file in this scenery folder to prevent FSDT LiveUpdate from putting back those BGLs during an update.

I too have ORBX Honolulu, Global Base, OLC_NA, Vector and Freemesh installed and have no CTD in PHNL, despite having Realtek drivers for my onboard sound (ALC-1220 with drivers 6.0.18507 from Asus).

If you already did it, then I have no idea what is causing your CTD.

@NBouc, thanks for your suggestion! When I initially got the crashes, I had disabled those files. On the second round of crashes I had not disabled them, so it doesn’t seem to relate to whether these files are active or not, sadly...

9 hours ago, NBouc said:

After doing it, I added a DONTUPDATE file in this scenery folder to prevent FSDT LiveUpdate from putting back those BGLs during an update.

DONTUPDATE file? I need this file! 😀

Benjamin,

I'm only following your thread because for the life of me I still don't understand why customers have bought FTX Honolulu City when there a free version of all the islands. IMHO, Oahu looks better in the freeware version. I even managed to get all the FSDT airports to blend beautifully with the freeware photo scenery version. It's one of my favorite regions because the coastlines and colors look amazing!

You should try the freeware version.

Jose

17 minutes ago, DJJose said:

Benjamin,

I'm only following your thread because for the life of me I still don't understand why customers have bought FTX Honolulu City when there a free version of all the islands. IMHO, Oahu looks better in the freeware version. I even managed to get all the FSDT airports to blend beautifully with the freeware photo scenery version. It's one of my favorite regions because the coastlines and colors look amazing!

You should try the freeware version.

Jose

How does downtown Honolulu look with this freeware as far as buildings and autogen are concerned?

1 hour ago, Bigt said:

How does downtown Honolulu look with this freeware as far as buildings and autogen are concerned?

The city in the FTX version is obviously much better than the freeware. But that's about the only thing that is better. The texture colors and coastlines are better in the freeware version. Just check out the user pics in the FTX forum and compare them with the freeware pics.

Edited December 9, 20196 yr by DJJose

Thanks for the response. Seems like the best of both worlds is to combine ORBX Honolulu city with the freeware for the rest of O'ahu. And of course FSDT PHNL for the major airport scenery.

Just now, Bigt said:

Thanks for the response. Seems like the best of both worlds is to combine ORBX Honolulu city with the freeware for the rest of O'ahu. And of course FSDT PHNL for the major airport scenery.

YEP! There's info on how to do this on the FTX forum. I do NOT have the payware version, but I might get it just to add the city to my current scenery.

4 minutes ago, Bigt said:

Thanks for the response. Seems like the best of both worlds is to combine ORBX Honolulu city with the freeware for the rest of O'ahu. And of course FSDT PHNL for the major airport scenery.

Check out what I managed with PHLI. See pics:

 

8 minutes ago, DJJose said:

YEP! There's info on how to do this on the FTX forum. I do NOT have the payware version, but I might get it just to add the city to my current scenery.

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 🙃

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?