OnCourse Software

It might be worth checking out this section in the manual, Martin. For GPS read FMC.

ADJUSTING FLIGHT PLANS FOR THE GPS
Please Note: This step is entirely optional Once you have created your flight plan a very useful feature is the Adjust FS FP for PF2000 option, available from the PFE main menu - but first a little more info so you understand why this can be so useful. When you create a flight plan in FS, or any other flight planner, it really doesn't care too much about the distance between waypoints or from your departure and destination airports, whereas ProFlight most certainly does. You see any waypoints that are too close together or too close to the airport can cause PFE a lot of problems when vectoring you from one to another. So during the compilation stage ProFlight will drop any waypoints it determines to be too close to either airport or too close together en-route. Consequently if you load the FS flight plan into the GPS it could and most probably will be very different (in terms of waypoints) to the one generated by ProFlight and used by PFE. What I like to do is have the two completely in sync so when I load the FS GPS I know it's showing me the exact same waypoints as there are in the actual ProFlight plan. And this is where the new option button comes in.

I never got round to doing that: maybe I should! Thanks again.

Here's an example of the above problem that I too sometimes get.

Quote:

[flightplan]
AppVersion=9.1.40901
title=LIMF to EGKK
description=LIMF, EGKK
type=IFR
routetype=3
cruising_altitude=38000
departure_id=LIMF, N45* 11.18', E7* 38.92', +000989.00
departure_position=36
destination_id=EGKK, N51* 8.73', W0* 12.57', +000195.00
departure_name=Caselle
destination_name=Gatwick
waypoint.0=, LIMF, , LIMF, A, N45* 11.18', E7* 38.92', +000989.00,
waypoint.1=LI, MF401, , MF401, I, N45* 15.18', E7* 39.07', +000000.00,
waypoint.2=LI, MF402, , MF402, I, N45* 15.25', E7* 44.74', +000000.00,
waypoint.3=LI, SIRLO, LIMF, SIRLO, I, N45* 9.27', E7* 59.57', +000000.00,
waypoint.4=LI, D135O, LIMF, D135O, I, N45* 2.64', E7* 54.04', +000000.00,
waypoint.5=LI, BARBY, LIMF, BARBY, I, N45* 6.50', E7* 41.93', +000000.00,
waypoint.6=LI, D003B, LIMF, D003B, I, N45* 15.18', E7* 39.10', +000000.00,
waypoint.7=LI, MATOG, LIMF, MATOG, I, N45* 23.18', E7* 35.37', +000000.00,
waypoint.8=LI, SCS, , SCS, V, N45* 44.74', E7* 20.31', +002539.0
waypoint.9=LS, MOLUS, , MOLUS, I, N46* 26.63', E6* 40.77', +000000.00,

This is the flightsim .pln A climbing turn to reach sufficient altitude to cross the Alps.
The compiler won't create it in Pf2000. The first wypt being SCS.
If I stay within the turn boundaries (which I should anyway) I don't get nagged. But if for any reason I stray outside
I start to get nagged continuously for the rest of the flight.

vololiberista

What flightplanner do you use and as it done this before?

Dave Leesley wrote:

What flightplanner do you use and as it done this before?

Hi Dave,
I use the FS9 flightplanner. What you see above 'is' the Fs9 pln. text. SIRLO is the actual SID for this departure. That works in PFE as I'm given the correct instructions and height (even though SCL is the first 'compiled' PFE wypt - SIRLO is built into the SID/STAR set up page in PFE). I think the problem lies in the fact that the climbing turn after SIRLO gradually returns to pass almost directly over the airport. As I said, if I stay inside the turn boundaries all is well. If I'm going too fast so that I cannot then I start to get the message which is relayed to me by each and every subsequent control centre.
What triggers the message?
vololiberista

If you stray just outside the parameters,then you will get the message,basically you have got to stay within the boundaries or face the consequences.
Maybe tweak the flightplan a little to try and avoid the nags from ATC...