A350 first flight - Discovered ISSUES so far [MSFS2020]

[Alvariteus]

Hi iniBuilds team.

 

First of all, congratulations for this plane. It is amazing, its potential is as GIGANTIC as the plane itself.

However, I would like to provide you a small feedback after my first flight, from Madrid to New York. More than 7 hours that I used to discover the plane completely. This issues are mostly bugs with, I think, an easy solution, but that affects very negatively the flight experience, so they should be addressed very quickly. I also leave a couple of photos I took arriving to New York JFK.

So let's start.

 

[SOUNDS]

- Sounds are in general TOO LOUD, from engines, to callouts to everything. It is true that it can be adjusted by the EFB, but this is not a definitive solution as the adjustments are unequal and all the overall experience regarding the sounds is spoiled. I think a sound levels refinement is desperately needed.

- AP disengage siren doesn't stop. The siren kept ringing after disengaging the AP, no matter what I did. Magically it stopped after going to the external view and going back to the cockpit view, so I guess this is a bug.

- Weird and expremely LOUD noise when gear down. After releasing the landing gear, a super noisy and weird noise appeared, specially in the cockpit but also with the wing view. I guess this is also a bug (at least the level it have).

[THROTTLE]

- Unable to use reverse thrust with my Thrustmaster Airbus TCA, no matter the configuration I use in the EFB, no matter the deadzone I put. So I assume this is a bug.

[EFFECTS]

- No contrails at all. No matter the flight level I am flying, nor the temperature outside, the engine do not produce any contrails. This is a bug that affects general flight experience quite a lot.

[SYSTEMS]

- There is no DME miles to the ILS shown when the ILS button is activated, no matter the distance I am to the localizer. So I guess this is also a bug.

[FLIGHT MODEL]

- Plane takeoffs too easily, almost like a helicopter, even loaded for a transataltic flight. I am not sure if this is a bug or not, but I am quite sure that the real A350 do not behave like this during takeoff. I think something needs more refinement here. Landing, however, was mostly okay, but I think the final approach speed was also too low.

[EXTERIOR]

- I don't know if I am doing something wrong, but cabin lights do not turn on at night, so the plane from the outside seems dark, even on ground unloading passengers.

 

This is all what I discovered for now. Surely more things will come during future flights, and I will report them in order to help you guys to improve this amazing product with quick updates. There are so many amazing things too. In fact, most of the things are amazing. Systems works very good, the plane behaves very realistically - I think- in the air (except for the details mentioned before), wing flex effects are amazing, and a long etcetera. To be the first version, the plane is in good condition, but just as happened to other developers, quick updates are needed to address these urgent refinements.

 

Please, keep working on this amazing product and I am sure this will be a reference for the long haul flight simulation.

Regards,

Alvaro.

Edited February 26 by Alvariteus

[Alvariteus]

Extra bug I forgot:

[SYSTEMS]

- When turning on the beacon light, external power seems to disappear, so all the systems turned off.

[EXTERIOR]

- Not sure if this is the A350's or GSX fault, but the jetway does not match the door, it connects more or less at the level of the cockpit.

Edited February 26 by Alvariteus

[NoBird]

45 minutes ago, Alvariteus said:

Extra bug I forgot:

[SYSTEMS]

- When turning on the beacon light, external power seems to disappear, so all the systems turned off.

[EXTERIOR]

- Not sure if this is the A350's or GSX fault, but the jetway does not match the door, it connects more or less at the level of the cockpit.

Its not GSX fault, happens also in the standard game.

[Alvariteus]

15 minutes ago, NoBird said:

Its not GSX fault, happens also in the standard game.

Thanks for the info!

[Eflyer]

1 hour ago, Alvariteus said:

Extra bug I forgot:

[SYSTEMS]

- When turning on the beacon light, external power seems to disappear, so all the systems turned off.

[EXTERIOR]

- Not sure if this is the A350's or GSX fault, but the jetway does not match the door, it connects more or less at the level of the cockpit.

The beacon lights automatically triggers the removal of the chocks and external power.

By design, the beacon lights is switched on only before pushback/moving so you should have your APU on at that time.

[nopixar]

