RC v3.1

[Guest joed1930]

joed1930A question regarding radar contact ver 3.1. The program works great with flight plans from Livewire & other outside sources. The problem is when I do a flight plan in fs9, try to fly this flight plan, it inserts a and a distant milage, also a heading. The milage & heading don't seem to be related at all to the flight plan but it is the first point to be flown. I've tried many times but this mysterious location keep comming up. HOW DO I GET RID OF IT??????Any help would be greatly appreciated.Joe

[jd 57]

i did a quick pln, and it looks like this[flightplan]AppVersion=9.0.30612title=KSAN to KLAXdescription=KSAN, KLAXtype=IFRroutetype=1cruising_altitude=12000departure_id=KSAN, N32* 43.81', W117* 10.53', +000014.00departure_position=27destination_id=KLAX, N33* 56.15', W118* 25.13', +000125.99departure_name=San Diego Intl-Lindberghdestination_name=Los Angeles Intlwaypoint.0=, KSAN, , KSAN, A, N32* 43.81', W117* 10.53', +000014.00, waypoint.1=K2, MZB, , MZB, V, N32* 46.93', W117* 13.53', +000011.99, waypoint.2=K2, OCN, , OCN, V, N33* 14.44', W117* 25.06', +000053.00, waypoint.3=K2, SLI, , SLI, V, N33* 47.00', W118* 3.29', +000023.00, waypoint.4=, KLAX, , KLAX, A, N33* 56.15', W118* 25.13', +000125.99, the k2 is not important. it is the checkpoints that are important. i believe if you do a low airway, or a high airway, the k2 is changed to the airway designator. the k2 may means that you are doing vor-to-vor flight planning (that is what i did on this plan).if you have a question about your flight plan, post it herejd

[Guest joed1930]

joed1930Hello JD,I did the same fp, ksan to klax. The first waypoint seems to be the problem, some 1900 miles @ 165 degrees. I don't know what causes it.I'll try to attach a screenshot for you.Joe

[jd 57]

just post the .pln file, or send it to mejd

[Guest joed1930]

joed1930I'll give this a try.[flightplan]AppVersion=9.0.30612title=KSAN to KLAXdescription=KSAN, KLAXtype=IFRroutetype=1cruising_altitude=12000departure_id=KSAN, N32* 44.07', W117* 11.30', +000014.00departure_position=PARKING 3destination_id=KLAX, N33* 56.15', W118* 25.13', +000125.99departure_name=San Diego Intl-Lindberghdestination_name=Los Angeles Intlwaypoint.0=, KSAN, , KSAN, A, N32* 44.07', W117* 11.30', +000014.00, waypoint.1=K2, MZB, , MZB, V, N32* 46.93', W117* 13.53', +000011.99, waypoint.2=K2, OCN, , OCN, V, N33* 14.44', W117* 25.06', +000053.00, waypoint.3=K2, SLI, , SLI, V, N33* 47.00', W118* 3.29', +000023.00, waypoint.4=, KLAX, , KLAX, A, N33* 56.15', W118* 25.13', +000125.99, This is the flight plan.The top line on the instructions on the panel after starting the flight seemed to be the first waypoint. 1909m/165 degrees/0Joe

[jd 57]

look like you have an old build of v3.1, which didn't know how to read fs9 flight plans. go get the latest build (see the anchored topic at the top of the forum), and download it, replace the files in your rcv3 directory with the files in the zip (replace if necessary), and try it againjd

[Guest joed1930]

joed1930Hello JD,I loaded the latest RC3.1,Fsuipc 3.12, also the other I believe the AdvDisp Dll, created another flight plan, Montgomery field, San Diego this time. No change in the first waypoint. Any other ideas?Thanks Very much for your help.Joe

[Guest joed1930]

joed1930Thanks JD for your patience. I stumbled around until I found & downloaded the latest RC 3.1 update. It works like a charm. Thanks again for your help.Regards,Joe