Jump to content
Sign in to follow this  
Woyzeck

Radar Contact 4 No Headings while flying

Recommended Posts

Hello,

 

I just downloaded Radar Contact 4 (RC4) for FSX Steam, installed it with no problem and it is working in FSX.  My only question is that I am using Simbrief.com to generate flight plans, and downloading the flight plan as the FSX/P3D version.  Once I depart the airport, I noticed that RC4 does not give me any headings in which to fly.  When I used RC4 with the FSX flight plans, I was provided detailed altitude and heading directions by the ATC.  I am not sure if I am doing anything wrong when I create the flight plan with simbrief, but i would like to have the ATC go back to providing detailed heading information.  Altitude directions are being provided such as "climb to flight level 350, etc"  What am i doing wrong?  Any help would be appreciated.  Thanks again.     

Share this post


Link to post
Share on other sites

The plan you load into RC4 must be in XML format and compatible with FSX.

I don’t have SimBrief so can’t help regarding that. If you can paste a small plan here I’ll test it, probably tomorrow.


Ray (Cheshire, England).
System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Are you sure the plan is sent  to the correct folder by SimBrief downloader? It must go to Documents\Flightsimulator X files for Radar Contact to fetch it correctly.

Edited by IanHarrison
clarity

Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.

Share this post


Link to post
Share on other sites

I use Simbrief and Radar Contact.  What I do is download the FSX/P3D Plan from Simbrief Dispatch Output page (scroll down the page) to a Directory (mine is Airbus Flight Plans).  When I select load flight Plan in Radar Contact I choose that Directory (Airbus Flight Plans) and load the required flight plan.  This all works 100%.  Radar Contact also remembers where you loaded the flight plan from last time and defaults to that directory after the first load.  Hope that helps.

 

 

Share this post


Link to post
Share on other sites

Hello,

Thanks for the responses.  Concerning your questions:

Mr. Proudfoot,

please see the flight plan below:

 

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KIND to KORD</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>22000</CruisingAlt>
        <DepartureID>KIND</DepartureID>
        <DepartureLLA>N39° 43' 2.30",W86° 17' 40.70",+000796.00</DepartureLLA>
        <DestinationID>KORD</DestinationID>
        <DestinationLLA>N41° 58' 28.28",W87° 54' 23.75",+000680.00</DestinationLLA>
        <Descr>KIND to KORD created by SimBrief</Descr>
        <DeparturePosition>PARKING 27</DeparturePosition>
        <DepartureName>INDIANAPOLIS INTL</DepartureName>
        <DestinationName>CHICAGO O'HARE INTL</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61472</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KIND">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N39° 43' 2.30",W86° 17' 40.70",+000796.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KIND</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MAREO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N39° 52' 58.07",W85° 14' 53.70",+000000.00</WorldPosition>
            <ATCAirway>MAREO5</ATCAirway>
            <ICAO>
                <ICAOIdent>MAREO</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BDOCK">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N39° 56' 6.00",W84° 14' 1.20",+000000.00</WorldPosition>
            <ATCAirway>MAREO5</ATCAirway>
            <ICAO>
                <ICAOIdent>BDOCK</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ROD">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N40° 17' 16.08",W84° 2' 35.15",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>ROD</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FWA">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N40° 58' 44.63",W85° 11' 17.01",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>FWA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SPANN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 15' 16.92",W85° 36' 32.51",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>SPANN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DAIFE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 16' 8.00",W85° 51' 19.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>DAIFE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WATSN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 17' 0.43",W86° 2' 7.21",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>WATSN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HAUPO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 20' 32.00",W86° 32' 24.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>HAUPO</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MKITA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 24' 0.00",W86° 41' 34.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>MKITA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PRISE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 32' 8.00",W86° 46' 53.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>PRISE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HULLS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 39' 24.00",W86° 47' 36.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>HULLS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="STYLE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 46' 26.30",W86° 48' 30.18",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>STYLE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DWEEB">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 51' 57.00",W86° 49' 46.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>DWEEB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VOGLR">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 56' 42.00",W86° 55' 7.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>VOGLR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CENAK">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N41° 59' 46.00",W86° 58' 31.00",+000000.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>CENAK</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KORD">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N41° 58' 28.28",W87° 54' 23.75",+000680.00</WorldPosition>
            <ATCAirway>WATSN3</ATCAirway>
            <ICAO>
                <ICAOIdent>KORD</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

[\spoiler]

Mr. Harrison,

I am pasting the .pln file into the correct folder in FSX SE.

Mr. Cooke,

It appears that I am doing the same thing but into the Documents/Flight Simulator X Files.

I do appreciate everyone's help on this issue.  Once again Thanks. 

Share this post


Link to post
Share on other sites

@Woyzeck,

I've copied your plan and saved it but neither P3D or ASP3D will load it. I've compared it to one of mine and I'm struggling to see what's wrong.

