Andydigital

Simply run the Navigraph exe on the FSX PC and it will install automatically, there is no need to do anything on the Displayunit PC.

It depends what products you have. If you only have Global and EU LC then no. If you have any regional products then ideally you want all of those active when you do a scenery update, but I realise that is not possible in all cases. Personally I now only have Global and EU LC installed neither of which need a scenery build as they include no airports, but I also have all the UK regional products installed which do require adding to the EFB library. If you leave FTX central in Global mode with Hybrid mode active you can run a scenery build now and that should capture the details of all the airports you have in your regional products. I don't have all my ORBX products installed though so can't confirm if it works 100%. So in summary if you are going to be flying into an FTX regional product and it wasn't active the past time you did a rebuild of the scenery in EFB, then yes you will have to rebuild it again this time.

Hi Theo, I suggest you send the log files to Urs via email as suggested by Travis in his last reply to you.

See rule number 3 Suitable keywords would be; Tablet iPad Android Windows RT Also if I remember correctly make sure you actually have a departure, arrival, and approach assigned in EFB or it won't switch to those pages, instead you will only get departure ground, enroute, then arrival ground.

Yes.

I will have to defer to Urs, I am out of suggestions.

Is it talking about the version of the sim you are using then? If you are using FSX and P3D you have to tell the data provider which sim you are going to use, if EFB then detects you are not using the sim selected in the provider it warns you.

I think this means that the Data provider version does not match the Display unit version, download a fresh copy of the installer from the website and reinstall both parts, that should fix it.

You can use as many display units as you like, I use two sometimes depending on what I am doing. The manual explains how to go about setting it up.

You need to either fix your seriously slow wireless connection or you need to buy a network switch to put into your room with the FSX and EFB PCs, then you can plug the switch into the wall socket and plug your PC's into the switch also.

There is a tutorial about how to enter details into the Runways.txt file in the FAQ section of the forum. viewtopic.php?f=3&t=1260 By the way Urs if you read this there are some pictures missing from said tutorial.

Try reversing the numbers in the runways.txt file. So if you had 10 09, try 09 10 instead.

I can never figure out which way to put the numbers so try putting the numbers the other way around and see if it helps i.e. LKTB 09 10 etc.

It's slower over a network for me but, it only takes about 15 seconds (not minutes) to load and that is wireless too. I have about 197 layers in my scenery.cfg and all of the FTX UK regional products plus FTX Global/Vector etc. Locally EFB loads more or less instantly.

Urs will have to take over from here I've clearly reached the limit of my ability to explain the situation as I understand it. Sorry.

Hi Richard, BLZZR2 is a SID and not an enroute waypoint, you can even see it in the ATS routing box, procedures are not normally included in the flight plan and if those waypoints aren't in FSX's navdata (which after all this time is very likely the case as FSX's own data hasn't been update since 2005) that is likely why they are dropped from your FSX plan when you export it. Try opening the FSX map and zoom in on the procedure and see if you can see the individual waypoints that go into making that SID, if you cannot see them then you have your answer I think. By the way SIDS and STARS are not editable in v1 of EFB, the original reasoning behind that decision was that the moment you edit a procedure it is no longer valid. I think it will be possible in V2 though.

You don't have any waypoints in your flight plan that's why, you only have a origin and destination plus SID or STAR. SIDS and STARS are not put in exported flight plans for some aircraft formats because the developers specifically tell third parties not to include them, PMDG for example is one such developer who will not allow Aivlasoft to include procedures in the rte plan as its not realistic and it causes problems for their FMC's. The pilot of such aircraft are required to enter the procedure manual by selecting them in the FMC. It's covered in the manual. EFB Version 1 development has been frozen for well over 12 months now, only bugs will be fixed. Version 2 has been in development for a significant time, any feature requests should be made in the Wishlist forum area for possible inclusion in V2.

Waiting won't make you feel any better, a release date is not on the horizon yet. You may as well use all the trial though.

There is a similar thread below discussing the same problem along with how to fix it. viewtopic.php?f=5&t=1468&p=8505&hilit=fs9+format#p8505

It's probably a fs9 formated file in that case which are not compatible with efb v1.

Please see the Frequently Asked Questions forum, in particular the thread linked to below Runways.txt / Runway identifiers are greyed out viewtopic.php?f=3&t=1260

A little more info is in the thread below if Frans is not sure what we mean. viewtopic.php?f=5&t=673&p=4051&hilit=yellow+rectangle#p4051

That sounds like the user is using the Windows Classic theme i.e. no yellow highlight box around active buttons.

EFB will not automatically put a flight plan into the Majestic FMC as far as I know, only aircraft that support the default MSFS GPS system will work with this automated process. Most FMC's require YOU the pilot to input the flight plan or at least load/import the plan into it and only IF EFB supports exporting plans to the aircraft in question.

Are you using the same Navdata cycle on both the Airbus and in EFB? If not then that is probably why they don't match, because procedures change all the time, that is why they need to be updated 13 times a year.