richboy2307

Yes, this has been logged and being looked into. It was not addressed as of v1.1.1. Thanks!

Oh wow, thanks for reporting back. I was not able to reproduce your issues with the routes you had mentioned so wasn't sure what could be going wrong. But yes just tested and confirmed the same problem upon importing a plan dispatched *without* a detailed navlog. I'll log the issue. Thanks!

Hi, Can you try to recycle the settings? (Select RUDDER CONTROLS TILLER to NO, then YES) and see if it works? Also how have you mapped your rudder axis? Is it via some external tool (FSUIPC/SPAD/Axis and Ohs)?

Thanks all, noted and reported. We're looking into these CTDs and have already resolved some as of 1.1.1 HF1. However rest assured work continues to try and nail these.

Hi, could you answer the following questions: What was the Simbrief flightplan that you are using? Are you using Navigraph or default navdata in your sim? Are you able to import that plan on the EFB (My Flight app)? If you try with a different route, are you still noticing the same problem? Is this happening on a specific variant (GE/PW or PAX/FREIGHT) or equally on all? Thanks!

Its something we have noted to look into, but can't say when or if it will be implemented at all. Thanks!

Yes this is still in the works and not in 1.1.1. Once fixed it will be noted in the changelog below. If not mentioned, safe to assume it is still being worked on. https://forum.inibuilds.com/forum/398-updates/

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

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!

*Ooops* Good catch. Reported, thanks!

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.

Hi thanks. We've had a couple other reports of this on our discord too. We're looking into it. Thanks!

Reported, thanks!

Hmm possibly an A300 thing, as it loads fine in the A310. Thanks will look into it!

Hmm yeah good catch. Reported, thanks!

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.

Thanks, i'll pass this on!

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)

Thanks for your report. We're looking into these. Meanwhile could you also provide: - What navdata source (Default or Navigraph)? - Sim version (SU15 beta or SU 14)?

Hi Thanks for the feedback. I'll pass it on!

I'll pass on the feedback, thanks!

Thanks i'll log it.

Ah there we go. Good to know, thanks!

No It wasn't addressed in 1.0.1 update. This is still being worked on. Thanks!

Hi, Please check in the latest version (1.0.1) released today 🙂