I create all my flight plans with FSC 8.2. RC reads these plans reliably. However, in some plans, waypoints in the RC4 display show up with numbers like ".30" or ".70". These correspond to actual waypoints in the flight plan and they are in the correct position, so it does not interfere with the flight. But I've always been curious as to why it might assign a waypoint a number like this instead of the actual name as used in FSC.-MJL

Can you open an affected plan using Notepad and copy and paste the contents here please?

I create all my flight plans with FSC 8.2. RC reads these plans reliably. However, in some plans, waypoints in the RC4 display show up with numbers like ".30" or ".70". These correspond to actual waypoints in the flight plan and they are in the correct position, so it does not interfere with the flight. But I've always been curious as to why it might assign a waypoint a number like this instead of the actual name as used in FSC.-MJL

the planner drives what you see in rc, so for some reason the planner is putting them in the .pln.sometimes when there is no name for an intersection, it's called by it's lat/long. is that what you are seeing?what planner did you use?jd

It looks like the numbers are the actual waypoint numbers. It uses the proper name for most waypoint, the number for others.This is the pln file from FSC:================================================================================[flightplan]AppVersion=9.0.30612title=KALB to KIAD description=KALB, KIAD type=IFRroutetype=1cruising_altitude=32000departure_id=KALB, N42* 44.82', W073* 48.28', +000282.00departure_position=01destination_id=KIAD, N38* 56.67', W077* 27.35', +000312.00departure_name=Albany Intldestination_name=Washington Dulles Intlalternate_name=waypoint.0=, KALB, , KALB, A, N42* 44.82', W073* 48.28', +000282.00,waypoint.1=KK, SAX, , SAX 115.70, V, N41* 04.05', W074* 32.30', +000000.00,waypoint.2=KK, BWZ, , BWZ 114.20, V, N40* 47.91', W074* 49.31', +000000.00,waypoint.3=KK, LRP, , LRP 117.30, V, N40* 07.20', W076* 17.48', +000000.00,waypoint.4=KK, JOANE, , JOANE, I, N40* 02.64', W076* 27.36', +000000.00,waypoint.5=KK, DELRO, , DELRO, I, N39* 57.93', W076* 37.52', +000000.00,waypoint.6=KK, BINNS, , BINNS, I, N39* 47.10', W077* 00.66', +000000.00,waypoint.7=KK, HYPER, , HYPER, I, N39* 41.04', W077* 13.51', +000000.00,waypoint.8=KK, MULRR, , MULRR, I, N39* 37.89', W077* 20.14', +000000.00,waypoint.9=KK, AML, , AML 113.50, V, N38* 56.08', W077* 28.00', +000000.00,waypoint.10=, KIAD, , KIAD, A, N38* 56.67', W077* 27.35', +000312.00,[FSC]DepartAPCode=KALB DepartNum=0DepartID=01DepartType=RwyDestAPCode=KIAD RouteType=1SID=STAR=DELRO2.LRPWP=1,VOR,SAX,SPARTA,41.0675,-74.5383,115.70,198.2833,-12.102,1,3322WP=2,VOR,BWZ,BROADWAY,40.7984,-74.8218,114.20,218.6120,-11.701,1,559WP=3,VOR,LRP,LANCASTER,40.1200,-76.2913,117.30,239.2277,-10.102,2,2192WP=4,Int,JOANE,JOANE,40.0440,-76.4560,0.00,238.9749,-10.102,2,15328WP=5,Int,DELRO,DELRO,39.9655,-76.6253,0.00,238.8649,-9.701,2,15068WP=6,Int,BINNS,BINNS,39.7851,-77.0110,0.00,238.7580,-8.800,2,14916WP=7,Int,HYPER,HYPER,39.6839,-77.2251,0.00,238.5104,-8.800,2,15305WP=8,Int,MULRR,MULRR,39.6314,-77.3357,0.00,238.3703,-8.800,2,15521WP=9,VOR,AML,ARMEL,38.9346,-77.4667,113.50,188.3218,-8.498,2,118====================================================================

