lonewulf47

Shimon, Thank you for your kind cooperation! I have uploaded the LLBG AFCAD BGL to this section. You can download, unzip and add it to the AFCAD path in the Server's documents path as described. It might be interesting for David Rozenfeld to know how EFB v2 handles AFCAD files. Whenever he is interested he might contact us here or directly to the developer through the support Email address.

I see. Obviously the Add-On BGL has its RWY 03/21deactivated for AI traffic (all RWY Flags set to FALSE). This way EFB v2 cannot depict this RWY because of this reason. Please send us a copy of the "AFX-LLBGade.BGL" file used in your Add-On to create an AFCAD.BGL for this purpose. BTW: who is the Developer of "Ben Gurion X"? The fact that there are 2 files is normal when using an Add-On. It just depicts the order how the files are recognized within EFB v2. It has no meaning for the user. It just helps us for troubleshooting.

Hello Jean, You cannot and should not ( is there any direction to do so?) do manual changes in the Server settings if not instructed to do so. The path for the Flightplan Folder is greyed out because it is not changeable (not even manually), as it is read directly from the registry. This value will overwrite manual changes. Please provide a full set of Support Files to give us the chance to analyze what is going on on your system. The fact that the registry points to a network path is a bit strange. Further on if you use FSX:SE you should only have entries in the FSX:SE tab, not in the FSX tab. So, before we can continue with troubleshooting we need the support files.

Of course there are no procedures for RWY 03/21 if the RWY is not depicted. What Add-On do you use for LLBG? Please make a screenshot of the Info page -> (i) Button left of the Airport name. It should look similar to the example below:

Hello Shimon, The information you rpovided is by far not sufficient. You might have noticed that there are different Simulators, AIRAC providers, ADD-On Designers etc.Please give us as many details as possible. We cannot provide any service without relevant information. So please indicate Build numbers of Server and Client, AIRAC provider (I guess its 1810 ISO 1018), Simulator Type, default or add-On airport etc, etc... Just as a sidenote: in the default installation all RWYs and procedures are available.

Sorry, Giuseppe, I cannot leave your comment unanswered and I would really propose to remain reasonable: - EFB v2 NEVER claimed to be a Flight Planning Tool - There are many Flight Planning Tools around that provide routings in numerous formats, even for EFB v1 and v2 - The Forum is accessible for anyone for free - The reason why we don't provide Exporters is clearly explained in the FAQ - I'm sure you know what the term EFB refers to. If not, I would stronlgy recommend to get all relevant information about - All manuals were available before purchase for free - You could try a full 30 days for free before purchase Claiming that you have wasted your money under these circumstances is not really fair, is it?

Hi Hans, Well, that at least sounds much better ? If there are warnings noted on the message panel, we might still need the Support files. Usually a warning appears if some scenery could not be found, but it does not have a direct influence on EFB v2 operation. Nevertheless it would be interesting to see the Server's Supportfile to check the nature of the warnings. Could you please create a Supportfile and post it here?

Hi Hans, Where did you send the Support Files to? The build# is indicating the actual version of EFB v2. If you check on the download page you will see that e.g. The Server Build is #59 (2.0.59) whereas the Client Build is #77 (2.0.77). The same figures are also shown on the Server and the Client windows in the Bottom Line. In nay case you should always install the latest builds.

Hi Hans, Welcome to the forum. It sounds a bit strange as all that you report here should happen automatically. Could you please provide a set of Support Files. Find the instructions here: https://forum.aivlasoft.com/topic/3046-how-to-create-a-support-file/ and post the files in this thread. We will then (hopefully) be able to analyze what happened to your installation. I would also be helpful to know which builds # you are currently using and which simulator exactly (FSX, FSX:SE).

Hello ???? (please observe the forum rules) In any such case please report the Build# of Server and Client and provide a set of Support Files. First of all check that you ALWAYS run Server and Client with full Admin Rights.

I have only JustSim's LEBL installed. Everything shows up correctly here. Aerosoft/SimWings usually offers various configurations for RWY activities. Could you please check all configurations (don't forget to re-build the database after changing the configuration) and report? It is very likely that one of the configurations uses an inactive RWY 02/20. EDIT: I have just noticed that SimWings simply made RWY 02/20 non-operational, i.e. there are no take-offs and landings allowed for AI traffic. All RWY labels are set to FALSE. This way EFB v2 identifies RWY 02/02 as non operational too. To overcome this simply use the method described here: https://forum.aivlasoft.com/topic/3005-afcad/

Hi ???? (please observe the forum rules) What does the setting (which should be automatically detected after first start/shutdown of both EFB and Simulator) show on your Client's Setting page? When looking at the path you manually enteres, it seems to me that the <username> is missing in your string. "C:\Users\Documents\Flight Simulator X Files" ishould look like this: " C:\Users\<Username>\Documents\Flight Simulator X Files". Please see also manual "3 Server", chapter "2.3.1 Simulator & Weather"

Did you by chance ever use the DIR TO function after having the new routing loaded to allow the routing being updated to the current A/C position? Just to make the difference clear between loading a FLP/Routing inflight and loading a saved flight (scenario) with a current FPL/Routing in EFB v2: When loading the (last ) scenario with a current FPL followed in EFB v2 you don't have to do ANYTHING. The A/C will start at its precious inflight position and the FPL/routing in EFB v2 is automatically synchronized. When REPLACING a FLP/routing inflight (even if it the same routing as used in the stored version), you will have to delete the old FPL/routing in EFB v2, enter the new FPL/routing and APPLY DIR TO to te next waypoint. Please read the description in the announcement thoroughly: " There is no automatic detection of the 'next waypoint'. " Maybe that's the part you missed. I have done this test a few times during testing of the new functions and I never encountered a problem with that, if following the procedures properly.

