aivlasoft
-
Posts
5,910 -
Joined
-
Last visited
Posts posted by aivlasoft
-
-
Hi Ray,
QuoteI did copy my Documents\Aivlasoft \Server folder from a backup
Did you do this before you opened this thread or after?
As far as I can conclude from the logfiles, you did copy an old data backup from August 2022, this is when Server version 2.3 #133 was the latest version. Between #134 and #135 a change in the database format took place and all databases had to be rebuilt then. Currently version 2.3 #138 is running and this version cannot cope with this old database.
To solve it, please do the following:
1) Quit Server, if running
2) Locate the following folder in the Server's data folder: "DbBuilder\Ready"
3) Delete the entire folder "Ready"
4) Start the DbBuilder and rebuild the database(s)
Hope this helps.
-
Hi Ruedi,
missing or not properly depicted online traffic is difficult to investigate. But usually it's a matter of the current settings. Did you already carefully read the user manual "DE Client.pdf", starting at page 130.
-
Reinhard,
if the Client wants to be connected to the IP 192.168.2.105, but the SIM PC's IP-address is 192.168.2.106 than obviously the SIM IP was changed recently. You can change the IP address of the SIM PC in the Client's settings file (clientSettings.txt).
Quit the Client, locate the Client's settings file (for a default installation the file is located in 'C:\Users\<username>\Documents\AivlaSoft\EFB2\Client\Settings'). Open the file using any text editor like Notepad.exe, then look for the '[Network]' section and then change the 'ServerComputerName = 192.168.2.105' to 'ServerComputerName = 192.168.2.106'. Instead of setting a fix IP-address you can also set the SIM computers name. Then save the file and start the Client.
-
STOP flooding all channels, please. We are not exclusively working for you!
You wrote an email to support, you wrote a PM to myself and finally you opened a new thread, always with the same question. I replied to your email, but you didn't answer my questions.
-
This update contains minor bug fixes and stability improvements.
-
I can only repeat what lonewulf47 already mentioned above. Just pressing "Save" will only change the colors for the current session, after a restart the colors are reverted back to default. You have to create your own color schema by pressing "Save as", and also press "yes" when you will be asked whether you want to have this new color schema as your default schema.
-
Page 23 in Client manual.
-
Did you follow the suggestion "switch profile filter off"? I guess that the airport LGPX has now a runway which is too short for the currently loaded A/C profile. Therefore the yellow hint appears. If you switch off the profile filter, then LGPX will be shown by EFB.
-
Did you rebuild the database already since the installation of the new airport? Maybe there are now two airports with the same ICAO code in MSFS?
-
I was expecting this answer. Unfortunately FSUIPC7 does not provide a meaningful name either.
For the time being I would use the name 'aircraft.ui_model' in the profile. As long as there is no other such name, loading the profile will work.
-
No worries 🙂.
-
Could you please provide a screenshot?
-
From the logfile I can see that there seems to be a valid path to the aircraft.cfg. If the file is not encrypted, EFB is reading the ICAO code from this file. Could you please upload this aircraft.cfg, thanks.
-
Did you already read the announcement here: https://forum.aivlasoft.com/topic/7600-update-23-137/
-
Today we have released a new update v2.3.137. Please read this information carefully.
MSFS - Loading flight plan to GPS
With MSFS System Update 11 (SU11) and Aircraft & Avionics Update 1 (AAU1) unfortunately parts of the GPS-Flight plan handling logic have been changed by Asobo/WorkingTitle (WT). Therefore, it seems that it is no longer possible to load the flight plan "EFB_current_gps.pln" automatically (using FSUIPC7) to one of the default GPS-Systems like G1000/3000 and/or GNS430/530, neither before the flight, nor while in flight.We regret this very much but we do not have a chance to change this behavior of MSFS. It seems to be the intention of Asobo/WT to no longer support this part of the interface although it is still described in the SDK. Maybe somewhere in the future, with one of the next MSFS-Updates it will work again, but we simply do not know this at the moment.
However, with the latest EFB update 2.3.137, it is still/again possible to load the "EFB_current_gps.pln" file in the world map of MSFS before your flight take place. This way a flight plan can be created in EFB and then loaded to MSFS.
Because we cannot anticipate whether loading the "EFB_current_gps.pln" via FSUIPC7 has an impact on the behavior of the GPS-Systems, and if it has, what kind of impact it will be, we recommend to temporarily suspend this function as follows:
- After first time running the Server v2.3.137, quit the Server.
- Running and exiting will create a new line in the file "serverSettings.txt" which is located in the folder "Settings" in the Servers data structure.
- This new line reads as follows: DoNotLoadMsfsGpsPlanToSimulator = False
- Change the value from 'False' to 'True', and then save the file.
- Now start the Server and it will still create the file "EFB_current_gps.pln", but it will no longer load it to the MSFS simulator.
Resetting the value from 'True', back to 'False', will reactivate loading the plan to the GPS-system via FSUIPC7.
GTN750 from PMS50.com
If you are using the GPS-System 'GTN750' from PMS50.com (premium version only), we have implemented a possibility to get a copy of the "EFB_current_gps.pln" as "fpl.pln", whenever the flight plan in EFB has been changed.According to the PMS50 documentation the file "fpl.pln" must be located in the folder "..\Community\pms50-instrument-gtn750\fpl\gtn750".
In order to tell EFB where the fpl.pln file has to be saved, you have to manually edit the file "serverSettings.txt" which is located in the folder "Settings" in the Servers data structure. To edit the file, use any text editor like Notepad.exe or similar. Open the file and search for the line which starts with "Pms50Gtn750FplFolder = ". After the equal sign add or copy/paste the absolute path to the folder "..\Community\pms50-instrument-gtn750\fpl\gtn750". -
NEXRAD only covers the US, not the entire world. As far as I can read from their page the data is not current, just archived.
We are looking for a worldwide data source of live data (precipitation radar data or images).
-
Please comply with the forum rules especially 2.1. Thanks.
-
There is no mobile app available.
-
As you might have overseen, EFB is a .NET-application which only runs outside of the MSFS process.
-
It is not yet defined. We are still testing.
-
First of all, please do not send emails to support and at the same time you start a new thread at the forum. Just one of them, please. thanks.
As I already replied to your email, it looks that some required folders of the simulator installation are missing. Try to uninstall the simulator and then re-install it.
-
Quote
So for issue #1, will the workaround implemented for issue #2 alleviate this as well?
Yes, it should.
2 hours ago, Berzerker said:Either figuring out the proper addition to add for the A320 profile or having a way to disable the automatic profile selector would be a more-than-good-enough workaround for now.
You can find the required name in the Server's log file (see next screenshot as an example). Just add the name which is displayed to the already listed names in the respective profile.
-
Obviously there are two different issues discussed in this thread. First, the name of the currently loaded aircraft in MSFS, and second, the names of AI aircraft provided by MSFS. Regarding issue #1, I have the latest version of Fenix' A320 running (v1.0.6.146) and FSUIPC7 v7.3.19 is installed. On the next screenshots you can see that the ICAO type designator is properly detected by EFB:
Regarding issue #2 I can only say that the malformed names are the names of AI traffic and not the name of the own ship. Although these names are created beyond the scope of EFB, I have implemented some 'filtering code' which is trying to extract the ICAO type designator from these malformed names. It will be available with next update which is planned to be released soon. Until then I don't see a workaround except to pause the AI generation by the aforementioned third party tools.
-
What you experience is most probably an old story which has its origin in the BGL data structure. I had to search for this old thread where it was discussed some years ago:
https://forum.aivlasoft.com/topic/2956-missing-runway-11-29-lfbd-efbv2
And here is the answer to all of this:
https://forum.aivlasoft.com/topic/2956-missing-runway-11-29-lfbd-efbv2/?do=findComment&comment=18017
EFB V2 ATC Control Area Inaccurate
in EFB v2 - Support forum
Posted
Sorry, but I don't know which data is used by VATglasses. EFB is using the free "VATSpy" data which is available from GitHub. It might be that this data is sometimes outdated but unfortunately I don't know of any other source for free and almost accurate and even regularly maintained data.