Hi,your problem lies in the way FSC has formatted the VORs in the flightplan,[flightplan]AppVersion=9.0.30612title=KALB to KIAD description=KALB, KIAD type=IFRroutetype=1cruising_altitude=32000departure_id=KALB, N42* 44.82', W073* 48.28', +000282.00departure_position=01destination_id=KIAD, N38* 56.67', W077* 27.35', +000312.00departure_name=Albany Intldestination_name=Washington Dulles Intlalternate_name=waypoint.0=, KALB, , KALB, A, N42* 44.82', W073* 48.28', +000282.00,waypoint.1=KK, SAX, , SAX 115.70, V, N41* 04.05', W074* 32.30', +000000.00,waypoint.2=KK, BWZ, , BWZ 114.20, V, N40* 47.91', W074* 49.31', +000000.00,waypoint.3=KK, LRP, , LRP 117.30, V, N40* 07.20', W076* 17.48', +000000.00,waypoint.4=KK, JOANE, , JOANE, I, N40* 02.64', W076* 27.36', +000000.00,waypoint.5=KK, DELRO, , DELRO, I, N39* 57.93', W076* 37.52', +000000.00,waypoint.6=KK, BINNS, , BINNS, I, N39* 47.10', W077* 00.66', +000000.00,waypoint.7=KK, HYPER, , HYPER, I, N39* 41.04', W077* 13.51', +000000.00,waypoint.8=KK, MULRR, , MULRR, I, N39* 37.89', W077* 20.14', +000000.00,waypoint.9=KK, AML, , AML 113.50, V, N38* 56.08', W077* 28.00', +000000.00,waypoint.10=, KIAD, , KIAD, A, N38* 56.67', W077* 27.35', +000312.00,An FS flightplan doesn't contain this information, FS gets it from elsewhere, edit the plan to remove the frequencies that I've highlighted in red, like this :-[flightplan]AppVersion=9.0.30612title=KALB to KIAD description=KALB, KIAD type=IFRroutetype=1cruising_altitude=32000departure_id=KALB, N42* 44.82', W073* 48.28', +000282.00departure_position=01destination_id=KIAD, N38* 56.67', W077* 27.35', +000312.00departure_name=Albany Intldestination_name=Washington Dulles Intlalternate_name=waypoint.0=, KALB, , KALB, A, N42* 44.82', W073* 48.28', +000282.00,waypoint.1=KK, SAX, , SAX, V, N41* 04.05', W074* 32.30', +000000.00,waypoint.2=KK, BWZ, , BWZ, V, N40* 47.91', W074* 49.31', +000000.00,waypoint.3=KK, LRP, , LRP, V, N40* 07.20', W076* 17.48', +000000.00,waypoint.4=KK, JOANE, , JOANE, I, N40* 02.64', W076* 27.36', +000000.00,waypoint.5=KK, DELRO, , DELRO, I, N39* 57.93', W076* 37.52', +000000.00,waypoint.6=KK, BINNS, , BINNS, I, N39* 47.10', W077* 00.66', +000000.00,waypoint.7=KK, HYPER, , HYPER, I, N39* 41.04', W077* 13.51', +000000.00,waypoint.8=KK, MULRR, , MULRR, I, N39* 37.89', W077* 20.14', +000000.00,waypoint.9=KK, AML, , AML, V, N38* 56.08', W077* 28.00', +000000.00,waypoint.10=, KIAD, , KIAD, A, N38* 56.67', W077* 27.35', +000312.00,Resave the plan and the waypoints should now be shown correctly,regards,...............Adrian19.

Adrian,Thank you for your help. I don't have FSC but surely it should be able to export a FS plan without those additional 'features'? To have to edit each plan before RC can show the waypoints will be irritating.

Yep, it's the VORs. I came across this a slightly different way, but it's good to know the specific problem.In FSC, you can inter a VOR as either a VOR or an intersection. If you enter it as an intersection, it doesn't include the frequency and thus works fine. The only limitation is SIDS and STARS, which are hardwired to VOR fixes, so you either have to enter the procedure manually (no big deal) or edit the flightplan.Thanks for the insight!

Yep, it's the VORs. I came across this a slightly different way, but it's good to know the specific problem.In FSC, you can inter a VOR as either a VOR or an intersection. If you enter it as an intersection, it doesn't include the frequency and thus works fine. The only limitation is SIDS and STARS, which are hardwired to VOR fixes, so you either have to enter the procedure manually (no big deal) or edit the flightplan.Thanks for the insight!

good to know!thanksjd