OE-PH1 wrote in Sun Feb 15, 2015 12:25 pm:the only thing is: I insert the RWY and SID in the FG route-manager, because when doing this in the mCDU the waypoints of the SID won't show up. But sometimes I need these points to be shown in my flightplan, for example in order to fly direct to a point or so.
At the moment you should only use the DEFAULT SID/STAR, because the other are not well supported (and they're not supported by the ND). I will fix this in the future, but for the moment use DEFAULT for SID and STAR.
OE-PH1 wrote in Sun Feb 15, 2015 12:25 pm:Then, after a while it is time to start descending. And I guess here the problem begins.
Normally I know that I have to pass a certain waypoint at 12000 for example. I want to descent with 1600 fpm, so I know where to start my descend. But when I set altitude to 12000 and VS to 1600 nothing happens. I have to reduce speed down to 250 or initiate the descent manually by switching off AP and after descend is stable engaging AP again.
I guess this is wrong?
- How do I get into descend mode properly in order to reach a certain waypoint at given altitude?
- Or just to change flight level (sometimes requested by ATC)?
First of all, you should initiate your descent around the TD (Top of Descent) point: it's marked on the flight-plan (take a look at the Nav Display) by a white arrow pointing down, on the right side of the route track line.
You can start the descent before, at or after the TD point.
In order to start your descent you have to select a lower altitude on the FCU: just rotate the Altitude knob on the FCU and select a lower altitude (lower than current altitude).
In order to make the FCU more realistic I changed the way you interact with it. Just selecting a different altitude does not automatically engage the descent (or climb if your climbing) mode: you have to select a vertical mode. You can choose DES mode (managed descent), OP DES (open descent) or VS/FPA mode.
After you have selected a lower altitude, if you want to engage DES mode you must
push the knob by
shift-clicking it. If you want to descent in OP DES mode you have to
pull the knob with
ALT+SHIFT+CLICK.
If you want to descent in VS/FPA mode you must select a vertical speed using the right-most knob on the FCU and then
pull the VS knob with ALT+SHIFT+CLICK.
DES mode will let you descent to the selected FCU altitude taking into account every altitude constraint set in the flight-plan that is higher than the FCU selected altitude.
OP DES mode will let you descent to the selected FCU alt ignoring all the constraints. VS/FPA mode will let you descent to the FCU alt by manually selecting the vertical speed (or the flight path angle if you're flying in FPA mode).
Both DES and OP DES will set the autothrust to THR IDLE and the speed will be managed by the pitch. VS/FPA will use the pitch to mantain the selected VS or FPA and will set the autothrust to SPEED/MACH mode.
I know that the SHIFT+CLICK and ALT+SHIFT+CLICK are not the best way to interact with the FCU, but i didn't manage to handle the push/pull interaction in a different way, because FG currently inhibits the use of the right click (this would be the best option) to interact with knobs and buttons.
However, you're free to can change this interaction mode in the configuration dialog (Menu -> A330-203 -> Configuration): the alternative configuration ("Shift to rotate knobs") allows you to use the SHIFT+DRAG to rotate the knob and CLICK to push/ALT-CLICK to pull. Select it if you're more comfortable with this interaction.
OE-PH1 wrote in Sun Feb 15, 2015 12:25 pm:But I have to say again: I never ever touch the thrust lever at any time. I know that Airbus' philosophy is: CLB for the whole route, even when descending or landing. Because CLB means: auto thrust "available up to" climb. By the way, I am flying with joystick: Thrustmaster T16000M.
Maybe it's some issue related to your Joystick configuration. Try to fly with keyboard (unplug the joystick before) and see if the THR LVR problem persists.
Furthermore it could be useful if you could send me your Joystick config. file, I could use it in order to fix the issue.
You can see the joystick config. file path in the Joystick configuration Dialog (Menu Help -> Joystick Configuration). Alternatively try to find it in $FGHOME/Input/Joysticks/ directory.
I hope this helped you.