Chevy

I think you're absolutely right, Guenther. EFB visualizes the problem but it seems that it cannot be blamed for being the problem. I wasn't aware of the behaviour of ASE and I think I should test this on my machine. The scenery I have problems with is Aerosoft's Germany VFR (esp. region North). But I cannot identify any problems there and even at Aerosoft there are no errors reported from other users. So I really don't know where to look at exactly. So Urs might be right: we have an idea of the error but we cannot track it down. Therefore it might help to fiddle around with FSX or to establish workarounds (FSUIPC in your case, uiautomationcore.dll in other cases, avoiding special airports in conjunction with EFB in my case). Really strange problem... Christian

Guenther, as I wrote above I already came across your topic over in the FSUIPC forum and I installed the latest version of FSUIPC just to see if it helps although I don't have VRInsight modules. Unfortunately for me the error persists. I could rule out FSUIPC as a possible culprit. (I got a crash even when totally removing FSUIPC.dll from my modules folder. ) Even without any other addons using the simconnect interface I got HRESULT: 0xC000014B, but only when flying over a special photoscenery. Disabling it or flying in other areas never showed me the error since. Perhaps I'm just lucky (because others encounter the error in different corners of the world), perhaps the scenery files are broken or erroneous - I don't know. I just seem to avoid the problem but I'm afraid it's still there. Somewhere... Cheers, Christian

Hello Travis, thanks for looking into this. There has been some mail contact between Urs and me in the meantime and he's got some simconnect logfiles from me. Nothing eye-striking in there... At the moment I can say that it has nothing to do with Couatl, Addon Manager, FSUIPC or EZCA - at least on my system. I can track it down to a scenery product: Germany VFR from Aerosoft. If I turn this one off, the error is gone. If I turn it on again I can reproduce Simconnect errors. I have no idea of a technical explanation as I don't know what photo sceneries and simconnect do make use of each other. Perhaps Urs has an idea. AFAIK I'm fine at the moment but I will keep on testing in other areas and try to find out whether the simconnect woes will hit me again. Cheers Christian

I think I should give it a try. Although I never had problems before with anything running beside FSX... And at the moment my problems seem to be tracked down to a special scenery. Thanks anyway. I'll report back when I will have given it a try. Christian

Hmmm, Frans, sounds very interesting and promising. Thanks for sharing this. I simply wonder whether this is an overall performance tweak or just the solution to the net framework hangups (Exception from HRESULT: 0xC000014B). I don't see a direct connection between your tweak and the error. What is that uiautomationcore.dll good for? What is it intended to do? And do I run any risk in trying your tweak? If I don't like it it seems i can simply restore the backup files, right? Cheers Christian

Hmmm, very weird that matter... There are others who share your problem. See the other thread here: http://www.aivlasoft.com/support/viewtopic.php?f=5&t=144 What sceneries do you fly over? I'm sure this has nothing to do with other modules making use of SimConnect (I tested with EZCA, FSUIPC and AddonManager - they don't play a role). Don't know about that task bar / screensaver thing. But last night I deactivated some heavy load photoscenery I was flying over (Germany VFR to be precise) and was able to complete a flight with EFB for the first time without encountering the hangups. I don't think that it's a problem of a specific scenery but perhaps FSX runs out of system resources and SimConnect terminates as the "weakest part" in the system? Just an idea from a non-expert... Although - if I get you right you flew over water at the time of the hungup. That doesn't fit to my theory... It's so strange... Cheers Christian

Hi @ all, I tried exactly what Rob suggested but it didn't help... Rob, was your solution succesful for your FSX? Did you get rid of the crashes? Urs, I sent you a couple of logfiles (two mails with different files from different flights) and hope you can do anything to fix this matter. It's simply not possible to end a flight at the moment with EFB running. I keep my fingers crossed that there are SimConnect gurus out there finding Columbus' Egg... Cheers Christian

Travis and Urs, unfortunately I'm out of time for flying for a few days. So I cannot answer all your questions at the moment. What I can say so far is: I'm running FSX with Acceleration Pack. I have numerous addons. The only ones that were running when the freeze occured were FSUIPC (registered) and EZCA (EZdoc Camera) I was not aware of a special use of FSX at the moment of freeze (no slew, no pause). I was just changing frequently between FSX and EFB (running on the same PC but on a second monitor, both in windowed mode). The freeze happened about 10 minutes after takeoff. I don't know yet if that is reproduceable. The start sequence was roughly what Rob suggested: 1) FSX, 2) load an aircraft (Carenado 185, no default aircraft!), 3) EFB Data Provider, 4) EFB Display Unit, 5) creating an activated route in EFB Surely I will comment on that in depth as soon as I have time again to get back to my home PC. Thanks for looking into this! Happy weekend! Christian

Hi Urs, unfortunately the HRESULT:0x000014B error hit me, too. After configuring a new computer system I reevaluate EFB under Windows 7 64bit and strongly love to buy it because it's a great program and one of the best addons ever developed for FSX. Too bad that the error occurs yesterday so that I'm not sure anymore whether I can spend money for EFB or not. I'll have to experiment in the next days what might be the culprit on my system. In the meantime I keep on hoping that a fix for this undocumented error might be found. Seems that a number of users are affected. I keep my fingers crossed. Cheers Christian

Thanks for your prompt inquiries. Don't bother: I'm looking forward to getting the hotfix and I'll keep on testing EFB next week. Happy weekend Christian

Hi Urs, as promised I just sent you my logfile via email. Hope to see a solution soon. Thanks a lot and Grüezi from Germany. Christian

Hi Urs, thanks for going into this. I will email you the log files today evening (as I'm currently in my office and have no hands on my FSX installation ). One thing I tried yesterday: I deleted the APX16190.bgl file and re-run the DataProvider. There were still error messages (you will find them in the log file) but this time the DataProvider did not shut down completely or aborted. It restarted as it should and I was able to start the display unit afterwards. In the end I copied the APX16190.bgl back to its original place and it seemed to work. Nevertheless it's not a satisfying workaround to perform each time. And the remainig errors prove there seems to be something wrong still. Cheers Christian

Hi there, your product seems exactly what I've been looking for and before I buy it I wanted to evaluate it under my Windows 7 (Beta) OS. I followed your installation and configuration manual exactly but every time I want to run the DataProvider.exe for the first time it aborts with the following error after having finished reading Flight Simulator data (c/p from the DataProvider_log.txt): I tried it several times, tried a reinstall of EFB but no luck. I don't know what might be wrong with the file "APX16190.bgl" because my FSX is standard (FSX + AccPack), only with Ultimate Terrain and some OrbX Sceneries. Even temporarily removing the bgl from the folder doesn't help. Any idea how I could make EFB run? Any help is highly appreciated. I can provide you with the full log.txt if helpful. Cheers Christian Fürst (Germany)