philippe

Right lol? I was pleasantly surprised myself...

I can confirm the problem persists on PC platform only. The Android version works!

Version 1.0.0.6 is accessible as experimental?

Hello, I have crashed twice so far on a trip from OMDB to ZBAA due to lack of fuel. Yes, I know, I was not monitoring completely my flight, but I was not expecting this (pause at TOD). I am using the Aerosoft A3xx Fuel Planner, with the correct wind data, etc., it generates a value of 27,484 kg of fuel. PFPX, with the nearly exact same values for PAX and cargo, gave me a result of 41,966 kg of fuel (trip at 33,856). That is a significant difference of fuel calculation if I understand correctly. The nm distance between PFPX and the planner was not too off (Aerosoft Fuel planner had it at 3159 nm, whereas 3234 nm for PFPX). That trip difference should not provide a fuel difference of over 11 tons of fuel. Does this make any sense or am I missing something? I am running version 1.0.0.2 for the A330, and 1.3.0.0 for the Airbus Professional series. Clean re-install for latest updates. Grateful for any assistance. Cheers

I tried something, seemed to have worked... I disabled GSX (in the MCDU) before inputting the data. The data loaded correctly. I then re-enabled GSX.

I even tried to manually input the data (rather than through the loadsheet) and the pax load freezes at 31.

I am also having the same issue. I have inputted 287 passengers, and only 31 are boarding. Cargo and fuel seem to load ok however, so far my issue is only with the passengers. Version 1.0.0.2 P3D v4.5 hotfix 2

Operating System: Windows 10 Home 64 bit Simulator version: 4.5 Airbus version: 1.2.4.0Add-ons in use: Active Sky P3D version 7062, ASCA, ENVSHADE, ENTEXSystem specs: i7 7700k overclocked at 4.9ghz, RTX 2070 (not overclocked), DDR4 Ram 16 gb G Skill overclocked at 2800 mhz Description of the issue: As I was reaching FL400, complete blackout Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? This is the first time I ever experienced this. Additional information (route, weights, special area where the issue occurred etc.): KLAS to CYVR, near waypoint LKV at FL400. Zero fuel weight 54549kg, Taxi weight 63063, takeoff weight 62520. I did experience a really weird stall issue before. I was on autopilot cruising to my TOC (FL400), went away from the PC for about 20 mins, and then when I returned the aircraft was at FL150, with IAS of about 180 knots at a stall. Engines were at almost max. I disengaged the autopilot, aimed down, regained speed, and re-engaged climb. I stopped at FL360 to see if all was ok, then resumed to FL400.

Absolutely

Nope, I definitely did reboot. I close my PC every evening. That said, I flew the exact same route and no issues. That event was weird... I cannot reproduce the bug (for now). I find it really odd that I had an ignition notification on the EICAS... I didnt know Aerosoft was in the business of simulating system errors on the Airbus! hahaha

Hello, I just checked and indeed it is version 1.2.4.0. Thank you. Ps. I am trying the same route again with the A319. Just reached TOC, so far so good. CI of 45. No ignition message on EICAS either.

Hello, The thread link is dead, so in the meantime, I will post it here. Please feel free to move my post to the other thread. Apologies for any confusion. Operating System: Windows 10 Simulator version: P3D 4.5 Airbus version: A319 Professional - latest official version, clean install.Add-ons in use: Active Sky for P3D v4, ASCA, ENVTEX ENVSHADE, REX Environment Force.System specs: i7 7700k overclocked at 4.9ghz, RTX 2070 (not overclocked), DDR4 Ram 16 gb G Skill overclocked at 2800 mhz Description of the issue: Midway through cruise, engines always go on idle when on autothrottle. Engine levers were on CL. I tried to re-initialise, switched to autopilot 2, etc. No effect, as soon as I put the engine levers back to CL with auto throttle, the engines go back on idle. I do have an ignition message on EICAS. I tried switching the ignition switch, nothing. I tried opening the APU, would not start (only available). Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? First time this happens to me. Additional information (route, weights, special area where the issue occurred etc.): Route UBBB to LOWW. Was at FL360 when issues occured. Take-off weight at 68831 kg. Fuel 11138kg (zero fuel weight 58236). 124 pax, 8095kg cargo. Trim 0.6

I also would like to know. In the meantime, I manually downloaded the updated AIRAC to a temp file and manually updated the QW folder in P3D v4.