lonewulf47

No Graham, This copy of magdec.bgl is not used for MS-based simulators. For these always the magdec.bgl of the respective simulator is used. The copy of magdec.bgl you mentioned in the **\EFB2\Server\DbBuilder\Base is exclusively used for X-Plane as X-Plane does not provide this kind of a magdec table. So in short - you don't need to update it. It does however also not cause any trouble if you do so, as I explained before. it is definitely NOT used in the DataBuilding Process for MS-Based simulators (FSX, P3D). HTH.

Hi Paul, No problem at all. You can use any simulator as long as you have a database for each of them.

Did you build a database for X-Plane and therefore defined the X-Plane Main Folder in the DatabaseBuilder?

Simulator running and NOT in Airport Ground Mode?

Juergen, EFB2 can only display what the Add-On Developer is providing in his Ground Layout BGL file. In the case of KIAH I see the radius for each gate. See attached screenshot. As the present A/C is an A32, all parkings not suitable for this A/C are greyed out. If you see something different, then it must be another version of the airport. I have the FSDT too.

Hi Kevin, This sounds like a corrupt installer. Did you download the latest installers? https://www.aivlasoft.com/download.html#a1530

Hi ??? (please observe the Forum Rules and sign your posts with your real name) EFB2 is designed as a stand-alone application. An integration into a VC is not possible. It is highly recommend to use a second monitor for EFB2 display. As for the checklist request I should point to the fact that EFB2 does not include any checklists other than the one sample from the basic install. The idea is that a (living) community would spread such checklists among the users.

Hi ??? (Please observe the Forum Rules and sign your post with your real name) I just did a refly of the mentioned routing and I couldn't see any of the issues you reported. Are you sure you didn't mix-up the two buttons "PROC" in the airport menu and "ARR" in the RSB (Routing Shortcut Bar)? Pressing "PROC" inflight always shows the ARR selection page of the airport in the title bar (normally "A" (Green) = closest) but also a manual selection can be used. Pressing "ARR" in the RSB always opens the ARR selection page of the destination. During the whole flight I pressed "PROC" and "ARR" several times and I never saw the issue you reported.

Hi Didier, Thank you for your kind words ! Using this folder name was exactly the cause. The thing is of course that you will now see a few entries in the DbLogfile pointing to the items in ...\scenery\... and being commented "no scenery found" as the DbBilder will now look for EFB2 relevant BGLs in that folder. I hope there are not too many... In this respect it was a bad idea to use a folder name which is used by default and contains non-pertinent stuff which therefore should be filtered...

Thanks for reporting. Nevertheless it sounds a bit strange as "magdec.bgl" is installed by default in P3D and can be updated by more recent data. But as a basic install the BGL must be in the mentioned path.

Hi Didier, The only explanation for that is that you might use non-standard installations paths. 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. You might want to check whether one of the path definitions coincidentially match your installation path. 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. I do use an external ORBX Path without any problems. You might consider to send a set of Support File to allow us tracing the SbBuilding Process.

Hi Didier, Can you check on the (i) page, which BGL is used to draw the ground layout?

Hi ??? (please follow our Forum Rules and sign with your real name) Are you aware of these two entries in our FAQ? https://forum.aivlasoft.com/topic/3887-fsaerodata-is-not-compatible-with-efb-v2/ https://forum.aivlasoft.com/topic/4264-why-are-ils-approaches-not-showing/

Thanks for advising !

Please send a set of Support Files.

Only missing after re-installation or also after re-running the DbBuilder?

Hi Faisal, Sounds great ! Same to you !

Ok, and here is the solution. 1.) Replace the original "OPIS_ADEX_ADE.bgl" with the new one below. Do not just replace the original BGL, but set it to OFF inorder to preserve it 2.) Copy the OPIS.BGL into your AFCAD folder in the Server's documents path The reason for this procedure is the following: The original "OPIS_ADEX_ADE.bgl" has RWY 10L/28R deactivated (that's how EFB2 interpretes it) by closing it or all AI traffic. This causes EFB2 to ignore the RWY, despite it being in the BGL with all necessary ILS data. The "OPIS_ADEX_ADE.bgl" below leaves the AI traffic settings unchanged. Nevertheless I corrected all misplaced ILS DMEs to give correct readings in the Approach Profile. But it would still not show the northern RWY, as for EFB2 it remains closed. I didn't want to change the AI settings inorder to not interfere with the Designers Intentions. That's why you have to copy the "OPIS.BGL" into the AFCAD path. After all changes re-run the DbBuilder and everything should show up correctly. I will add OPIS.BGL to the AFCAD list at a later stage. OPIS_ADEX_ADE.bgl OPIS.bgl

Hi Faisal, "Wrong Info In, Wrong Info Out"... Exactly😀 Thank you for the BGL. I'll have a look into it and report.

Hi Faisal, Generally spoken, the primary remedy is for the developer of the airport AddOn to issue a proper airport layout BGL. EFB2 can only display what the Sim is providing. In the case op OPIS I have no clue as to how the layout BGL is done. Therefore the two possibilities exist: either the developer issues a proper BGL or you send me the BGL in question (to be found on the Airports Info page under "File(s)") and I'll have a look whether I can solve the issue.

Hi Carl, No, you're not doing anything wrong. The actual NAT Track Message contains only one track "A" (see below, original NAT Track Notam). This is due to the vastly reduced traffic between the continents due to the present Corona Pandemic.

Hi Jonas, Yes, I have yet to find the real cause for EFB2 "misbehaving" during DbBuilding. Must be something in the original BGL, but so far not obvious to me. The corrections are implemented in the AFCADs too, however this results in kinda hybrid display. While in EFB2 Approach Profile the ILS DME distances would be correct, the actual distance reading in the A/C would still be wrong as the "tuneable" part of the ILS DME is still misplaced. To be honest, I can't remember the reason for the EETN AFCAD file being made. Maybe some oddities in airport layout. For the actual Drzewiecki airport however the AFCAD is no longer needed.

Hmm, I might have been a bit too quick. I just did a fresh install of EETN on my second system and I saw exactly the same. When looking at the procedures after running the DbBuilder, there was the remark "no Localizer" for all ILS and LOC approaches. When looking at my "big" system I saw a different "Tallinn EETN.bgl" installed there. Maybe I have changed this already at an earlier stage and forgot in between...😁 You might give it a try with the attached BGL. It also incorporates the correct DME locations. Tallinn EETN.bgl

No idea. I don't see any similar report on my install and I have exactly the same airport...

Hi Jonas, That looks somewhat strange to me in two respects. "ILK" and "IIB" are ILS(LOC) identifiers. Localizers do not have a name, unlike VORs and NDBs. So I wonder a bit why EFB2 is looking for a name at a LOC. what name is ADE showning? I have the very same airport installed and I do not see this. The ILS is showing normal parameters without a name.