. . . as used in SIDs and STARs are missing.
This is not unique to FSBuild but other Navigraph exports as well. The example here is relative to a post elsewhere regarding the take-off path from one runway being correct (curved to exit transition point) and the other from the opposing runway being incorrect (direct to transition).
Here's a paste from the 1013 FSBuild 2.4 SID for ESMS:
---------------
NEXI2B RW17 /T171/UA 700 17 55.548056 13.373778
NEXI2B /LT/T028/IC003 --- 17 --- ---
NEXI2B NEXIL --- 17 56.339139 13.733111
NEXI4C RW35 /T351/UA 636 35 55.523078 13.378911
NEXI4C 45DME --- 35 55.608867 13.361639
NEXI4C OEM22 --- 35 55.737956 13.609333
NEXI4C NEXIL --- 35 56.339139 13.733111
-------------
The NEXIL4C path generated matches the published SID of ESMS at Eurocontrol with the turning points correctly defined by coordinates. The aircraft using the FMC SID database followed correctly to the NEXIL transition with a curve and then a slight turn midway to NEXIL. FSBuild mapped the same path.
When the user did a NEXIL2B departure the turns at intercept were ignored and the path followed was direct to NEXIL. FSBuild also displayed a direct to on its map.
Is it Navigraph that supposed to provide the soft waypoints to provide coordinates to designate turning waypoints? Apparently the descriptive line "/LT/T028/IC003" had no effect in the FMC nor plot on FSBuild. I believe the user's aircraft model was the LDS 763.
Is it Navigraph's responsibility to provide soft waypoints if not in the coded departure routes they use? The published charts do not have soft local waypoints as many do (typically labeled similar to D013).
Here's a link to the original post:
http://forum.avsim.net/topic/336173-i-c ... sidsstars/
Login
Register
FAQ
Search
