lonewulf47

Hi ??? (please observe our Forum Rules) I would think that you didn't activate the A/C symbol (and maybe missed some Manual reading)

Hold it ! You have updated to which build #?? 116? This is not the most recent build. The most recent is #117 ! Update to #116 was long a go. Why did you not update before? With build #116 you cannot, I repeat cannot read data from P3DV5. For this you need build #117 and FSUIPC6 !

Hi James, No, if you have updated to new #117 build, you can build one database for each P3DV4 and P3DV5. More important is that you use FSUIPC6 for both simulators. So, when starting EFB2 Server, you select the database for the Sim you inted to use.

Hi Marc, Yes, I saw this coming out yesterday. As I can see this is not affecting EFB2 unless they are not going to alter major items in the airport SDK. I do regular flights every day and haven't come across most of the reported issues, except for the "invisible mountains" in some approach paths. One of them is in the approach for LSZS Samedan RWY03, just abeam San Gian Chapel...😀. I'm sure many of the CTD's are also due to improper handling of Add-Ons that are "believend" to be compatible. As you might have noticed, we are about to release the #117 build today. We will soon find out...

No worries, Marc I'm usually scanning the LM Forum for information about an upcoming Hotfix, but so far I haven't seen any information about one coming up shortly. Of course hotfixes are always due within short time after an initial release, but usually no major components are addressed.

...and this information is based on what reference?

Hi Peter, Are you talking about a LIPX Add-On or Default? In default the APX50150 reflects the correct state. See below: If you're using an Add-On this of course replaces the default navaids and may need some editing. In case you are using RFSB's LIPX Verona Villafranca, you may navigate to the scenery path, set the original BGL "LIPX_ADEP4_ADE.bgl" to "LIPX_ADEP4_ADE.OFF" and copy the attached file into the scenery path as replacement. This should bring back the missing ILS. Don't forget to re-run the DbBuilder to read the new BGL into your database. LIPX_ADEP4_ADE.bgl

