Jump to content

Search the Community

Showing results for tags 'panel states'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • General Forum
  • Aircraft
    • Concorde-X
    • A3xx Master Series
    • Screenshots
  • Tools
    • FSL Hardware Interface
    • FSL Control Center
    • FSL Spotlights
  • Cockpit Building
    • Chat about cockpit building
  • easyJet Crew's easyForum
  • British Airways's The BA Club
  • Aegean Airlines's The Pub of Accord
  • Wizz Air's Topics
  • My little software corner's Developments


  • A319-X Liveries
    • PBR User Submitted Liveries
    • Older Non PBR Liveries
  • A320-X Liveries
    • Older non PBR Liveries
    • FSX & P3Dv3 Liveries
  • A321-X Liveries
    • User Submitted Liveries
  • A3XX Misc Files
    • Cabin Textures
    • EFB Backgrounds
    • A320-X - Unsupported Mods
    • Utilities
  • Concorde-X Files
  • FSL Aircraft Paint Kits
  • Spotlights
  • Hardware Interface for Prepar3D v4 & v5
  • Legacy Interfaces
  • Olympic Air Virtual's Files
  • Wizz Air's Files
  • Eurowings Crew's Configs / Textures / Sounds
  • Eurowings Crew's Operational Files
  • My little software corner's Downloads

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1 result

  1. Jonathan Fong

    Issues with Panel States

    Recently, I tried my hand at making some panel states for the A320X so that I didn't have to start from cold and dark every time I flew the aircraft - rather, I could load the plane in a 'turnaround' configuration as if it were fresh off a previous flight. This worked well; however, some members of my VA (who are helping to test the states) and I noticed a few issues in the way the A320X handles panel states: If I loaded one panel state then loaded another state afterwards, some items become unusable/broken, most notably the MCDUs. The IRS INIT lat/long page doesn't update with the aircraft's actual position - say, if I make a panel state at London Heathrow then try and load the same panel state at New York JFK (in a different sim session, of course), the IRS coordinates remain at London Heathrow. Now, this didn't seem to cause any major issues because the IRSs appeared to align to the aircraft's actual geographical location, but it's still slightly concerning. Any chance that these could be fixed? I'd really like to be able to load different starting configurations.
  • Create New...