How the plane rotates really bugs me too. It literally takes off like a crisp packet in the wind… and the way the pitch control works initially has zero smoothnes…It does detract from an absolutely gorgeous looking aircraft with some small bugs but also some great features. The whole flight model is…questionable at best. It’s a shame really I was really looking forward to this. It’s not unflyable, but when it behaves like that, you can’t help but be bothered by it considering all the hype around it. And yet nobody during testing not even the real pilots who streamed it said a word about it. No flare mode either…? You can pretty much make no inputs all the way down to the ground…. Really hoping it improves over time with patches…

Edited February 27 by nopixar

[Seth2413]

- Navigraph charts dont work in EFB. 

- Also the enroute maps come on the  disappear when they feel like it.  

- AP siren wotn turn off (unless go to external view to turn off - BUG!!)

- Had major issue with click points in and around screens.  For eg trying to slect a runway brake point was near impossible as click points just wouldnt work for me and had to press my left mouse button multiple times for it to work.  

- Takeoff is ridiculous.  

- Descent at one stage go to 7200 ft/min and it was ithin profile.  

- Biggest issue is that auto tune doesnt work with Beyond ATC.  I know its not their job to see if works with other programs but BATC is probabaly one of the most used programs out there, surely could have made sure it worked with it (like it does with GSX intergration I see).  

 

I guess all the work went into the 2024 version perhaps, guess what inibuilds there are a lot of people still using 2020, please fix these errors, lots of hype but a bit of a let down unfortunately for me.  

Edited February 27 by Seth2413

[Jestersstick]

Thx for heads-up re BeyondATC auto-tune bc I was going to fire it up next flight. I assume thats on BATC's end and they will update app soon. I know I had similar issue in another a/c and next day BATC update fixed it.  I wouldnt say the GSX integration works in 2020...that would be a stretch bc I couldn't re-fuel. Easy fix was turning off GSX-integration option and doing it the normal way. Ease of take-off was a surprise b/c I had a full load, but I work in an office and dont fly 350s for a living so I just rolled with it. I also noticed its extremely easy to over-speed during taxi, which is odd considering the weight/mass- that may not be an issue in fs24 b/c of the new taxi-physics or w/e MS claimed they had in it.  Im sure these bugs can be ironed-out soon and INI will show us FS20 users some love b/c there certainly is a lot of simmers holding off on 24 b/c it has probs. Overall, I enjoy the a/c and love the attention to detail while at cruising alt b/c I have no intentions of trying to descend and land if the AP-alarm wont shut off.

[Alvariteus]

5 hours ago, Eflyer said:

The beacon lights automatically triggers the removal of the chocks and external power.

By design, the beacon lights is switched on only before pushback/moving so you should have your APU on at that time.

While I may agree on the procedure of turning on the beacon lights, that doesn't mean that the plane should quit chocks and external power when turning them on. It is a complete nonsense and unrealistic.

[Awemeter]

8 hours ago, Alvariteus said:

Hi iniBuilds team.

 

First of all, congratulations for this plane. It is amazing, its potential is as GIGANTIC as the plane itself.

However, I would like to provide you a small feedback after my first flight, from Madrid to New York. More than 7 hours that I used to discover the plane completely. This issues are mostly bugs with, I think, an easy solution, but that affects very negatively the flight experience, so they should be addressed very quickly. I also leave a couple of photos I took arriving to New York JFK.

So let's start.

 

[SOUNDS]

- Sounds are in general TOO LOUD, from engines, to callouts to everything. It is true that it can be adjusted by the EFB, but this is not a definitive solution as the adjustments are unequal and all the overall experience regarding the sounds is spoiled. I think a sound levels refinement is desperately needed.

- AP disengage siren doesn't stop. The siren kept ringing after disengaging the AP, no matter what I did. Magically it stopped after going to the external view and going back to the cockpit view, so I guess this is a bug.

- Weird and expremely LOUD noise when gear down. After releasing the landing gear, a super noisy and weird noise appeared, specially in the cockpit but also with the wing view. I guess this is also a bug (at least the level it have).

[THROTTLE]

- Unable to use reverse thrust with my Thrustmaster Airbus TCA, no matter the configuration I use in the EFB, no matter the deadzone I put. So I assume this is a bug.

[EFFECTS]

- No contrails at all. No matter the flight level I am flying, nor the temperature outside, the engine do not produce any contrails. This is a bug that affects general flight experience quite a lot.

