Zach21GF

I was also a bit surprised that I was told to fix it that way as neither the thread linked or the file mentions anything about the issue I had. Once again a massive thank you! Your help is greatly appreciated.

I did the entries cause that seemed to be what the Aivlasoft team said I should, however after another restart your configuration tool trick worked.

I am afraid that didn't work for me, thank you for the suggestion though! I've added my runways.txt file so someone can hopefully tell me what I am doing wrong in it as well Tried your trick again after another restart and this time it worked, not sure why but as long as it works I don't ask questions. Thanks man!

Well I was hoping you could tell me what to put in the file as the issue the post you have shared is not the issue I am having. I don't have any grey runways, they are simply not there, and the runways that are there have the correct identifiers, so I am not sure what you want me to change? The file itself does also not mention a solution for runways (with assumingly the correct identifiers) that are in FSX but not in the EFB. Should I put all the EHAM runways like this? EHAM 18R 18R EHAM 36L 36L EHAM 18L 18L EHAM 36R 36R EHAM 09 09 EHAM 27 27 And so on...

I am not sure how that works? It seems to be for airports with runways that have the wrong designation, which I don't think is the case here as the runways are simply not there, and for such a case it is stated in the runways.txt file that: // C) if a runway in reality (and in Navdata) is existing, but is not available in FSX // *** this case is not possible to assign *** I don't get the errors anymore, however the runways are still not visible. Perhaps you could give me an example of what I should put in the runways.txt file? Simply putting in "EHAM 18R" and so on did not fix the issue.

It does not seem to have solved my problem at the moment, I will try again tomorrow, perhaps it will be more successful after a PC restart. Thank you for the input though!

Hey, I just bought Aivlasoft EFB and so far I must say it looks good! However I have encountered a problem at FlyTampa's Amsterdam scenery, there seems to be 2 runways missing from the EFB despite having the scenery loaded in P3D and having tried the simulator scenery data update twice. The specific errors I am getting are: Navigation data runway ident 04 at airport EHAM could not be assigned to simulator runway. Navigation data runway ident 18R at airport EHAM could not be assigned to simulator runway. Navigation data runway ident 22 at airport EHAM could not be assigned to simulator runway. Navigation data runway ident 36L at airport EHAM could not be assigned to simulator runway. Images: Missing runway 22/04: https://gyazo.com/32edbbaa6e0116905d84b45fc6a7edc1 Missing runway 18R/36L: https://gyazo.com/183f10b9fc69fc6668e2686a4762d5f4 Regards, Zacharias