lonewulf47

See manual: 6 Flightplan, Chapter 2.3, Flightplan via Uplink

Don't forget that you also can use the uplink directory in the server path. You have sooooo many possibilities to uplink😀! I'm sure one of those will fulfill your requirements...

You're welcome! One of the great advantages of flight simming ...😉

Hi Todd, It is neither a Navigraph nor NavDataPro problem but a Flight Simulator problem 😀. The problem can be identified by pressing the Ctrl+Alt+A combo. It shows a mismatch between the THR 06L used on the ground layout and the one used in the AIRAC data. In this case the difference is just above the "trigger distance" of 1000 m. Therefore EFB2 cannot assign any procedure for RWY 06L. (see also missing DEP procedure). I'm not sure when this THR displacement was issued. According to the official ground chart is it now active. I'm also not sure whether this is a temporary shortening or not. in any case, using the correct THR position brings the procedures back on RWY 06L. See screenshot. As a temporary solution you can use one of the the attached BGL in the AFCAD folder of your EFB2 installation. Be sure to re-run the DBBuilder therafter. We will publish and amend these BGLs also in the Contributions AFCAD section. In case you have already used a CYUL AFCAD file, delete the old one and replace it with one of the new ones. For Default CYUL: CYUL.zip For FlyTampa CYUL: CYUL_FT.zip

Just a shot in the dark: FSUIPC (correct version) installed?

Hi ??? (please sign your posts with your real name according to our Forum Rules) This is most probably a small bug that was lurking around for quite some time already on a few approaches. It mainly happens when the connection to the preceding approach transition or STAR fails. As I'm unable to reproduce it here, I presume that this is already corrected and will be puiblished in a future update.

Get -> Get the actual take-off weight for performance calculation max-> use MTOW for performance calculation Normally the actual weight is used and shown. Nevertheless it is still possible to switch between ACTUAL and MAX. That's why both "Get" and "Max" Buttons must be available.

Hi Tom, Actually you don't need to convert the flightplan into X-Plane format, as this is done automatically as default function. Whenever you have entered a flight plan in EFB, it will be available as "EFB_current_gps.fms" in the "\X-Plane 11\Output\FMS plans" directory. You can then load this flightplan into any default GNS/GPS of X-Plane. Unfortunately there is no dataref available to do this automatically, as we do on FS-based simulators. The specs for the X-Plane fms-flightplan ar to be found here. https://developer.x-plane.com/article/flightplan-files-v11-fms-file-format/ Just be aware that due to those specs the same AIRAC Cycle needs to be used on EFB and X-Plane.

Yes, I agree, however this depends on the scenery which has been unsed to create the database. Could you please check on the (i) Information page, which BGL is being used to display this scenery? And then of course please also submit the Support File of the Server. There must be a mismatch in your scenery build up.

Hi Jacques, It seems that you are not completely familiar with the way EFB2 works. Airports are depicted according to the data available from AF (AFCAD) BGLs in your Simulator. It your airport, be it default or AddOn does not incorporate the required RWY, EFB cannot use it. The default variant of CYYC does not incorporate the requested RWY 17L/35R. See the attached screenshot. A remedy would be if someonce could create a AF BGL that incoprorates the missing RWY or if any AddOn with all RWYs avaiable would be installed.. As soon as EFB2 recognizes the RWY in question, all procedures are available also for this RWY, provided of course that this AF BGL also contains - in this case - both ILSs for RWY 35R and 17L. BTW, were you able to find RWY 17L/35R in your Simulator Installation??

Hi Michel, Thank you for your offer. We will soon reorganize our contributions section for Profiles and will include your profiles into our collection. Anyway thank you very much for your contributions.

Hi John, To add to what Urs has written, so far I have only seen a Freeware Add-On published in AVSIM: https://library.avsim.net/esearch.php?DLID=208350 but only for FSX and without any information on neither quality nor usefulness. Once a AFCAD BGL with basic ground layout is available, at least all procedures could be flown. Maybe someone frem the community can help?