[SYSTEMS]

- There is no DME miles to the ILS shown when the ILS button is activated, no matter the distance I am to the localizer. So I guess this is also a bug.

[FLIGHT MODEL]

- Plane takeoffs too easily, almost like a helicopter, even loaded for a transataltic flight. I am not sure if this is a bug or not, but I am quite sure that the real A350 do not behave like this during takeoff. I think something needs more refinement here. Landing, however, was mostly okay, but I think the final approach speed was also too low.

[EXTERIOR]

- I don't know if I am doing something wrong, but cabin lights do not turn on at night, so the plane from the outside seems dark, even on ground unloading passengers.

 

This is all what I discovered for now. Surely more things will come during future flights, and I will report them in order to help you guys to improve this amazing product with quick updates. There are so many amazing things too. In fact, most of the things are amazing. Systems works very good, the plane behaves very realistically - I think- in the air (except for the details mentioned before), wing flex effects are amazing, and a long etcetera. To be the first version, the plane is in good condition, but just as happened to other developers, quick updates are needed to address these urgent refinements.

 

Please, keep working on this amazing product and I am sure this will be a reference for the long haul flight simulation.

Regards,

Alvaro.

I 100% agree with the flight model on takeoff and the gear drag being too loud. It sounds like it’s a static sound because regardless of where you are within the aircraft the volume of the gear drag is the same. Nonetheless the plane defiantly has some issues but as you said before it has great potential and will end up being one of the best a350s we have ever had in a flight sim. 

[LNOSS]

Not BATC issue. Ini has to fix the auto tune issue.

 

BATC has stated that.

[GopherCH]

2 hours ago, Seth2413 said:

 

- Had major issue with click points in and around screens.  For eg trying to slect a runway brake point was near impossible as click points just wouldnt work for me and had to press my left mouse button multiple times for it to work.  

 

I have the same. Do you use a headtracker by any chance? I use TrackIR and I have a feeling it's related to camera movement. If I stay completely still (which is super hard) then the clicks work. As soon as the cursor moves just a tiny bit, it doesn't accept clicks. Could potentially also happen if  there's turbulence and the camera shakes, don't know.

[jez481]

I use TrackIR and find clicking on the FMS very difficult unless completely still, then it's ok.

I'd agree with the above post that head tracking could be an issue.

Something for iniBuilds to check please - head tracking vs FMS input - thank you.

[Seth2413]

23 minutes ago, GopherCH said:

I have the same. Do you use a headtracker by any chance? I use TrackIR and I have a feeling it's related to camera movement. If I stay completely still (which is super hard) then the clicks work. As soon as the cursor moves just a tiny bit, it doesn't accept clicks. Could potentially also happen if  there's turbulence and the camera shakes, don't know.

No sorry I dont.  Ive done 2 flights, first I actually did in VR and it was stable enough but second was just terrible, had to double click everything at first and then at one stage it just would not until I did about 5 button presses.  

[aza091]

3 hours ago, Alvariteus said:

While I may agree on the procedure of turning on the beacon lights, that doesn't mean that the plane should quit chocks and external power when turning them on. It is a complete nonsense and unrealistic.

I totally second this. It's not a procedure, it's a bug or a wrong design feature.

[martheshep]

9 hours ago, Seth2413 said:

- Navigraph charts dont work in EFB. 

- Also the enroute maps come on the  disappear when they feel like it.  

- AP siren wotn turn off (unless go to external view to turn off - BUG!!)

- Had major issue with click points in and around screens.  For eg trying to slect a runway brake point was near impossible as click points just wouldnt work for me and had to press my left mouse button multiple times for it to work.  

- Takeoff is ridiculous.  

- Descent at one stage go to 7200 ft/min and it was ithin profile.  

- Biggest issue is that auto tune doesnt work with Beyond ATC.  I know its not their job to see if works with other programs but BATC is probabaly one of the most used programs out there, surely could have made sure it worked with it (like it does with GSX intergration I see).  

 

I guess all the work went into the 2024 version perhaps, guess what inibuilds there are a lot of people still using 2020, please fix these errors, lots of hype but a bit of a let down unfortunately for me.  

I have encountered all the problems you met! The descending rate reached 7700 ft/min and I was like wtf.

[Alvariteus]

