- Messages
- 6,506
- Country
Just my opinion, but I would not create waypoints unless they are missing or wrong in the sim.
-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
Help with RNAV approach
- Thread starter squawkingvfr
- Start date
- Messages
- 238
- Country
Thanks, I'm confused at the moment. I've now compiled these several times.
1st time - I did both the approaches and waypoints. in the file, all waypoints were called out as "Terminal_Waypoints". When I ran a flight, I was given the choice to choose another approach, and all the approaches, except for the localizer one, were doubled, there were 2 instances of each approach to choose from. And it appropriately sent me to JEGDO Transition to the active 32 as it automatically chose RNAV 32
So I thought, ok, maybe the World Map lied and there are approaches by default at the airport. So I removed both the approaches and waypoints and compiled
2nd time - I missed that you could choose an approach in the World Map, so I'm not sure what showed there, but, in game, when I went to choose an alternate approach, my only choice was visual 32 (as opposed to the wind I had set up to force Rwy 14
3rd time - compiled just the approaches and not the waypoints, did the same flight, this time I saw I could see the approaches in the World Map, all 4 associated with the airport. So I did a move to to cruise, checked to see what approaches were available? None. Just visual 32 (as opposed to the vectors to 14 ATC told me it would do)(I was looking to do ILS14).
4th Time, compiled with all waypoints as "Waypoints" in the approaches, this time, I see one reference to each approach in the world map, but in game I don't get too choose another approach, and it's crashed twice now, once when boston approach was about to give me instructions after contact after takeoff, the second when I attempted to access the VFR map after having been given instructions from Boston Approach.
I think I'll go back to using "Terminal_Waypoints" and include the waypoints in my airport this time. Tomorrow since it 1:30am
- Messages
- 238
- Country
So...
As noted... relying on the waypoints in the game caused ATC to send me to 12,000 ft for a 10 minute IFR flight from KLWM to KASH, normally 2000 ft
Not including the Waypoints with the build and changing the type of intersection from Terminal_Waypoint to Waypoint in the approaches caused crashes.
I'm not sure why last time I saw two listings for each approach when I included the waypoints in the build, although, come to think of it, I forgot to check that.
Upshot being, everything worked best if I included the waypoints in the build along with the approaches, and called the intersections Terminal_Waypoint in the approaches.
After the update, everything seems to be working, I can click on the an approach and it draws it in the World Map mode, although, my ILS approach doesn't look like I expected when approaching from KLWM to KASH. There's still some weirdness in that the "duplicate" waypoints sometimes flash in the World Map. I'm hoping we'll see some improvements in ATC in the near future anyway. Hmm, I suppose I should tell MSFS to delete approaches in the compile (even though there are none at the airport in question), maybe that will help with the flashing?
Be that as it may, I expect either that's correct (the way the ILS approach looks in the World Map) and I just haven't figured out why yet, or my approaches need some adjustment. As noted, I did not include the VOR's as IF's for the Transition legs, even though that's what they're called in the CIFP. I still have some learning to do. So... Expect to see KASH and 69NH (with water runways, too) on Flightsim.to in the very near future.
Thanks everyone for your support.
As noted... relying on the waypoints in the game caused ATC to send me to 12,000 ft for a 10 minute IFR flight from KLWM to KASH, normally 2000 ft
Not including the Waypoints with the build and changing the type of intersection from Terminal_Waypoint to Waypoint in the approaches caused crashes.
I'm not sure why last time I saw two listings for each approach when I included the waypoints in the build, although, come to think of it, I forgot to check that.
Upshot being, everything worked best if I included the waypoints in the build along with the approaches, and called the intersections Terminal_Waypoint in the approaches.
After the update, everything seems to be working, I can click on the an approach and it draws it in the World Map mode, although, my ILS approach doesn't look like I expected when approaching from KLWM to KASH. There's still some weirdness in that the "duplicate" waypoints sometimes flash in the World Map. I'm hoping we'll see some improvements in ATC in the near future anyway. Hmm, I suppose I should tell MSFS to delete approaches in the compile (even though there are none at the airport in question), maybe that will help with the flashing?
Be that as it may, I expect either that's correct (the way the ILS approach looks in the World Map) and I just haven't figured out why yet, or my approaches need some adjustment. As noted, I did not include the VOR's as IF's for the Transition legs, even though that's what they're called in the CIFP. I still have some learning to do. So... Expect to see KASH and 69NH (with water runways, too) on Flightsim.to in the very near future.
Thanks everyone for your support.