Transair

Florian, there's got to be something amiss here either with your system, or xbox connectivity or whatever. It's not the aircraft. Too many people do not have any issue at all with it. So don't give up on the 350; look for other interference, I'd suggest.

ok thks for reply...

Jack...tried again. With Speed, there does not seem a way to change 'Managed' Speed in the FMS at all. Looks like you have to go to 'Selected' mode only and stay in it to achieve a desired speed/mach. Also with CRZ level, I can try selecting a different FL in the FMS, (which IS blue), but it reverts to the flight plan level each time. So again, it seems you have to use 'Selected' mode to achieve a different level.

Thank you for fixing much of the TCAS/XPDR events. While I can see an LVAR for the Wind Shear switch (INI_WXR_PWS_SWITCH), I can't successfully get SPAD to activate it. Is it possible to investigate this one?

Hi Jack. No, different problem I think. When already in CRZ the FMS shows a green speed/mach number. e.g. Managed speed is, say .80. I want to CRZ at .84, but as it is in green, I can't change it to the higher mach number. It won't let me. If I 'use 'select' mode on the FCU, I can CRZ faster, but if I then revert to 'managed' mode, the speed reverts to the green speed as shown in the FMS. BUT, I'll look at this again tonight.....perhaps when I select the FCU speed, the FMS DOES go blue....this I will check ....apprec your comment

odd... i flew to LPMA (2024) last week with no issues, but last night, I crashed twice due to this issue...Pics above exactly what I saw last night. I had previously deleted MSFS LPMA so don't have a conflict. CORRECTION: I DID uninstall LPMA, but from 2020 edition. And I flew in there after installing MSFS2024 but without uninstalling LPMA in 2024. So all good now. The scenery is fine now!

First, I love the 350, especially in 2024. Very stable, beautiful model etc etc.. BUT I'm finding the sounds in certain circumstances are really detracting from it. - Power reduction Flex MCT down to CLMB produces a quite different and sudden note change (whereas the Fenix 320 is smooth, slight reduction and similar sound) - Nose-gear retract sounds far too noisy and prolonged. -Nose-gear extension should produce a slight roar as it meets the airflow -Reverser deployment sound is sudden, and a different tone again. -Reverser stow and engine spool-down sounds too immediate. hopefully this may get passed to the team for investigation.

Yes I am getting this too. A/C descended well below STAR with managed mode and all parameters set correctly. Had to fix temporarily with VS.

ok...I've never had an issue, but I have deleted the files each time. thks

does that include deleting the WORK folder as well?

I think the extension of the nose gear is normally significant (slight roar) and an associated thump as it extends into the airflow.....that seems to be missing here too

yes, it would be interesting to see the logic behind the 'cabin ready' advice....is it time related, or position related, or something else? Can it be manipulated?

I find it may not go 'normal' until about to line up. Doesn't seem to on the apron at all for me.

went to Thrustmaster site. They suggested disconnecting from PC, then restart computer and reconnect TCA. I have an odd feeling that the 350 update may have compromised the TCA settings somehow - not sure, but doing the above has completely rectified it. Hope it works for you. ( in MSFS Controls - Sensitivity, I could see the N/W steering was central but the X and Y axes were hard over, causing the control surface deflections).

yes got the same....see other comments at v1.0.9 EGT re this...

found the issue with my TCA sidestick. I found that the ailerons/elevator were not neutral in MSFS, which had caused spoiler deployment and other control events, so re-installed the TCA....now all perfect (However, I then found that TCA camera settings overrode Chaseplane, so had to delete them in MSFS).

yes...also getting temp set as 315 on Eng#1 (first flight - not turnaround). On cranking, N3, N2 rise, then N1 to 9.5% with no fuel flow + 'COOLING' advice illum. So I uncranked the engine, start Eng#2, waited for #1 to reduce temp - about 165 worked, then re-started #1. That seems to work, but agree with others - should be a ready inibuilds fix for it. ( MSFS2020)

It was great to hear of the L/T Radio Panel being incorporated into the 350. I can now use the panel for comms, but for NAV 1 or 2, the frequency transfer button (standby-active) doesn't work for me. Can Inibuilds look at this for a subsequent update.

so do I but in 2020.....Spoilers on one side are raised after start-up, thereafter unflyable..

Hi...I'm using chase plane, and when in certain views after 350 start-up and push, I get the LH or RH spoilers up, so can't fly at all now..... could the update have affected joystick or other peripheral settings?

anything from inibuilds??

Eddie.....thanks. That will fix my FMS issues too I think On another topic I know, but is there any resolution in 1.0.9. on Logitech/Saitek Radio Panel, which has been raised quite a bit?

thanks...is this also uploaded as a snippet in SPAD?

I regularly receive flap config and F/Ctl flap/FMS disagreement warnings when pushing back and starting an engine after a turnaround. This never happens on a first flight, but only on subsequent ones. Does this relate to checklists, state of aircraft or something else? The aircraft is prepped completely each flight. To stop the warnings, I can lower flaps but this is not a normal procedure during pushback, or clear the messages. Is this a common occurrence?

thanks.....look forward to any change