Hi Michel, Great news! Thank you for reporting ! Enjoy !

Hi Michel, I must admit that I have no idea what is going on on your system. Inorder to trace an error we of course need to be able to reproduce the error on our side. Unfortunately this is not the case. Whatever aircraft I load in X-Plane, its profile is properly identified and loaded. As I understand your problem description you are saying that every other A/C in X-Plane loads its profile properly, just not these two, right? This is something I have never seen before and I'm definitively out of ideas what is causing this. Just as an idea about any programs running under Windows, it is heavily recommended to run every program as admin. I personally have activated the respective checkmark in the compatibility tab of every *.exe file. No idea whether this could be of any help, just one more shot in the dark... And one more thing, just to confirm: we are talking about X-Plane 11.30 and higher and Windows 10, right?

Hi Michel, Well that's very strange indeed. I quickly installed the Fokker 50 into my X-Plane and copied your F50 profile into my EFB2's profiles folder. It shows up normally as you can see in the screenshot attached. I have no explanation as to why the profile is not showing up in your installation. Just one hint: Could it be that you are also using a FSX/P3D database and you have selected the wrong database?

Hi Ray, Great to hear that is worked as predicted. Airport elevations are - despite all possible means to avoid - always a problem and cannot be sorted out all the time. My personal "handling" of such anomalities is to check out a newly installed airport whether anything is wrong with airport elevation. In most cases the elevation correction tool from ORBX vectors will do. Sometimes even the developers of an AddOn offer elevation correction BGLs. Nevertheless my guess is that this is a neverending task, if you chose to have 500+ aiports installed worldwide...😉

Hi Michel ?? are you aware that the Client needs to be restarted after a new profile is entered? The indexfiles have to be rewritten. If it doesn't work after restarting the Client, please attach the failing Profiles in your next post. There's nothing else required than opening the .acf files in PlaneMaker, exactly as you did.

Hi Michel, What do you mean by that? Are you unable to open the respective *.ACF files or do they not provide the necessary information?

Ray, I have a temporary solution for you, to make at least the default airport available as SPJC. Make a distinctive Directory for SPJC. I still have the good old "Addon Scenery" in use and within that I created an "airport" SPJC, and within that the normal "Scenery" folder. This finally looks like that: D:\Prepar3D v4\Addon Scenery\SPJC Lima\Scenery. just like a common AddOn Scenery setup. Put the two BGLs below into that folder, add the new Airport SPJC to the scenery.cfg and re-run the DbBuilder. SPJC_ADEP4_ow.bgl SPIM_ADEP4_ow.bgl It is absolutely necessary to also put the slightly modified SPIM BGL into that folder to allow EFB2 to recognize the proper airport. Both those BGLs are derived from the default BGL, but slightly modified to allow SPJC to be displayed. The second SPJM BGL has a slightly diesplaced ARP to allow SPJC to "take over". Please give it a try😀 As far as I have seen, it sems to work in my P3DV4 install...

Hi Ray, The problem is, that for the old ICAO SPIM there are no more procedures available. IF there were any kind of AF BGL for SPJC, all ARINC procedures would of course be available in EFB2. I'm not even sure whether the default ICAO code can be changed in the stock file. This would require a complete redesign. So in fact if nobody in the community has produced a dedicated AF file for SPJC, there is no way procedures can be made available. A very uncomfortable situation, I agree and much simpler to handle in X-Plane...😀. There of course the community has produced a basic Global Airport file long ago.... In this respect the X-Plane community is far ahead of the "Rest of the World", but only in this respect...😀

Hi Ray, Yes, this is one of the rare changes when a new airport was set up close to the old one or at the same location, but vastly enlarged. The new ICAO ID is now SPJC, but of course this one is not included in any of the default databases. Inorder to gain access within EFB (and the sim...) you need to either: 1) Produce your own AFCAD file for SPJC - or - 2) install and Add-on, but I'm afraid there is none so far...🤔

