https://ibb.co/qFSYgQT

Don't ask me  how, but this time, on MAN TOGA,climbed out of Rwy28 at Kigali, clicked on the ALT knob, throttled back to CL, switched A/THR on, then AP1, and .................I am lost for words🤣

Edited June 5, 20206 yr by vc10man

Followed this thread with interest as I never have had such problems with the AS 330. Just completed a flight from Kigali to Nairobi, no problems (pitch never exceed 15 (on take off), went as low as 5 on accelerating to climb speed, and in 290 knot climb was around 7.5). As for high altitude being a problem I regularly fly the AS 330 from HAAB (Addis Abba) to FAOR (Johannesburg), also without these pitch problems Also use ORBX Africa LC so its not a scenery thing.

Looks like "something" sorted itself out though.. Thinking about this you did mention not injecting any weather in those first problem attempts. I assume you are on V4.x not V5, as without injected weather you have the wind bug in V5 that can cause major upsets

If it was a simple clear weather scenario in V4.x I am wondering what the outside temperatures were at the time of these upsets. I have had occasion where the network connection to my Active Sky has failed, and it reverts to a clear weather default scenario and chaos breaks loose especially if in climb. And then one sees that the SAT is ridiculously high for the given altitude and there is no way one can climb - engines cannot generate enough thrust even at full throttle to keep going up.

So just speculating that maybe a combination of high outside temps (unrealistic) plus asking the plane to attain 250 plus knots and stay on a VNAV climb profile may have resulted in  a no-can-do situation, triggering A-FLOOR, and you had enough power to level off and regain control, but as soon as going back to AT/AP and commanding a climb, it was rinse and repeat.

5 hours ago, geolpilot said:

I assume you are on V4.x

Still on v4.5 HF3

Very interesting reply. Thank you.

Now here's one conundrum that manifested it self last night. Exactly everything the same except Kigali to Brussels. Engaged 4x compression to save time. Guess what? Over the Med before the Adriatic, it ran out of fuel when I initially loaded it with 60000kg😲 and lost all electrical power, just blank black screens🤨

So, decided to have another go this time without the 4x compression or any compression for that matter. And guess what again? After a long monitored flight from Kigali, am now on decent into Brussels without a hitch. How weird is that? So, does it allude that the AS A330-300 does not like compression modes as it burns fuel faster? Dunno!

There was me, all along wondering why a 4x sim compression flight would cause the fuel to evaporate. Did not quite rightly make sense.

Tonight, a short hop, Frankfurt to London.SimBrief said 15.65k kgs fuel ,I went for 17k kgs. And what happened? Surprise, surprise, the aircraft ran out of fuel, or something ran out because all the screens just suddenly went blank exiting the Runway at EGLL. Either fuel, or something caused the generators to go pop.

Now, A330 aficionados, do kindly explain that phenomenon. Meanwhile,I will get back to aircraft far more reliable that this 'word-not-allowed' 😡

https://ibb.co/TvFPXJ4

Edited June 7, 20206 yr by vc10man

Can anyone shed light on why, the PF, when answering the PM during Before Start checklists, adjusts the QNH knob back to the standard 1013 when Active Sky P3D has just told me it is 1021? Most annoying.

From my many years of experience of PC-support I can recommend: Do a complete re-install of your PC, setup P3D from scratch and everything will work fine!

I do this 3-5 times per year. After P3Dv5 came out I had to do it one time only and since then everything is working perfect.

I'm flying the different Aerosoft Busses every day (the A333 since 2 weeks on an IVAO Portuguêse Cargo-Tour) ) and NEVER had any of your issues. Neither in P3Dv5 nor before in P3Dv4.
So in many cases, like yours, it's the fastest way to get rid of any issues: New PC-Setup.

😉Don't blame Aerosoft, as there are hundrets or thousends of other Aerosoft Airbus Pilots without this/these issues
And: If you would look into the Aerosoft Airbus manual you will find: The busses are not build to work with different than 1x time.
Ralf

Edited June 10, 20205 yr by skystar

On 6/10/2020 at 7:21 PM, skystar said:

From my many years of experience of PC-support I can recommend: Do a complete re-install of your PC, setup P3D from scratch and everything will work fine!

I do this 3-5 times per year. After P3Dv5 came out I had to do it one time only and since then everything is working perfect.

I'm flying the different Aerosoft Busses every day (the A333 since 2 weeks on an IVAO Portuguêse Cargo-Tour) ) and NEVER had any of your issues. Neither in P3Dv5 nor before in P3Dv4.
So in many cases, like yours, it's the fastest way to get rid of any issues: New PC-Setup.

😉Don't blame Aerosoft, as there are hundrets or thousends of other Aerosoft Airbus Pilots without this/these issues
And: If you would look into the Aerosoft Airbus manual you will find: The busses are not build to work with different than 1x time.
Ralf

Yeah, bog-standard answer---do a complete re-install. Never mind the fact that I just did a complete new back-to-scratch Windows 10 re-install only a month ago!

Very helpful reply, but thanks no thanks.Do not see a reason to do what you suggest when I have no issues whatsoever with aircraft from developers that concentrate solely on developing aircraft instead of a developer that does buses, trains, planes and sceneries Enough said..

And just because your altruistic scenario of 'all is perfect in my world',----- good for you---does not necessarily allude that all is perfect elsewhere.If that was the case, P3D would not be bringing out HFs, any less or more  than scenery developers bringing out patches.

I have a choice at the end of the day. Either keep plodding on because 'hundreds or thousands' of other AS users have no issues(wonder why they have a Forum then?), or just ditch the thing!

 

 

Well, what a great response. My 13 year old couldn't have said it better.
You do have a very specific issue and no one can help cause no one else does have this issue. So instead of finally getting rid of the issue you search on who to blame for your obviously "faulty" setup. Well, feel free to do whatever you want 😉
All the best!

Ralf

Edited June 12, 20205 yr by skystar

14 hours ago, skystar said:

obviously "faulty" setup

I'd like to let rip here.......................but I will hold my vitriol and say zilch. Auf Wiedersen Aerosoft word not allowed!!

On 6/10/2020 at 8:21 PM, skystar said:

From my many years of experience of PC-support I can recommend: Do a complete re-install of your PC, setup P3D from scratch and everything will work fine!

 

This is such a terrible answer, I don't even have words. I'd also like to let it rip, but being an adult and such and not wanting to get banned, I'll hold my tongue. 

Edited June 13, 20205 yr by Ricardo41

Well, it is a bit short sighted to dump on the add-on and/or developer, when it has proven it can work without the issue you experienced on that one single specific route. And it has been working for many, many other people. As you say, P3D V5 is basically half beta with hotfixes still coming out and you might have just discovered a new issue... Before you throw me the old "but addon X from dev Y works fine on the same route Z", unless you know exactly how all parts interact between sim and addon, it is a pointless argument.

I mean, do what makes you happy. Just my two cents.

On 6/12/2020 at 2:27 AM, skystar said:

obviously "faulty" setup. Well, feel free to do whatever you want 😉
 

A gentle word to the wise. On this forum, alluding to the fact that some one may have a "faulty" setup is akin to telling them that they're a bad driver. It never ends well... 

On 6/14/2020 at 9:18 AM, garydpoole said:

A gentle word to the wise. On this forum, alluding to the fact that some one may have a "faulty" setup is akin to telling them that they're a bad driver. It never ends well... 

🤣