Other bug I found for the team of iniBuilds to solve asap. In this case in the A350-1000.

[FLIGHT CONTROLS]

- The plane does not turn on ground, having all well configured, and with the gear showing like it's turning. The plane, however, goes straight and it was not possible to solve it, so a good flight that wasruined and a lot of time wasted in its preparation. Photo is attached. This one is so far the most frustrating bug and the first one that produces me a no-go.

[Delta_A350]

some things in the cockpit are pink and checkered. like when a file doesn't work. engines randomly stopped then i couldn't bring the landing gear down.

[kevinh]

17 hours ago, Seth2413 said:

- AP siren wotn turn off (unless go to external view to turn off - BUG!!)

It works for me. Press the AP disconnect a second time. That shuts the warning off.

[kevinh]

3 hours ago, Alvariteus said:

Other bug I found for the team of iniBuilds to solve asap. In this case in the A350-1000.

[FLIGHT CONTROLS]

- The plane does not turn on ground, having all well configured, and with the gear showing like it's turning. The plane, however, goes straight and it was not possible to solve it, so a good flight that wasruined and a lot of time wasted in its preparation. Photo is attached. This one is so far the most frustrating bug and the first one that produces me a no-go.

 

It sounds like the nosewheel is skidding (applying too much tiller angle before the turn rate builds up). Taxying in MSFS isn't great (it's improved a lot in FS24 apparently). You must make tiller inputs slowly or the nosewheel will skid. Only make tight turns with GS less than 10 knots.

Nosewheel skidding will happen in a real airliner if you apply too much tiller too quickly. So this is a realistic effect and you need to keep tiller inputs slow and only increase the tiller as the turn rate builds up. I find setting reactivity to 0 in the tiller axis helps as it responds slower.

[Seth2413]

11 hours ago, martheshep said:

I have encountered all the problems you met! The descending rate reached 7700 ft/min and I was like wtf.

Yeah I just in my virtual airline post that the A350 is causing flights to be rejected because of its descent rate (like above).  The VA will waive the rejection but just goes to show how many this is affecting.  I know there will be issues but surely WTF are beta testers doing.  We pay (in my case $120 Aust dollars!!!) for these things and they should be better, not good enough really.  

[Alvariteus]

2 hours ago, kevinh said:

It sounds like the nosewheel is skidding (applying too much tiller angle before the turn rate builds up). Taxying in MSFS isn't great (it's improved a lot in FS24 apparently). You must make tiller inputs slowly or the nosewheel will skid. Only make tight turns with GS less than 10 knots.

Nosewheel skidding will happen in a real airliner if you apply too much tiller too quickly. So this is a realistic effect and you need to keep tiller inputs slow and only increase the tiller as the turn rate builds up. I find setting reactivity to 0 in the tiller axis helps as it responds slower.

It is not the case, as I tried all lond of angles. The plane was just unresponsive to the turn, even seeing the wheels react to the imput as it is shown in the photo 😕

[ben4muk]

7 hours ago, Alvariteus said:

It is not the case, as I tried all lond of angles. The plane was just unresponsive to the turn, even seeing the wheels react to the imput as it is shown in the photo 😕

Experience the same issue.  I did a test (MSFS2024).  I took a plane without GSX, fired her up and tried to taxi.  No problem whatsoever.  I then reset the flight, this time I did a GSX pushback.  I got an MSFS warning of Gear Damage.  When I the try to taxi, I get the problem described...  No matter how slow or how much input, nosewheel turns, but the plane is always "skidding".

[heinzy87]

Some issues and questions below:

1) Has anyone has problems with trying to deactivate the hot brake smoke ? Doing maintenance (repair brakes and tires) like on the PMDG 777 doesn’t fix it ?

2) I also have the issue of the autopilot siren staying on for a long time.

3) finally, there’s no landing smoke for the rubber burn on touchdown - or am I missing something ? 

[ben4muk]

28 minutes ago, heinzy87 said:

Some issues and questions below:

1) Has anyone has problems with trying to deactivate the hot brake smoke ? Doing maintenance (repair brakes and tires) like on the PMDG 777 doesn’t fix it ?

2) I also have the issue of the autopilot siren staying on for a long time.

3) finally, there’s no landing smoke for the rubber burn on touchdown - or am I missing something ? 

2) Did you clear the warning?