14 hours ago14 hr I don't like doing posts like these but as a consumer I feel a little let down. This A350 has been a thorn in my side since version like 1.8 I think. WASM crashes every time I try a flight over 4 hours. Haven't been able to update the navdata using navigraph in for what seems like eons now. STAR waypoints corrupt and if you try and fix them you run the risk of a WASM crash. Engine fans at 1 point just straight up didn't spin. Now after SU 5.1 we have panel / flood lighting issues. The list just gets longer and longer. I get it, Xbox isn't easy to code but you committed to having an Xbox version and I paid to have the plane.When it first released it was almost flawless. I love the A350 but right now it's just not flyable on console. I want to fly it so bad. I think if there is 1 thing that bugs me the most, it has to be the navdata issue. It worked fine on release and the broken or corrupt STARs. Inibuilds please fix this plane because I'm starting to get the feeling is console simmers are getting out on the back burner. I love your products but I'm not going to lie...they have been an absolute nightmare to fly since SU4.
9 hours ago9 hr For the engine did you replace the oil in the efb maintenance page? Im having no issues on Series X.
4 hours ago4 hr Author No. If your referring to the comment about the fans not spinning it was back in version 1.0.8 where you would start the engines and get the full sounds and everything but the fans wouldn't spin. It was a bug. This plane has just been a headache since it's update after release. Then again, 2024 has been an absolute nightmare for me in general since SU4. My biggest gripe has to be the Navdata issues that have plagued Xbox. Both PMDG and Inibuilds haven't fixed this issue yet. Something big must have broke after SU4.
Create an account or sign in to comment