December 31, 200520 yr Commercial Member i don't have any add on planes. ;-)i suspect, that when you load the fmc, you're just doing the identifiers, and it looks up the lat/long for themsuper flight planner is giving you what it thinks the lat/longs are, and that is what i'm basing it on.i'm sure their are hundreds of people that load the fmc's, with the plans they use with rc, and they aren't having this particular problem. i would be suspect of the data in super flight planner, but i have no data to back it up.i may try to take the superflight planner plan you sent me, and generate it by hand in fs9, and save the .plnthen compare the two. that will prove/disprove my theoryjd JD Read my blog
December 31, 200520 yr Funny thing is, the NavData cycles from www.navdata.at have one single set for both SFP and PSS. You are supposed to download the PSS one (to use for the FMC), and there is a little utility to convert that into SFP format to be used by SFP. This should mean both FMC and SFP have the same data.Pat, before taxi do you import the .pln into the FMC as a 'company route', or do you enter in each waypoint into the LEGS page manually?If you import the plan, there should be no lat/long error between the plan, FMC, and RC, since it all comes from the single .pln you made. If you enter each waypoint in manually, PSS will look for it's own lat/long database and place waypoints according to that.I would recommend you make a single .pln in SFP. *Import* that into the FMC, and open the same .pln in RC as well. There should now be no errors in the lat/longs.Subs
January 1, 200620 yr Hi SubsThe way I have been doing it is to use the Super Flight Planner Data Wizard to import all Nav Data from FS9 into Super Flight Planner. I then used the convert button in Super Flight Planner to convert these to the correct format for Super Flight Planner. I then compiled the plan in Super Flight Planner and exported this to FS9.Then with the PSS Airbus FMC I import the plan from FS9 and then do exactly the same importing the same plan into RC4. So if everything is using the same scource for Lat/Lon ie:FS9 database via the .pln file why the discrepancies. My brain hurts.As JD has pointed out to me in an E-Mail even the Departure and Destination Airports have slightly different Lat/Lons yet they were derived from the same scource in FS9 when compiling a plan with Super Flight and Planner and then compiling the plan with FS9.JD has left me some homework to do so I shall attempt that and see if it sheds any more light on this.Regards Pat
Create an account or sign in to comment