lonewulf47

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.

Hi John, If the ILS'es in ESGG are properly depicted in the respective BGL, they are also properly depicted in EFB2. The main problem ist that with time some ILS'es are replaced and therefore have changed crequencies and/or IDs. This is one of the disadvantages in the FSX/P3D way the navaids are defined. There's little we can do about that. The presently valid data for ESGG ILS are: RWY 21: 108.50 NGG RWY 03: 110.30 SGG If the BGL of your ESGG airport does not match these values, the ILS cannot be depicted, as they must be consisted with the AIRAC data in use on your installation. In case the default airports are affected, it is a good idea to have a look at Hervé SORS' https://www.aero.sors.fr/navaids3.html lovely freeware update for the default navaids. In Eurpoe region also ILS are updated. This is how my default ESGG looks like:

Hi Leo, Just look for the name of the BGL of the airport not showing the ILS correctly (Airport Information). It may well be that this file contains outdated information. As a first step you may have a look (if not already known) into this excellent freeware source, which updates at least most of the stock navdata: https://www.aero.sors.fr/navaids3.html European ILS'es are updated in the World Navaid Package. For the rest of the world individual ILS update packages are available.

Hi Davide, Yes, that's one way to do it and that's the way many designers change an old stock ILS by inserting the new "on top" of the old one. The only side effect is that the old ILS is still also tuneable on the old 190.50 frequency with the old ID CAS. Nothing else happens. Nevertheless I have attached my own version of the new BGL with the new ILS only and the GS and ILS-DME moved to the correct position. LIMF_ADEP4_ow_new.bgl

Hello Davide, Could you provide the active BGL for LIMF? I'm afraid this one is still using the old frequency 109.50, ID CAS. Current (correct) would be: 108.7, ID ITOC. EFB can only display an ILS which matches the current datacycle.

