aivlasoft

Hi Steve, good to hear that you could bring it to work.

Hi Mark, thanks very much for this link.

Dear customer, today we have released version 1.5.1. It contains some improvements due to some reports concerning the DataProviders settings dialog (Navigation data). This latest version can be downloaded from the downloads page. http://www.aivlasoft.com/download/index.html

A proper installation of FSX (and acceleration package, or SP1 and SP2) will do the job.

Steve, Where, or at which step, you would like to point to the FSX folder and why do you want to do so? There is no need to do so, since you only have to select the folder where you want EFB to be installed into. I cannot imagine why EFB should create this folder, except you have selected (or copy/paste it) into that single text box where you can select the installation folder for EFB. Please see the installation and configuration manual, section 1, page 10. As already answered in the other thread you mentioned, the DataProvider is getting the information for the paths to be read from the scenery.cfg on your system. I guess that you should do a clean re-install of your FSX installation.

Hi Steve, if you install FSX there is a screen where you can select the target folder. But this screen (or at least the place on that screen where you can select the path) is not obviously and you must be very careful to not stumble over it. The DataProvider is reading the scenery.cfg file which contains all the paths to the installed scenery files. It they still point to the C-drive although your installation is now on the D-drive, then you should re-install your FSX from scratch.

@ Renaissanceman, according to the forum rules, please sign your posts with your real first name. Thanks. The exception you mentioned is raised by FSX and there is no real solution except trying to re-install (FSX, not EFB). But there is no guarantee that it works without this exception after a reinstall. Fore more information, please read this topic in the FAQ section: viewtopic.php?f=3&t=145

Hi, it seems that the DataProvider cannot find a properly installed "SimConnect" on that computer.

Hi Graham, yes, EFB is proceeding according to the scenery.cfg file.

@all, the problems on the server could be fixed. Downloading of online data works again.

Walt, maybe you additionally want to read this post: viewtopic.php?f=5&t=1600

Marc, you might want to read this one: viewtopic.php?f=5&t=1598

Hi Don, there was a problem on the server which I hope is now fixed. Could you try again? Thanks. [EDIT] It's not yet fixed ... still working on that. [EDIT - 2014-02-11] Server is up and running. No further problems detected. Download of online data works.

Hi Uwe, no problem because of your English, my English is also not perfect I think that EFB is not the right tool to fly under VFR. There is another very good tool called "Plan-G" (http://www.tasoftware.co.uk/planG.htm), or maybe the browser based application http://skyvector.com/ could be of help.

Graham, try to not forget that after every change in your FSX installation you have to run the "Scenery data update" from the DataProviders menu. Only this way you can be sure that the DataProvider is accessing the right data files according to your current installation.

Walt, I don't own the AAXE but I assume that it's the same reason as in other aircraft of this realism level. In r/w the flight plan does not include the procedures because they are depending on the current weather situation and therefore runways in use. Although if you save your plan with the "save procedures" attribute, they are not forwarded to the AAXE file. You have to select the procedures from the MCDU in your aircraft, as soon as you have received your clearance.

Luis, if you ran the full setup and you have selected to install the AIRAC cycles then they are located in your FSX-installation folder. There you will find a folder named "AivlaSoft" and below this folder the two navigation data folders can be found.

hi Simon, Thanks for your detailed information. Very interesting and of course your environment gets me a bit jealous No, I didn't program any fixed numbers where's the limit. To be honest the maximum of DisplayUnits that I ever have connected was four. So I must assume that it's only a matter of the performance of your network and the computers you are running within. IIRC, all of what is displayed in the status bar should also be logged in the logfiles. They are usually located as follows: C:\Users\[username]\Documents\AivlaSoft\EFB\Logfiles

Hi Simon, thanks for the error message. It's even more confusing now. That message let me assume that the problem lies beyond EFB's scope. It's also interesting that you can connect with a DisplayUnit on another computer but not on the same computer. Since I have no experience with BootCamp I cannot say whether this is a possible cause for the problems or not. But there is another thing that might be relevant: In the logfile I can read that you are using an IP address in the range of 10.0.0.x which is definitely not the range for private (class C) networks. Private networks should start with 192.168.0.0. For more details see here: http://en.wikipedia.org/wiki/Private_network Maybe the combination of Windows Home with the class A network address could cause the problems?

Firas, I guess one thing has been left: try to update to the latest AIRAC cycle, or at least re-download the latest revision of the currently installed cycle.

Unfortunately not. Most probably the new installation of EFB doesn't help because the cause of the problem is beyond EFB.

Hi Simon, thanks for the detailed information! As far as I can read from the error message "system.invalidoperationexception cannot accept new outgoing messages ..." it has to do with the Queuing of outgoing messages. Queuing is a functionality of the .NET libraries and I use it to send messages. Unfortunately I cannot read the entire error message from your screenshot and it's also not logged. Next time when this error happens could you try to copy/paste the error message? Especially the part after "... because" could be interesting. You report that you have installed EFB on a NEW Win7 computer. Maybe there is something missing on that machine?

Hi Ray, unfortunately it is not yet in beta. I'm behind the schedule ...

Hi Oliver, thanks for the screenshots. It looks like you have selected another Windows color schema than "Windows 7" (maybe "classic", "basic" or similar).