Alvariteus

You are so funny.

My tone? Aggresive? What's wrong with my tone? I am spending my time giving them feedback just to help them know what my issues are to get them solved asap. And do you know why I want them solved asap? Well, I will be aggresive now so that you know what aggresive and demanding tone is: I spent 92 EUROS on a plane that was launched near unflyable at first. I am being patient and positive with my feedbacks at all time, but is a SHAME that I have to enjoy a product with much lower quality than that of MSFS 2024 paying exactly the same money and without a cabin modeled. They said they can't optimize it? And why Fenix could? Why PMDG could on its 777 which is as big as this plane or more? I don't buy these excuses. And while is true that they are updating it weekly, and if you read my post you will see this is the first thing I say, I think is shameful having more bugs than other customers paying the same, and less features and no modeled cabin, which makes it a different product. I don't need the access to the MSFS 2024 version because I will not switch to that sh** simulator in its current state, I don't like the comercialization policy they followed. I love that they decided to launch it for MSFS 2020 as well, but if they knew that the plane in MSFS 2020 was worse, they could have delay a little the MSFS2020 version until it is at the same level And I think I can and I must say all this because I payed 92 euros my friend. I would never say anything like this to FlyByWire or Horizon which are people who are providing planes to the sim for free on their free time. But here I am a customer and I have a level of demand equal to the price I have paid. I trust iniBuilds in the sense that I think that they will solve all these things and they will make this plane at the level of the price, but it currently still isn't. As a customer I am demanding and I will keep being demanding and giving feedback about things I don't like and potential bugs because that is what I should do.

A350 after patch 1.0.2 First of all I want to thank the iniBuilds team for keep working in the plane and gradually solving the many issues it has. Here are the things that are solved to me and not, regarding my initial post, in a constructive way to help keeping this aircraft improved and reach a high level. [SOUNDS] - An explosion sound is still heard during rotation, which ruins the immersion during takeoff. SLIGHTLY IMPROVED, BUT NOT SOLVED ❌ - The flaps deployment sound when on cabin view is amazing, but it should be a liiitle bit quieter in my opinion. NOT SOLVED ❌ [EFFECTS] - There are still no contrails shown at any condition in MSFS 2020, something that should be addressed soon. SOLVED ✔️ - The rain effect in the landing gear that is shown while taxiing still appears once the airplane is stopped and parked, giving the impression that something is burning down there. NOT YET TESTED - No rain removal effect when wippers on. This effect should be added just as it is achieved in the Fenix or even freeware products, so it shouldn't be that difficult to get. NOT YET TESTED - Weird lighting of the wippers while landing and wing lights are on. They are shown as directly illuminated, but this should not be the case. NOT YET TESTED [SYSTEMS] - The AP disengage alarm still doesn't stop. The alarm keep ringing after disengaging the AP, and stops only after going to the external view and going back to the cockpit view. This makes me think that the master buttom to stop the alarm actually works, but the sounds are not responsive to the given input. SOLVED, WITH NEW CONTROLS CONFIG ✔️ - ALL screens in the cockpit got freezed and made me cancel a flights. This happened after trying to insert the step climbs in my route. I have seen other people with this very same issue in other situations, so I think this is a big bug that have to be solved urgently. SOLVED, BY THE MOMENT ✔️ - Screens' response to inputs is just BAD. Many times I have to clic a lot of times just to get one thing done, and this is a huge problem while flying online and during situations in which you have to perform a lot of tasks in a short period of time. NOT SOLVED ❌ - Impossible to activate BTV due to a very poor Navigraph integration. Having Navigraph updated at all places, the plane shows a message regarding Navigraph database when trying to display the destination airport to select the taxiway to vacate in order to get the BTV working. The funny thing is that the airport map is shown in the departing airport, but never in the arriving one. PARTIALLY SOLVED, BY NOT ACTIVATING AIRPORT MAP ON DEPARTURE AIRPORT ✔️ - Autobrake mode selector is broken. There are two parts in that selector, one for the runway condition and another one for braking intensity. No matter which one I choose, it will always react to runway condition, so braking intensity is impossible to be selected. In this sense, autobrake without BTV is always medium. SOLVED ✔️ - Autolanding is just not here. The plane is unable to do a correct flare and crashes into the runway during the autoland. Is urgent to solve this because, as you know, we sometimes have to land with very low visibility and we want to want to avoid neck and spine problems to our passengers. NOT YET TESTED - Beacon light still removes chokes and external power when turning it on, which makes no sense and it is completely unrealistic. This bug (or "feature"?) should be removed asap. NOT YET TESTED [FLIGHT MODEL] - Plane still takes off too easily. It even rotate unitentionally before giving it any input from the joystick just because is light or the trim configuration that the plane itself gives is incorrect. PARTIALLY SOLVED ✔️ - Flight model while flying manually is bad after rotation. The plane tends to respond in a very unsolid manner as soon as it rotates, as I try to reach 15 degrees of pitch on takeoff (with good speed), moving the nose up and down slightly, something that should not happen. It reminds me of what Headwind's Boeing 787 did before the update that mostly solved this, but of course that product was and is free. IMPROVED, BUT NOT SOLVED ❌ - The reaction to joystick inputs on final approach is a little bit too sensitive and the aircraft, in my opinion, overreacts a bit. Considering how big and heavy it is, the movements should be a bit smoother, which also helps to improve the accuracy of the approach. NOT SOLVED ❌ - More or less in the same way as above, something similar happens during taxiing. The aircraft reacts too immediately and too quickly in turns. I think it should feel a bit heavier, and be more "lazy" and lagging when interpreting inputs during turns on the ground. NOT SOLVED ❌ - Weird reaction to speedbrakes when the plane is over the path of descent. It is Airbus logic to try to reach the path back when you are over it, but this planes do it too abruptly, specially when speedbrakes are deployed to help it. This have to refined. NOT SOLVED ❌ [EXTERIOR] - Still bad lighting regarding windows at night from the outside. The cabin should be completely illuminated while on ground (before departing and after arriving) with systems on and enough power. In general, lighting should have phases according to the phase of the flight, as other MSFS2020 have, but this is not the case in this plane. NOT SOLVED ❌ [NEW ISSUE DISCOVERED] - Extreme lag happens when loading the destination airport map to choose the BTV parameters. Loading of airport maps desperately need optimization. - Hydraulics liquid use seems excesive, needs to many reloads. Engine oil is in the high part of consume for this aircraft, but still acceptable.

