August 4, 201411 yr Hi I use prosim737 when entering a route into prosims fmc it displays it on my nd now if i enter the same route into pilot2atc, then check the map when flying it shows me around 5-10 miles of to one side ive tried this with other aircrafts fmc and have the same problem result is atc telling me im off course, at the moment ive altered the allowed heading variance for the error to stop, is there any reason for the discrepency Mhazy
August 4, 201411 yr Commercial Member I suspect, but don't know, that the data for the lat/lon of the waypoints in the two databases are different or the Mag Variance for each point are different. This should be reduced when we get the ability to import current SIM data into PIlot2ATC. Your temporary work-around sounds like a good one. Regards, Dave
August 8, 201411 yr Author Hi Heres the route Although it applies to all my routes Egnx to egll Dty Cpt Egll Nothing special standard vor stuff Mhazy
August 8, 201411 yr Commercial Member Seems OK here. Although this route does not validate against CFMU. Try this one: DTY4P DTY BNN1C Just thinking here: At what zoom level does it show you off course and do you get ATC vectoring you back onto the correct course. Clive Joy
August 9, 201411 yr Author Hi Will try your route looks like sids I use sometimes use out of egnx rwy 27 Zoom is out quite far not sure what though as never looked Yes I get atc vectoring back on course Plan is built up in pilot2atc and copied into prosim737 fmc software The fact I get vectoring back on course, shows it as being different to my fmc although same info is in both fmc and pilot2atc Ive increased distance for now in pilot2atc for atc warning so it gets me over problem but would be nice to get same routes in both programs working together Mhazy
August 9, 201411 yr Commercial Member This definitely sounds like a difference in the lat/lon of the waypoints in the two databases. I don't know where prosim737 gets its data, but if it's from the sim, then when we get to the version of Pilot2ATC that lets you import local scenery files then it could resolve the issue. In the mean time, I think you definitely came up with the best solution. Dave
Create an account or sign in to comment