On my last two flights with RC, shortly after takeoff, I've been told to go on a heading that does not get me on my flight plan. I thought maybe it was just vectoring for traffic, but after several minutes of going the wrong way, I decided to request a direct to to get me back on track. However, when I Press "9" and then "1", I get something like the following:1-< 2>2474m/02-< 3>2461m/03-< 4>2458m/04-< 5>2457m/05-< 6>2451m/0Prev-8 Main-0 Next-9I've used the direct-to option before, but this has happened on my last 2 flights. I loaded the correct flight plan in RC and received clearance to my destination airport.Anyone know why I'm being told to go on what appears to be the wrong heading after departure and then why my waypoints are showing up in the list?FS9ASAWinXP, SP3RC v4.3.3845Thanks!Stacey

On my last two flights with RC, shortly after takeoff, I've been told to go on a heading that does not get me on my flight plan. I thought maybe it was just vectoring for traffic, but after several minutes of going the wrong way, I decided to request a direct to to get me back on track. However, when I Press "9" and then "1", I get something like the following:1-< 2>2474m/02-< 3>2461m/03-< 4>2458m/04-< 5>2457m/05-< 6>2451m/0Prev-8 Main-0 Next-9I've used the direct-to option before, but this has happened on my last 2 flights. I loaded the correct flight plan in RC and received clearance to my destination airport.Anyone know why I'm being told to go on what appears to be the wrong heading after departure and then why my waypoints are showing up in the list?FS9ASAWinXP, SP3RC v4.3.3845Thanks!Stacey

how many named checkpoints are you in your plan? post your .pln herejd

how many named checkpoints are you in your plan? post your .pln herejd

[flightplan]title=KLGA to KORDdescription=KLGA, KORDtype=IFRroutetype=3cruising_altitude=38000departure_id=KLGA, N40* 46.38', W73* 52.21', +000021.00departure_position=13destination_id=KORD, N41* 58.51', W87* 54.23', +000672.00departure_name=LA_GUARDIAdestination_name=CHICAGO-O'HARE_INTLwaypoint.0=, KLGA, , KLGA, A, N40* 46.38', W73* 52.21', +000000.00, waypoint.1=, , , COATE, I, N41* 8.10', W74* 41.42', +000000.00, J36waypoint.2=, , , LHY, V, N41* 28.32', W75* 28.57', +000000.00, J36waypoint.3=, , , DGRAF, I, N41* 41.10', W76* 13.21', +000000.00, J36waypoint.4=, , , LHY45, I, N41* 44.31', W76* 25.20', +000000.00, J36waypoint.5=, , , MINEO, I, N41* 46.11', W76* 31.20', +000000.00, J36waypoint.6=, , , REBBL, I, N41* 52.57', W76* 55.58', +000000.00, J36waypoint.7=, , , WAAKE, I, N42* 20.31', W78* 40.51', +000000.00, J36waypoint.8=, , , DKK, V, N42* 29.26', W79* 16.26', +000000.00, J36waypoint.9=, , , JLGON, I, N42* 34.46', W81* 25.51', +000000.00, J36waypoint.10=, , , GOOSS, I, N42* 40.49', W82* 0.13', +000000.00, J36waypoint.11=, , , ATTIX, I, N42* 55.01', W83* 25.50', +000000.00, J36waypoint.12=, , , FNT, V, N42* 58.00', W83* 44.49', +000000.00, waypoint.13=, , , EMMMA, I, N42* 53.03', W84* 34.50', +000000.00, waypoint.14=, , , LTOUR, I, N42* 50.57', W84* 55.05', +000000.00, waypoint.15=, , , GRR, V, N42* 47.12', W85* 29.49', +000000.00, waypoint.16=, , , DITCA, I, N42* 44.50', W85* 43.00', +000000.00, waypoint.17=, , , WLTER, I, N42* 41.11', W86* 3.03', +000000.00, waypoint.18=, , , RHIVR, I, N42* 38.45', W86* 16.14', +000000.00, waypoint.19=, , , PAITN, I, N42* 33.39', W86* 43.21', +000000.00, waypoint.20=, , , WYNDE, I, N42* 27.20', W87* 6.36', +000000.00, waypoint.21=, , , FIYER, I, N42* 23.51', W87* 19.16', +000000.00, waypoint.22=, , , ERNNY, I, N42* 20.19', W87* 32.03', +000000.00, waypoint.23=, , , PAPPI, I, N42* 16.11', W87* 36.25', +000000.00, waypoint.24=, , , ORD, V, N41* 59.15', W87* 54.17', +000000.00, waypoint.25=, KORD, , KORD, A, N41* 58.51', W87* 54.23', +000000.00, AppVersion=9.1.40901

