lonewulf47

Hi Jean-Luc, I see that you are working with an unsupported OS (WIN7). Please do the follwing to make sure that everything is uninstalled properly: - Uninstall both Server and Client - after uninstalling check the follwing paths for being DELETED: - C:\ProgramFiles\AivlaSoft\EFB2 - C:\Users\<Username>\Documents\AivlaSoft\EFB2 if those paths are still available, the uninstaller might not have removed everything properly. Delete both EFB2 paths and reinstall EFB2 with the newest installers.

Yes, most probably because you changed the number in the ClientSettings.txt while the Client was still running. When closing the Client, the file was rewritten using the current settings...

Mike, For any reason that is unknown to me, you are using different port numbers on Server and Client. While your Server uses #51748, youtr Client listens to #57892. This way of course no communication can be established. To overcome this situation is is necessary to use the same port number on both Server and Client. Do the following: - start the Server - got to the System Tab and select "Settings and more" - open Settings - under TCP network change the Port number to 57892 - press apply - close the Server Thereafter start EFB2 the usual way. Connection should be established normally now.

No, there are no incompatibility issues with ORBX Central. I use it from the beginning along with EFB2 without any issues. Rearranging the sceneries is in no way related to connection issues between Server and Client. It just means that whenever you added/deleted an ORBX scenery through the Central, you need to re-run the DbBilder. Whenever referring to any problems it is extremely helpful to provide a complete set of support files.

Hi Stephan, Yes, this is correct. Unfortunately the developers of TopCat are not very helpful in providing profiles for newer aircraft. That's one if the main disadvantages of TopCat.

Information missing. Did you ever consider checking our Forum Section here: https://forum.aivlasoft.com/topic/3005-afcad/

Hi ??? (please observe the Forum Rules and sign your post with your real name) See manual "5 Client", chapter 12.3 Settings, page 118, Settings. For coverage of the Terrain see chapter 10, Terrain, page 86

It may happen that ILS procedures are not listed in the PROCedure selection dialog at certain airports, although the ILS exists in real world. To understand why this may happen, we should have a clear understanding of the 'big picture' which I will try to explain: An instrument approach procedure (IAP) is a sequence of instructions regarding position, altitude, speed etc and it determines how an airplane has to be flown along a predefined track to finally get securely to the instrument landing system (ILS) and down to the runway. All these instructions and requirements are described in the so called AIRAC cycles which are updated every 28 days. Simplified, an IAP contains elements which are 'virtual' and elements which are 'physically existing'. Radio navigation aids (short 'Navaid') like ILS, VOR, DME, NDB, are the physically existing elements, whereas all the instructions and constraints of a procedure are the 'virtual' elements. When REAL world meets SIMULATED world ... AIRAC cycles for the simulation are provided by either Navigraph (product name "FMS data") or Aerosoft (product name "NavDataPro"). Navigraph AIRAC cycle data is provided by Jeppesen, Aerosoft data is provided by LIDO/Lufthansa. We are using these real world procedures in our simulators, but unfortunately all the physically existing elements often do not match their real world counterparts. As per design the FSX/P3D navaid database is contained in BGL-Files (e.g. APX*.bgl, or NVX*.bgl). The vast majority of these files have been created many years ago. While the real world procedures (AIRAC cycles) are updated every 28 days, mostly our simulators are remaining static. Because simulator data is static, it is getting more and more outdated. As long as default airports (aka stock scenery) are concerned, it is of utmost importance to keep them up-to-date. We strongly recommend the use of this fantastic freeware: Hervé SORS' Navaid Update Package https://aero.sors.fr/navaids3.html As long as ILS'es on European airports are affected, it is sufficient to use the World Navaids Package. If ILS'es outside Europe are affected, you will need to regionally update according to the list provided on the above website. If you fly worldwide it is recommended to use the World Package. Please read the information given on the website to fully understand what the content of the various update packages are. If Add-On airports are affected, the designer of the airport is responsible for a correct airport BGL which reflects the present moment regarding the navaids. Conclusion To be able to properly depict an instrument approach procedure in EFB, it is required that AIRAC data and SIMULATOR data MATCHES. If it doesn't match, EFB cannot depict the procedure for obvious reason and as a result of this the procedure is not available in the PROCedure selection dialog. A word to X-Plane users: In X-Plane this problem does not exist as X-Plane uses a complete updateable database which is valid for all navaids. Add-On Airports do - in contrary to the FSX/P3D system - not contain any navdata. Preview of next update #116 (planned 10 April 2020) With the next update #116 the content of the list of available approach procedures will be changed in a way that all procedures are listed, but outdated or even missing localizers will then be displayed as a caution (see image below). Also procedures with missing and/or outdated localizers can be selected.

Hi Pericles, First of all I would suggest to scan this forum for similar threads of missing ILS. Usually, it's all a matter of outdated files. In your case we don't even know whether you use the default or an AddOn airport, which would also be a helpful information. If you are referring to the default airport, then our suggestion - as already pointed out a few times in such cases - would be to update the default BGLs by this fantastic freeware source: Hervé Sors' Navaid Update Package https://aero.sors.fr/navaids3.html This will also update all European ILS'es to the current state. If an add-on Airport is affected, you need to ask the designer of this airport to provide an updated airport BGL. See also: https://forum.aivlasoft.com/topic/4264-why-are-ils-approaches-not-showing/

Hi Albert, Please check on the airport information page/tab "nearby navaids", which navaids are listed for Copenhaben (the closest ones). See attached example.There might be all ILS'es listend, but with different fequencies and/or Idents, which causes their exclusion.

