Zach21GF Posted February 19, 2018 Share Posted February 19, 2018 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 Link to comment Share on other sites More sharing options...
Jason Posted February 19, 2018 Share Posted February 19, 2018 Hi Zach, I had this issue yesterday and managed to sort it our from the post below, which I stumbled on whilst going through the forum. It did work for me. Thanks Jason Link to comment Share on other sites More sharing options...
Zach21GF Posted February 20, 2018 Author Share Posted February 20, 2018 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! Link to comment Share on other sites More sharing options...
aivlasoft Posted February 20, 2018 Share Posted February 20, 2018 https://forum.aivlasoft.com/topic/1195-runwaystxt-runway-identifiers-are-greyed-out/ Link to comment Share on other sites More sharing options...
Zach21GF Posted February 20, 2018 Author Share Posted February 20, 2018 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. Link to comment Share on other sites More sharing options...
aivlasoft Posted February 21, 2018 Share Posted February 21, 2018 15 hours ago, Zach21GF said: Perhaps you could give me an example of what I should put in the runways.txt file? https://forum.aivlasoft.com/topic/1195-runwaystxt-runway-identifiers-are-greyed-out/ This is THE example. I really don't know how to explain it in more detail. Link to comment Share on other sites More sharing options...
Zach21GF Posted February 21, 2018 Author Share Posted February 21, 2018 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... Link to comment Share on other sites More sharing options...
aivlasoft Posted February 21, 2018 Share Posted February 21, 2018 Hi Zacharias, sorry, I have to apologize! I only now saw the screenshots in your first post. I always thought that it is a problem of the runway assignment. Sorry again. Ok, back to square one. From the screenshots you provided, this seems to be a problem which is caused by the underlying BGL file(s) from FlyTampa. EFB does not change BGL files, it only reads them and analyzes its content. In other words, if there are runways missed on the EFB ground chart representation, then you have to switch over to FlyTampa to ask for support. The entries you made in the file runways.txt can be removed. Sorry again for troubles, that was not my intention. Link to comment Share on other sites More sharing options...
RayProudfoot Posted February 21, 2018 Share Posted February 21, 2018 On 20/02/2018 at 12:23 AM, Zach21GF said: 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! After making the change to the runways using the configuration tool provided you need to start FSX/P3D so the indexes can be rebuilt. Then exit FSX/P3D, Start EFB and rebuild the database. It worked for me. Link to comment Share on other sites More sharing options...
Zach21GF Posted February 22, 2018 Author Share Posted February 22, 2018 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! Link to comment Share on other sites More sharing options...
RayProudfoot Posted February 22, 2018 Share Posted February 22, 2018 19 minutes ago, Zach21GF said: 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 Runways.txt UPDATE: Just seen your latest reply. Good, problem solved. You still need to remove those entries from runways.txt. Remove the EHAM entries. They’re not doing anything. When you say “that didn’t work for me” please be specific. What didn’t work? The configuration tool for EHAM gives you the option to enable all runways. I know as I had the same problem and that fixed it. Perhaps you can provide a screenshot of the utility and your chosen option. Link to comment Share on other sites More sharing options...
Zach21GF Posted February 22, 2018 Author Share Posted February 22, 2018 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. Link to comment Share on other sites More sharing options...
RayProudfoot Posted February 22, 2018 Share Posted February 22, 2018 2 minutes ago, Zach21GF said: 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. The entries weren’t needed for that problem. Glad you’re sorted. Link to comment Share on other sites More sharing options...
Zach21GF Posted February 22, 2018 Author Share Posted February 22, 2018 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. Link to comment Share on other sites More sharing options...
Recommended Posts