Jump to content


  • Posts

  • Joined

  • Last visited

About CWHeadley

CWHeadley's Achievements


Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges



  1. Yes, I've done that. I have cleared every throttle setting on the HOTAS, the Keyboard, and the Mouse. I can finally get the throttle to move if I assign the throttle to these functions: throttle 1 Axis (0 - 100%) throttle 2 Axis (0- 100%) throttle Axis Increase throttle Decrease Throttle. The throttle will move. It will go from the Idle detent right to the Toga detent, regardless of the values I place in the calibration on the EFB. I could really use some help here.
  2. I need to add that I am using a single throttle quadrant. The X52 HOTAS to be precise. At the default setting, the throttle calibration sees the throttle moving but nothing happend to the throttles in the flight deck.
  3. I cannot get the throttle to work at all. The calibration screen on the EFB shows the throttle moving, but on the flight deck, the throttles do not move at all.
  4. Essentially, what does it do and what does it connect to?
  5. Okay, so chalk Me up as and absolute idiot. On the simbrief downloader, I was looking at ONLY the P3D/FSX download link. Totally blew by the Aerosoft AirBus link at the VERY TOP. *sigh* It formats the flight plan in a .pln as it should, but it also formats it FOR the Aerosoft AirBus. I just used that link, loaded up the A320 and sure enough, it loaded right in. Sorry for taking up your time guys. However, that is a good bit of information for simbrief users. Be sure to use the AeroSoft AirBus at the top to download your flight plans!
  6. Okay, so the other threads on this topic didn't really resolve the issue I am having or they didn't go directly to the problem I am having. I purchased the A320/A321 Professional. I am using P3D V4.5 I am currently learning the Aircraft using the JetBlue A320 tail N828JB. What I am trying to do is get a simbrief flight plan to load into the MCDU using the company route feature since I cannot seem to get it to load automatically when I load the aircraft. Quirks of Simbrief are that their file names are pretty damn long, so I have edited the generated filename from KSMFKPHX_FSX_19May20.pln to KSMFKPHX.pln I will post the contents of that file at the end of the help request. Here is the file path to the FlightPlan directory. C:\Users\calvi\OneDrive\Documents\Aerosoft\General\A3XX Flightplans So, the Aerosoft package comes with a few flight plans installed in the flightplans directory. They are EDDFEGLL01.pln FLALHR1.pln LOWLFMNO1.pln Of those three, only the EDDFEGLL01.pln will actually load into the MCDU. See first image. The rest give the same error as the flight plan I am trying to insert into the company route field. The next two images are the scratch pad entry and then the error when I try to enter it into LSK1. The last image is the update from Navigraph showing that My navigation data is up to date. I guess the question is, have I missed a step? One flight plan works so I don't think it is a file path issue. Any help would be greatly appreciated. As promised, here is the contents of the file plan. <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KSMF to KPHX</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>37000</CruisingAlt> <DepartureID>KSMF</DepartureID> <DepartureLLA>N38° 41' 43.60",W121° 35' 26.80",+000027.00</DepartureLLA> <DestinationID>KPHX</DestinationID> <DestinationLLA>N33° 26' 3.40",W112° 0' 41.70",+001135.00</DestinationLLA> <Descr>KSMF to KPHX created by SimBrief</Descr> <DeparturePosition>16R</DeparturePosition> <DepartureName>SACRAMENTO INTL</DepartureName> <DestinationName>PHOENIX SKY HARBOR INTL</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="KSMF"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N38° 41' 43.60",W121° 35' 26.80",+000027.00</WorldPosition> <ICAO> <ICAOIdent>KSMF</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SCTWN"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N38° 37' 50.57",W121° 27' 4.47",+000000.00</WorldPosition> <ATCAirway>SCTWN2</ATCAirway> <ICAO> <ICAOIdent>SCTWN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BLD"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N35° 59' 44.84",W114° 51' 48.88",+000000.00</WorldPosition> <ICAO> <ICAOIdent>BLD</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="PRFUM"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 30' 24.46",W113° 56' 34.85",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>PRFUM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SINHO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 20' 16.99",W113° 37' 51.39",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>SINHO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WOTRO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 10' 7.89",W113° 19' 15.68",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>WOTRO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DRK"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N34° 42' 9.19",W112° 28' 49.23",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>DRK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HATRK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 31' 14.83",W112° 18' 9.50",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>HATRK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MAIER"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 26' 47.19",W112° 13' 48.90",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>MAIER</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WEBAD"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 19' 51.80",W112° 12' 1.16",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>WEBAD</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="COYOT"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 10' 4.15",W112° 9' 29.24",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>COYOT</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BRUSR"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 5' 10.29",W112° 8' 13.50",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>BRUSR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MAHEM"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 0' 16.43",W112° 6' 57.90",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>MAHEM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="PXR"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N33° 25' 58.87",W111° 58' 12.72",+000000.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>PXR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KPHX"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N33° 26' 3.40",W112° 0' 41.70",+001135.00</WorldPosition> <ATCAirway>COYOT4</ATCAirway> <ICAO> <ICAOIdent>KPHX</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document>
  • Create New...