July 4Jul 4 Yeah cant click anything on the overheard.. takes forever to find the super small clickspot for the button. Unflyable :( Never had this issue with another aircraft. Only the ini a300
July 6Jul 6 Staff Hello all,Following the initial beta release of SU6, we are pleased to report that the clickspot issue encountered in SU5 appear to have resolved with SU6 Beta 1.However it is still worth noting that this is beta so it's possible that users might encounter other issues if deciding to opt into SU6 Beta,Thank you.
July 7Jul 7 Chaseplane doesn't work in the beta and that's a dealbreaker for me. Cant fly without it now. I will just hold off flying the A300 for now i guess. Its weird that no other aircraft has ever had that clickspot problem for me. Ever. I wonder what happened. Edited July 7Jul 7 by tjockklat
Friday at 07:59 PM3 days So, basically, those who don't do betas are stuck with an INOP plane until SU6 is released?
Friday at 08:13 PM3 days Staff 9 minutes ago, lmhariano said:So, basically, those who don't do betas are stuck with an INOP plane until SU6 is released?Hi,The aircraft isn't INOP, it can be inconvenient to users to have to click more centrally or maneuver the camera around in excess in order to click a certain button; however this doesn't prohibit the user in flying the aircraft in anyway. Even in the current SU5 environment I still find myself flying in A300 regularly while having the same clickspots as everyone else. We understand the frustration caused, and thankfully Asobo were able to rectify the issue in SU6 returning functionality to clickspots as intended but the plane was never in a position to where one couldn't fly it. Thank you :)
Saturday at 11:25 AM2 days 14 hours ago, IniJamir said:Hi,The aircraft isn't INOP, it can be inconvenient to users to have to click more centrally or maneuver the camera around in excess in order to click a certain button; however this doesn't prohibit the user in flying the aircraft in anyway. Even in the current SU5 environment I still find myself flying in A300 regularly while having the same clickspots as everyone else. We understand the frustration caused, and thankfully Asobo were able to rectify the issue in SU6 returning functionality to clickspots as intended but the plane was never in a position to where one couldn't fly it. Thank you :)Yes, indeed. I do use the aircraft (freighters only) since the release for MSFS 2020 almost every flight. Now the 2024 premium version.The aircraft is very good to fly and to operate, even with the clickspot issue.But if I had a wish....I am still missing this:APU exhaust (I know ini works on it)and brighter red beacon and position lights during the day time. I know this is an Asobo problem in MSFS 2024 in general, but PMDG did it somehow better for their fleet...Anyway, a good aircraft for MSFS.By the way, I am an aircraft technician, I know what I am talking about..
4 hours ago4 hr On 7/24/2026 at 5:13 PM, IniJamir said:Hi,The aircraft isn't INOP, it can be inconvenient to users to have to click more centrally or maneuver the camera around in excess in order to click a certain button; however this doesn't prohibit the user in flying the aircraft in anyway.Ok. Where can I enable Pitch Trim 1 and Yaw Damper 2, if mousing over does not reveal any clickspots at all?For reference, Pitch Trim2 and Yaw Damper 1 do engage; I can find a tiny clickspot on the edge/aft surface Edited 4 hours ago4 hr by lmhariano
3 hours ago3 hr Staff 36 minutes ago, lmhariano said:Ok. Where can I enable Pitch Trim 1 and Yaw Damper 2, if mousing over does not reveal any clickspots at all?For reference, Pitch Trim2 and Yaw Damper 1 do engage; I can find a tiny clickspot on the edge/aft surfaceThe clickspots with the current issue are within the center of the button/switch, one just has to move the camera a little more, it's easier said since I use TrackIR I'll be candid but it's still not impossible. Regardless the fix will be arriving with SU6 so it's moot to back and forth about usability or personal usage preference.
Create an account or sign in to comment