Well, no, it does not require the Sim to be started inorder to look at an airport. The above screenshot was taken without the Sim running. It it does not show up with the Sim off, there is indeed a problem with the database. But from our side it is virtually impossible to find the cause as we have no insight into your installation. As far as Prepar3D V4.5 is concerned, I can confirm that FAGG is included in the default scenery and therefore should show up when selected. The default FAGG is included in default scenery file "APX53440.bgl", to found in the default scenery path "\Prepar3D v4\Scenery\0605\scenery". This is valid for any P3DV4 installation.

Without additional information it is impossible to discuss this. I can however not confirm your issue in P3DV4. It is still available as default airport. See below:

Hi William Yes, it's obvious. The correct ILS data are as follows: ILS09 D108.50 IDIA ILS10 D109.50 IDEL ILS11 D111.30 IDMR ILS27 D110.50 IDLH ILS28 D110.30 IPLM ILS29 D110.90 IDGM Obviously some of the ILS IDs are not correct anymore. A correct ID is required to properly identify the ILS. If you are familiar with ADE you may be able to apply the corrections to the respective BGL. EDIT: I see that the original BGL provided by the Add-On developer has almost all DME's and sone GP wrongly positioned! This file is a complete mess! You might try this BGL below to see correct DME placement and correct ILS IDs of all Navaids. VIDP_ADEX_ADE_without_T2.bgl Just make sure that this replacement is only valid for the configuration "without_T2". If you chose to select another configuration the old and erroneous BGL will again be activated. Also before replacing the BGL set the original BGL to OFF or remove it to a safe place before copying the replacement into the scenery path.

Hi John, Just make sure you fully understand what SORS Navaid Update does (provided you use the default setting): It replaces - where applicable - the default NVX* and APX* files and renames the originals inorder to keep them for restoring purposes. No 3rd party files are modifed. As any 3rd party (add-on) BGL has priority over the default scenery, any wrong navaid in an add-on will be in higher priority and thus possibly not properly displayed. EFB2 follows exactly the same priority as the simulator. Do not be too annoyed by the "Conflicts" list provided by the SORS Navaid Updater. This list mainly copes with NDBs and VORs which are also used in other area scenery like ORBX'. The ydo not create havoc, they usually are even useable despite the conflict indication. I personally NEVER did anything to solve any conflicts as I use all of the ORBS areas. That would be a tremendous effort to solve all conflicts there...😀 We have created an additional means to use a BGL in highest priority when placed into the AFCAD folder. This is mainly used for Ground Layout problems. Of course also a different Navaid may be shown in such an AFCAD BGL, however this will never be tuneable! Tuneable navaids are restricted to any BGL's in any scenery path, following the usual priority schedule. This is (unfortunately) how navaid tuning works in all MS-based simulators. In this respect X-Plane is much more advanced. There the basic navadata are fully updateable with the latest AIRAC data, thus there will never be a discrepancy between tuneable or non-tuneable navaids as everything is derived from the same file. To answer your two questions: 1) IMHO there is no reason to make a restore piont as the World Navaid Package does not change anything in the default scenery folder. You can always restore it to original (default) by the SORS Navaid Tool. I never had any misfortune when using SORS Navaid Update and I use it for many years now. 2) No, read here. https://forum.aivlasoft.com/topic/3887-fsaerodata-is-not-compatible-with-efb-v2/ FsAerodata manipulates the default BGLs in a way that EFB2 simply cannot cope with. So in short: if any add-on airport is still missing a navaid (mostly ILS of course), it is actually the add-on publisher's duty to modify the BGLs to reflect today's (AIRAC) state. This said, I'm fully aware of the fact that most of the add-on developers are not really helpful in that respect. In a few exceptional cases we may also provide help in creating valid BGL with correct Navaids. This service must however be of limited use as it is quite time-consuming to do all necessary corrections.