New Wayoints/Routes not showing in FS

[Sasa]

Hi Guys,

I collected a list of wayoints for Antarctica from various sources and now would like to see them in FSX. Problem is: They just don't show up there.

Here's a sample of a waypoint connected to others. Everything compiles fine but the route (and waypoints) neither become visible on FSX's map neither is it possible to find them when making a flight plan.

<Waypoint
	lon="-8.2650000000"
	lat="70.6383333333"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="NEU30">
	<Route
	      routeType="BOTH"
	      name="NeuToHal" >
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W1" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W2" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W3" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W4" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W5" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W6" 
		      altitudeMinimum="300"/> 		      
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="W7" 
		      altitudeMinimum="300"/> 
		<Next
		      waypointType="NAMED"
		      waypointRegion="S1"
		      waypointIdent="ZTH08" 
		      altitudeMinimum="300"/> 		      
	</Route> 	
</Waypoint>
<Waypoint
	lon="-8.6350000000"
	lat="70.6383333333"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W1">
</Waypoint>
<Waypoint
	lon="-10.6133333333"
	lat="71.5566666667"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W2">
</Waypoint>
<Waypoint
	lon="-12.7600000000"
	lat="72.3066666667"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W3">
</Waypoint>
<Waypoint
	lon="-15.0750000000"
	lat="73.0300000000"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W4">
</Waypoint>
<Waypoint
	lon="-17.5816666667"
	lat="73.7216666667"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W5">
</Waypoint>
<Waypoint
	lon="-20.3016666667"
	lat="74.3833333333"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W6">
</Waypoint>
<Waypoint
	lon="-23.2400000000"
	lat="75.0066666667"
	waypointType="NAMED"
	magvar="0.0"
	waypointRegion="S1"
	waypointIdent="W7">
</Waypoint>

Any ideas what could have gone wrong here?

Bests,
Sascha

 

[BASys]

Hi Folks

Sascha -
Your data has likely compiled ok,
but you're looking at the wrong pole.

Try recoding for lat="-70.6383333333"

ATB
Paul

 

[amahran]

Hi Folks

Sascha -
Your data has likely compiled ok,
but you're looking at the wrong pole.

Try recoding for lat="-70.6383333333"

ATB
Paul

You've got eyes of steel

 

[Sasa]

Sascha -
Your data has likely compiled ok,
but you're looking at the wrong pole.

Arrgghhh!!! How stupid can one single person (=me) be!?
Thanks so much for figuring that out! I'm working with coordinates below lat -60 for months now - no idea how I couldn't see that. Thank you so much!

Next question: Even when creating an airway between the waypoints that are closest to the two airports (Neumayer and Halley station in this case), FSX can't find a low or high altitude route between them using the FSX Flight Planner.
I tried to create a flightplan between some airfields in Texas that have no navaids closeby but only waypoints connected to routes (same as in Texas most airstrips in Antarctica don't have navaids hundreds of miles around). But even in case of Texas FSX insists on sending you to the next VOR or NDB first before entering a route/airway on the flight plan. Is that on purpose meaning this is the same in real world?
This would make it impossible in Antarctica to create flightplans except the direct airport-to airport GPS version.

Bests,
Sascha

 

[BASys]

Hi Folks

Sascha -
Are you saying, as your "next question" infers,
that after recompiling with lat="-7 whatever"
you can see your route in the FSX map ?

I've tried, and can't see your route there.

If it had compiled correctly,
it should display on both the map and flightplanner.



AIUI -
The format of your waypoint definitions is incorrect.

You can't just say -
waypoint name/coords, next, next, next, next.



All route nodes are properties of individual waypoints.

You need to declare every waypoint,
each of which must contain their relevant route's previous/next nodes.

i.e.

Waypoint 1
	coords/id data

	Route A
		Previous node
		Next Node
	Route B
		Previous node
		Next Node

Waypoint 2
	coords/id data

	Route A
		Previous node
		Next Node
	Route Z
		Previous node
		Next Node

FS then builds up its route matrix from those waypoints.



Please see attached working example routeing zip
for EGPD Dyce/Aberdeen
to EGPC Wick
to HMR X-RAY - Atlantic Rim (thats west of Orkney/Shetland).

Its a subset of those displayed on this screenie, (not the obvious Aberdeen radial set).

Click here for larger version



The following was for IFR.

I've not played with this recently,
but from recall,
I've had limited success with new routes from existing airport to new airport,
though it might be easier for new routes from new airport to new airport.

For adding/extending a new/modified route from an existing airport,
you are cloning the existing node components from that existing airport,
so automatic route selection in the flightplan dialog might not work as expected.

IIRC, and I'd need to test further,
to avoid vectoring via relatively adjacent VOR/DME, etc.,
your airport's AFDs need to include nodes for both departure and approach
and your routes have to also include those same nodes for both departure and approach.



PS
Where does your region code "S1" come from ?
S == South American states, (which possibly includes Antarctica, though possibly as faked ICAOs).



PPS
altitudeMinimum="300" might possibly be a little too low for your intended route,
as thats only 300 metres AMSL -
- IIRC, the Antarctic Treaty prevents flights below 1000 metres AGL, (disturbance of wildlife).
- Your route might possibly intersect terrain which summits higher than 300 metres AMSL.



HTH
ATB
Paul

 

[Sasa]

Hi Paul,

Right. I'm able to see the waypoints now where they belong. I've also seen that my routing wasn't correct and I corrected it to the format you suggested so that the route was visible in the map.

I think you are right that I have to add routing nodes to the AFD files but this would be something I have to fake because most of those skiways (except the hubs) don't have any. I got the waypoints from some pilots flying down there and some of that stuff is from their personal files that they created. They usually just take off, go on to the next waypoint, then the next one and so on. On arrival of each waypoint they have to make a position report.
In that case I think the most elegant solution will be to just manually create flightplan files and add them to the finished scenery product. Most FMCs can read those anyway so that this will be the most realistic solution so far.

P.S.: Region code S1? No idea actually. I opened one of the few default airports down there in ADE and got this region code.

And yes, a few more meters than 300msl might be a good idea.

Bests,
Sascha

 

[jvile]

PS
Where does your region code "S1" come from ?
S == South American states, (which possibly includes Antarctica, though possibly as faked ICAOs).

Paul

ADE finds some Navaids with the Region Code S1

I think the S1 may be a Region code error in FS. FS could have made it up but that does not follow the SA, NZ, and several other Region codes Antarctic is using.

It appears that Antarctic uses the Region Code which is north of the area of the Airport and Navaids since there is no World Region code listed as S1.

Both FS9 and FSX list an S1 region code in the area of SAWB