What planner created that one. It looks off with all of those extra comma fields, etc., and label duplications. I'm an FS9 user but the non-XML format for FSX is the same to my knowledge.There used to be a problem with Active Sky 6.5 and earlier. There was an option called convert flight plans to FS9 that if checked doubled up those fields. The solution was to leave it unchecked. If ASA has such an option turn it off.Here's one of mine created with FS Build:[flightplan]title=KMSP to KMDWdescription=KMSP, KMDWtype=IFRroutetype=3cruising_altitude=29000departure_id=KMSP, N44* 52.55', W093* 13.18',+000841.00departure_position=30Ldestination_id=KMDW, N41* 47.09', W087* 45.08',+000620.00departure_name=MINNEAPOLIS-ST_PAUL_INTL/WOLD-destination_name=CHICAGO_MIDWAY_INTLwaypoint.0=KMSP, A, N44* 52.55', W093* 13.18', +000000.00, waypoint.1=UKN, V, N43* 16.48', W091* 32.14', +20000.00, waypoint.2=DBQ, V, N42* 24.05', W090* 42.32', +29000.00, waypoint.3=CVA, V, N41* 42.30', W090* 28.59', +29000.00, waypoint.4=CVA42, I, N41* 15.55', W089* 45.43', +29000.00, waypoint.5=BDF, V, N41* 09.35', W089* 35.16', +29000.00, waypoint.6=MOTIF, I, N41* 13.46', W088* 30.03', +29000.00, waypoint.7=MINOK, I, N41* 28.07', W088* 21.47', +29000.00, waypoint.8=JOT, V, N41* 32.47', W088* 19.06', +29000.00, waypoint.9=KMDW, A, N41* 47.09', W087* 45.08', +000000.00,

What planner created that one. It looks off with all of those extra comma fields, etc., and label duplications. I'm an FS9 user but the non-XML format for FSX is the same to my knowledge.

Yes, that was it. I created the original flight plan with FSBuild as well. However, when I loaded the Flight Plan in FS9, I changed the cruise altitude in the FS9 flight Plan editor and re-saved it. After re-saving with FS9, the flight plan looks like what I posted above (i.e., with the extra commas).That's probably something that RC should be able to handle?Thanks!Stacey

Here is a quickie .pln created in FS9:[flightplan]AppVersion=9.1.40901title=KANE to KDLHdescription=KANE, KDLHtype=IFRroutetype=2cruising_altitude=9000departure_id=KANE, N45* 8.28', W93* 12.94', +000911.99departure_position=PARKING 4destination_id=KDLH, N46* 50.48', W92* 10.82', +001427.99departure_name=Anoka Co-Blainedestination_name=Duluth Intlwaypoint.0=, KANE, , KANE, A, N45* 8.28', W93* 12.94', +000911.99, waypoint.1=K3, AADCO, KANE, AADCO, I, N45* 17.10', W93* 12.46', +000000.00, waypoint.2=K3, MASWE, KDLH, MASWE, I, N46* 46.91', W92* 2.14', +000000.00, waypoint.3=, KDLH, , KDLH, A, N46* 50.48', W92* 10.82', +001427.99, RC will handle this format AFAIK. I don't think it likes all of those blank fields created when the FSB plan was loaded into FS for your edit. jd did make some adjustments to accommodate this a long time ago.I have quickly adjusted the cruise altitude in a .pln file by overwriting it in Notepad and saving the file. You also if you need to can adjust this preflight in RC itself for ATC purposes. You can also in FSB the ability to import an FS9 .pln file, adjust the cruise altitude, and rebuild with export - probably the best way especially if you use the weather interface and fuel planning.My method I always save my routes in FSB, make changes, and rebuild/export in FSB taking advantage of its connection to Active Sky and fuel planning which would change with cruise altitude changes due to winds aloft and aircraft density altitude performance. I never cared for the FS8 planner drag and drop preferring a freeware FS8 planner (NAV 3.0, then NAV 3.1 for FS9) using charts I had from my real world days. I also found out that at least for the FS9 planner I can't print it because Internet Explorer is not my default browser (according to some posts elsewhere) and it failed on me.I went to FSB when I started flying proprietary FMC facilitated aircraft.I am not sure it isn't an FSB problem in using the same FS8 and FS9 format and not producing those extra fields. That being said I never had trouble with any add-ons sticking with just FSB for creating and modifying either loading FSB or FS9 plans into FSB unless a waypoint is missing.

