and I would like to take a flight today, with a completely empty community, without GSX and without SPADNext

7 minutes ago, Lenovouser said:

Thrustmaster TCA hardware

You said earlier you are using the Bravo? Do you use both?

Yeah, for a test I'd just use the TCA native in MSFS without any of the other things and SPAD. I use spad, and it is easy to get a binding wrong.

My Honeycomb Bravo is currently not even connected and is in the process of being repaired. Honeycomb Alpha is also not connected.

In the past it never caused any problems when everything was connected

But as I said, neither is connected

So indeed this is icing what causes it. I have to be honest here: I really appreciate a lot the Fenix devs do and how they communicate, but it's inacceptable that after one and a half year the aircraft still becomes unflyable in icing conditions (unless you turn off icing in MSFS, which no other payware aircraft needs). This should have been fixed and stayed fixed after the last winter.

34 minutes ago, Fiorentoni said:

So indeed this is icing what causes it. I have to be honest here: I really appreciate a lot the Fenix devs do and how they communicate, but it's inacceptable that after one and a half year the aircraft still becomes unflyable in icing conditions (unless you turn off icing in MSFS, which no other payware aircraft needs). This should have been fixed and stayed fixed after the last winter.

Its not icing he turned it off and still had the same problem. Even if he did the icing would of disappeared in the heat. 

7 hours ago, Lenovouser said:

My Honeycomb Bravo is currently not even connected and is in the process of being repaired. Honeycomb Alpha is also not connected.

In the past it never caused any problems when everything was connected

But as I said, neither is connected

Generally, the sort of issue you see occurs with a flap axis - MSFS will overwrite anything we send it - so my suggestion to start with would be to unbind (completely) the flap axis you have set up, both in MSFS and in whatever external program you have - and try again.

Edited November 29, 20232 yr by Aamir

13 hours ago, Fiorentoni said:

So indeed this is icing what causes it. I have to be honest here: I really appreciate a lot the Fenix devs do and how they communicate, but it's inacceptable that after one and a half year the aircraft still becomes unflyable in icing conditions (unless you turn off icing in MSFS, which no other payware aircraft needs). This should have been fixed and stayed fixed after the last winter.

Icing has been fixed for some time now.

13 minutes ago, threegreen said:

Icing has been fixed for some time now.

No it has not, at least not completely. From what I‘ve read on Discord they already acknowledged there‘s something wrong and it will be fixed with the next update.

I flew yesterday in Russia and it was cold and cloudy and my pitot tube just froze on approach and my speed tape got stuck on 220 kts with the AT not working anymore and the AP going off and the aircraft stalling. Obviously pitot heat is auto on the Airbus, so this should never happen. I had to manually turn pitot heating on and got my speed tape back working just before landing.
Also I‘m pretty sure the aircraft was completely iced on approach because it flew like an iceblock. I had engine and wing anti ice on for the entire descent (and climb beforehand).

2 minutes ago, Fiorentoni said:

No it has not, at least not completely. From what I‘ve read on Discord they already acknowledged there‘s something wrong and it will be fixed with the next update.

I seem to remember it was fixed but started to cause problems again when V2 Block 1 was released.

Edited November 30, 20232 yr by threegreen

Hi,

I'll get back to you after a few days.

Yesterday I reinstalled MSFS and only Fenix... Without GSX Pro, without SPADNext etc.

Then I wanted to test a short flight KSFO - KLAX.

After about 20 minutes in the air I had the well-known "GPU Overhed Error" again... Which keeps coming up sporadically for me.

I just don't feel like it anymore... I don't want to use MSFS and I don't want to use Fenix.. That's enough for me... I've been trying to get it to work for 1-2 weeks, while I'm busy with a problem. other problems occur (NVIDIA GPU Overhead Error)

just rubbish.

I have a P3D installation and will only fly in P3D... At least everything works... including the weather radar 🙂

MSFS is completely down for me until MSFS 2024... I've finished with MSFS 2020.

Nevertheless, thank you to everyone who wanted to help me... See you again in MSFS 2024 🙂 Until then, I'll stay with my beloved and stable P3D V5.4

Hi,

Me again 🙂

As you could read recently, I was pretty frustrated.

You sit at the PC for over a week because of a Fenix problem, then other errors come from MSFS.

Since it didn't give me any peace and I don't like giving up, I tried Fenix again.

Now I have been able to complete the last 3 flights normally and everything went normally... What did I do?

I completely redid the TCA profile in MSFS Settings and lo and behold it worked again.

Problem fixed... I still want to thank everyone who tried to help me.

Glad you got it fixed. 

Even though I might add, complete reinstalls are just a waste of time and server resources.

52 minutes ago, Lenovouser said:

Hi,

Me again 🙂

As you could read recently, I was pretty frustrated.

You sit at the PC for over a week because of a Fenix problem, then other errors come from MSFS.

Since it didn't give me any peace and I don't like giving up, I tried Fenix again.

Now I have been able to complete the last 3 flights normally and everything went normally... What did I do?

I completely redid the TCA profile in MSFS Settings and lo and behold it worked again.

Problem fixed... I still want to thank everyone who tried to help me.

So let us know what exactly was set wrong to cause your problem.

 

I think I didn't make a mistake...

I haven't changed my profile for Fenix in MSFS since the release... But somehow it's been causing problems since the last Fenix update.

I simply created a new profile for TCA in MSFS and now it doesn't cause any problems.

I don't know why the first profile causes such problems

Also, for your GPU CTD you encountered, this is a common issue with newer Nvidia Drivers.

I use 531.29. Other users report that 536.23 is also stable. Whenever I play using an updated (current) Nvidia driver, I get a "Your GPU has overheated" CTD. Good luck!

Edited December 4, 20232 yr by WestAir