zacrux

Good to know... Many thanks...

No.. for some reason I assumed that EFB switched screens automatically... ground - departure-enroute-approach .. etc ... Probably a bad assumption on my part .... You know it is sooo painful to have to press a button and all that A great product BTW ... Any plans to tie EFB to a tablet screen ?

I get auto screen switches on take off, but I don't seem to get them on arrival and approach ?? What does EFB key on to determine what phase of flight you are in ?

Duh!!! I was putting the exclusions in the wrong runways.txt file ... Close this one...

I emailed it back, but it may be too large... let me know if you don't get it.

Another stupid question .. concerning KFLL Navdata runway ident 10L at airport KFLL could not be assigned to FSX runway Navdata runway ident 28R at airport KFLL could not be assigned to FSX runway Info - Available FSX runways at this airport are as follows: 09L, 27R, 09R, 27L, 13, 31 I have added this to my runways.txt files KFLL 09L 10L KFLL 27R 28R KFLL 09R nil KFLL 27L nil KFLL 13 nil KFLL 31 nil but I still get the: Navdata runway ident 10L at airport KFLL could not be assigned to FSX runway Navdata runway ident 28R at airport KFLL could not be assigned to FSX runway In the data provider window.. I am certian EFB is reading the runways.txt file because I get other errors if I use a TAB instead of a space in my additions. Any ideas ?

I really meant to clarify that you can just add this to the end of the runways.txt file and not have to enter it in the section where the airport data is actually located in the runways.txt file. For example: KIAD... data .... .... KORD..... data ... ... ... KIAD 10L 09L or does it have to be... KIAD..... data ... ... ... KIAD 10L 09L KORD....data ... ... ...

Does it matter where you put the runway info? (just an example not real ) KIAD 10L 09L