Did you re-run the DbBuilder after removal of all FsAerodata Files? What are you referring to with "Version 2.058"? Please bear in mind that only the most recent version of EFB2 (build #114) is supported.

Thanks for reporting. Yes, the first synchronizing needs some time as the whole database will be transferred to the Client. Depending on the WiFi speed, it may take some time.

Hi Stefan, As far as I know the MS Surface Tablets use Win10 ar Operating System. Therefore it should be no problem to connect. WiFi is not a problem either. At times I use a Laptop via WiFi as my Client Display.

Hi ??? (please sign your posts with your real name as per Forum Rules) You might want to have a look at this thread: https://forum.aivlasoft.com/topic/3898-pmdg-737u/ The problem can easily be solved. There's also the Manual which gives some clues about editing a profile.

Hi Gary, No new license is required. If you have your new system up and running, just install EFB2 on that system using the present key. We recommend to download the latest installers from our website: https://www.aivlasoft.com/download.html Just make sure you are talking about EFB2. An EFB1 license would not be valid for EFB2.

Hi ??? (please sign your posts with your real name as per Forum Rules) You might need to look after an updated airport Scenery. EGSS has some time ago changed the RWY designators to 04/22.

Hi ??? (please sign your posts with your real name as per Forum Rules) First of all we need to know which airport BGL is used to draw the ground layout. Please check on the airport information page (i). EFB is not messing up any parking positions. It just draws what is available on the repective BGL.

Yes, Please read our FAQ here: https://forum.aivlasoft.com/topic/3887-efb-v2-is-not-compatible-with-fsaerodata/

Hi Jerry, All the mentioned ILS'es are availble on my install. The problem is usually not the AIRAC Database, but the local BGL, where the ILS'es are defined. This is unfortunately one of the biggest problem areas on all MS-based simulators. While e.g. on X-Plane ONE single database is updated and compared, in MS-based simulators there are still "multiple databases" used. Each add-on BGL has its own definition of ILS data, which in turn is not always the most current. The main parameter we changed for build #114 is that ILS'es are now identified by their identifier, rather than by their frequency. So I would bet that on the airports you mentioned in your post, the ILS identifiers are not as required by the newest AIRAC. See attached screenshots fo these two airports KMCO and LIEE. Unfortunately most Add-On developers regard their products as kinda "fire-and-forget" items, not really caring for updated BGLs for the community. In all MS-based simulators however updated BGLs with correct ILS information are of utmost importance. I should nevertheless also add that the above samples are taken from the P3D default database, which seems to be correct. I have no idea why your (Add-Ons?) airports do not show the same ILS'es. This might need more investigations. Your basic complaint about the non-availability of ILS'es however is not correct.

Hi Leo, Start Menu/Units/Runway Dimensions Alternatively see Manual 5 Client: Chapter 12.3.2 ff

Well Ray, that's exactly what I'm doing: Flight Simulation, not Air Traffic Simulation. I do not see any reason to cope with so-called "Artificial Intelligence" (an insult to every intelligent being) just to be disturbed at the worst moment in the worst way😀! I have coped with REAL Air Traffic during my whole flying career. Believe me, there's absolutely no motivation to see random BS crossing my way all the time...😂

Hi Bernd, Great to hear that it works normally now. With best wishes for 2020!

Hi Ray, I must admit that I have no idea how the simulator handles AI traffic. I did not change anything within those assignments. For the two RWY BGL RWY 04R/22L has take-off and landings to either side. My AI traffic is always set to off as I do not want any A/C moving around beyond my control...😀

Hi Bernd, Well, in fact those "graphic issues" look like oversized AI-Traffic Symbols. Please check the size setting in the start menu under "Settings/aircraft". However, I must admit that I never have seen them soooo big as the size is limited to a figure of 3, which is by far smaller that this. Standard value is 0.8. Please submit a Support file for the Client to check the issue thoroughly.

BTW, RFSB did not a really good job when they updated the BGLs with their fix. They changed the frequency but NOT the ident. Furthermore the ILS LOC and the DME are misplaced. Find below the corrected files. For 1 RWY configuration: Just disable the original LIPZ_ADEP4_ADE.bgl by setting it to OFF and replace it with the one below. LIPZ_ADEP4_ow_1RW.bgl For 2 RWY configuration: Just disable the original LIPZ_ADEP4_ADE.bgl by setting it to OFF and replace it with the one below. LIPZ_ADEP4_ow_2RW.bgl

Hi Ray, Actually you gave the answer right in the first line😀 You tune 110.30 and the ILS becomes active. Thing is that this frequency is not valid anymore. The new frequency for RWY 04R is 109.95 Ident VTS. This is one of the crucial things in all FS-based simulators. You can only TUNE the frequency which is stored in the respective BGL (default or Add-On). EFB - because it is based on actual ARINC data - can only show and use the actual, current frequency. There is in fact no other workaround for this to alter the frequency and the ident in the Add-Ons BGL. Would you work with X-Plane this would not be an issue as X-Plane has only ONE database, which is used for ALL default and Add-On scenery.

EFB2 Build #114 is fully compatible with the add-on systematic of ORBX Central4. I use it daily and have done 2 vanilla installs of P3DV4 recently.

Hi ??? (please observe our Forum Rules) Ever checked this: https://forum.aivlasoft.com/topic/3005-afcad/ ? The problem comes from JetStream Design, not from EFB...😀 because they deactivate the RWY for AI traffic.

Hi John, No, at present there is no predefined profile available for the Airbus A330-300, but with help of the Profile Editor it is easy to create one. Alternatively we could of course create a profile for the A330-300 if you can provide me with the following information: - name of the *.air file - applicable min RWY length (~1600 to 1800m used for airport filtering) - MTOW in kg (235'000 kg?) - MLW in kg (185'000 to 187'000 kg?) for all other parameters we will use standard values that can be adjusted individually to your liking - or - Someone of the community has already created one and can publish it here 😎?