Jump to content

richboy2307

Moderator
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by richboy2307

  1. Thanks for your feedback!

    Yes we are always looking to optimize performance of our products wherever possible.
    Recently released v1.1.1 is the most performant version of the plane so far.

  2. Hi, could you answer the following questions:

    1. What was the Simbrief flightplan that you are using?
    2. Are you using Navigraph or default navdata in your sim?
    3. Are you able to import that plan on the EFB (My Flight app)?
    4. If you try with a different route, are you still noticing the same problem?
    5. Is this happening on a specific variant (GE/PW or PAX/FREIGHT) or equally on all?

    Thanks!

  3. For the airbuses you can do so by swapping the active databases on the MCDU.

    For the A320Neo:
    - Press MCDU MENU button > Select FMGC > select the SECOND NAV DATA BASE > Then reselect the ACTIVE NAV DATA BASE

    For the A300/310:
    - Press MENU button > Select FMS > select the SECOND DATA BASE > Then reselect the ACTIVE DATA BASE

  4. Hi we don't support running this scenery with PG disabled as we can't account for the lack of Bing data.

    It's unfortunate that the height data is so dramatically different but it's so severe that it would require a completely different version of the airport and terrain to be made.

    Thanks!

  5. Yes the letters might be different. The more important thing is you have the correct axis assigned to the appropriate function (aka don't assign brake axis to the rudder axis)

     

    Unfortunately not able to recreate this issue on our end. I would recommend creating a new blank profile for the rudder pedals, then assign the axis's separately.

  6. Hi, can you confirm in your settings you don't have any assists on or any other tool/utility running that would control the fuel/payload of the aircraft?

    Just to confirm that it isn't some addon conflict, try running with only the A300 in your community folder (no additional liveries either)

    To do this easily you can:
    1. Rename your existing community folder to ``_Community``
    2. Create a new ``Community`` folder in its place.
    3. Copy only the ``inibuilds-aircraft-a300-600`` folder inside it.
    4 .Run the sim and see if same problem persists.

    If yes, then you can close the sim, and restore your original folder as follows:
    1. Copy the ``inibuilds-aircraft-a300-600`` folder back to ``_Community``,
    2. Delete the new ``Community`` folder you made
    3. Rename the ``_Community`` folder to ``Community``

    If no, then that means there is some other addon conflicting with the ini A300. Usual suspect is bad liveries, so you could try by adding only some of the other a300 liveries in until you can reproduce the problem. Same process for other addons till you find the culprit.

  7. Hi thanks for your report. 

    We're looking into these soft-WASM module crashes which cause the plane to become unresponsive.

    In the meanwhile could you also provide:

    - Nav data source? (Navigraph or default)
    - Sim version? (SU15 Beta or SU14)

    • Like 1
×
×
  • Create New...