aivlasoft

The important thing is to not run both installers simultaneously. Just complete the Server installation, then start the Client installation, or even vice versa. It is not relevant whether you run the DbBuilder immediately after successful installation of the Server, or if you run it after you also have installed the Client already.

Please create and upload a support file from the Client and one from the Server.

Please upload a support file from the Server. Are you talking about changes/enhancements which you created using the DbBuilder's function "Enhance / Update runways" ?

Yes, of course. Sorry for the typo. Nevertheless, I'm still trying to find a workaround.

Try to do the following steps: Quit any running instance of the Server and the Client(s) Run the uninstaller from the Windows Menü, for both the Client and the Server Reboot computer(s) Download the latest complete installers from the download page of our website: https://www.aivlasoft.com/download.html Run both installers, one after the other, and make sure you run the installers as administrator

Hi Colin thanks for reporting. It seems that the 8.33 kHz COM frequencies got another row-code than the legacy 25 kHz frequencies and therefore the 8.33 kHz frequencies will not yet appear on the radio panel while the legacy ones do. I have to fix this with next update.

Hi Steffen, did you already have a look at the file 'add-ons.cfg' in 'C:\ProgramData\Lockheed Martin\Prepar3D v4' ? Are there any suspicious entries? Could you please create a support file and upload it here, or - if you prefer - send it to support@aivlasoft.com.

Hi Andrew, it has not resolved itself, it was necessary to first update the EFB AIRAC data using the Navigraph FMS Data Manager, not only Navigraph Navdata Center which updates MSFS navdata but not EFB navdata. To keep your system up-to-date you always have to update both, Navigraph AIRAC cycle for EFB a n d for MSFS.

Now that we have read that X-Plane shall be released in December we decided to release the update 2.3 #135 which supports X-Plane 12.

Today we released the new update 2.3 (build #135) which contains the following improvements: Changes required to support X-Plane 12 Minor improvements for better procedure depiction MSFS SU11 compatibility regarding airport names (requires a rebuild of all databases) Latest online data files for VATSIM and IVAO

Unfortunately there is now work around yet. G3000 is still working as expected but not the G1000.

Will be fixed with next update. Next update is already on final now.

There is no distinguishing between certain errors and therefore the Server brings itself to front whenever an error is being logged.

Great to hear that everything is now working as expected.

The folder C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\AIRAC contains two subfolders: Each of them can hold a navdata cycle. From your screenshots I can see that you are a user of Navigraph FMS Data. On the screenshot with the logfile excerpt I can see that the DbBuilder also is creating a database with Aerosoft NavDataPro. If you don't intentionally use Aerosoft too, then I recommend to ... 1) Delete the content of the folder 'Aerosoft NavDataPro' 2) Delete your database using the 'Delete' button in the DbBuilders dialog 3) Create a new database using Navigraph FMS data It might be that then the warning does no longer appear.

Thanks for the screenshot. This is a completely different message than what you described in your previous posts. I always thought you are talking about a program update to version 1.22. This message is telling you that you have AIRAC cycle 2210 from Navigraph installed in the folder C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\AIRAC\Navigraph FMS Data, but obviously you did not yet rebuild your EFB database using the DbBuilder function "Update Navdata". As soon as you have updated the database, this message will no longer be displayed.

Could you please upload a screenshot where I can see the warning message?

Did you already check the content of the file C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\Updates\latestVersions.txt

Hi Jim Then I assume that you did not run the auto-update instead of having downloaded the installers from the website and ran them manually. Is that correct? If the installers ran without error then the registry keys should have been altered to the new location. Aren't they?

From the logfiles I cannot see a cause for this. Maybe it comes from an old 'latestVersions.txt' file which is located in the 'Updates'-folder in the Server's/Client's data structure. Do you run an automatic backup software which might replace this file? Zurich is the default location after a fresh installation. As long as FSUIPC does not connect with the simulator, a new position cannot be received and therefore the closest airport cannot be determined. Please check whether the latest and proper version of FSUIPC is installed on your computer. From the logfile I can see that the connection with the Client is established. It should not be possible to run two instances of the Server at the same time on the same machine. How did you manage this?

Thank you for your request. Currently we do not have plans to introduce this functionality in the near future, but we will keep it on our radar and probably reconsider our decision if we get more requests regarding this functionality.

Did you already read the announcement here: https://forum.aivlasoft.com/topic/6938-x-plane-12/

Timeout means that the network seems not to be able to transport the file airport.bin.zip within a certain time frame. I had this too several months ago and finally it turned out that an older network cable was the cause. I replaced the old cable through a new one and everything was working again. In other words, check your network infrastructure (router, firewall, antivirus, cables, maybe other recently installed software, any other configuration changes etc.)

If you create a flight plan using the 'copy/paste' window (see manual for details) and you enter a waypoint as described above (N57.15W49.661666) this will be properly recognized, but you cannot enter such a coordinate waypoint using the 'Insert' dialog. The insert dialog only allows to select from, or search for waypoints in the currently loaded database.

Thanks, this is exactly what I tried to explain in my post above.