logged Fs2020 A350 bugs (v1.0.6)

[LineDX]

Hi @iniBuilds team, love flying this plane but here and there. there are some random bugs which I would like to report. Using latest V1.0.6

1. In fs2020 T.O.THS is always out of range at cold and dark startup but gets normal after engine start. In FS2024 its always the normal and set to correct settings. Not sure if it is normal or not. 

2-When open offset menu, the drop down list does not disappear after clicking the items.  You have to press the ESC button after selections for lists to disappear.

3- Randomly the tab does not automatically change to correct segment of the flight. Happens rarely though. Noticed it today, it did not change from T/O to CLB when the ac was in climb mode. But after reselecting the PEFF menu it corrected. 

4-FLEX temperature is always +67. Not sure if it is right?

5-Plane still takes off with nil or near to none input after V1. 

6-The ac did not capture the ALT constraint during managed climb mode. Example, departing OPKC BADUL1 DEP. KC509 has an ALT cap FL070 but it did not capture and continued to climb just like OP climb when the AC was in fact in Managed CLB..It was maintaining the managed speed though. 

7-Did not capture the STAR constraint ALT/FL during managed DES. VDEV more than 2500ft thus unable to capture the GS altitude of 3000ft set on FCU. Happening on MIMAL1 ARR and ILS36RZ for OPLA..

8-OIS menu items on the right side of the OIS screen does not show a green border around them as used to be in previous updated. Its hard to see selected items. The left side of the menu shows the green borders correct. 

Hope all these bugs get fixed in the next updates. 

Regards 

Edited March 31 by LineDX

[LineDX]

@inibhulds @haza2 @richboy2307 can you please review my post. 

 

Also noticed, while enroute and zooming ND in for BTV setup it showes dep airport randomly. Using navigraph. FYI 

[richboy2307]

Hi @LineDX

Thanks for your report.

1. I'm not able to reproduce this issue. I've tried spawning at the gate at a few different airports in the -900 and -1000 and each time its loaded with a proper THS value. Can you please share exactly which variant and airport/gate you're having this issue at?

2. Thanks noted.

3. Will keep an eye out on next test flights but in the meanwhile if you observe any specific condition it didn't jump on let us know for tracking.

4. It changes based on conditions (OAT, RWY COND, A-ICE, TOW, AIR COND and TORA). In its computations it will try to go for maximum thrust derate possible for the given conditions.

5. Further refinements in progress regarding rotation behaviour.

6. & 7. Thanks, I was able to reproduce. Noted.

8. The airport shown for ANF will depend on distance from PPOS to airports. There may be instances where this difference is marginal for both DEP/ARR airport and as such one airport may get shown over the other.

Thanks!

[LineDX]

Thank you for looking into it Vrishabh, T.O.THS issue is present no matter what airport/gate the aircraft is at. Both variants, but only in FS2020. Example, OPKC gate 60, CYHZ gate 20. This bug only in FS2020. FS2024 works fine. 

Will keep you posted. any update on the OIS selected items border colors? 

Regards

 

[richboy2307]

16 hours ago, LineDX said:

T.O.THS issue is present no matter what airport/gate the aircraft is at. Both variants, but only in FS2020. Example, OPKC gate 60, CYHZ gate 20. This bug only in FS2020. FS2024 works fine. 

Not sure what's different about the 2020 install on your instance. We all tried internally, and a few of our testers as well yet we cannot reproduce the issue on either BATT or Ground Power.

 Example:

 

16 hours ago, LineDX said:

Will keep you posted. any update on the OIS selected items border colors? 

They're highlighted blue to indicate which one is the active option if that is what you mean. It will also highlight in blue as you hover your mouse over it.
So for example in the below image DISPLAY TYPE OLD is active. This is part of the redesign in one of the last few updates.

Thanks!

[LineDX]

Hi @richboy2307 I tried cold and start, turned all 4 batteries to ON, but still T.O.THS shows out of range as shown in the screenshot. strange, its only in FS2020. FS2024 works as expected. 

 

Regarding the menu items, highlighted blue is very light and hard to see. If you guys can make it dark blue, it would be easy to see the selections. Have a look at the attached pic(edited in ms paint with little dark blue border) I see someone else on the forum had the same issue. 

Regards

Edited April 3 by LineDX

[LineDX]

Hi team, updated to version 1.0.7 and many of the above reported bugs still exist. 

1. In fs2020 T.O.THS is always out of range at cold and dark startup even after following the above mentioned instructions. 

2-When open offset menu, the drop down list does not disappear after clicking the items.  You have to press the ESC button after selections for lists to disappear.

6-The ac did not capture the ALT constraint during managed climb mode. Example, departing OPKC BADUL1 DEP. KC509 has an ALT cap FL070 but it did not capture and continued to climb just like OP climb when the AC was in fact in Managed CLB. It was maintaining the managed speed though. 

7-Did not capture the STAR constraint ALT/FL during managed DES. VDEV more than 2500ft thus unable to capture the GS altitude of 3000ft set on FCU. Happening on MIMAL1 ARR and ILS36RZ for OPLA.

 

New ones:

1-The TCAS does not generate any TA/RA even when traffic is visible. Even the aircrafts don't change the shape/color when comes in close proximity. 

2-switch the TCAS from TA/RA mode to standby and then back to TA/RA mode does not clear ECAM notification. 

3-When change the MACH speed in the CRZ mode from managed to selected. The ETA does not change in the CRZ tab in PERF section. It's bug. MACH.78 and M.88 has the same ETA for the T/D which is 94miles away. This can't be right. 

Regards

 

 

[LineDX]