[flightplan]title=KLGA to KORDdescription=KLGA, KORDtype=IFRroutetype=3cruising_altitude=38000departure_id=KLGA, N40* 46.38', W73* 52.21', +000021.00departure_position=13destination_id=KORD, N41* 58.51', W87* 54.23', +000672.00departure_name=LA_GUARDIAdestination_name=CHICAGO-O'HARE_INTLwaypoint.0=, KLGA, , KLGA, A, N40* 46.38', W73* 52.21', +000000.00, waypoint.1=, , , COATE, I, N41* 8.10', W74* 41.42', +000000.00, J36waypoint.2=, , , LHY, V, N41* 28.32', W75* 28.57', +000000.00, J36waypoint.3=, , , DGRAF, I, N41* 41.10', W76* 13.21', +000000.00, J36waypoint.4=, , , LHY45, I, N41* 44.31', W76* 25.20', +000000.00, J36waypoint.5=, , , MINEO, I, N41* 46.11', W76* 31.20', +000000.00, J36waypoint.6=, , , REBBL, I, N41* 52.57', W76* 55.58', +000000.00, J36waypoint.7=, , , WAAKE, I, N42* 20.31', W78* 40.51', +000000.00, J36waypoint.8=, , , DKK, V, N42* 29.26', W79* 16.26', +000000.00, J36waypoint.9=, , , JLGON, I, N42* 34.46', W81* 25.51', +000000.00, J36waypoint.10=, , , GOOSS, I, N42* 40.49', W82* 0.13', +000000.00, J36waypoint.11=, , , ATTIX, I, N42* 55.01', W83* 25.50', +000000.00, J36waypoint.12=, , , FNT, V, N42* 58.00', W83* 44.49', +000000.00, waypoint.13=, , , EMMMA, I, N42* 53.03', W84* 34.50', +000000.00, waypoint.14=, , , LTOUR, I, N42* 50.57', W84* 55.05', +000000.00, waypoint.15=, , , GRR, V, N42* 47.12', W85* 29.49', +000000.00, waypoint.16=, , , DITCA, I, N42* 44.50', W85* 43.00', +000000.00, waypoint.17=, , , WLTER, I, N42* 41.11', W86* 3.03', +000000.00, waypoint.18=, , , RHIVR, I, N42* 38.45', W86* 16.14', +000000.00, waypoint.19=, , , PAITN, I, N42* 33.39', W86* 43.21', +000000.00, waypoint.20=, , , WYNDE, I, N42* 27.20', W87* 6.36', +000000.00, waypoint.21=, , , FIYER, I, N42* 23.51', W87* 19.16', +000000.00, waypoint.22=, , , ERNNY, I, N42* 20.19', W87* 32.03', +000000.00, waypoint.23=, , , PAPPI, I, N42* 16.11', W87* 36.25', +000000.00, waypoint.24=, , , ORD, V, N41* 59.15', W87* 54.17', +000000.00, waypoint.25=, KORD, , KORD, A, N41* 58.51', W87* 54.23', +000000.00, AppVersion=9.1.40901

doesn't look like a valide .pln file. everything after the = has extra commasjd

doesn't look like a valide .pln file. everything after the = has extra commasjd

This was my steps:1) Created the plan in FSBuild, exporting in FS2004/FSX format.2) Look at the plan from inside notepad. Those extra commas are not present.3) Start FS94) Load the flight plan5) Change the cruise altitude6) Save the flight plan in FS97) Look at the plan from inside notepad. The extra commas are present.When I do not re-save the flight plan from within FS9, I do not have the problem originally stated at the beginning of this thread.Thanks,Stacey