News:

Buying something from Amazon? Please consider using my affiliate links - Amazon.com or Amazon.co.uk - You get your stuff, Plan-G gets a little boost :)   

Main Menu

Saving a plan in FSX and FS9 format

Started by AuPif, December 30, 2012, 12:01:02 AM

Previous topic - Next topic

AuPif

First, thanks for making this wonderful planner available!

I am using a russian aeroplane in FSX (Tu-154 b2) that in turn uses a navigation calculation routine requiring flight plans in fs9 format. So, I have been creating my navs by running fs9, with fsnav, just for this purpose. Plan G works very well for me in FSX. I have tried to export  to fs9 format using the export procedure, by selecting FS2004 format, however  when I do so, Plan G still saves under FSX format. Is it not working because I am using an FSX data base and Plan G is not designed for this? Or is there a step I am missing when going from one format to the other?

Thanks in advance for any advice that may be provided.

AuPif.

tim arnot

No, export is not dependent on the data source. Open the plan in notepad, you'll see it's clearly different from an fsx plan.

Tim. @TimArnot

AuPif

I have opened the plans with notepad. That's how I see what format they are in. And a plan exported under "export as 2004 flight plan" still is written as a fsx flight plan. Here is, attached, a small plan I have saved in various ways:

- exported as FSX format
- exported as FS2004 format (both above files are in FSX format)
- same plan made and saved under FS9 (in FS9 format this one)

I wonder if I am not doing something incorrect when I do the FS2004 export. Is there a special step different from FSX export?

Thanks if you can help.

AuPif.

tim arnot

Ok, looks like you have to change to the FS9 data set to export as FS9 format.

Tim. @TimArnot

AuPif

Thanks for the clarification. Plan G is such a nice tool, we tend to ask too much...

AuPif.

tim arnot

I'm sure there was a reason I did it that way, but I don't remember what it was. I'll look at it in the next update and see if it's an easy fix...

Tim. @TimArnot