Changes to build 252:
"Fixed Export FSX did not use legacy parking names for start position"
Thank you!!
Scott
"Fixed Export FSX did not use legacy parking names for start position"
Thank you!!
Scott
- Welcome to Plan-G Forum Archive.
News:
Plan-G has over 1700 followers on FACEBOOK! Click HERE and add your support
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
Plan-G / Plan-G v4.0.0 / FSX / Exported Flight Plan Greyed-out
October 20, 2021, 05:51:34 PM
Yes, I still fly FSX (can't afford hardware for a new PC just yet)
I've been using Plan-G successfully for years, thanks!! Good stuff!
Plan-G v3.2.2 is installed on my Win10 laptop. FSX is installed on my Win7 desktop. Plan-G exports flight plans across my network successfully and FSX is able to read and execute the exported flight plan. In other words, Plan-G v3.2.2 works as expected.
Recently, I've upgraded to Plan-G v4.0.0 on my laptop. The setup and network connection was successful and flight plans can be exported across the network successfully as expected.
The only difference is, FSX is unable to open the exported flight plan from Plan-G v4.0.0. By that I mean, FSX sees the plan, but the "OK" button to load the flight plan is greyed-out in FSX.
If I create the exact same plan using Plan-G v3.2.2 and export it across the network, the "OK" button in FSX is not greyed-out and the flight plan loads as expected.
I've used notepad to examine the difference in the two example plans below. There are a few differences but most notably are:
"VFR Hancock Co-Bar Harbor to Blue Hill v3.2.2.pln" contains this entry: <DeparturePosition>PARKING 2</DeparturePosition>
"VFR Hancock Co-Bar Harbor to Blue Hill v4.0.0.pln" contains this entry: <DeparturePosition>Parking Ramp GA Small 2</DeparturePosition>
If I edit "VFR Hancock Co-Bar Harbor to Blue Hill v4.0.0.pln" using notepad so that the entry reads "<DeparturePosition>PARKING 2</DeparturePosition>", the "OK" button in FSX is no longer greyed-out, the plan loads, and everything works as expected.
This seems to have something to do with selecting a particular starting position in Plan-G v4.0.0 vs Plan-G v3.2.2, even though they are the exact same starting positions, airports, and flight path.
If I create the exact same plan and starting position using only FSX (no Plan-G), the "OK" button is not greyed-out and notepad reveals the entry to be
"<DeparturePosition>PARKING 2</DeparturePosition>".
This is a very minor issue in an otherwise excellent program so maybe I'm missing something in the export.
Any ideas?
Thank you,
Scott
I've been using Plan-G successfully for years, thanks!! Good stuff!
Plan-G v3.2.2 is installed on my Win10 laptop. FSX is installed on my Win7 desktop. Plan-G exports flight plans across my network successfully and FSX is able to read and execute the exported flight plan. In other words, Plan-G v3.2.2 works as expected.
Recently, I've upgraded to Plan-G v4.0.0 on my laptop. The setup and network connection was successful and flight plans can be exported across the network successfully as expected.
The only difference is, FSX is unable to open the exported flight plan from Plan-G v4.0.0. By that I mean, FSX sees the plan, but the "OK" button to load the flight plan is greyed-out in FSX.
If I create the exact same plan using Plan-G v3.2.2 and export it across the network, the "OK" button in FSX is not greyed-out and the flight plan loads as expected.
I've used notepad to examine the difference in the two example plans below. There are a few differences but most notably are:
"VFR Hancock Co-Bar Harbor to Blue Hill v3.2.2.pln" contains this entry: <DeparturePosition>PARKING 2</DeparturePosition>
"VFR Hancock Co-Bar Harbor to Blue Hill v4.0.0.pln" contains this entry: <DeparturePosition>Parking Ramp GA Small 2</DeparturePosition>
If I edit "VFR Hancock Co-Bar Harbor to Blue Hill v4.0.0.pln" using notepad so that the entry reads "<DeparturePosition>PARKING 2</DeparturePosition>", the "OK" button in FSX is no longer greyed-out, the plan loads, and everything works as expected.
This seems to have something to do with selecting a particular starting position in Plan-G v4.0.0 vs Plan-G v3.2.2, even though they are the exact same starting positions, airports, and flight path.
If I create the exact same plan and starting position using only FSX (no Plan-G), the "OK" button is not greyed-out and notepad reveals the entry to be
"<DeparturePosition>PARKING 2</DeparturePosition>".
This is a very minor issue in an otherwise excellent program so maybe I'm missing something in the export.
Any ideas?
Thank you,
Scott
Pages1