specialsk

Hi, I never really flew the A330 much if at all after this as there was a drop of other aircraft that I was playing with. I did go back and check my settings and everything was ticked OFF except Automixture, which I disabled. Next time I get back in that bird we will see if that fixes it. Thanks for the suggestion!

Wondering if anyone can share what they have found to work well, I haven't started playing around with it so thought I'd ask first. TIA

Yes, out of the box it is, but you can deaden by adjusting the sensitivities. Start with like -30 for the + and - and then tweak from there.

First time I've flown this plane. I'm using the RR passenger variant and when I got close to CL400, it dropped down to under FL390, and then went back up and then down to FL374 and has been holding there for some time. The MCP is set to FL400. Anyone else seeing this?

I can confirm that this is now resolved with the latest Aircraft and Avionics Update 3 that just dropped this week. Thanks for getting it fixed, I haven't flown the plane solely for that reason.

I'm also having the same problem, and I saw a Captain Canada video the other day showing he also having the issue so sounds like this is a bug.

Whenever I click "Complete Purchase" it continuously requires me to do the CAPTCHA which is the most annoying CAPTCHA I've ever was forced to use. Does the same thing on the website and inimanager.

I can attest to the fact that if you set up your approach (STAR and RWY) during flight the TOD comes way too late. Just did YSSY to NZAA and it had my TOD at FL370 about 120 miles from the airport and put me into a managed 5-6,000 fpm/descent for the better part of the descent lol

Interesting, I wonder why I stopped getting that error when I updated GSX?

I had the same issue even with using the profile that is linked above. There was an update to GSX Pro that needed to take place. That happened either late Sunday or early Monday so make sure you go to your GSX installer and install the update that should be there waiting for you. After I updated the issue went away for me.