Another thought: What is the exact name of the control that your throttle is bound to, and how are you binding it (in MSFS directly, FSUIPC, spad.next,...)? 

I believe there are several different, differently named throttle controls, and FSUIPC adds yet more options to the mix ("send directly to MSFS" or to FSUIPC's calibration). Depending on how the Fenix is implemented, I can imagine how some of these controls might be injected too late in the pipeline and might interfere with some FADEC or other throttle logic.

Not at my computer right now, so I can't check how I assigned mine unfortunately.

Edited May 22, 20224 yr by martinboehme

I use TCA stick as well but with Honeycomb Bravo and I do not have problem you do. I'm assuming you are using slider for throttle. Here is recommended setup  for your setup.

http://fenixsim-19919629.hs-sites.com/knowledge/tca-throttle-is-not-able-to-be-calibrated

2 hours ago, firhatsaurus said:

dont mean to brag, but I'm an a320 rated IRL, so i know how to operate this bird hehe.

PRO TIP: Mentioning this up front will keep people from thinkin' you're just another pretend pilot like the rest of us yahoos and save you from getting a bunch of silly questions from people who should be listening to you. 👍

3 minutes ago, MDFlier said:

PRO TIP: Mentioning this up front will keep people from thinkin' you're just another pretend pilot like the rest of us yahoos and save you from getting a bunch of silly questions from people who should be listening to you. 👍

Not to mention that if I were a real life A320 Pilot I would not go to AVSIM to discuss a possible bug with some randos, but would file a support ticket right away with feedback from my real life experience.

But what do I know?

He did that. I was just having a little fun with him.

5 hours ago, Fiorentoni said:

I think you need to watch some tutorials. You don't set N1 on the A320, not even on TO and certainly not in cruise.
Also you have A/THR active, as one can easily read on the PFD, so all the blue thing does is indicate your throttle position.

That isn't actually true. In TO and FLEX/MCT you are setting N1 as those are manual thrust modes. Any time you are in manual thrust the thrust lever sets N1. 

In autothrust the blue doughnut indicates the maximum N1 the ATS will set. Normally that's CLB N1, but it will be less than that if the lever isn't in the detent.

15 minutes ago, kevinh said:

That isn't actually true. In TO and FLEX/MCT you are setting N1 as those are manual thrust modes. Any time you are in manual thrust the thrust lever sets N1. 

In autothrust the blue doughnut indicates the maximum N1 the ATS will set. Normally that's CLB N1, but it will be less than that if the lever isn't in the detent.

No that's not true. In TO you set maximum thrust (so the end of the throttle axis), but in FLEX/MCT the N1 depends on the MCDU setting, while the physical throttle position is always the detent. You technically you don't set N1, but tell the aircraft to set N1 according to FLEX temp.

4 minutes ago, Fiorentoni said:

No that's not true. In TO you set maximum thrust (so the end of the throttle axis), but in FLEX/MCT the N1 depends on the MCDU setting, while the physical throttle position is always the detent. You technically you don't set N1, but tell the aircraft to set N1 according to FLEX temp

Read Kevinh's reply again. I think you both are missing each other's points perhaps 🙂

TO and FLX/MCT are N1 targets only. But CL facilitates whole trust range from idle to CLB power. Whereas the former two detents do not.
There is a reason why you annunce "MAN(ual) FLEX XX degrees & AUTOTHRUST BLUE" during a takeoff. 🙂

15 minutes ago, Fiorentoni said:

No that's not true. In TO you set maximum thrust (so the end of the throttle axis), but in FLEX/MCT the N1 depends on the MCDU setting, while the physical throttle position is always the detent. You technically you don't set N1, but tell the aircraft to set N1 according to FLEX temp.

No, thats a misconception. How do you imagine the thrust setting gets to the engine, from the MCDU or from the thrust lever position? TO and FLEX/MCT set N1 through the engine FADEC. TO is a computed takeoff thrust rating based on ambient conditions, not maximum N1. In effect the thrust lever is sending the engine a digital signal which is the demanded N1.

It's not much different in a 737 but without the physical detents. TO and CLB thrust will alwaysoccur at the same thrust lever position under FADEC control.

Edited May 22, 20224 yr by kevinh

1 hour ago, kevinh said:

No, thats a misconception. How do you imagine the thrust setting gets to the engine, from the MCDU or from the thrust lever position? TO and FLEX/MCT set N1 through the engine FADEC. TO is a computed takeoff thrust rating based on ambient conditions, not maximum N1. In effect the thrust lever is sending the engine a digital signal which is the demanded N1.

It's not much different in a 737 but without the physical detents. TO and CLB thrust will alwaysoccur at the same thrust lever position under FADEC control.

Alright I guess we meant the same thing, anyway what you said 🙂

Finally after 3 days struggling, I found the fix, you cant moved your installed folder or else it will mess the systems, so the solution is to use this apps https://flightsim.to/file/1572/msfs-addons-linker , so you can link your fnx-aircraft-320 folder to your community folder without moving it. 

49 minutes ago, firhatsaurus said:

Finally after 3 days struggling, I found the fix, you cant moved your installed folder or else it will mess the systems, so the solution is to use this apps https://flightsim.to/file/1572/msfs-addons-linker , so you can link your fnx-aircraft-320 folder to your community folder without moving it. 

Glad it worked out for you, and thanks for sharing this information, probably valuable for others with that problem. The app by the way is excellent, I use it every day to only load the scenery I need for my flight. This drastically reduces any possible conflict and loading time.