Anyone here using SU11 beta?
Not sure if this is a DX12 thing (reverting to DX11 to check) but the Fenix’s screens are corrupted with gibberish.
Hope to heck it’s DX12 causing it. Double eek if not.
It also happens on the PMDGs. Seems to be DX12
2 Likes
That ain’t good! 
Was recently taking off from Bergen, Norway. Was all MCDU preflight complete when noticing live weather being a jerk, so switching to a weather preset instead.
During the takeoff roll I went from flex to TOGA to compensate for atmospheric alterations. The end of that runway was coming at us pretty quickly. Was fun to notice how flex settings are indeed very real and very complete.
So yeah. An airbus sometimes takes off with TOGA, but mostly when you’re just not cutting it. Haha.
I don’t think it’s DX12. I fly Fenix A320 and PMDG 737 normally with DX12 (and the latest Nvidia driver released yesterday). But I’m on SU10. There is only the issue with DLSS which makes these aircraft displays blurry. Asobo promised a fix for this.
Is there any problem known for the Thrustmaster Airbus Captain Pack for the last update?
My throtles are not working well anymore.
Maybe check the above links to see if any or all of the steps will need to be repeated after the update.
1 Like
already tried them, my throtles still all messed up 
Do your throttles work with other aircraft?
What exactly are your throttles doing or not doing that they should be? Are they not registering movement at all or are they just not moving the virtual levers as you’d expect?
1 Like
My throtles go straight to reverse when i try to set idle.
And straight to climb / TO when i move it up…
are you sure you have the correct axes mapped, as that sounds like the symptoms of the ‘0-100%’ axes?
alternatively, the throttle controller calibration in the MCDU might need to be redone
2 Likes
yep.
What happened is that i installed a fresh windows 11 and a fresh MSFS, so i lost all my configs from the past install.
Since i calibrated using the Thrustmaster app - have all set according to fenix tutorial and did the calibration on the MCDU.
So, when you did the mcdu calibration, the throttle axis values climbed for each detent as you’d expect, from max reverse up to TOGA?
If they did, then MSFS and the Fenix A320 are apparently reading the correct values from the throttle, so how that then differs from using the throttles to actually fly the aircraft, I’m not sure.
If you’ve already asked on the Fenix Discord, then you might have to submit a support ticket to Fenix.
In SU10 there was no problem. It comes with SU11
It’s the combination of DX12 and the SU11 beta in combination, apparently.
1 Like
Is it? So I have a different logic then. SU10 + DX12 = OK. SU11 + DX12 = not ok. So maybe it’s caused by SU11 beta?
So if someone says “seems to be DX12” then I just think it seems to be SU11.
Maybe it is the DX12 implementation in SU11 beta? Are you a lawyer 
Maybe. But still, DX12 works fine in SU10. So what’s the culprit here?
Without access to the source code, any discussion of who is to blame is pointless. The fact remains that the screens are not broken unless you have opted into both the SU11 beta and the DX12 beta.
Any news when Fenix will release the A321 Freighter version to keep up with the PMDG-Johnsons?
Ah some variants of that Airbus would be so refreshing and cool and interesting to fly.