I confirm that after your configuration setting suggestion the AP disengage alarm works well. Thanks 👏🏻

It could be this! My configuration was different. I put it as you say and try it on the enxt flight. Thanks for your help.

This is the support forum.

Yes, I am pressing it once, because if I press it once again the AP connects again, so I don't know how to do to turn off the alarm without going to the external view and back to the cockpit. Regarding the TO config buttom I do that as a temporary solution, but it should not be like that. Regards!

Hi Speedbird. Contrails in MSFS2020 are not shown, only plame with this issue in the sim and reported bu more people. Rain removal effect by wippers have never been in this plane as far as I know. Do you understand what I mean with “removal”? I am happy thay you dont have any issues with the AP disconnection sound, but in my case the master buttom do not turn off the alarm and the red sign do not disappear unless I go to the external viee and go back to the cockpit. Yes, the screen response is bad, no problems related with being in other screens. The T/O config buttom also works very bad as well. I will check about the beacon light issue in the OIS, thanks for the advise. Regards!

Hi iniBuilds team and hi everyone. After my feedback post that I leave at the end of this one too, and that suddenly became pretty popular in the forum, a patch was launched as you all know. This one solved some of the most urgent issues, like for example many problems with sounds, but I am sad to see that is still a long journy to be able to call this potentially incredible aircraft as a final product. I would rather call current version as v0.9.1. For this reason, and together with so many people that is also posting in the forum, I want to continue to contribute my two cents with this feedback that I present to you below, since I have read posts from the iniBuilds team in which they say that they are working based on the comments about bugs from users, since many of them have not been discovered during the 10 beta testers feedback that I have read they have had before the release. This makes me conclude that a lot of feedback is needed to iniBuilds in order for them to turn this product into a final product that is in line with its price. I believe that it is the most expensive single purchase of aircraft software right now in MSFS2020 once taxes are added, and perhaps the second most expensive aircraft in the simulator considering that it includes two variants. So this product needs a lot of urgent work to reach the standard that justifies its price. That said, I detail my feedback on version 1.0.1: [SOUNDS] - An explosion sound is still heard during rotation, which ruins the immersion during takeoff. - The flaps deployment sound when on cabin view is amazing, but it should be a liiitle bit quieter in my opinion. [EFFECTS] - There are still no contrails shown at any condition in MSFS 2020, something that should be addressed soon. - The rain effect in the landing gear that is shown while taxiing still appears once the airplane is stopped and parked, giving the impression that something is burning down there. - No rain removal effect when wippers on. This effect should be added just as it is achieved in the Fenix or even freeware products, so it shouldn't be that difficult to get. - Weird lighting of the wippers while landing and wing lights are on. They are shown as directly illuminated, but this should not be the case. [SYSTEMS] - The AP disengage alarm still doesn't stop. The alarm keep ringing after disengaging the AP, and stops only after going to the external view and going back to the cockpit view. This makes me think that the master buttom to stop the alarm actually works, but the sounds are not responsive to the given input. - ALL screens in the cockpit got freezed and made me cancel a flights. This happened after trying to insert the step climbs in my route. I have seen other people with this very same issue in other situations, so I think this is a big bug that have to be solved urgently. - Screens' response to inputs is just BAD. Many times I have to clic a lot of times just to get one thing done, and this is a huge problem while flying online and during situations in which you have to perform a lot of tasks in a short period of time. - Impossible to activate BTV due to a very poor Navigraph integration. Having Navigraph updated at all places, the plane shows a message regarding Navigraph database when trying to display the destination airport to select the taxiway to vacate in order to get the BTV working. The funny thing is that the airport map is shown in the departing airport, but never in the arriving one. - Autobrake mode selector is broken. There are two parts in that selector, one for the runway condition and another one for braking intensity. No matter which one I choose, it will always react to runway condition, so braking intensity is impossible to be selected. In this sense, autobrake without BTV is always medium. - Autolanding is just not here. The plane is unable to do a correct flare and crashes into the runway during the autoland. Is urgent to solve this because, as you know, we sometimes have to land with very low visibility and we want to want to avoid neck and spine problems to our passengers. - Beacon light still removes chokes and external power when turning it on, which makes no sense and it is completely unrealistic. This bug (or "feature"?) should be removed asap. [FLIGHT MODEL] - Plane still takes off too easily. It even rotate unitentionally before giving it any input from the joystick just because is light or the trim configuration that the plane itself gives is incorrect. - Flight model while flying manually is bad after rotation. The plane tends to respond in a very unsolid manner as soon as it rotates, as I try to reach 15 degrees of pitch on takeoff (with good speed), moving the nose up and down slightly, something that should not happen. It reminds me of what Headwind's Boeing 787 did before the update that mostly solved this, but of course that product was and is free. - The reaction to joystick inputs on final approach is a little bit too sensitive and the aircraft, in my opinion, overreacts a bit. Considering how big and heavy it is, the movements should be a bit smoother, which also helps to improve the accuracy of the approach. - More or less in the same way as above, something similar happens during taxiing. The aircraft reacts too immediately and too quickly in turns. I think it should feel a bit heavier, and be more "lazy" and lagging when interpreting inputs during turns on the ground. - Weird reaction to speedbrakes when the plane is over the path of descent. It is Airbus logic to try to reach the path back when you are over it, but this planes do it too abruptly, specially when speedbrakes are deployed to help it. This have to refined. [EXTERIOR] - Still bad lighting regarding windows at night from the outside. The cabin should be completely illuminated while on ground (before departing and after arriving) with systems on and enough power. In general, lighting should have phases according to the phase of the flight, as other MSFS2020 have, but this is not the case in this plane. This is all I can gather for now. If I find or remember anything else I'll leave it here as a reply. I encourage all of you who have more bugs and glitches in version 1.0.1 to report them here as well so that the iniBuilds team can have as much feedback as possible together in one post. And this goes out to the iniBuilds team: the plane has huge potential and a lot of good things, but it's still just a good beta. Please, urgently fix in the next few hours or days at least everything that's reported in this post. Other minor tweaks may come with future updates, but all of this I've mentioned is necessary in order to consider this plane as a complete initial product. Nothing else to add. Best, Alvaro.

The configuration was correct, and I didn't change it from previous flights, but thanks for your help! 😄

I'll give it a try asap to see what of the described issues have been solved and what not. Thanks!

This is the MSFS 2020 version forum because is the simulator I have. And I think I have 100% realism too.

In my case I used GSX pushback but no damaged gear alert was displayed. Also, I used GSX pushback as well on two flights with A350-900 and this didn't happen, so I think bugs' behaviour are random, which is annoying. Also, I reverse thrust didn't work in the first flight but it worked in the second and third (the cancelled one, but I tried it) without any configuration change, which is also weird. And also nm to the ILS were shown in the second flight, while in the first one they didn't. SO I guess there is a lot of uncertainty on wether bugs will ruin or not a flight, which is pretty annoying. All these issues described in this thread should be addressed in a matter of days, if not hours, with an urgent update by the @iniBuilds @iniBuilds Team.

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 😕

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.

I don't have FSRealistic so that's something about the plane.

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.

Thanks for the info!

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.

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.

Hi. I am currently doing my first flight with the A350 in MSFS 2020 but no contrails are shown flying at FL380 and with TAT -31 ºC. I attach a photo. Why could this be possible? Thank you 🙂