Jump to content

aivlasoft

Administrators
  • Content Count

    4,797
  • Joined

  • Last visited

6 Followers

About aivlasoft

  • Rank
    Site Admin

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

6,297 profile views
  1. to 1): It seems that the XML-Reader does not like the "รง" in the downloaded file. I will fix it with next build #114. to 2): There is additionally an option in FSGRW similar to "Create export data" which you have to tick, otherwise no data output will be created (at least this was available in the past when I was using this weather engine).
  2. It seems that build #113 contains a bug which does not assign the ILS in all situations. I'm working on a fix. Sorry for the inconvenience. Workarounds These workarounds are only required until build #114 will be available, and only if you have to run the "Update Navdata" only. Running the "Update Simulator" function, after you have installed or uninstalled scenery data, does NOT require a workaround. You don't have to run both workarounds, only 1) OR 2): 1) Always run "Update Simulator" after you had to run "Update Navdata". or 2) Delete the database and create a new one. This includes the internal call of the above mentioned function.
  3. it seems that build #113 contains a bug which does not assign the ILS in all situations. I'm working on a fix. Sorry for the inconvenience. Workaround (only until build #114 will be available, and only if you have to run the "Update Navdata" only): 1) Always run "Update Simulator" after you had to run "Update Navdata" or 2) Delete the database and create a new one. This includes the internal call of the above mentioned function. You don't have to run both workarounds, only 1) OR 2).
  4. Hi Robert, it seems that build #113 contains a bug which does not assign the ILS in all situations. I'm working on a fix. Sorry for the inconvenience.
  5. Hi Erick, from what I can read in the logfiles, it seems that the 'scenery.cfg' file is either corrupted, or the path to this file is somehow corrupt. The scanning process only lists 13 layers of scenery, which is definitely not correct. The default installation has around 120 layers. I don't know your installation but I see that sometimes the drive letter is given as X:\ (in capital letters) and sometimes as x:\. Are you working with virtual drives or similar, maybe so called 'junctions' ? What also is an indication of a non-usual operating system installation is that the path "\Program Files (x86)" is located at drive X:\ and not (as usually) on drive C:\. It's almost impossible to give you the right advice in this situation. First what I were checking is the file 'scenery.cfg'. It seems that this file is corrupted. If this does not help, I don't know what else could help, except to do a fresh and clean installation of at least the flight simulator, but maybe also the operating system.
  6. Hi Roberto (?) Could you please provide a set of support files? ("Set" means one from the Client and one from the Server, both of them should cover the same time period). Thanks.
  7. As @KiloJuliett already answered, EFB is based on .NET framework which is a product by Microsoft. We currently do not have plans to bring an EFB to the market which is either based on iOS or Android.
  8. Hi Michael, Scanning FS9-type airports has been disabled in the DbBuilder long time ago when we realized that some of the FS9-type airports contain undocumented features which EFB could not cope with. We decided then to no longer support FS9-based airport BGLs and with the next build the DbBuilder did no longer scan such files. For almost a year now such airports have been ignored when the DbBuilder was scanning the airport BGL files, and obviously no one ever missed such an airport in EFB. Unfortunately (my mistake, sorry) with build #113 this feature has unintentionally been reactivated and therefore the DbBuilder now is scanning these old FS9-based airports again. As a result of this, the logfile now contains some 'old' error entries again. It will be removed again with next build #114.
  9. Hi Erick, please provide a set of support files, one from the Server and one from the Client. They should cover the same time. Thanks.
  10. Hi Michael, did you update the database ("Update Navdata")? Did you also update to build #113 already? I can see the PARQ3R arrival with Navigraph 1912.
  11. Hi Jean-Luc, I don't think that this has to do with the update. When VATSIM FIRs are not displayed then it is usually the problem that the data download from VATSIM does not match with the local data definitions. This is a problem which I cannot solve unfortunately.
  12. Hi Michael, I'm sorry, but I also have no other possibilities than using ADE. Because EFB v2 is not compatible with FS9 airports I recommend to exclude these airports from the scanning process.
  13. Hi Erik, please try to restart both computers, Client and Server side. Then try again. It the problem still occurs, please create a set of support files and upload it here. Thanks.
  14. Hi John, I don't know who or which label offers the latest version of EDDF, but I recommend to ask this question at avsim.com or maybe VATSIM has its own recommendations?
  15. Hi Vadim, We had to tighten some checks in the BGL-parser.
×
×
  • Create New...