richboy2307

Hi, there is a known issue affecting the ability to set reverser on throttle. Should be addressed in a future version. If you're on PC, there is a workaround until the next fix is out - 1) Locate your [ThrottleData.ini] file. Steam users: \AppData\Roaming\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo\work Microsoft store: AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\microsoft-aircraft-a320neo\work 2) Changed the following from false to true: to Once you then save this .ini file and reload the aircraft it should work.

Thanks, yes known issue and expect a fix in upcoming versions.

Thanks moved to the right section. I'll check with our sound engineer but I believe its meant to be just ambient external sounds.

Hi have you tried to clear your scenery indexes? Also try with only PHNL in your community folder to see if you still notice this issue. Just to eliminate any conflict with another addon. To run with a blank community folder without losing your addons: 1. Rename your existing community folder to ``_Community`` 2. Create a new ``Community`` folder in its place. 3. Copy only the PHNL 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 PHNL folder back to ``_Community``, 2. Delete the new ``Community`` folder you made 3. Rename the ``_Community`` folder to ``Community``

Hi, please try to clear your scenery indexes:

No you aren't doing anything wrong. Logged, thanks!

Cannot reproduce as of v1.2.0 update. Thanks!

Replied here: Thanks!

Apologies, this is a known issue with the ThrottleData.ini file and will be fixed in a future version. Hi. If you are using tiller axis, please set RUDDER CONTROLS TILLER to NO in the EFB. If you are using your rudders to steer, then please ensure this is set to YES instead, and also ensure the PEDAL DISC button is not pressed in on the tiller (see image). Additionally you cannot turn sharply at higher speeds, keep speeds below 10kts GS in order to do so. Thanks!

Hi thanks for the report. Logged. We take all reports seriously and address issues that we can successfully reproduce to see what may be the cause. Neither we, nor the testers personally encountered such issues in testing prior to release. However of course we can't test every different combination of setup/configuration out there so we rely on these reports to try and get to the bottom of these. Your patience and understanding is greatly appreciated. Thanks!

Thanks we'll look into it.

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.

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/

*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!