LineDX

Hi team @iniBuilds There is a big problem in FS2024/A350. The bloom and lens flare causing too much brightness in the flight deck. For example, when turn on the batts and ext power the lights behind these buttons is too bright. The main panel is also very bright specially the OIS map. I read on MSFS forums, its a known issue with FS2024 as Microsoft does not give an option to turn off bloom and lens flare. but if ini pushes microsoft they can bring these controls back just like FS2020. Even the cockpit textures are little blurry compared to FS2020. Pleas have a look at the attached video. Microsoft Flight Simulator 2024 2025 (1).mp4

Is patch 1.0.9 coming out today?

Reporting bugs in a proper way is very important for the elimination of bugs and further polishing of the product. Some of the users are very good at it. Would like to thank one user @Der Michel who has been quite dedicated reporting issues the 350. I am sure team finds it hard sometimes seeing that many reports but I appreciate users like Der Michel who has been doing lots of bug/problems reporting to the team. In the end its beneficial for the product and users. Thank you and thank you @iniBuilds listening to community and working hard on the product. It's an amazing aircraft.

Hi team, since updated to v 1.0.8 there are some issue with auto land. The approach and landing goes fine but shortly after touch down the airplane starts veering/yawing to the right and end up in the grass. Here is the scenario. Possible bug. OPIS ILS 28L.

Yes

Hi team @iniBuilds during flight from EGLL-OTHH, when time compression set to 4X The clock does not move 4X. video attached. Possible bug.. Microsoft Flight Simulator 2024 2025.mp4

Regarding the fms2 not showing/cycling sub menus. The scenario is: Cold and dark startup at OTHH gate 75(stock airport). Over panel :set OIS. Flight plan imported from simbreif. Fuel and zfw set. Dep/arr charts selected. FMS1. Flight Plan imported/winds imported. Weights set. T/o performance done on OIS and sent to fms1 FMS 2. THE PAGES CYCLE AT THIS MOMENT. Surv page. Set ATC/com set. Kusa selected for vatsim weather. (hoppie already set). Update the atis. Open the atis clicking the arrow key. Then go back. AT THIS POINT FMS 2 FLT PLAN AND PERF PAGES WON'T OPEN/CYCLE AS SHOWN IN THE ABOVE VIDEO

Had this wasm as well in FMS1. The scenario was. Cold and dark. Barts and external power on. Flight Plan not loaded, no weights set. Click on fms1 top menu and had a wasm. But if load cold and dark, Barts and Ext 1 and 2 connected. Flight plan created/imported in OIS.weights set, chats set. No wasm on fms 1 then. Strange. Never had this issue before.

Hi team @iniBuilds after updating to v1.0.8. FMS2 does not open sub menus . Please have a look at the attached video. Cleared WASM. but no joy. Also, when loading the airplane and go inside the cockpit. hear a crashing/hammering sound for sec, like something falling hard. Did not notice in in previous builds. Microsoft Flight Simulator 2024 2025.mp4

Hi team @iniBuilds after updating to latest v1.0.8. pressing the EXT1 and EXT2 behaves very strange. There is a delay for light to go from AVAIL to AUTO. Also , there is long delay in clunk sound as well. It's for sure different from the previous builds. Possible bug. Microsoft Flight Simulator 2024 2025.mp4

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

Hi @iniBuilds Managed vs selected speed ETA to TOD is the same whereas managed speed is M.85 compared to selected M.88. Technically, selected speed ETA to TOD should be earlier than managed but ETAs are the same for both managed vs selected speed. Looks like its a bug.

Hi @richboy2307 The taws logic, I made sure all the sound settings are on. Taking off from YYC and flying west towards the mountains at lower altitudes, without flaps, without gears many of the TAWS callouts are missing like Terrain ahead, too low flaps, too low gear. GPWS callouts come up like 2000. and so on.

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

Team inibuilds said they are working on it to fix it.

The below mode scans traffic -9900' to +2700' ft. same as above mode scans -2700' to +9900' . Norm is +-2700' . Hope that makes sense.

100% agree with you capt. Tom. This is one of the most unpractical thing in FS. I have already suggested to @iniBuilds in another post to make it optional in OIS. Regards

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.

1.0.7 can hear the Taws sounds but some are missing or something wrong with logic. Don't hear *terrain ahead". No retard sound on landing as well.

Hi @iniBuilds, I really like the new flight planning tool in OIS. Please add the CI option on the form as currently it does not have the CI option and most of the flight plans generated it gives CI 15. Also UAL2018 output format does not generate any OFP. Gives an error. Please look into it. Regards

Hi @iniBuilds how about making engine and sensor covers an option in OIS. Many of the users like me, we start from the gate and in real life when you get the plane form gate engine and sensor covers are not there until or unless the plane is parked for extended duration of time. Please make it optional so that users who want to have the covers on they can do so from the OIS menu and people who don't want they can turn it off from the OIS menu. Regards

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

same issue. team has logged it and they are looking into it.

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

Hi @richboy2307 thank you for your kind support. The headphone simulation was already turned off, still don't hear the TAWS warnings. RESET WASM, re-installed but no joy. Hope it gets addressed. Regards