A330 messing up again

[DeeJay]

Hey!

The A330 is messing up again at my system. Like every time before, it happened suddenly, but continuously, without having changed anything. It wasn't even after a MSFS 2024 update.

So, what happens:

- Several knobs don't illuminate or don't go extinguish, when pressed. For example: The "FD" button. the "AP1" and "AP2" buttons, the APU buttons, the "CSTR" button,... They are functional, but their state isn't visible, they remain in the state of illumination as they have been when the flight initialized.

- Manually inserting waypoints (into discontinuities) creates a huge mess in the ND. They are not recognized, neither by the FMGC, nor by the AP. However, they do show up in the ND, but "additionally" to the old waypoints. From that point, even the DIR function doesn't overwrite any waypoint before the DIR point. The AP flies it correctly, but the ND shows a mess of casual lines, the more DIR you enter, the more wrong lines.

- Fuel calculation is completely wrong. The FMGC calculates too much consumption, thus showing values up to -90 tons for the destination, however, when I arrive, I have 40 tons too much onboard. I've also got the impression, that the plane ignores time acceleration. So when it flies 2 hours in 4x mode, it burns the fuel for 2 hours, not for 8 hours, as it should.

- The plane "half" starts the engines as soon as the APU bleed is switched on (!), even before the engine mode selector is in IGN/START position. If you then start the engines by procedure, it only starts "the rest", which is basically only a few seconds to full idle.

 

I already have deleted the WASM folder, which resulted in no change. So, I have no idea, which direction I should troubleshoot in. Have you got an idea, what could be so wrong here. Similar things already happened before, then, they have suddenly disappeared (without action), and suddenly came again (and again without any action by my side). Only happens in the A330, no such problems so far in the A350 or the A300.

 

Thanks in advance.

Best regards,

Dominik

[haza2]

8 hours ago, DeeJay said:

Hey!

The A330 is messing up again at my system. Like every time before, it happened suddenly, but continuously, without having changed anything. It wasn't even after a MSFS 2024 update.

So, what happens:

- Several knobs don't illuminate or don't go extinguish, when pressed. For example: The "FD" button. the "AP1" and "AP2" buttons, the APU buttons, the "CSTR" button,... They are functional, but their state isn't visible, they remain in the state of illumination as they have been when the flight initialized.

- Manually inserting waypoints (into discontinuities) creates a huge mess in the ND. They are not recognized, neither by the FMGC, nor by the AP. However, they do show up in the ND, but "additionally" to the old waypoints. From that point, even the DIR function doesn't overwrite any waypoint before the DIR point. The AP flies it correctly, but the ND shows a mess of casual lines, the more DIR you enter, the more wrong lines.

- Fuel calculation is completely wrong. The FMGC calculates too much consumption, thus showing values up to -90 tons for the destination, however, when I arrive, I have 40 tons too much onboard. I've also got the impression, that the plane ignores time acceleration. So when it flies 2 hours in 4x mode, it burns the fuel for 2 hours, not for 8 hours, as it should.

- The plane "half" starts the engines as soon as the APU bleed is switched on (!), even before the engine mode selector is in IGN/START position. If you then start the engines by procedure, it only starts "the rest", which is basically only a few seconds to full idle.

 

I already have deleted the WASM folder, which resulted in no change. So, I have no idea, which direction I should troubleshoot in. Have you got an idea, what could be so wrong here. Similar things already happened before, then, they have suddenly disappeared (without action), and suddenly came again (and again without any action by my side). Only happens in the A330, no such problems so far in the A350 or the A300.

 

Thanks in advance.

Best regards,

Dominik

Hello!

Are you running SU3?

Kindest. 

[DeeJay]

Yes, the info at "release notes" says SU 3 - version 1.5.21.0

[Eddie]

Hello,

Thank you for the follow-up. It is recommended to opt-out of the beta (back to SU2, which is the LIVE version) if you do not wish to participate in an unstable game environment. 

Thank you 🙂 

[DeeJay]

Well, I only joint the beta option because your A350 site told me to do so in order enable the updates to work properly. If you tell me that this isn't neccecary anymore for the A350, I will be happy to go back to the stable version again. Can you confirm that? Meanwhile, similar problems as described above also crop up at the A350.

[Eddie]

2 hours ago, DeeJay said:

Well, I only joint the beta option because your A350 site told me to do so in order enable the updates to work properly. If you tell me that this isn't neccecary anymore for the A350, I will be happy to go back to the stable version again. Can you confirm that? Meanwhile, similar problems as described above also crop up at the A350.

Hello again,

Yes, the SU3 environment is not recommended at this time. 
Also, for clarification, could you please point me to where it says you must enable the beta for the 350 to function properly? Much appreciated. 🙂

[DeeJay]

OK, thanks.

17 hours ago, Eddie said:

could you please point me to where it says you must enable the beta for the 350 to function properly? Much appreciated. 🙂

Obviously I can't anymore, because the note with the need to do that seems to have disappeared from the installer page. This once was noted at the installer page of the A350 withon the ini manager, along with the advice to erase the WASM folder. Both seem to be removed for obvious reasons.

[Eddie]

No worries at all. That disclaimer was indeed relevant back then but removed as it is not mandatory anymore. That specific update earlier this year was needed for the functionality of the aircraft. 

Please let me know if you see more positive results after switching versions.
Thank you! 🙂 

[DeeJay]

Thanks a lot! I quickly tested my most important aicraft, among them your A300, 330, 350 and some other models and they finally seem to work fine now again 🙂

(even if switching back versions brings its own problems with the general controls).

However, I didn't do a full flight so far.

[jaybird]

On a related note, I don't have all the problems of the OP, but what IS very broken is the throttle control, after takeoff I'm in a Flex mode, but when prompted to climb thrust I drop back on my Thrustmaster to what SHOULD be climb, and it never see's it 😞 This also means that LNAV never kicks in apparently, so effectively its dead in the proverbial water. It's not my hardware, so is this likely to be SU3? Its a REAL hassle switching between Live and Beta thanks to the way they do things.... I'd just like to know if it will likely fix my problem, I want to fly cargo in the 330. 

Thanks