Genista

Hello. With a fully configured PMS and all that; If I press TM mode but autopilot is OFF, it will command 000 EPR and retard the throttles. Is it by design/ on purpose ?

same here, in 1.0.2. ILS or LOC will not engage. Not flying in VR.

Yep to both. GMT and weight updated right before TO. If I engage TM with AP off: With AP ON:

Hello, Still the case as of 1.0.2. IAS mode is very lazy and in general will be 20KIAS too slow

(1.02) Seeing the same here. All the PMS data is filled and yet it shows 000 and retards throttles as soon as I try to engage TM after TO. Until I engage AP - then, TM goes to climb EPR instead of 000.

Hello, To increase immersion, I was wondering if we could have an "auto" mode where flight engineer autocomplete checklists are automatically started after a set of user actions. For example here are some ideas: Engine Start: park brake OFF+Beacon light ON+5 seconds After Start: All 3x engines running + 20 seconds Line Up: Strobe lights + LDG lights on Climb: RA above 1500ft AGL Descent: within 150nm of destination, negative V/S, and selected ALT lower than current

Hello, At the moment the Paper Flight Bag and the perf card are emitting light, like a tablet would. Barely noticeable by day but looks out of place by night. See the difference between the "flaps 33" table chart (blends naturally with cockpit lightning) and the landing speed card (weirdly bright) below: Could this emissive light be disabled ? And instead we rely on the beautiful night lightning of this addon to read the PFB and card ?

Yep, even beyond the control units, the sensor used to capture the values themselves have their own inaccuracies, so you never have exactly the same value between same systems:

Oil Delta-T (temperature difference between oil coming out and oil coming into the engine from the heat exchanger) is mirrored on both engines. In this picture, only engine 1 is running, so the delta T of engine 2 should be 0. Thanks,

For point 2, I think we have the same, reported here:

Reactivity is nice and appreciated. Such a buggy build should not have been pushed in the first place though. I wonder if ini could consider opening an "experimental" channel to separate stable, "playable" builds (like 1.03 was) from the ones lacking test (like 1.04).

Hello, Despite what the changelog says, the bug reported below is still happening: Had it just now while taking off from EFHK 22R. Bump was hit a 133kts, way below VR

Hey Nico, no problems, this is fully understandable. Maybe a written clarification of what exactly does this option do would help then ? Maybe a note saying "we recommend leaving this setting "off" if you use a separate tiller axis" or something along those lines ?

Hey, many thanks for your input. Putting that option to OFF indeed appeared to solve the issue on take-off ! @devs: If this is intended behavior maybe it should be OFF by default (?)

Already reported here (I think it's the same issue ?) -> Staff said they'll take a look, fingers crossed !