@richboy2307 please review the autosave file with TO THS showing out of range with all batts on and external power connected. 

TOTHSoutofrange.bin

Edited April 15 by LineDX

[richboy2307]

Hi @LineDX

On 4/9/2025 at 5:02 AM, LineDX said:

1. In fs2020 T.O.THS is always out of range at cold and dark startup even after following the above mentioned instructions. 

On 4/15/2025 at 7:48 PM, LineDX said:

please review the autosave file with TO THS showing out of range with all batts on and external power connected. 

I've even tried loading into your autosave file but not seeing this (though as mentioned noted your issue). Will see if can be reproduced on any testers systems but in any case I don't expect this to be a major bug. Even if you are getting that on spawn it shouldn't affect flight at all as the aircraft mainly re-trims after engine start as you have mentioned.

For anyone else reading this thread, this automatic trimming will usually happen after you have done the following:

• Update your weights via OIS LOADSHEET page (SET ZFW and SET FUEL)
• Fill in the FUEL & LOAD Page of the FMS (especially ZFWCG) with new values
• After engine start, observe automatic re-trim to the managed trim value.
• Troubleshooting: In case it does not set the correct value, DISARM and then ARM your ground spoilers again to trigger the auto-trim process again. 

On 4/9/2025 at 5:02 AM, LineDX said:

2-When open offset menu, the drop down list does not disappear after clicking the items.  You have to press the ESC button after selections for lists to disappear.

Should be fixed in 1.0.8

On 4/9/2025 at 5:02 AM, LineDX said:

6-The ac did not capture the ALT constraint during managed climb mode. Example, departing OPKC BADUL1 DEP. KC509 has an ALT cap FL070 but it did not capture and continued to climb just like OP climb when the AC was in fact in Managed CLB. It was maintaining the managed speed though. 

7-Did not capture the STAR constraint ALT/FL during managed DES. VDEV more than 2500ft thus unable to capture the GS altitude of 3000ft set on FCU. Happening on MIMAL1 ARR and ILS36RZ for OPLA.

As for VNAV in general, team is working on a larger update to the logic that will improve VNAV calculations and ALT CSTR compliance. This will come in a future update (1.0.9 at the earliest, though may be later as its still undergoing refinement and testing process).

 

On 4/9/2025 at 5:02 AM, LineDX said:

1-The TCAS does not generate any TA/RA even when traffic is visible. Even the aircrafts don't change the shape/color when comes in close proximity. 

Thanks already logged and team is actively working on it.

On 4/9/2025 at 5:02 AM, LineDX said:

2-switch the TCAS from TA/RA mode to standby and then back to TA/RA mode does not clear ECAM notification. 

The TCAS STBY ECAM can be triggered by any of the following,
‐ Select STBY in the TCAS mode option list on the SURV CONTROLS page of the MFD, or
‐ Select STBY in the XPDR mode option list on the SURV CONTROLS page of the MFD, or
‐ Set the ALT RPTG button to OFF on the SURV CONTROLS page of the MFD.

As its status is controlled by more than just the TCAS mode (TA/RA), probably what happened in your case is as follows
- You set the TCAS mode from TA/RA to STBY
- The ALT RPTG button also automatically set itself to OFF (by design)
- You set the TCAS mode from STBY back to TA/RA
- The ALT RPTG button remained OFF (by design)

So ensure none of the following are set STBY or OFF to make the ECAM disappear.

 

On 4/9/2025 at 5:02 AM, LineDX said:

3-When change the MACH speed in the CRZ mode from managed to selected. The ETA does not change in the CRZ tab in PERF section. It's bug. MACH.78 and M.88 has the same ETA for the T/D which is 94miles away. This can't be right. 

Reported.

Thanks!
 

[LineDX]

18 hours ago, richboy2307 said:

Hi @LineDX

I've even tried loading into your autosave file but not seeing this (though as mentioned noted your issue). Will see if can be reproduced on any testers systems but in any case I don't expect this to be a major bug. Even if you are getting that on spawn it shouldn't affect flight at all as the aircraft mainly re-trims after engine start as you have mentioned.

For anyone else reading this thread, this automatic trimming will usually happen after you have done the following:

• Update your weights via OIS LOADSHEET page (SET ZFW and SET FUEL)
• Fill in the FUEL & LOAD Page of the FMS (especially ZFWCG) with new values
• After engine start, observe automatic re-trim to the managed trim value.
• Troubleshooting: In case it does not set the correct value, DISARM and then ARM your ground spoilers again to trigger the auto-trim process again. 

Should be fixed in 1.0.8

As for VNAV in general, team is working on a larger update to the logic that will improve VNAV calculations and ALT CSTR compliance. This will come in a future update (1.0.9 at the earliest, though may be later as its still undergoing refinement and testing process).

 

Thanks already logged and team is actively working on it.

The TCAS STBY ECAM can be triggered by any of the following,
‐ Select STBY in the TCAS mode option list on the SURV CONTROLS page of the MFD, or
‐ Select STBY in the XPDR mode option list on the SURV CONTROLS page of the MFD, or
‐ Set the ALT RPTG button to OFF on the SURV CONTROLS page of the MFD.

As its status is controlled by more than just the TCAS mode (TA/RA), probably what happened in your case is as follows
- You set the TCAS mode from TA/RA to STBY
- The ALT RPTG button also automatically set itself to OFF (by design)
- You set the TCAS mode from STBY back to TA/RA
- The ALT RPTG button remained OFF (by design)

So ensure none of the following are set STBY or OFF to make the ECAM disappear.

 

Reported.

Thanks!
 

Thank you for looking into it and for your kind help @richboy2307. Much appreciated.