Hi Peter, No, this is - unfortunately - a pure FSX/P3D problem, where the ILS (as all other navaids) are defined in the respective BGL of either the Add-On or the Default scenery. I see both mentioned ILS showing up correctly on the default (updated by Hervé Sors' fantastic World Navaid Package) airports. Therefore it is not a ARINC database problem, but an Add-On problem. It might be necessary to update the respective Add-On's airport BGL. I must however state that I use NavDataPro. Nevertheless those data should be consistent beween the two main databases Jeppesen and LIDO. BTW, if an ILS is reported outdated you can still use it as the BGL still provides an useable ILS beam. It is just not consistent with the current database. Remember: an ILS can only be tuned if it is provided by the airport's BGL! Unfortunately more and more ILS become outdated due to small changes in either frequency or ID, or both. There is nothing we can do about. It's this unfortunate layout of navaids within FSX/P3D. The best remedy to at least have all default airports/navaids updated it the mentioned free service: https://aero.sors.fr/navaids3.html For European Airspace also all ILS are updated.

You're welcome, Jessy. Don't forget that you can update all files from time to time, just to make sure that all procedures are properly recognized. Enjoy !

Hi ??? (please sign with your real name according to our Forum Rules) How did you update to #116? Did you possibly uninstall the previous build and do a completely new Install? To me it soulds like the respecitve files have been deleted. Please read here: https://forum.aivlasoft.com/topic/3003-minima/ Last update to cycle 2005 is pending. But cycle 2004 can neverthelss be used.

Please check Windows StartMenu under AivlaSoft: (also mentioned in the Manuals...) This will create the support files on your desktop !! It's all there and documented in the Manuals !!

Hi Matthias, I would suggest to replace the original BGL by the one below. Just set the original to off and unzip it into the installation path: "\Prepar3D v4\SimMarket\JustSim-EDDL v2 P3Dv4\data\Scenery" The original BGL contains a few misplaced ILS DME's...😀 I take it that you are using P3DV4. AFX_EDDL.zip

Hi Ray, There's one thing that I don't understand at all. If you DECIDE to proceed to an alternate (there's no reason to have an alternate routing before that point), why don't you just enter HDG mode, clear the active routing and select a new destination, add some Waypoints and Procedures and enter the routing with applying DCT TO and select NAV again? PLANNING an alternate before flight is something completely different, as you of course require an alternate by your FOM (unless your planning is based on Isolated Destination). But once you DECIDE to proceed to an alternate you will just have to start a new Flight Plan (routing). Of course we are rethinking a possibility to have an Alternate Routing already prepared in any suitable manner, but ATM we're a bit overly busy with other important work. But again, the chances that you actually proceed to that Alternate are not extremely high, as there is (and this comes from my personal real world experience) a considerable difference between the Operational Alternate (as required by your FOM) and the Actual Alternate, based on the actual diversion decision. Thanks God I didn't have to do too many diversions IRL (if I remember correctly there were some 6 or 7) and only ONE of those went to the Planned Alternate... Having an alternate routing prepared in the FMC didn't help a bit. That's why we dropped it as a general requirement. One more thing that makes a prepared Alternate Routing also obsolete is a scenario which happened to me twice. Due to a technical malfunction halfway enroute the destination became unavailable due to RWY length limitations and we had to proceed to an alternate offering enough RWY length. This kind of diversion asked for a complete re-routing and again was not within our preflight considerations. So you see, Real Life teaches you a different lesson - and we simmers do want to have it as real as it get's - dont'we? 😉

Please, do not cross-post !! It's all explained in this thread: https://forum.aivlasoft.com/topic/4268-prepar3d-v5-compatibility PLEASE READ CAREFULLY !!

Yes, I found the same thing, not surprising though...😀 In any case DO NOT ATTEMPT to update the database by linking it to P3DV5. This will produce unpresictable results und you might lose you P3DV4 database. As long as you keep your P3DV4 database updated, you can cross-use it with P3DV5 FOR DISPLAY ONLY. For understandeable reasons the airport's ground layouts will reflect those that you have installed in P3DV4. You will be advised as soon as a fully P3DV5 compatible update is available. Until then every use of EFB2 with P3DV5 is on your own risk and responsability.

Please, just use the one from our Contributions/AFCAD link. It is updated to the latest FlyTampa V2 layout !!

Please check here: https://forum.aivlasoft.com/topic/3005-afcad/

Definitely 😀! Thanks for reporting ! You might have found that even in the newest version 5.1 the ILS Frequency for RWY 21R is outdated. You may use the attached BGL to correct this situation. Just set the original to "OFF" and copy this new one into the scenery path and rebuild the database. FAOR_ADEP4_NMG.bgl

Well, that's exactly what I was referring to with a DbUpdate -> Database Update. After that process the database is updated according to the newest status on your simulator, scanning for all installed airport sceneries. This takes in account all sceneries in the traditional scenery.cfg as well as all entries in the add-ons.cfg (so-called packages). The MNG airport in question must be added to the scenery.cfg as the installer does not add it automatically as one would expect of a modern installer. The installer I just purchased today is named "nmg_faor_v51_p3d4.exe". Installing the scenery with that installer and adding it to the scenery.cfg results in proper display of the airport ground layout as can be seen in the attached screenshot. This layout is created by the "FAOR_ADEP4_NMG.bgl" installed in the scenery path of the airport and used by EFB2. I'm sorry if I can't be more specific. This is just a basic install and it requires nothing else than executing the newest installer and adding the installation path to the scenery.cfg.

Yes, there is always a way to correctly show an installed airport😀 That's what EFB2 is here for. But it needs to know where FAOR is installed. The file you mentioned is indeed the default location for FAOR. Did you run a DbUpdate after the scenery update? What is the exact location of the scenery? Please provide a set of Support Files. Edit: I have just installed FAOR and it shows in EFB2 with the Ground Layout of FAOR_ADEP4_NMG.BGL. I must however state that the installer is quite rudimentary. It does not provide an entry in the scenery.cfg. You have to do this manually.

Well, then I'm out of explanation posibilities. A LogFile with a previous build number in a fresh install is simply not possible - never! Sorry to say that but there must be any kind of Gremlin on your machine that replaces such a file with a previous build.

Hello Jean-Luc, What you describe here is technically not possible. A new default install with the newest #116 builds CANNOT prduce anything with respect to the #115 build UNLESS Do you use any automatic file backup/restore utility??? If yes, you need to deactivate it for EFB2 !!

Hi Jean-Luc, Thanks for keeping up your patience! Enjoy !

Sounds great! Make sure that no link to any file of the previous installation exists (e.g. as a Startup shortcut).

Hi Jean-Luc, Normally not, but nevertheless before reinstalling make sure that NO REMAINDERS AT ALL are on any disk. I must admit that I'm not familiar with the reliability uof uninstallers within WIN7. We recommend installation in default paths. Server & Client are only around 98 MB.