OnCourse Software

Welcome to our Product Support Forums

Ctrl+Shift+S (??)

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 2 of 2  [ 14 posts ]
Jump to page « 1 2
Author Message
Dave March
Post subject: Re: Ctrl+Shift+S (??)
Posted: Sat Jan 20, 2024 3:06 pm
Site Admin
Offline
 
Posts: 6122
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
If you're loading your Little NavMap flight plan into your FMC then surely the following must help
Quote:
ADDED a new option to the Advanced Options page called 'Flight Plan Filter'. Basically this option provides a means by which you can use a flight plan, containing a SID and/or STAR, which you would normally load into your FMC and PF3 will remove the SID (except the SID exit waypoint) and the STAR (except the entry waypoint). Currently it's quite difficult to load most SIDs/STARs into PF3 as most of the waypoints are very close together, so you can end up have two flight plans... one for your FMC and the other for PF3. The SID exit point altitude will be retained from your original flight plan, as will the altitude for the STAR entry point. The descent profile will also be retained from the original flight plan but PF3 will continue to put your cruise altitude into the first waypoint following your SID exit point (if included), upto and including the original flight plan's TOD. You will not be able to alter any of the altitudes from within PF3 when loading such a flight plan as we've had many users voicing their desire for PF3 not to change their flight plan, especially the descent profile. Full details for this option are provided in the updated PF3 User Guide.

In addition to the above you can also load a flight plan containing no procedures at all when this Flight Plan Filter option is selected and in that scenario PF3 will again enter your cruise altitude in the first waypoint and all those waypoints upto and including your original flight plan's TOD. The descent profile will remain unchanged. When using such a flight plan (with no SID and STAR) you will be able to adjust your altitudes as you can now.

This feature will only work with a valid flight plan. Basically that means it should be in XML format and each waypoint should have a valid altitude, so default FS9 or FSX flight plans would not be valid. The former as it's not XML and the later as the XML file does not include waypoint altitudes.

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
martinlest
Post subject: Re: Ctrl+Shift+S (??)
Posted: Sat Jan 20, 2024 3:09 pm
Offline
 
Posts: 1308
Joined: Sun Dec 26, 2010 3:33 pm
 
Looking again at what you wrote above Dave, I just realised that something is very strange. You said that the waypoint RIVAM was registered by PF3 as Top of Climb? You mean climb, really? Not descent? Waypoint RIVAM was close to my ToD in the aircraft FMC!

This is the flight plan that I load into PF3. As you can see, RIVAM is very far from being ToC :?
<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>LTFM to LIRF</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>38000</CruisingAlt>
        <DepartureID>LTFM</DepartureID>
        <DepartureLLA>N41° 16' 30.99",E28° 45' 7.00",+000325.00</DepartureLLA>
        <DestinationID>LIRF</DestinationID>
        <DestinationLLA>N41° 48' 0.00",E12° 14' 17.99",+000014.00</DestinationLLA>
        <Descr>LTFM, LIRF created by Little Navmap 2.8.12</Descr>
        <DepartureName>Istanbul</DepartureName>
        <DestinationName>Rome Fiumicino Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61472</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="LTFM">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N41° 16' 30.99",E28° 45' 7.00",+000325.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LTFM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FM011">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 34' 40.34",E28° 17' 24.81",+012143.89</WorldPosition>
            <ICAO>
                <ICAORegion>LT</ICAORegion>
                <ICAOIdent>FM011</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VADEN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 3' 56.00",E27° 12' 58.00",+036236.68</WorldPosition>
            <ICAO>
                <ICAORegion>LT</ICAORegion>
                <ICAOIdent>VADEN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ADUNO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 3' 39.00",E25° 27' 7.80",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LB</ICAORegion>
                <ICAOIdent>ADUNO</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PDV">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N42° 3' 12.30",E24° 52' 34.70",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LB</ICAORegion>
                <ICAOIdent>PDV</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LETNI">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 5' 48.99",E22° 36' 21.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LB</ICAORegion>
                <ICAOIdent>LETNI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="XAXAN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 8' 12.11",E21° 19' 36.10",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LW</ICAORegion>
                <ICAOIdent>XAXAN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KU502">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 14' 35.95",E20° 39' 26.24",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LA</ICAORegion>
                <ICAOIdent>KU502</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="POD">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N42° 23' 10.31",E19° 15' 16.60",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LY</ICAORegion>
                <ICAOIdent>POD</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DBK">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N42° 33' 13.84",E18° 16' 38.79",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LD</ICAORegion>
                <ICAOIdent>DBK</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ORAKA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 32' 13.00",E17° 12' 2.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LD</ICAORegion>
                <ICAOIdent>ORAKA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="RIVAM">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 29' 57.01",E15° 46' 22.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>RIVAM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ERPOG">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 28' 42.00",E15° 12' 9.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>ERPOG</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ESODU">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 26' 34.01",E14° 19' 53.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>ESODU</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="TIXIR">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 15' 19.01",E13° 53' 30.00",+038000.00</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>TIXIR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ASPIR">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 11' 20.00",E13° 44' 15.00",+037654.39</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>ASPIR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MOPUV">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N42° 3' 35.00",E13° 16' 55.00",+028691.20</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MOPUV</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LAT">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N41° 32' 28.00",E12° 55' 5.00",+014188.90</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>LAT</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WP1">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N41° 38' 24.29",E12° 35' 15.88",+007594.59</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="LIRF">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N41° 48' 0.00",E12° 14' 17.99",+000014.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LIRF</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>


Top
Profile Quote
Dave March
Post subject: Re: Ctrl+Shift+S (??)
Posted: Sat Jan 20, 2024 4:16 pm
Site Admin
Offline
 
Posts: 6122
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Sorry, senior moment typo. Yes of course, TOD

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
martinlest
Post subject: Re: Ctrl+Shift+S (??)
Posted: Sat Jan 20, 2024 4:20 pm
Offline
 
Posts: 1308
Joined: Sun Dec 26, 2010 3:33 pm
 
Quote:
If you're loading your Little NavMap flight plan into your FMC then surely the following must help
I tried a few flights with that option active last week, but I didn't notice any change.
Quote:
This feature will only work with a valid flight plan. Basically that means it should be in XML format
Perhaps I messed up: do I have to load an xml format flight plan into PF3 then (as per the PF3 instructions), I can't use the usual pln format - as in the example I posted above? I don't see anything about xml format in the thread "New flight plan processing in Beta 3.21.88 (optional)" In fact, in my little experiments, PF3 doesn't even see an xml format file in the flight plan folder, only pln. :?

I will give it another go next time, but as I say, the real problem is that it's proving very hard to get the ToD I need to respond to, the one in the aircraft, to match the one in PF3 (which itself always doesn't correspond to the one in my LNM flight plan).
Quote:
Sorry, senior moment typo. Yes of course, TOD
:lol:


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 2 of 2  [ 14 posts ]
Return to “PF3-ATC at its best” | Jump to page « 1 2
Jump to: