Hi,

I made a flight plan in LNM 2.6.7 LZTT-EPLL and exported to FSX - pln format. AS2012 draws all the LZTT-EPLL waypoints and adds direct back to the LZTT. As a result I have 310 nm in AS2012 instead of 183 nm in LNM and in FSX.

I found in IFR Tatry (LZTT) to Lublinek (EPLL) .pln
probably a bug:

    <FlightPlan.FlightPlan>
        <Title>LZTT to EPLL</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>18000</CruisingAlt>
        <DepartureID>LZTT</DepartureID>
        <DepartureLLA>N49° 4' 25.00",E20° 14' 28.00",+002356.00</DepartureLLA>
        <DestinationID>EPLL</DestinationID>
        <DestinationLLA>N49° 4' 25.00",E20° 14' 28.00",+002356.00</DestinationLLA>

There should probably be:

N51° 43' 18.77",E19° 23' 53.28",+000607.00

just like at the end of the plan:

        <ATCWaypoint id="EPLL">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N51° 43' 18.77",E19° 23' 53.28",+000607.00</WorldPosition>
            <ICAO>
                <ICAOIdent>EPLL</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

The plan is displayed correctly on the plane (PMDG JS41), RC4 and FSX.

Other plans from version 2.6.7 have the same bug, Plans from version 2.6.6 do not have this bug.

Regards

wojtek

 

Meh. 😞 Seems this crept in when adapting the export for MSFS (all same code).

This affects all FSX, P3D and MSFS flight plan exports.

Thanks for reporting. Have to see if I can make a quick update.

Alex

Hi Alex,
When can I expect this bug to be fixed? I don't know if I should go back to version 2.6.6 temporarily.

Regards

wojtek

Soon. Let's say mid next week but don't nail me on it. The 2.6.8 will contain quite a few bug fixes.

Alex

4 hours ago, albar965 said:

Soon. Let's say mid next week but don't nail me on it. The 2.6.8 will contain quite a few bug fixes.

Danke Alex, ich werde geduldig sein;)

wojtek

Of course, since version 2.6.8 I have no errors in flight plans, thank you, but in the new Little Navconnect I get a red message:

"Too many errors reading from simulator.Disconnected. Restart LNC ..."

I have to restart the LNC, sometimes twice to make it reconnect. So far back to LNC 2.6.7, he doesn't have this problem.

regards

wojtek

18 hours ago, wbober said:

Of course, since version 2.6.8 I have no errors in flight plans, thank you, but in the new Little Navconnect I get a red message:

"Too many errors reading from simulator.Disconnected. Restart LNC ..."

I don't see this here. Try to increase the update interval. Network code did not change for years.

LNM 2.6.10 is the latest, BTW.

Edit: Try to disable AI. Maybe this helps.

Alex

Edited March 6, 20215 yr by albar965

Unfortunately, none of the suggestions help, but that's not a big problem, I'll stick with Little Navconnect version 2.6.7.
Thanks Alex,
Wojtek