Jump to content

aivlasoft

Administrators
  • Posts

    5,930
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Hi Janek

    Usually such an issue is because of new or changed callsigns which are not yet reflected in the data files. I definitely need more information like screenshots and other details for further investigations. Please also create a support file from the EFB Server when the issue happens.

  2. Hi Pat

    all data from and to the simulator will be read/written via FSUIPC. Setting the transponder code works for all default aircraft and most of all payware aircraft. However I cannot say whether FSLabs is using other ways to set the transponder code. Before asking this question in the FSLabs support forum please make sure you have updated EFB Client and Server to the latest version 2.2.130 and please make also sure to have the proper FSUIPC version installed. If it still doesn't work then, I suggest to ask the question in their forum. Thanks.

  3. Hi Peter,

    it seems that these two lines are taxiways which have been (unintentionally) added by Asobo/MS.

    EFB is depicting closed taxiways in red (by default). You can change the color settings for closed taxiways to 'transparent', then they will no longer be visible, but this will then be true for all closed taxiways on all airports.

     

  4. Today we released a new update 2.2.130.

    This update will fix a bug which prevented to save and restore the callsign under rare conditions.

    This update also introduces the new MSFS flight plan data format which slightly differs from the previous FSX format.

     

    IMPORTANT:

    If you have installed FSUIPC7, version 7.2.12 or 7.2.13, please read this topic from the FSUIPC support forum:

    https://forum.simflight.com/topic/93661-fsuipc-7213-provides-wrong-path-for-flight-plans-folder/

     

  5. Today we released a new update 2.2.130.

    This update will fix a bug which prevented to save and restore the callsign under rare conditions.

    This update also introduces the new MSFS flight plan data format which slightly differs from the previous FSX format.

  6. Hi Jean-Claude

     

    If I understand what you described above then the EFB Server location (on Client side) was given as an IP-address, not as a computer name. After the connection between the Client and the Server did not work, you changed the Server location from 'IP-address' to 'computer name', then the connection worked. Am I right so far?

     

    A possible explanation could be as follows (I'm trying to explain it in layman terms):

    The network configuration of each computer in a local network allows to select whether the IP-address of the computer is fixed or variable, where 'fixed' means that you assign an IP-address manually, and 'variable' means that the IP-address is assigned from an instance outside of your computer, but within your local network. This 'instance' is called 'DHCP server' and usually (in a private home network) this is handled by the router. Most of the routers today have a built-in DHCP functionality.

    I assume that your computers are configured to get a dynamic IP-address from the DHCP-Server. IP-addresses provided by a DHCP-Server will have a so called 'lease-time' which is more or less an 'expiry date'. In a simplified manner this means that the EFB Server's IP-address will change from time to time.

     

    I assume that in the scenario which you described, the Server got a new IP-address and therefore the Client could no longer establish a connection using the old, expired IP-address.  As soon as you changed the EFB Server's location from 'IP-address' to 'Computer name', the current and valid IP-address for the EFB Server was requested internally from the so called DNS service (domain name system) which 'looks' for the IP-address of a given computer name. This service will always provide the current IP-address and therefore it is more flexible to define the EFB Server's location as a 'Computer name' than as 'IP-address'.

     

    There are also possibilities to configure a DHCP server in a way that some IP-addresses (or even IP-address-ranges) will not be changed, but that's another story.

     

    On 11/25/2021 at 4:42 PM, Trinidad said:

    BUT amazingly (MSFS being closed at that time), EFB showed me the map of the airport I just took off from and the exact location

    Don't forget, even if the Client is not connected to the Server, the Server 'knows' where your aircraft is. As soon as the Client connects with the Server, the Client receives the current position and data of the aircraft. This is one of the advantages of a 'Server-Client' architecture.

     

    Hope this is not too confusing ...

     

  7. Hi Orest

    thank you for bringing up this question. I did some tests to make sure I will give you the right answer. While testing I found a bug which I must have overseen in the past. The callsign will only be applied to a flight plan when this flight plan was imported as an ICAO formatted plan. I have to apologize for any inconvenience and I will fix it with the next update. It seems that I was too much focused on importing flight plans from SimBrief or PFPX when I developed this feature.

     

    For the time being the callsign is only applied to the current EFB flight plan if the flight plan was imported in the ICAO flight plan data format as displayed here:

     

    (FPL-SWR1662-IS
    -A20N/M
    -SDE2E3FGHIJ1RWXY/LB1
    -LSZH0740
    -N0459F290 DCT DEGES Z2 OSDOV M738 ADOSA L612 ALBET DCT
    -LIPZ0035 LOWL
    -PBN/A1B1C1D1O1S2 DOF/211121 REG/HBASA EET/LOVV0009 LIMM0018 OPR/SWR PER/C RMK/TCAS)

     

     

     

  8. Hi Peter,

    I don't own the CRJX so I don't have an insight into the manuals. Maybe the following data is published in the manuals and you could provide them for the CRJX, so we can create and provide a profile:

    • Required RWY length
    • ICAO Approach category
    • MTOW
    • MLW

    If you also own the CRJ550, 700, 900 then the above mentioned data would also be good to know to update/create the respective profiles in EFB.

     

  9. Hi Harry

     

    1) from the dbBuilder Logfile I can see that the data path from the Server is located at a location which is synchronized with "OneDrive".

    OneDrive is not supported. Please read here: https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/

    I strongly recommend to uninstall EFB Server and Client using the Windows uninstaller, then re-install using the latest installers for Server and Client from the download section. When re-installing, please select a data path which is not synchronized with OneDrive.

     

    2) there is an error logged which might point to a missing file or path. Please check whether the file 'C:\ProgramData\Microsoft\Fsx\scenery.cfg' is available.

     

    3) Can you please provide the scenery.cfg? Thanks.

     

  10. Thanks for the screenshots.

     

    From the screenshot I can see that your flight goes to KDCA, therefore EFB is looking for active frequencies at KDCA.

    Such dependencies and agreements between certain airports are not defined in the VATSpy configuration files which are used by EFB.

     

×
×
  • Create New...