aivlasoft
-
Posts
5,914 -
Joined
-
Last visited
Posts posted by aivlasoft
-
-
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
52 minutes ago, jfmitch1716 said:I had both the server and the Client on drive D. When I updated I forgot this and they ended up in C drive.
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?
54 minutes ago, jfmitch1716 said:How can I get rid of the files on D drive plus the registry key would be pointing at the wrong set of folders.
If the installers ran without error then the registry keys should have been altered to the new location. Aren't they?
-
Quote
Every time I start EFB server, it tells me that a new version is available (build 1.22)
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?
QuoteAS-2210/R1 is now loaded but it opens at Zurich every time and does not connect P3D and the EFB Client
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.
5 hours ago, jfmitch1716 said:I did have two instances of each (the server and the client) but changed that.
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.
-
On 10/20/2022 at 1:54 PM, CTN808 said:
Thanks, this is exactly what I tried to explain in my post above.
-
You have to distinguish between 'static' data and 'dynamic' data. 'Static' in this regard means the database which contains information about the airports and navaids, while 'dynamic' data means position and attitude data provided by X-Plane via UDP. Both are required for proper operation.
The dynamic data exchange seems to work with XP12 already with EFB 2.3 #134, while the database can only be created after the next EFB update 2.3 #135.
-
As I already mentioned here, the current EFB version 2.3 #134 does not yet support XP12. To fully support XP12 some code changes must have been done. Please be patient, EFB 2.3 #135 will be released asap after the official release of XP12 (except there will be some last minute changes in XP12 which have to be adapted first in EFB).
-
Good news, forwarding the flight plan is also working with XP12. It seems that the file format did not change.
Let's hope that it will not take too much time until the official release.
-
As mentioned earlier, here is a first state about the integration of X-Plane 12:
Some code changes in the DataBuilder's code were required, because the 'global scenery airports' got a new location. Finally we are able to create a new XP12 database. Also the UDP connection is now working and the Server is receiving the aircraft position and other aircraft data. So far so good.Next we will test are the flight plan features and then we will inform again here.
BTW, do not except the new version 2.3. #135 BEFORE X-Plane 12 will be released. EFB does not support 'early access' (aka Beta) versions for obvious reasons.
Thanks for reading.
-
After several tests we came to the finding that something must have changed on Asobo's/MS' side. The waypoint type 'User' seems to no longer be treated the same way as before SU10. One can easily test this as follows: Create a simple flight plan in MSFS, from one airport to any other airport and add one or two user waypoints. This flight plan will now be displayed properly. Then save this flight plan and close MSFS. Now restart MSFS and try to load the flight plan which have been created before. You will see that the airports are still displayed properly while the user waypoints between the airports are now depicted at the Northpole. The legs between the airports will be depicted 'straight upwards' to the Northpole.
However, it seems that a flight plan which contains only 'official' waypoints such as airports, navaids and/or fixes, can still be created and forwarded by EFB. Such a flight plan will also be depicted properly in the G1000 NXi from Working Title.
As long as MSFS cannot read or interpret the user waypoints it creates itself, there is nothing we can do from our side to remedy the situation.
-
Maybe the option button "ACFT". These option buttons are depending on the chart type, which means you can have it ON on the ground chart, but OFF on the world map and vice versa.
-
It seems that it has to do with the recent SU10. We are investigating ...
Database builder not updating to AIRAC 22/11
in EFB v2 - Support forum
Posted
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.