Jump to content
Sign in to follow this  
Talek

flightaware routes don't work with FSC9

Recommended Posts

hi

i have a problem with flightaware routes, for example i want to do this flight:

http://fr.flightawar...0510Z/KSFO/EDDM

 

SFO SAC J32 FMG KU72M PIH BIL VLN 5430N 10000W 5930N 9000W 6200N 8000W ALSAK KENKI 6500N 6000W 6500N 5000W 6500N 4000W 6400N 3000W 6200N 2000W BALIX UP59 NINEX UP59 NEXUS UM90 LONAM UL7 PAM UP62 TEBRO UL603 TESGA UZ729 BOMBI T104 BURAM

 

When i copy this route in FSC9 it shows me this weird route:

 

 

What's wrong ? It makes me that for every route on flightaware

Share this post


Link to post
Share on other sites

Try this:

SFO SAC J32 FMG KU72M PIH BIL VLN 5430N10000W 5930N9000W 6200N8000W ALSAK KENKI 6500N6000W 6500N5000W 6500N4000W 6400N3000W 6200N2000W BALIX UP59 NINEX UP59 NEXUS UM90 LONAM UL7 PAM UP62 TEBRO UL603 TESGA UZ729 BOMBI T104 BURAM

 

Seems the spaces mess things up. Same thing happened when I put that route into FSBuild.


Clarke Kruger - CYEG 

 

 

Share this post


Link to post
Share on other sites

Thanks it works but FSC9 doesnt show things like "5930N9000W" they are just direct routes between VLN ALSAK KENKI BALIX , but no coordinates.

 

Which route do i have to put in PMDG 747 FMC, the flightaware route ? your route ?

Share this post


Link to post
Share on other sites

Ok i just figured out how it works in FSC9

if W is more than 10000:

5430N 10000W = 54N00 in FSC9 and FMC

if W is less than 10000:

5930N 9000W = 5990N

6200N 8000W = 6280N

 

etc ...

Share this post


Link to post
Share on other sites

I would check the formatting of your lat/long points...flightaware uses a different format than FSC and they can't be directly copies over. FSX used a five-figure lat/long point.

 

For example:

 

Flightaware: 5430N 10000W

FSC: 54N00

 

Flightaware: 6500N 6000W

FSC: 6560N

 

If the long is > 100, the N (or S as the case may be) goes in between the lat and long and the leading "1" in the long is dropped (first example)

If the long is < 100, the N (or S as the case may be) goes at the end.

 

There are more variations...for example if you're flying in an area of east longitude...I'd suggest looking at the formatting of the lat/long points in the area you're flying in to see the proper format.

 

Hope this helps.

 

EDIT: ah, you beat me to it :-)


Dave

Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 4080, 55" Samsung Q80T, 32GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, HP Reverb G2, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...