gderreck

Greetings Yes, how silly of me regarding networking. I network my installation. Good idea FSUIPC. Very solid program. Continuously updated. Author probably understands FSX as well as, or better than, the folks who wrote it.

Thanks for the reply. I take your point and can understand why you'll be moving to FSUIPC in the next version. I assume network setup will be ok? How will you do that? WideClient? However, it sort of reminds me of Microsoft in general. We lean so heavily on the products that Microsoft creates, that when they don't perform perfectly, we are extremely disappointed. I'm not pointing a finger at you. But look around the internet at the MS haters. And yet, Google (who makes toys) and Apple (who makes pretty toys) get a free pass. Re the exception. Maybe a small patch to catch it and provide a message to user. I only say this, as some who see that may think you sell broken software, which is not the case. Thanks Graham

Greetings I'd like to update an issue and send information re another issue. I had been having issues with EFB display unit not opening and/or EFB interfering with other networked applications communicating with FSX. -it is so trivial I hate to mention it, but the issue with EFB not opening was this: the shortcut had the correct location of the exe file, but the Start In: directory was my documents folder. I deleted the Start In: and all was OK. -I worked around EFB interfering with other programs by holding off opening EFB data provider and display unit until all other FSX/associated programs loaded. This is FYI for anyone else who may have experienced the same issues. Current Issue If I close the data provider after FSX exits, an exception is thrown by the data provider. Am using version 1.51. The exception information is attached (exception.txt). I must say that FSX does not always close down correctly, and that may have something to do with the EFB exception. However, the exception seems to be thrown no matter how FSX closes down. I should point out that the EFB logs, both in the application file and Users\..\AppData\Local, are blank at the moment, if that means anything. Thanks Graham exception.txt

It's been awhile since I last reported the status of the issue. I got around to uninstalling 1.51 and reinstalling 1.5.0.19605. That seems to have cleared up the problem. I am once again able to use EFB with the other addons installed on the networked computer. This is FYI. If you have any other advice, please let me know. Thanks Graham

Hi Urs Thanks for the reply. When I uncoupled the display unit from the WideClient autostart list, I was able to run the display unit with little difficulty. However, I am now having issues with other networked applications which use simconnect. At random (usually every second time I started FSX), ProATC-X, Super Traffic Board and Active Sky Next; wouldn't connect to the FSX machine. When this happened, I had to restart both machines. I removed the autostart entries in WideClient for the above applications and ran them separately. That didn't work. I was able to eliminate WideClient as the culprit. I ran AI Traffic.exe with nothing running on the networked machine and only FSX on the main machine. AI Traffic.exe made the connection. I then took the EFB data provider out of exe.xml and ran fsx 10 times without the data provider. ProATC-X, Super Traffic Board and Active Sky Next all connected immediately to the main machine on each occasion. I really don't want to fly without EFB. However, I can't have the program disrupting the operation of other software. Until I get this sorted out, EFB will have to stay in the closet. I am going to uninstall the new version of the program and install the version I purchased; to see if that rectifies the problem. Running the display unit on the FSX machine is not an option. As a further test, is it possible to have a second version of simconnect for EFB only? Probably not, but just a thought. In the meantime, perhaps you can help me isolate the cause of this. Thanks, Graham

Hi Urs Nothing in the event viewer. What if I uninstall the display unit and reinstall the full installer? I should point out that I downloaded the update only. Not the new full installer. Also please note, that the display unit is being started by WideClient on the client machine. I don't start WideClient until FSX is up a running on the main computer. Data provider is running before I start WideClient. Thanks Graham

Hi Urs The log files on both computers FSX(data provider) and client(display unit) are both emtpy....0 bytes. This is in the main install folder for each module. Anywhere else I should look? Just wondering...should I download and install the full updated installer on the client machine? Thanks Graham

Really hate to bump my own post. However, the issue in my original post reoccurred. It is random. I would like to know how to solve this. Thanks in advance for your help and support.

Greetings I just updated to version 1.51. Data provider is OK. However, now the display unit will not open. Nothing onscreen, nothing in task manager. Tried shortcut and exe file in EFB folder. How do I fix this. Would like to use the program. No issues before update. Please NOTE: FSX was also running when this occurred. Thanks Graham EDIT: I got back on the machine later. FSX not running. Started data provider. Started display unit on networked computer. Display unit opened and functioned as expected. Would still like to know what might cause the issue.

Thank you William and Urs. I ran the scenery update routine and voila, airport information is now showing FSDreamteam/CYVR/etc, etc, You know, the funny thing is, I could have sworn I ran the routine previously. Obviously not. FSDreamteam CYVR is the Vancouver airport scenery with the highest priority in the scenery library. Is that the criteria that EFB uses to determine which scenery file to use for airport info? I am asking for future reference. Thanks again, Graham

Hate to bump my own post, but is there an answer to this? If not, is there an alternate support option? Thanks Graham

Greetings I have just purchased and am using, EFB. Thank you for creating an excellent product. I do have a question. What criteria does the program use to determine which bgl file to use in order to get airport information. I'll use CYVR as an example: I have FSDreamteam's CYVR. I have it set at a higher priority than Orbx PNW in FSX scenery library. EFB apparently uses Orbx PNW scenery bgl as source of airport information. I fly out of FSDT Vancouver Intl, not Orbx PNW. How do I ensure I am getting the information for the airport configuration I am flying into/out of? Thanks for reading this. Thanks for your help. Graham