Please never try to install any software just "over" existing if not explicitly allowed. So in short: use the standard Windows uninstaller an reinstall the program. As a normal network requirement port numbers have to be identical in any case. Otherwise no communication between Server and Client is possible. What you did is to install a Client which had not the same build numbes as the Server. In this specific case it was just a bad idea as we had to change the port number for some compatibility reasons right getween the two builds. I would strongly recommend to download both newest builds from our Server: https://www.aivlasoft.com/download.html and un- and reinstall both Server and Client. It's very quickly done and the best way to have identical builds installed. For future updates it is important that ALWAYS BOTH SERVER AND CLIENT must be updated if prompted so. Never update one component and delay updating the other. This will avoid any further conflitcs.

Hi Roger, We finally found the cause of this misbehaviour. All normal Approach Procedures at URSS are temporarily suspended and replaced by so-callled TEMPO Procedures. While Jeppesen/Navigraph just withdraw the apporaches (but funny enough only for the ILS 02 & 06), LIDO/NavDataPro keeps publishing all normal procedures. The procedures are suspended as from Feb 13, 2020. So as a conclusion using Navigraph data you will not be able to see the ILS apporaches in EFB until the normal procedures are reinstalled. Only NavDataPor shows all correct procedures. Nevertheless you can of course still tune the respective ILS, as the frequencies are listed on the information page. The changes are based on Russian NOTAM A0533 and are estimated to last until Apr 29, 2020. But according to my experience these estimates are not reliable.

Hi Roger, What AIRAC Cycle are you working with? Coud you please also send a complete set of support files to our support mail address?

It's from AIP Switzerland. Unfortunately there is nothing specified in the AIP about the 744. Not many airports have an assignment list for each parking stand. The main reason for designing stands for large A/C is usually double jetty to allow for better passenger handling. In your case you can of course use all stands in that list for B744 too. Someone from Apron Control would be more suitable to answer your questions.

Stephan, Maybe just as a heads-up here's the official list for large A/C stands at LSZH according to the current AIP Switzerland:

Hi Stephan, I see what you mean, but this is beyond our influence. EFB2 just checks the wingspan from the Aircraft's CFG file against the size of the parking stand, as it is defined in the airport's AFCAD bgl. If the wingspan is bigger than the size of the parking stand, the stand is greyed out. This solely depends on the accuracy level used by the designer. Unfortunately many stands have a radius just below 30m, which will of course grey out for the B747. It would require a rework of the respective AFCAD bgl according to the officially published stand sizes. I guess it could also be done by ADE. Nevertheless you can still select a position to your liking, even if they are greyed out.

For the figures in the table please check under Settings/Miscellaneous. We use a different design here. Other information is not provided by the AIRNC file.

Hi Roger, That sounds a bit strange. I did the following: I used the original APX58160.bgl, which has no ILS,es at all. Then I made a dummy airport URSS Sochi in the Addon Scenery Directory, put your URSS_ADEX_ADE.BGL into the dummy scenery folder. Then I added the URSS Sochi to my scenery.cfg and reran the DbBuilder. Thereafter I see the following: All ILSes are available and correct. So I have no clue what is going on on your system. With the original APX58160.bgl and your URSS_ADEX_ADE.BGL you should be able to see all ILSes at URSS Sochi.

Roger, We see an anomaly with the entry on line 2) in the airport information. In the example from your install it reads "Full" at the end whereas it shound read "Base". We therefore must assume that the regular "APX58160.bgl" was manipulated by your earlies FSAerodata experiments. I take it that you did not use SORS' regional updates for the ILS, such as the Russian Region for this BGL(see below). Using this regional update could possible restore the "APX58160.bgl" to a useful state. It would be helpful if you could post the "APX58160.bgl" from your present installation to allow us a few tests,

The (entire) correct path for the Navigraph files is: "C:\Users\<Username>\Documents\AivlaSoft\EFB2\Server\AIRAC\Navigraph FMS Data" This should be automatically used by the update manager. I have no idea why it is not used, as I don't use Navigraph. Maybe some other users of Navigraph data can help here.

Does that mean that you still don't see the ILS'es indicated as in my post above? This makes no sense at all. Have you ever checked, which BGL is used in the database? (EFB Info Page of URSS). The BGL indicated there is responsible for the ground layout. As long as there are all ILS'es correctly included in this BGL, there is no reason why the apporaches should not show up in EFB. They do in mine anyway as you can see in the above screenshot. I even made a test with the BGL you supplied above by opening an AddOn Aiport with that BGL. No surprise that all ILS'es show up correctly.

Stephan, I have checked all three possible AFCAD BGLs and all are showing TWY B as in my above post. So, I'm sorry, I'm running out of ideas what could be wrong in your install. The only thig I can confirm that all is looking normal with the LSZH_AFX-OP-STD.bgl for standard settings. But as mentioned, also the two others are showing TWY B correctly. The only thing I could recommend is to completely re-install the LSZH scenery with the newest installer.

Roman, It is impossible to find out what is going on in your simultor's database. All I can say is that the APX58160.bgl updated by the last SORS Navadata updates contains 2 ILS'es: - RWY 02 110.50 IAD - RWY 06 111.10 ISO and they show up exactly the way I have posed above. The date of the APX58160.bgl is 27.02.2020 Sorry, but I'm out of ideas because I see that everything is ok on my side with the default ILS'es.

Hi Stefan, Do you mean this one? It shows up regularly on my install after applying the update for Aerosoft's LSZH and re-running the DbBuilder.

Hi Jürgen, Do you use the EDDF AFCAD BGL offered here? https://forum.aivlasoft.com/topic/3005-afcad/ As the display of several runway procedures is dependent on the selected configuration, it might usegul to give this a thought. Don't forget to re-run de DbBuilder after using this BGL.