Delete this from \AppData\Roaming\Microsoft Flight Simulator\EXE.XML
<Launch.Addon>
<Name>FenixA320</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
</Launch.Addon>
Is anyone having trouble with not being able to engage autopilot? If so how did you fix??
3 flights today - no problem with the AP.
Not even the included Inibuilds aircraft work with the default EFB. Since the Fenix Planes are even further “detached” from default MSFS systems, I would not get my hopes up. That’s a GOOD thing - it’s part of why they work so well in 2024!
You make good points. I wonder if Microsoft/Asobo are trying to replace Simbrief and Navigraph?
https://planner.flightsimulator.com is updated almost weekly, so a lot of development effort is being put in it.
How are the Fenix frame rates in FS24 compared to other jets?
Last time I checked they said FS24 support was “experimental”.
even when I press the AP1 in the plane it will not turn on after doing the above. Are you in 2022 or 24?
I have had an issue with my the Fenix(all variants) in 2024 for the past few months at this point. The issue I’m having is that 90% of the time when I spawn the aircraft and turn on the BAT and the GPU all Screens in the cockpit apart from the EFB and the battery voltage indicator, display no info and just get slightly brighter.
Try closing the fenix app and reopening it. It may have logged you out
Didn’t fix the issue.
trying fresh install of fenix installer and aircraft
I have been struggling with an issue that at the moment seems to be affecting the A320 and the A321 IAE variants installed on my system. I had been having a hard time figuring out what was going on since everything on the engine display shows normal however, as soon as I throttle up, the aircraft veers to the left and becomes uncontrollable. After doing clean installs of the Fenix, removing the file folders and reinstalling, I decided to open up the Engine Debug under Dev Mode and saw the information attached. From what I see, it seems that for some reason, Engine 1 is producing a very different amount of thrust and behaving far differently from Engine 2 despite being at the same thrust lever position (e.g. Engine RPM, ITT, Fuel Consumption, Gross Thrust are all off). I don’t see anything in the config files that jumps out as an easy way to fix this discrepancy, but wondering if there is something in the base code that is causing this?
Make sure that all your hardware bindings are checked for conflicts of the Autopilot binding setting of your choice. Just yesterday in SU2, I saw that my mouse movement continuously gave me a disconnect. Also on my Airbus flight stick, I had originally set up a binding for “external/cockpit” but noticed after SU2 that there was also an axis setting there that created a conflict with that, which in turn gave me a Autopilot disconnect. It’s frustrating if the bindings are not checked. Another factor which influences the frequency of an Autopilot disconnect, is the turbulence setting of the sim. It was stated somewhere online that this should be set to “low”. I also changed my high to low and it seems to help a bit.
Hi There, I have been noticing of late when I have to change the arrival information within the FMC during flight, I cannot confirm the change. I get the panel words turn orange and unable to get them green. Is this a known issue and is there a fix for it. I keep getting a pop up stating words the effect “you need to add the heading first”.
Whats going on?
You need to switch to heading mode before you can change the arrival procedure. Then you can confirm it.
What do you mean switch to heading mode? I am usually flying with AP activated and Nav mode is on.
If you are already on the STAR, you switch from Nav mode to Heading mode, then you can change the arrival procedure. Then go back to Nav mode. That’s the Airbus way to keep you on course. If you’re not on the STAR you don’t have to do that.
arr thanks for that. really appreciate it