Won't display Vancouver+ Flight Plan

[stanshear]

I've been going through the handbook and getting to grips with Plan-G.  Tried to load an old existing flight plan whihc I've attached, but in the PLAN window it just displays the starting airport, Delta Heritage Park CAK3 for each leg, viz. 12 repetitions of CAK3.  I've attached the pln file and would appreciate it if you could load it and see if it's the same for you.  Maybe you can spot the problem.  Thanks
Stan

[tim arnot]

That's because every waypoint in the plan *is* CAK3. Looks like you managed to save it that way. I'm afraid you'll need to build a new plan.

[flightplan]
title=CAK3 to CAK3
description=CAK3, CAK3
type=IFR
routetype=1
cruising_altitude=11000
departure_id=CAK3, N49* 5.00', W122* 56.00', +000009.84
departure_position=25
destination_id=CAK3, N49* 5.00', W122* 56.00', +000009.84
departure_name=Delta Heritage Air Park
destination_name=Delta Heritage Air Park
waypoint.0=CAK3, A, N49* 5.00', W122* 56.00', +000009.84,
waypoint.1=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.2=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.3=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.4=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.5=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.6=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.7=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.8=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.9=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.10=CAK3, A, N49* 5.00', W122* 56.00', +000000.00,
waypoint.11=CAK3, A, N49* 5.00', W122* 56.00', +000009.84,

[stanshear]

Ooh wow, how the heck did that happen?  The route shows up in FSNav and is a standard one which I never created. See the attachment.

Stan

[stanshear]

I found the problem.  The original plan was created in FSNav and then exported to FS Planner.  The plan that ended up in FS Planner just showed the origination and destination airports, which, being a round trip, were the same.  I'll check this out.  Its an FSNav problem.  Sorry to trouble you guys, but at least I determined what was happening.

Happy flying
Stan