Prof_Plumpy

Not sure either. Cleared all caches and did a fresh install. My guess is its coded to run all services via system A since its everything causes a reduction, including things that dont run on system A.

Minimal aileron movement after take off. Bleeds system A dry. If you switch on the PTU it will bleed system B dry too.

Hi, thanks for the reply. It still happens when coming into land even in auto. The four systems cant cope with use.

Thanks for the reply. Loss of tiller AND rudder. Both. The rudder pedals go to neutral position. Moving rudder/tiller does nothing, the pedals wont animate/move when you look down at them. Loss of Hydraulics, yes, lots. Even coming into land with some side stick action it bleeds the pressure away to near zero. Lots of little orange messages flashing up.

Has happened a few times now, line up and start thundering down the runway. Some distance down the runway the rudder will go to neutral position and stop responding to joystick inputs. If you're lucky and near/past VR you can pull back and use ailerons to correct the issue. Eventually the rudder comes back into operation. My theory is the hydraulic system. Using brakes or tiller/rudder will deplete the hydraulic pressure very quickly. The plane has 4 systems and when you dab the brakes you can see a noticeable drop in system pressure. Usually A and B, then they are slow to recover. I let the FE sort the panel out but from past experience I turn on the PTU B-A system ON as A system will deplete quickly without the help, you will also get warning messages flash up briefly about system pressure. Should he put B2 and C2 to AUTO instead of leaving them in the off position?

Can we adjust the Z please? Have a 1604nm cruise and I keep seeing the Z bleed off screen.

Everything on the plane uses degrees C, except for the cabin temp which is degrees F. Since everything else (including the air feeding the cabin) is in Celsius, could we get the cabin temp changed too please?

Ive been getting this problem since release. Example: Out of VHHX there is a max alt 7000 till WHISKY (its a repeatable scenario). Then you dial in the step climb (100 or 130, cant remember). Change the PMS height to 100/130, sometimes its set to cruise alt, but it makes no difference what number is in the PMS box. Hit VNAV and wait, nothing. Hit TM, nothing. TM and VNAV, nothing. It just refuses to climb. Someone posted a video link to this exact scenario and shows it doing nothing. You can add a V/S of at least 1000, let it start to climb until at least >1000FPM, then hit VNAV. If it is under 1000FPM it just goes back to <insert doing what ever it wants here> Even holding alt at FL130 then doing the VNAV/TM/PMS results in nothing unless you make sure it climbs >1000FPM then VNAV it. There was a post from the flight manual that stated "add new alt, press VNAV" and it will climb. Currently 1.0.5, cleared all caches and old folders. Problems still persists.

Just to add to this. I use the Auto FE and he sets the hydraulics. On the little caution panel a bunch of hydraulic related items flash up briefly. You will also notice the brake pressure bleed away to zero with each application of brakes. If you look at pressure in system A and D it often shows no pressure. So the fun part happens on a long-ish taxi (happened yesterday). You line up, press go and press full send on your 226,000kg plane out of Melbourne for Tokyo. A few feet down the runway ALL hydraulic pressure leaves you, now with no working rudder/ailerons. You quickly turn to the FE panel and hit both PTU switches and hope you get some pressure back. Halfway across a grass field the pressure comes back with rudder and ailerons, rotate and airborne. When the auto-FE sets hydraulics, don't believe him and check yourself. Make sure A, B, C and D all show pressure. Have now done an all clear of all caches (WASM etc) and doing another test flight, looks like all 4 systems got pressure this time. 1.0.5

I got this too

Brilliant video, nice watching someone else do it. You and I, while we did the same departure, we have a few differences. (Use VOR/HDG until the 104 RADIAL after WHISKY, then get bored and hit INS), and usually MTOW 226,000kg. If a light hop to RJTT, then I will derate the engines and use manual thrust and VS to 250ias since I dont trust the TM/VNAV combo. One thing your video didn't do (that mine does), when you dialled in a new alt increase, your ALT stayed at "7000 ALT" until you hit VNAV. Mine almost always jumps up to "7200 ALT CAP" (always adds 200 feet to your currently selected alt) and starts the slow climb, regardless of what has been dialled into the ALT box. Did you use 1.0.4 or 5? The runway trim wheel happens infrequently but does happen for me. Made a video, its gone somewhere on my computer. Will wait till the new update this week and try again on Thursday. Thank you for your videos!

Doing the usual VHHX-RJTT, take off RWY13 Track 136 115.5 VOR, climbing 7000 till WHISKY in 1.0.4 Tristar Dial in FL370, haven't pressed any button to intervene/change. ALT window changes from 7000 ALT to 7200 ALT CAP (while 37000 is in the SELECT ALTITUDE box) and slowly climbs, uncommanded 500FPM. Fine, what ever, we are going to climb anyway. Hit VNAV, plane climbs at 500FPM. Cycle TM button to get the PMS EPR to work, and then we get climb thrust (apparently we shouldn't need to cycle TM button, just hit VNAV). So now in CMD1, TM/VNAV/VOR, happy at 250knots. Plane heads upwards, trim wheel start slowly turning to pitch up, and up, and up. We are now >6000FPM and speed quickly dropping. Stick pushes forward to slow climb rate and gain speed but the trim wheel continues to trim for a nose up attitude for some time. Eventually it all sorts itself out and we doing M0.83 to FL370 Anyone else have the trim wheel and stick fight each other? Below picture was borrowed from another post but illustrates the sequence needed to gain altitude.

INS auto import, then added manually. Was not aware it put in more waypoints, just figured it would load 9 then go back to waypoint 1. Maybe I should RTFM. Tested in 1.0.4 and it did import the next 10. Runway 13 departure out of VHHX. There is a VOR inline with the runway (TH VOR 115.5 heading 136). The plane will fly towards it, then wiggle/rock flies better after 1.0.4 (slight twitch) over top before settling back to 136. Nearing Max ToW of 226,000kg No, all my screen shots are sunrise/sunset related. Will try and capture more useful data. Out of VHHX, past TH VOR, alt hold 7000 until WHISKY. Clean configuration, 250knots. Past WHISKY you turn 90 degrees to intercept CH VOR 112.3, 104 degrees. 1.0.4 held the altitude much better. When dialing FL290 into the AP the ALT jumped from 7000 to CAP 7200 and stayed there until I hit VNAV. Now the fun part, after hitting VNAV the engines went to idle, then up past max EPR in the TM box, then settled at CLIMB TM EPR. Then it went to +5000FPM, lost speed and triggered AoA mode and TM turned off. Intervened with 500fpm, then VNAV/TM with more speed and now nearing Japan at FL290. Step climp to LF310 from 290, the ALT box reads ALT CAP 29300 and the plane slowly climbs before hitting any alt change buttons (VNAV/VS).

I have had a few issues with altitude/VNAV. Out of VHHX there is a max alt of 7000 feet untill 17nm past the VOR. The plane will (mostly) settle at 7000 feet in CMD VNAV/TM mode. ALT CAP and should stick at 7000 Now when you dial in a new alt and do nothing else, it will often start to climb by itself. One time dialled in a new alt increase and it started going down, probably as it was in a turn and thats the way the plane was going vertically at the time. According to the normal ops page above it should hold until you engage ALT SELECT+VNAV. There is also a lag of a few seconds between hitting VNAV and anything happening. Back to OPs problem. Did you enter data on pages 1/2/3? (Weights/ToD/Cruise info)