Jump to content

aivlasoft

Administrators
  • Posts

    5,928
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Hi Bernd,

     

    Quote

    I assume, that UT Live is sending the information to P3D and the EFB is receiving it from there ? Or is there a direct link UTLive - EFB ?

    EFB is getting traffic data from FSUIPC which is reading this data from the simulator. There is no other way of getting traffic data (except 'snapshot' data from the online networks VATSIM and IVAO). No direct connection between EFB and UT.

     

    10 hours ago, wolkenschieber said:

    This happens as well in ProSim as well as in the EFB.

    If the error appears in both programs in the same way, the reason for the problem must be found in or before the data source which supplies these two programs.

     

  2. 14 hours ago, OldTiredSailor said:

    MSFS reads the flight plan from wherever I tell it to read

    This might be correct as long as do it manually via the MSFS GUI.

    But unfortunately it cannot be selected when forwarding a flight plan via the FSUIPC interface. Using the interface the flight plan MUST be copied to the folder mentioned above by lonewulf47. This restriction cannot be circumvented.

     

    14 hours ago, OldTiredSailor said:

    I am on day 3 of a 30-day trial - IF I uninstall ALL the AivlaSoft stuff and then reinstall - will I still have 27 days to continue the trial?

    Yes.

  3. Tobias,

    thanks for the files. I had a look into them using ADE (Airport Design Editor) and I can see that the runways 36L/18R and 36R/18L are somewhat fake runways. I have no idea why the designer of this airport created these two fake airways.  Both of them have a length of 60m which is 'bad luck' because EFB is filtering fake runways which are <= 50m.  In other words, EFB cannot do anything, you would need to edit the BGL file to remedy this.

     

    You may try to use the EDDF file for the EFB database from the 'Download/AFCAD' section of this forum. Please read carefully the instructions on that page and DO NOT REPLACE YOUR AIRPORT IN THE SIMULATOR, use it only in EFB.

  4. Tobias,

    First question is: Which designer created this airport?

    Second question: if your EFB Client is running, please select EDDF as your active airport. Then press on the info button ('i') on the right side of the button 'Airports'. This will open the airport information window. There you can see a list of files which are used to depict the airport. Either number 1 or 2 is the path to the main airport BGL-file.  Can you provide this file for further investigation?

  5. Ingo,

     

    not every single scenery is skipped, only these directories which do not contain relevant data for the EFB database. It is still scanning 3949 BGL-files which might be OK.

     

    From the logfile I can see two different kind of errors:

     

    1) The access to the path: C:\Users\Ingo\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\elhakimi-eddf-terraforming\scenery\world\scenery\eddf-terraforming-scene.bgl is denied. You have to check your system why this problem occurs.

     

    2) Some of the paths from the PC-6 addon are getting to long. This is a known problem with MSFS because its paths are sometimes unusually long.

     

    If you ever come to the point where you will do a new installation of MSFS, try not to use the default path instead of an own partition. This will significantly reduce the length of certain paths.

    For the time being I recommend that you try to fix error no. 1 and then try again. BTW, creating a new database is only required if there is not yet a database available for the simulator type. If you already have a database, just use the function "update database". For further details please consult the manuals.

     

  6. Hello,

     

    thank you for sending the files. I have analyzed them and came to the following conclusion:

     

    First of all a brief description about the so called 'package-system' and the relations between the files 'add-ons.cfg' and 'add-on.xml':

     

    The file 'add-ons.cfg' is kind of a table of contents and it contains the list of your add-ons and for each of these add-ons a path to the directory where the files of the add-on are stored. There are two locations where the file 'add-ons.cfg' can be found, one is below '%ProgramData%' and one is below '%AppData%'.

     

    The file 'add-on.xml' contains information about the add-on itself. One part of this information is whether it is a scenery-add-on, or not. If it is a scenery-add-on then the file must contain an XML-node containing the text 'scenery'. This is what the DbBuilder is looking for.

     

    Basically the logfile entry '-- No scenery category found' is OK, because there are add-ons listed in the add-ons.cfg which do not have a scenery node (e.g. FSLabs, or FSUIPC). But if the '-- No scenery category found' entry is logged for a scenery-add-on then this is an indication of a serious problem, or in other words, it looks like the 'scenery-node' in the add-on.xml has been removed or has been commented out. If no 'scenery node' can be found in a certain add-on.xml, the DbBuilder will no longer try to scan this add-on when it is creating/updating the database.

     

    Quote

    I guess, let me clarify my question. Is there any way to have the EFB scan all add-ons even if they are listed as disabled, and utilize custom scenery over default scenery, even if it's disabled? I thought that's what the checkbox was supposed to do, but it doesn't seem to be scanning it properly.

    That's correct. The DbBuilder distinguishes between active and inactive sceneries by simply reading the 'Active=true/false' flag in either the 'scenery.cfg' or in the 'add-ons.cfg' file(s). If the box 'Check all' is ticked then all add-ons will be considered, regardless whether the flag is set to true or false. If the box is no ticked, only active scenery add-ons will be considered.

     

    In the logfile which you sent us I can see for example the following entry:
    -- No scenery category found in: C:\Users\<username>\Documents\Prepar3D v5 Add-ons\Flightbeam - KDEN\add-on.xml

     

    This seems to be a valid scenery add-on of KDEN airport, but it looks like the corresponding add-on.xml does not contain a 'scenery-node' (see above) and therefore this add-on will no longer be considered in the process of creating/updating a database.

     

    Conclusion:
    I don't know what exactly the Lorby-Organizer is doing when you set a scenery to ON or OFF, but from my point of view it seems that it does some changes in the add-on.xml file. Could you please check whether the content of the file C:\Users\<username>\Documents\Prepar3D v5 Add-ons\Flightbeam - KDEN\add-on.xml will be changed in any way when you switch the KDEN scenery from ON to OFF and vice versa?

     

     

     

×
×
  • Create New...