Jump to content

aivlasoft

Administrators
  • Posts

    5,891
  • Joined

  • Last visited

Everything posted by aivlasoft

  1. I do not own REX accu season so I cannot say whether these are all the necessary definitions, but these definitions are correct and will exclude all folders (and their subfolders) named this way.
  2. Thanks very much for your tests and reports. A better way than deleting/removing a folder would be to figure out a naming pattern for the files which should be excluded from the scanning process. As you might know, in EFB you can define a kind of a blacklist for folders and (bgl-)files to exclude. Have a look at the following location: C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\DbBuilder\Base. There you can see two files which start with 'BglSceneryExclude...', one is exclusively for MSFS whereas the other is for FSX and all versions of P3D. Just open the file with any text editor (like Notepad.exe). On top of the file you will find detailed explanations about how to use this file. If you have any questions, feel free to ask here.
  3. Seems to be that one of the recently released airports is the cause for it. Please let me know which airports you have installed just before the problems came up. Thanks. @HondaJet it seems that it has nothing to do with the Navigraph update. On my systems there were no issues when I was upgrading the databases. It must have to do with a certain airport.
  4. I guess that this is the reason for the message. But from my point of view this is not "annoying", it is meant as a service to let you know whenever the simulator's database has been altered whereas EFB database was not updated to reflect these changes. Rebuilding the database means to run the function "Update simulator" from the DatabaseBuilders dialog. For further information on proper database handling please see the respective manual.
  5. According to the logfile the cause for the error is different than to what the poster above described. The missing comservices file is just a subsequent error and not the reason for the non-existing database. Unfortunately there is one of the zillions of the MSFS binary files which seems to be corrupt and therefore the DbBuilder throws an overflow error when it is trying to read it. In your post you write that you have installed some new airports. Please undo this action and then try each airport after the other and after each airport try to create the database. This way you can isolate and then eliminate the faulty airport. From the logfile I can also see that you have chosen a data folder for EFB Server and Client which is located on a drive which is synchronized with OneDrive. According to the installation manual you should not do that instead of selecting a data folder at a location which is not synchronized with a cloud storage service (https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/)
  6. Hi Jürgen thanks for your reply. If you don't mind and to be honest, I'm not very keen to update this old code and if it already works for P3Dv6 then I suggest to wait until some more users are asking for an updated version.
  7. I have found the source code. So far so good. But it will be difficult to implement the required changes because I have no longer a license and also no longer a P3D installation on my system anymore. Would you be ready to do some tests when an updated version would be available?
  8. Sorry for the late answer. I have to dig for the source code and will let you know about the result.
  9. Thanks for uploading the files. From the DatabaseBuilder's logfile I can see that only 980 airports (instead of approx. 25'000) have been found according to the different add-on.xml files and scenery.cfg. I must assume that something went wrong when you updated your P3Dv5 installation.
  10. Could you please create a set of support files, one from the Server and one from the Client. Please upload them here for further investigations. Thanks.
  11. You will find all the required information and links here: https://www.aivlasoft.com/
  12. Have a look at these screenshots. 1) KCLM ILS08 via JIGEB: This is a good example for so many approaches, especially in the US where you fly over a VOR or a fix, then outbound to another fix where you make a procedure turn and then fly back the same way again. Here you have to pass the waypoints in the red circles twice. If the 'logic' were taking just the closest waypoint, then all the waypoints after ELWHA were being considered as passed as soon as you pass ELWHA for the first time. Another example where taking only the closest waypoint could lead to unwanted effects. Approach EDDS ILS25 via REU25: While on the northeast leg (068°) passing IBIRU, or later at DS522, the waypoints on the 'other side' are too close to get activated, especially when you don't fly accurate enough on the desired track. From my point of view there is no reason to change the currently implemented logic. It works for a vast majority of situations, and for all not covered cases just use the DIR-TO function to sync the flight plan.
  13. Especially on certain (RNAV-) approaches this will not work because the waypoints are too close to each other. That's the reason why the requirement was implemented that all waypoints before must be passed. Otherwise the sequence might get a hick-up.
  14. This is the logic which is implemented already. A WPT is considered as passed if you fly over or by within a range of 3 NM. However, the condition is that all waypoints before must also be passed. Changing an arrival and/or an approach when you already are on this arrival or approach will always cancel the above mentioned logic because changing an arrival and/or an approach will change/remove multiple waypoints in the flight plan and therefore the logic must be manually reset. If you change your flight plan you always have to use the DIR-TO function to re-sync the logic with your current flight plan. There is no other way to accomplish this.
  15. That's fine, thanks. Just a few thoughts from my side as the programmer. To implement a logic in a program one requires that clear and unambiguous rules are available, which this logic must then strictly follow. I think that there are a lot of different possibilities in the situations described above, so that it is almost impossible to identify all cases and to determine an appropriate set of rules from them. Not always every situation can be solved with a program (at least not with reasonable effort), therefore the DIR-TO function was implemented, which allows the pilot to make its decisions based on his experience and the situational awareness and then to act accordingly.
  16. Sorry, my fault. You're right, the path cannot be indicated because the file isn't recognized. Look for the respective airport folder in '..\official\onestore'. If you have located the folder, look for the folder '..\scenery'. There you should see the airport file having a postfix '.fsarchive'.
  17. Unfortunately we do not have this airport in our collection. You can check in the installation path (path should be mentioned in the 'i'-window of the airport) whether the file type is '.fsarchive'. If so, the airport data is encrypted as I mentioned above.
  18. Unfortunately airports which have been purchased through the in-game-marketplace are often encrypted due to copyright reasons. Such airports cannot be read by EFB (see restrictions). I don't know whether this is the case for the airport that you are talking about. Can you provide the ICAO code and the developer?
  19. If you forget it, how shall the software know about it? I guess that this is not possible. Why not just use the DIR-TO function in such a situation? If programmable at all, such a logic would be far too error prone.
  20. The values for speed are taken from the output of the simulator. There is not much we can do in this regard.
  21. Hi Rene you can use the same installation for all simulators, but you have to create a database for each simulator first. Then, to switch from one simulator to the other, just change the database. You can do this by selecting the required database in the DatabaseBuilders dialog. Please see the manuals, thanks.
  22. What kind of data format (which program creates it) do you mean with .fpl ? Did you already have a look in the manual "6 EN Flightplan.pdf" ? There are several options to load a flight plan into EFB.
  23. P3D requires FSUIPC, as described in the manuals. See also here: https://forum.aivlasoft.com/topic/7783-incorrect-airport-on-startup/
×
×
  • Create New...