|
Post by mikeking on Feb 13, 2023 14:56:53 GMT
Hello, I just downloaded and installed Airac 2301-R1. I went to plan a LUVUM dep from EGBB and notice that although there are some intersections showing, all the SID ones are not and LUVUM itself is missing.
I went to force full installation but no improvement. Then I disabled all 3rd party scenery as in the manual and 'OK' the scenery library, which made many of the existing IC vanish.
Certain I am doing something wrong.
Any ideas please?
Thanks Mike
|
|
|
Post by Herve Sors on Feb 13, 2023 16:02:07 GMT
Hello Mike, No, you're not doing anything wrong LUVUM as well as the BBNxx and BBExx intersections used for this departure are terminal intersections that are not included in the default FS files and are not added by the FSXP3D update package either. May be in the future, I can consider correcting those terminal intersections as well (at least some) but it is a tremendous amount of work and is difficult to keep up-to-date. Since then, you can add missing terminal intersections using the Europe terminal intersection file (EuropeINT_T.bgl) you will find here www.aero.sors.fr/navint.htmlDo not install any En route additional file since en route intersections are already included in the FSXP3D package at least if if you checked the "Airways, en route and RNAV fixes option Hope it will clarify Regards Hervé
|
|
|
Post by mikeking on Feb 13, 2023 16:27:34 GMT
Many Thanks Herve,
I wil give it a go, what puzzles me is that the terminal intersections were showing up to a (unspecified) while ago, but seemd to vanish. I dont know exactly when, but it may have coincided with me installing 'Plan G' and interfacing the FSXSE data with it. Cant be sure and dont want to insult that very nice prog! I hadnt 'flown' using VatSim for a while so kind of lost track of it all.
Regards
Mike
|
|
|
Post by Herve Sors on Feb 13, 2023 18:13:19 GMT
Ok. We're speaking here of the simulator map and GPS displays. I just checked the situation inside the default FSX-SE file and the updated one included in my package for the following intersections as referenced in the LUVUM 1M & 1Y departure: BBE23, BBE24, BBE25, BBN11, BBN12, BBN30, BBN32, LUVUM There's none of them in the stock FSX-SE file as well as in my updated file. So, if you see some on your FSX Map/GPS display, they come from somewhere else.. Of course, it does not concern any external display that is not necessarily linked to FS data and may use its own database
Let me know
Hervé
|
|