GPS and flight plan questions...

[whammo11224 0]

I noticed that when I create a flight and I select "high altitude airways" for the route, the route is thousands of miles long for a short flight. It appears that route information is corrupted. Also in the GPS window "facility information", when you select an airport with multiple ILS's and communication frequencies, you can't see all of them in the window. There is no way to scroll up or down.

 

Thanks

[whammo11224 0]

Just did another test. RJTT-RJOO flight. Used the default flight planner. Used "high altitude airways". The flight planner created a route that was 15,000 miles long. Seriously, no one else is seeing this?

[BRIAN1158 1]

Hi,

Try this flight plan at 8000 Feet........

 

RouteFinder
Route generator for PC flight simulation use - NOT FOR REAL WORLD NAVIGATION
©2005-2007 ASA srl - Italy

Computed route from TOKYO INTL (RJTT, RJ) to OSAKA INTL (RJOO, RJ): 7 fixes, 232.2 nautical miles

Cruise altitude between FL080 and FL080
RJTT (0.0nm) -DCT-> NAKNO (24.1nm) -Y18-> MITOH (36.5nm) -Y18->
SILVI (71.4nm) -Y18-> FUSOH (143.9nm) -Y184-> HIKNE (186.8nm) -DCT->
RJOO (232.2nm)

 

Details:

ID      FREQ   TRK   DIST   Coords                       Name/RemarksRJTT             0      0   N35°33'12.00" E139°46'52.00" TOKYO INTLNAKNO          304     24   N35°49'04.81" E139°24'32.89" NAKNOMITOH          256     12   N35°47'34.32" E139°09'26.37" MITOHSILVI          256     35   N35°43'08.00" E138°26'44.00" SILVIFUSOH          254     72   N35°31'26.69" E136°58'47.01" FUSOHHIKNE          239     43   N35°14'15.45" E136°10'37.04" HIKNERJOO           226     45   N34°47'04.00" E135°26'21.00" OSAKA INTL

Tracks are magnetic, distances are in nautical miles.

RJTT DCT NAKNO Y18 FUSOH Y184 HIKNE DCT RJOO

[back]

[FransCKes 1]

Yes, I noticed that the P3Dv2 Flight Planner has some serious problems. Most of my existing flights that worked with P3D 1.4 no longer work. One or more of the waypoints go to lat 0 long 0. Trying to create new flights doesn't always work, either.

 

Frans Kes

[g_precentralis 191]

Does P3D V2 offers new navdata?

[TurboTomato 90]

I'm having similar issues at times - I mentioned it on the thread I started about the Project Airbus A319 and assumed it was an issue with that aircraft but it seems not. I managed to get round it by re-creating the flight plan (and that goes for anything I've saved in P3D2 as well) every time I wanted to use it.

[Piper9t3 25]

The default P3Dv2 flight planner and GPS are no different than what you got with FSX and we all know how inaccurate that was.  Makes me wonder what navdata cycle comes stock with the P3Dv2?  Nevertheless, the more realistic flight planners function outside the sim and have updateable navdata cycles as far as I am concerned. 

[n4gix 4,947]

Prepar3D uses precisely the same database that is used by FSX. Because of the way Microsoft/ACES compiled nav data in literally thousands of .bgl files, it is not really "updatable," even though Herve Sors does cyclic updates for some things, airports are not included, nor are high and low airways.

 

There will always be a disconnect between real world navdata and FS/P3D. Until and unless L-M decide to completely gut the legacy navdata system and replace it with a unified database, we are stuck with this issue.

[g_precentralis 191]

Well for now, they just made sim looks better. Not enough for me.

[whammo11224 0]

It's not that it's the same as FSX. FSX never had a GPS problem like this. "Direct GPS works, but not the airways.

 

Thanks

[TurboTomato 90]

There's definitely an issue - when I reloaded a saved flight the flight plan was broken (aircraft immediately started to turn and then when I checked the GPS the flight plan was showing my next waypoint as 2500nm away) and every time I tried to select the Flight Planner from the menu it would CTD.

[vonmar 122]

As a test, this is the original flight plan
*******************************************
<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KDTW to KCLE</Title>
        <FPType>IFR</FPType>
        <CruisingAlt>25000</CruisingAlt>
        <DepartureID>KDTW</DepartureID>
        <DepartureLLA>N42° 12' 44.00",W83° 21' 12.00",+000643.00</DepartureLLA>
        <DestinationID>KCLE</DestinationID>
        <DestinationLLA>N41° 24' 39.00",W81° 50' 57.00",+000791.00</DestinationLLA>
        <Descr>KDTW, KCLE</Descr>
        <DeparturePosition>04L</DeparturePosition>
        <DepartureName>Detroit Metro Wayne Co</DepartureName>
        <DestinationName>Cleveland-Hopkins Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61472</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KDTW">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N42° 12' 44.00",W83° 21' 12.00",+000643.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KDTW</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CRL">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 2' 52.00",W83° 27' 27.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>CRL</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ASLLI">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 0' 41.00",W83° 31' 26.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>ASLLI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WOOST">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 41' 44.00",W82° 47' 21.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>WOOST</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DJB">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 21' 29.00",W82° 9' 43.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>DJB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KCLE">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N41° 24' 39.00",W81° 50' 57.00",+000791.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KCLE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>


After I exit P3DV2 I had another look at the flight plan and alot changed ... all waypoints are now 5000nm apart
****************************************************************************************************************
<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KDTW to KCLE</Title>
        <FPType>IFR</FPType>
        <DepartureID>KDTW</DepartureID>
        <DepartureLLA>N42° 12' 43.98",W83° 21' 12.00",+000643.00</DepartureLLA>
        <DestinationID>KCLE</DestinationID>
        <DestinationLLA>N41° 24' 38.98",W81° 50' 57.00",+000791.00</DestinationLLA>
        <Descr>KDTW, KCLE</Descr>
        <DeparturePosition>04L</DeparturePosition>
        <DepartureName>Detroit Metro Wayne Co</DepartureName>
        <DestinationName>Cleveland-Hopkins Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>9448</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KDTW">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N42° 12' 43.99",W83° 21' 12.00",+000643.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KDTW</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CRL">
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>CRL</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ASLLI">
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>ASLLI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WOOST">
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>WOOST</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DJB">
            <ICAO>
                <ICAORegion>KK</ICAORegion>
                <ICAOIdent>DJB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KCLE">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N41° 24' 38.98",W81° 50' 57.00",+000791.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KCLE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>