lonewulf47

Exactly. DH is - at least at present - only used for Low Minima Approaches, which means ILS. For future Precision Approaches like RNAV/VNAV (AR) possibly also DH may be published, but to my knowledge none are published so far.

Thank you for your kind words on our EFB. Let me answer your question as follows: DH is only displayed where applicable, e.g. CAT II & III ILS and explicitly named as such (DH). The rest is DA/MDA. In the above example the values for the CAT 1 approach is 1250 FT DA, for the LOC it is 1300 ft MDA. Minima are NOT included in AIRAC data. Editing of our own individual Minima Files is done by us. Please note that in this example default values are displayed with amber background. Where applicable there are also individual Minima Files available in the download section https://forum.aivlasoft.com/topic/3003-minima/ , which show the real or at least close to real Minima Values.

This seems to have been a temporary issue with the weather message stream. I also saw it ONCE, but at present not anymore. Not the first and not the last such mishap when it comes to third party data streams over the Net...

Hi Janek, Please re-run the DbBuilder and check again. This should resolve the issue.

Hi, Unlike the other simulators EFB cannot detect X-Plane on its own. Inorder to connet to X-Plane you need to first SELECT the X-Plane database and THEN start EFB Server and Client. This will the allow connection to X-Plane.

In MSFS the active EFB Flightplan in *.pln format (EFB_Current_gps.pln) should be stored in: "C:\Users\User\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState" That's where MSFS is reading flight plans from. This path is automatically set by FSUIPC7. There was however a bug in FSUIPC/ V13, where this path was erroneously set to "..../LocalCache". This bug was corrected in V14 of FSUIPC7. This path is also stores in the Sever Settings under: [SimulatorMsfs] .. .. FlightplanFolder = C:\Users\User\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ I have no idea however why the default FlightPlans shoud be stored in: ...users/onedrive/documents It should be noted that EFB SHOULD NOT BE INSTALLED INTO OneDrive! This is not a vaild installation path for EFB and proper function is not guaranteed. See also FAQ: https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/#comment-17906

In addition to what I wrote before I should also state at this point that your screenshots look a bit "strange" to say the least. RWYs 34L & R are almost 1 km apart. So the situation on your screenshots is by no means meaningful. I have no idea what airport is depicted on your ground layout. When did you run the DbBuilder last time?

Hello Reinhold, I'm sorry but from now on we whoud obey the Forum Rules and continue this thread in English. I'm wondering why EFB is not depicting both RWYs. I guess we are talking of the default airport of HEGN. Looking at my P3DV5 installation both RWYs are properly depicted. Unfortunately I don't have P3DV4 installed anymore on my system. Thus I have no means to check the P3DV4 files. Why the Sim shows both RWYs but EFB shows only one is beyond my understanding. Technically speaking this is actually not even possible as both EFB and P3DV4 use the same BGL. Could you please post a screenshot of the Airport Info of HEGN? (see below)

Hallo Reinhold, Da fehlen schon noch ein paar Angaben wie z.B. Simulator, Default oder Add-On Flugplatz etc. Wir brauchen schon ein paar Daten mehr, um überhaupt irgendeine Aussaage zu machen.

1. It's only a warning, not an error. So no harm is done anyway 2. The respective paths are specified within certain packages. Please do not try to prove anything by showing camouflaged screenprints If a solution is needed, the only way is to create a set of Support Files and send them to support@aivlasoft.com

See manual "5 Client", Chapter 2.3 "X-Plane" -> profile loading. You do not have to use the *.acf filename, but the name used in "ICAO-Code for ATC" which can be seen in Planemaker under the tab "standard/author". See attached sample for the default C172. If there is no code, you neeed to create one or load the profile manually. This is unfortunately an X-Plane limitation which cannot be changed.

EFB only uses either NavDataPro or Navigraph data. There is no third data source.

We encountered exactly the same problem and found out that the flightplan was directed into ...\localCache instead of ...\localState. After inquiring with Pete Dowson he admitted that they had erroneously changed some variables. It took however a few weeks until the new and corrected version was published...

Hi Rolando, "Run WINDOWS 11 PRO, MSFS2020 v1.21.13.0 and FSUIPC V7.2.13" That's exactly the problem. FSUIPC 7.2.13 has a bug which returns a wrong path information. Update to the newest FSUIPC 7.2.14 and the problem is solved...😃

Have you checked whether this specific profile is available in your profiles? You may check the download section of this forum: https://forum.aivlasoft.com/topic/3002-profiles/

A very good solution would be to read the manuals... Manual 5 Client: Chapter 12.2.8: Options: "Forward flight plan to default GPS"...

Unfortunately some of the scenery installed through MarketPlace use data encryption which is not readable for anyone outside MSFS. Therefor EFB is unable to read any such airport information. Nevertheless we have created a possibility to use generic BGLs to have at least some basic layout displayed in the EFB Ground Chart. Please copy the attached file into the AFCAD path of the EFB Server and rebuild the database (in a standard installation to be found at: C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\). Thereafter you should at least see a basic layout of the airport with the most inportant Parking Stands. FSIA.mfs

Nope, it's an issue with the Lorby Organizer. it is however difficult to trace as you didn't provide the requested Support Files yet. Please do the follwing: Make a full Database Rebuild with all scenery activated and then make a set of Support Files and send those UNEDITED to: support@aivlasoft.com

Ok, I see what you mean. I was still a bit too much inclined towards MSFS and I just now realized that you are talking about Prepar3D. In facht the mentioned function should actually do exactly what you expect it to do. For Troubleshooting I recommend to do a complete scan and then create a complete set of support files. This will allow us to do a deeper troubleshooting into this issue. I must neverheless admit that I'm not completely sure whether this function is still working properly after LM introduced the new add-on packages system with P3DV4 ff. Edit: Urs just reviewed the code an confirms, that using the checkbox "scan all scenery" works as intended. So, whatever problem surfaces, we need in any case the support files and an accurate description of the case. In any case it is important to know, that whenever a new scenery is added, a complete rebuild of the Scenery Database is necessary.

Hi, Yes, the easiest method to have all Add-Ons in the EFB database is to run a DatabaseBuild with ALL add-Ons enabled. If you then disable a few, EFB OPS is not hampered. However if you happen to position on a default airport which is actually a disabled Add-On, you will see the airport layout of the Add-On. That's all. But to be honest, I don't think that you would take-off or land on a disabled Add-On, wouldn't you? This of course also means that whenever you add a new Add-On airport, you will have to re-enable all disabled Airports to have all airports scanned by the DatabaseBuilder. Individual disabling can take place thereafter upon your liking.

Please observe our Forum Rules and post your request in English.

Good to hear. Thanks for reporting!

Thank you, Dejan, I was afraid you were using this version...😃 It is confirmed by Pete Dowson that versions 7.2.12 and -13 are buggy inasfar that they return a wrong datapath from MSFS. The bug is (unfortunately) not yet corrected with a new version, but as an intermediate fix you can download the attached exe-File (internally numbered 7.1.2.4) FSUIPC7.exe Please deactivate the original FSUIPC7.exe to FSUIPC7.off and copy this new file into the FSUIPC7 path. Thereafter the flightplan should be forwarded to the correct path and therefore be enabled to be read by MSFS for all default A/C.

Hi Dejan, Thank you for the kind words on EFB. Before we go too deep into troubleshooting, may I ask you which version exact of FSUIPC7 you are using?

Yes, I'm afraid that Asobo/MS has done a few basic changes without giving any information. We have to investigate what teh reason for this is. for the time being there's nothing else possible than to stand by and wait for more information. Sorry for that.