Hi Marc, Thanky for your contribution. I have already added two B748 files into our "Contributions/Profiles" section. You might check in your profile whether it is really suitable to allow a B747-800 operation on Snow or Ice or Soft fields. Snow or Ice in the context of Profile parameters means that it will be allowed to operate in Arctic/Antarctic environment with only runways available on the Ice Shelf ? However as there are most probably no such aiports in the worldwide airport list there is no harm done with such an entry.

John, This is one of the "Classics" in Flight Simulation. While in ground mode at RJFR press Ctrl+Alt+A. This will depict the Runway layout as it is given with the current ARINC data. You will note that tis airport is a few NM east of the airport depicted in P3D. This simply means that the airport in P3D is wrong. Nothing more and nothing less. EFB V2 can of course not depict any procedures that are not linked to the runway in the simulator if the latter is completely wrongly positioned. That's why you get the warning text when opening the Procedures Panel. There are two remedies: 1. You create your own RLFR sirport with the help of a simple creation too like ADE - or 2. You ask Lockheed Martin to correct the default file My guess is that method 1. is simpler...? Maybe even someone of the community wil be able to help you with a custom created airport BGL. Btw when looking on Google Earth at hte position of the default (wrong) airport ite, it looks as if there are some remainders of a previous airport installation. Dont' forget that even P3D data are quite old. Edit: going back to around 2006 in Google Earth's timeline you can see that at this time the old airport was still operational and the new just finished with the RWY still marked closed.

Ok, thank you, Terblanche! Greetings and best wishes for the upcoming summertime...?

Thank you ??? (sorry, I'm still trying to figure out which one is your first name... excuse my ignorance for foreign names..??) If you agree, I will publish those profiles in our "Contributions/Profiles" section to make them available for download to the community.

Profile recognition is SOLELY based on the *.air file name which must be unique, whereas manufacturer etc. are only required but not unique entries. While looking at the data of your B747-8i profiles I see that you didn't increase the "Parking Min Radius, which should be increased to at least 35 m. I also see that for the Max takeoff weight you used a figure of 442253 kgs, whereas my sources are using 447700 kgs for both -8 and -8F. It's of course still possible that the PMDG manual uses different figures.

no, this is not possible as EFB v2 does not read flightplan data directly from the simulator. I'm afraid that you will have to suffer from that additional work or - alternatively - aske the delevoper of your tool that it shall allow for multiple transfers of the flightplan e.g. using the uplink folder.

Yyes, you can use the "uplink" folder. This folder accepts various formats, amont others also the "*.pln" format used by FSX and P3D. See also the manual "6 Flightplan", chapter "2.3 Flightplan via Uplink".

You have now exactly the problem that I described above. You have now TWO profiles called up by EXACTLY the same Airfile names ! Of coures ONE of the new profiles will be called up, but EFB will not be able to distinguish between the freighter- and the passenger version. I'm sure that whether flying the freighter or the passenger plane, the EFB v2 status window only shows ONE of the two, but always the same. In your case either Boeing 747-8 V3 or Boeing 747-8F V3, unless you always select the profile manually. To overcome this situation you need to limit the selectable Airfile names to the available names without wildcard, i.e. B747-8I for the passenger variant and (B747-8F? or whatever the freighter's *.air file is named) for the freighter variant. Do not use multiple or wildcard entries if not absolutely necessary!

Yes, I see. To be honest this makes me think about whether we have allowed Wildcards for this entry at a certain stage of development. I have to find out with Urs. It is still a bit difficult to find out what you have done to your B747-8 profile ? Generally spoken you need to create a new profile (maybe based on the old B747-400), change the respective figures (mainly the weights) and then enter ONLY NAME OF THE AIRFILE (B747-8I), as long as the old profile of the B747-400 still exists in your profile collection. No two same Airfile name entries are allowed in two different profiles. Do not carrry over the old Airfile names into your newly created profile if the OLD profile still exists. This would mix up the (internal) index and can lead to the effect that the new entry is not recognized. So in short: you should have a new profile for the B747-8i, which connects to the PMDB B747-8i through its Airfile name B747-8I, and the old profile for the B747-400, which connects through the above mentioned airfile names to the B747-400. I would still be interested in seeing your newly created profile.

Hmm, why do you put an Asterisk (*) at the end of the entries in the Airfile Names? Wildcards are not allowed in this input field. This is definitely wrong. Only the FULL NAME of the respective ".air file is required, written exactly as in the installation used by PMDG. As I do not use the B747-8, I'm unable to see what PMDG uses. It doesn't require multiple entries as shown in your Screenie. Just use the NAME of the *.air file without any pre- or suffixes. See the example for the PMDG B777-200: In this case the entry in the AirFile names field would then be: B777-200LR

Jürgen, I have created a NZAA.BGL for the Stock NZAA Airport. You can follow the procedure described here: https://forum.aivlasoft.com/topic/3005-afcad/ by downloading and unzipping this file into the mentioned directory. Be aware that this is not reflecting tha actual state of NZAA airport, it just gives you the same (wrong) airport layout that P3D v4 is using...? For comparison see also Google Earth view of NZAA Airport.

My guess is that you didn't fill in all fields correctly, in particular the name of the *.air file. Could you please post your profile XML file here and I'll have it checked. Please also indicate the name of the *.air file that PMDG is using for its 747-8.