Runway 07C/25C optional requestable for Landing for the User (AI Traffic only use 07L/25R and 07R/25L for Landing).Runway 18 requestable from FS ATC for depature by User (AI Traffic not use it, limit by FS Engine).optimized AI Traffic roll of Runway and Taxi to Gate handling.Excludes optimized to remove object of other addons.Stoplines and Gatelines in the south apron not displayed in P3D (FSX was not effected).Some Fixes in the AFCAD Aivlasoft EFB was not able to select Runway 18 for Depature Some Gates has a small offset from the centerline.You might consider to send a set of Support File to allow us tracing the SbBuilding Process. I do use an external ORBX Path without any problems. Whether or not an external ORBX library is used has no influence on that behaviour, as long as you don't use your own path definition which might match one of the definition in the abovementioned Exclusion File.
You might want to check whether one of the path definitions coincidentially match your installation path. Under "C:\Users\User\Documents\AivlaSoft\EFB2\Server\DbBuilder\Base" you will find a file named "BglSceneryExclude.txt", where many well known paths are collected to allow the DbBuilder a certain filtering for non-scenery paths. The only explanation for that is that you might use non-standard installations paths. In fact all the addons I've placed outside of the "Lockheed Martin\Prepar3D v5\" folder are ignored, flagged as " !! Skipped !! (Exclude definition)", including Orbx ones that reside in the "Orbx Main Library". 11:45:32.379 Debug : #464 add-ons.cfg (ProgramData, SceneryPath) D:\P3D\World\EU\Suisse\Aerosoft Geneva Professional V5\Scenery !! Skipped !! (Exclude definition) 11:45:25.352 Debug : ++ Found scenery category in: D:\P3D\World\EU\Suisse\Aerosoft Geneva Professional V5\add-on.xml My LSGG addon is found but skipped ("Exclude definition"). You're right! I should have begun checking this point!
0 kommentar(er)
