Posts by rdpm

    Hello, Jan.

    Sorry to insist on this. IMHO I can confirm after googling and checking other sources that HDG PRESET function is not correctly simulated: in real aircraft when the pilot preselects a heading prior to takeoff by turning the HDG selector (but without pushing/pulling it), that heading keeps preselected. After liftoff at 30 ft the RWY TRK mode activates (to keep the runway axis) until pilot pulls HDG selector, in that moment HDG lateral mode activates.

    In AF2, there is no RWY TRK mode but instead HDG mode activates after liftoff without pilot input, and the plane would make a roll at such a low altitude. Not realistic.

    Just for info.

    Regards,

    Ricardo

    Hello. My version is of the end of January.

    What I read somewhere in the changelog is that you can change (on ground) the ALT CRZ in the MCDU by clicking the corresponding key adjacent to value shown in PROG page. Doing so and inserting the suggested value (or any other), it is only reflected in MCDU and not in FCU window, and apparently is ignored. Maybe I am doing it wrongly.

    Regards.

    Quote

    Also to my knowledge you can engage HDG on the ground, it does not arm, it goes straight to active mode. But we have yet had a real world pilot confirm this. Nobody does this in the real world... I know that rotating the heading knob kicks out armed NAV mode on the ground. Not sure what happens if you pull the knob though.


    HDG is the basic lateral mode, so it has to activate in the air when there is no other mode. Also this is implemented to the best of my knowledge, interpreting the FCOM and reading between the lines here. If RWY TRK is active then we would not have to use HDG right away. On automatic engagement the heading synchronizes to the present heading, so no turn is commanded by the flight director.

    Hi Jet-Pack.

    I enclose an excerpt from FCOM where explains HDG PRESET mode before takeoff. In fact, there are SIDs that tell the pilot to keep a given heading after takeoff until a certain altitude (for example) and then resume managed navigation by going straight to a F-PLN waypoint (DIR TO). Before activating HDG mode after takeoff, RWY TRK mode is kept and appears in FMA.

    Please check with a real pilot.


    "The system has a HDG/TRK preset function for takeoff and go-around.

    If the flight crew chooses not to fly the flight plan after takeoff or go-around, they may preset a HDG or

    a TRK on the FCU by turning the HDG/TRK knob. The value they set remains displayed in the FCU

    HDG/TRK window until they pull the knob.

    OPERATION AT TAKEOFF

    HDG/TRK preset is available before takeoff and up to 30 ft RA. Turning the HDG/TRK knob before

    30 ft sets the desired HDG/TRK. As a consequence:

    - NAV is disarmed

    - At 30 ft, RWY TRK is annunciated until the HDG/TRK knob is pulled.

    OPERATION AT GO-AROUND

    Whenever the LOC*, LOC, LAND or GA modes are engaged, the HDG preset is available. If the

    flight crew rotates the HDG/TRK knob to set the value, it will remain displayed in the window. Pull

    out the HDG/TRK knob to activate the mode and turn the aircraft to the preset value.

    When overflying the MAP, HDG/TRK will synchronize with the current value. The HDG/TRK preset

    function is no longer available.

    CANCELLATION

    The flight crew can cancel a preset HDG/TRK by:

    - Engaging the NAV mode using the DIR TO

    - Pushing in the HDG/TRK knob (arming NAV mode)

    - Disengaging AP/FD."


    Quote

    We have tried to follow the FCOM as closely as possible. There, if I remember correctly, it says that RWY TRK follows a RWY mode when there is no NAV mode armed after takeoff. So to my knowledge RWY TRK only activates if RWY has been active. And for that you require a LOC signal.

    Yes, I think you are right. Except that RWY TRK activates at 30 ft if there is a HDG PRESET before takeoff, until pulling HDG knob to activate HDG mode.


    Quote

    Otherwise I tried to use the new feature for suggested ALT CRZ by clicking the corresponding LSK in MCDU, but when I insert it there is no reflection in FCU ALT window nor PFD display.

    Please check what I am doing wrong here.


    Sorry for my questions, I like your A320 and would want it to be as realistic as possible.

    Best regards.

    Hello.

    I just wanted to point out something I think is erroneous regarding AP/FD modes displayed in FMA (upper area of PFDs), after creating a flight plan to be flown in managed modes:

    - When starting the takeoff run, vertical mode SRS is properly engaged, but lateral mode should be RWY (or RWY TRK provided there is no ILS associated to takeoff runway) instead of blank until CLB mode activates at ACC ALT.

    - When a heading is preselected before takeoff, likewise RWY (TRK) should be active during takeoff run but HDG mode is in blue below, waiting for pilot to pull HDG knob to activate it. In AF2, HDG mode becomes active just after liftoff, which is incorrect as aircraft might begin a roll at a very low altitude.

    - When in flight if I make a DIR TO towards a waypoint, it seems to me that F-PLN from that waypoint disappears (I have to check it again anyway).

    - Otherwise I tried to use the new feature for suggested ALT CRZ by clicking the corresponding LSK in MCDU, but when I insert it there is no reflection in FCU ALT window nor PFD display.

    Best regards.

    Hello. I was not aware of this feature, so I decided to try it. I am not able to display the controls, supposedly activated via C key.

    I have tried several aircraft, with and without a route planned.

    Please help.

    The engine master switches (RUN/OFF) and the engine mode selector (CRANK/NORM/IGN) should already be pre-assigned. I connected the device to the steam version and they worked out of the box.

    Thanks for the update, but for me only Master switch (ON/OFF) works, not the three positions selector.

    I will keep investigating the issue.

    Disconnect the throttle quadrant or disable it in the controller settings by clicking on it in the list at the bottom, set enabled to false.

    Then click into the central area of the throttle (where you see movement when you move the slider), then press backspace to delete that assignment.

    Plug the quadrant back in or re-enable it and you should be all set.

    Thank you for your instructions. Now it works as expected.

    Regards.

    The thrust levers don't actually have the detents at the correct positions. They should be at about 55% and 75% but they built it with detents at 40 and about 72% or so. We now internally detect that device and because of that we know the hardware detents and use our code to match those to the detents in the virtual cockpit. You should be able to use the same hardware detents for the Q400 flight idle, C90GTx flight idle and F18 and F15e max military thrust (without afterburners) detents in the virtual cockpit.

    Hello, Jet-Pack.

    I have just received the TCA Quadrant throttles, and as you remark, there is a mismatch between physical detents and position showed in Aerofly A320 cockpit. But from your comments I understood that it was corrected internally by software.

    Otherwise I own also the A320 TCA sidestick, but throttle control is assigned to both joysticks if connected, but I only want control from the TCA Quadrant not from the joystick´s slider. Any help?

    Thank you.

    I received the Thrustmaster TCA Officer pack last week. It works a treat with the A320 in Aerofly FS2 and the detents work great. The engine switches work out of the box, but I can't seem to find a way to utilise the selector switch (Crank, Norm, Ign/Start), as there are no control mappings for it.

    Hello, thanks for the info.

    I will get mine probably tomorrow. What surprises me nicely is that detents work great out of the box, as well as ENG masters (no mapping for those).

    MSFS users report lack of precision in throttle detents. I will check all ASAP and report.

    Hello Jet-Pack.

    Thank you for the update. For me, as I reported recently, imho there are still some major issues in A320 that keep me out of flying this aircraft realistically, or at least from enjoying it:

    - Lack of TOC/TOD arrows in ND and indications in MCDU F-PLN page ->you have to guess where to start the descent

    - Strange behaviour when starting in a parking position from cold and dark or engines started: the FCU ALT windows seems to show the actual elevation of the airport. Same happens in INIT page of MCDU, where CRZ FL is not allowed to be modified.

    Please, please, check this before porting the beta version to stable.

    Best regards.

    I only fly the A320, and I am very familiar with standard and emergency procedures of this aircraft thanks to my career.

    The main misbehaviours I see in this Beta version are so far:

    - Unrealistic engine start procedure from C&D: you can start engines without air bleed from APU and even with fuel pumps off.

    - Problem with TOD indication on ND.

    - NAV database outdated.

    But otherwise is an excellent A320 simulation.

    Cheers.

    Hi.

    Is there any chance to see A320 Navigraph implementation in the future? I think it has been asked before, but many people owns this subscription, that otherwise is compatible with the rest of flight simulators.

    Regards.

    Hello.

    I´ve been using this feature several times, but accidentally I found some actions that I think should be corrected for the sake of realism.

    I use the procedure: BAT ON -> APU ON -> APU BLEED ON -> ENG PUMPS ON before starting the engines, but lately I forgot the last two steps and also was able to start the engines.

    Clearly incorrect behaviour, please check.

    Regards.

    Happy New Year to everyone.

    Sorry if this has been asked before, but since I own AF2 I am wondering about the resolution of DLC areas in terms of LOD, only to compare with MFS/P3D counterpart. I couldn´t find this information in any forum or documention.

    Regards.