I entered your waypoints into Aivlasoft's EFB and successfully generated a plan which is accepted by ASP3D and P3D. So probably RC4 will accept it too. It's below if you want to load it. Maybe someone can see what's wrong with yours. It's baffling.

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
  <Descr>AceXML Document</Descr>
  <FlightPlan.FlightPlan>
    <Title>KIND to KORD</Title>
    <FPType>IFR</FPType>
    <RouteType>HighAlt</RouteType>
    <CruisingAlt>22000</CruisingAlt>
    <DepartureID>KIND</DepartureID>
    <DepartureLLA>N39° 43' 2.40",W86° 17' 39.80",+000796.00</DepartureLLA>
    <DestinationID>KORD</DestinationID>
    <DestinationLLA>N41° 58' 43.00",W87° 54' 17.40",+000667.00</DestinationLLA>
    <Descr>Created by AivlaSoft EFB Version 2.2 (build #130)</Descr>
    <DeparturePosition />
    <DepartureName>Indianapolis Intl</DepartureName>
    <DestinationName>Chicago-O'Hare Intl</DestinationName>
    <AppVersion>
      <AppVersionMajor>10</AppVersionMajor>
      <AppVersionBuild>61637</AppVersionBuild>
    </AppVersion>
    <ATCWaypoint id="KIND">
      <ATCWaypointType>Airport</ATCWaypointType>
      <WorldPosition>N39° 43' 2.40",W86° 17' 39.80",+000000.00</WorldPosition>
      <ICAO>
        <ICAOIdent>KIND</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="MAREO">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N39° 52' 58.10",W85° 14' 53.70",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>MAREO</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="BDOCK">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N39° 56' 6.00",W84° 14' 1.20",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>BDOCK</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="ROD">
      <ATCWaypointType>VOR</ATCWaypointType>
      <WorldPosition>N40° 17' 16.10",W84° 2' 35.10",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>ROD</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="FWA">
      <ATCWaypointType>VOR</ATCWaypointType>
      <WorldPosition>N40° 58' 44.60",W85° 11' 17.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>FWA</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="SPANN">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 15' 16.90",W85° 36' 32.50",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>SPANN</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="DAIFE">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 16' 8.00",W85° 51' 19.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>DAIFE</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="WATSN">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 17' 0.40",W86° 2' 7.20",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>WATSN</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="HAUPO">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 20' 33.30",W86° 32' 35.20",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>HAUPO</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="MKITA">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 24' 0.00",W86° 41' 34.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>MKITA</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="PRISE">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 32' 8.00",W86° 46' 53.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>PRISE</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="HULLS">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 39' 24.00",W86° 47' 36.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>HULLS</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="STYLE">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 46' 26.30",W86° 48' 30.20",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>STYLE</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="DWEEB">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 51' 57.00",W86° 49' 46.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>DWEEB</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="VOGLR">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 56' 42.00",W86° 55' 7.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>VOGLR</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="CENAK">
      <ATCWaypointType>Intersection</ATCWaypointType>
      <WorldPosition>N41° 59' 46.00",W86° 58' 31.00",+000000.00</WorldPosition>
      <ICAO>
        <ICAORegion>K5</ICAORegion>
        <ICAOIdent>CENAK</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
    <ATCWaypoint id="KORD">
      <ATCWaypointType>Airport</ATCWaypointType>
      <WorldPosition>N41° 58' 43.00",W87° 54' 17.40",+000000.00</WorldPosition>
      <ICAO>
        <ICAOIdent>KORD</ICAOIdent>
      </ICAO>
    </ATCWaypoint>
  </FlightPlan.FlightPlan>
</SimBase.Document>

 


Ray (Cheshire, England).
System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

This screenshot shows a comparison between my plan on the left and yours on the right. The most obvious difference is the inclusion of a named SID on yours but it would be odd if that was the cause.

I don't have SimBrief so can't try generating a plan using that. Do you have this problem with all plans or just this one?

Edited by Ray Proudfoot
Unable to load JPG. Will try later

Ray (Cheshire, England).
System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Maybe I am not understanding correctly but RC4 does not give you verbal headings throughout the flight. It gives you vectors if you request them for take off and landing. In addition it will give you the next waypoint on your filed plan, with the distance and bearing from your current position: but this is not announced. It is a message block.


Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.

Share this post


Link to post
Share on other sites

Mr. Harrison,

 

You are correct.  It does all what you say, but does not provide any verbal headings while flying.  Thanks.  

Share this post


Link to post
Share on other sites
3 hours ago, Woyzeck said:

You are correct.  It does all what you say, but does not provide any verbal headings while flying.  Thanks.  

It won’t. You’re expected to fly your flight plan.

The only exceptions are:-

1) fly runway heading after takeoff clearance (sometimes).

2) when you’re off course by more than the deviation value in Settings.

3) once inside 40nm of arrival airport and flying vectors issued by Approach.


Ray (Cheshire, England).
System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Awesome.  Thank you for your responses.  I guess I was used to the default MS FSX version that gave you turn by turn directions.  At least I know its more realistic and working.  Once again, thanks. 😀

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...