A350 AFTER patch v1.0.1 - Discovered ISSUES so far [MSFS2020]

[Alvariteus]

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.

 

Edited March 3 by Alvariteus

[Speedbird721B]

Alvaro,

I like the idea of this post, but I think you need to investigate a little before reporting all of these as bugs or issues. I have no problems with contrails in 2020. The rain effect when wiping has been removed, but I believe ini have said they are working on implementing that. I don't have any issues with my AP Disconnect Sound. I press the Disconnect Button on my hardware twice and have never had problems. Are you sure the screen response is bad? Sometimes I need to click the screen once or twice for it to receive the input, but if you have your cursor on another screen, say the MailBox, and are trying to change MFD Settings, the cursor will need to jump to the MFD, resulting in a slight delay. Clicking which screen you want on the KCCU before inputting may help. The Beacon Light removing GPU can be changed in the OIS. Are you using the recommended Sensitivity Settings? I'm not saying the aircraft is perfect, and you raise a lot of valid points, but reading the manual, Discord, and this Forum can help with some of your issues. Fixes are coming.

[Alvariteus]

1 hour ago, Speedbird721B said:

Alvaro,

I like the idea of this post, but I think you need to investigate a little before reporting all of these as bugs or issues. I have no problems with contrails in 2020. The rain effect when wiping has been removed, but I believe ini have said they are working on implementing that. I don't have any issues with my AP Disconnect Sound. I press the Disconnect Button on my hardware twice and have never had problems. Are you sure the screen response is bad? Sometimes I need to click the screen once or twice for it to receive the input, but if you have your cursor on another screen, say the MailBox, and are trying to change MFD Settings, the cursor will need to jump to the MFD, resulting in a slight delay. Clicking which screen you want on the KCCU before inputting may help. The Beacon Light removing GPU can be changed in the OIS. Are you using the recommended Sensitivity Settings? I'm not saying the aircraft is perfect, and you raise a lot of valid points, but reading the manual, Discord, and this Forum can help with some of your issues. Fixes are coming.

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!

[Speedbird721B]

Alvariteus,

Yes, I know what you mean about removal. iniBuilds, to my knowledge, removed the effect you see, as they were not happy with it for the release version. It's being tweaked and should be added in a later version. 

Are you only pressing the AP Diconnect once? Binding a disconnect button to my hardware and then pressing it once and then again a second or two later cancels the sound.

Try to press and hold the TO Config Button for three seconds.

[Kevin Stein]

Hi Alvariteus, 

 

I must agree with you on a few of these points. 

The touchscreen can use some improvement and doesnt always click on the first try or the second occasionally. While most of the time it works, every 5th or so click you have to click twice which really interrupts the flow. 

I have also had some issues with the TO Config button as it occasionally fails to register but i think thats just the planes logic and if i press it shortly before take off after the plane has processed all the data it seems to work with a short press. But i may have just been lucky that one time, who knows. 

I have had no issues with the AP disconnect button sounds on my end and the sound stops after pressing the button twice as it should. But i did have some issues with the callout where the plane would call out the minimums and 100 above at the same time as the 300 and 200 callouts which i dont believe to be the case irl. The bang on rotation is also a bug i believe which is quite unpleasant. 

Flight model wise the plane could definetley use a rework as it feels way to sensitive and kinda like there is no yaw damper and the plane just kinda moves all over the place with even a very slight input. 

I have also had the screens fully freeze making me cancel a 16 hour flight on final which was quite frustrating... But this issue has been reported a lot and is surely being worked on. 

Other than that i can only think of the GSX cargo loaders not really being in the right place and also the GSX integration to be very confusing especially with the load page. Like do i have to set ZFW and request boarding or just one or the other??? Why are the passenger counts only up to 45 or so then just stops? Same with refueling... For now i just let GSX load without touching the Load page then once gsx is done i just load the aircraft then and set the weights. Seems to work best so far. 

 

 

[Alvariteus]

On 3/4/2025 at 12:43 AM, Speedbird721B said:

Alvariteus,

Yes, I know what you mean about removal. iniBuilds, to my knowledge, removed the effect you see, as they were not happy with it for the release version. It's being tweaked and should be added in a later version. 

Are you only pressing the AP Diconnect once? Binding a disconnect button to my hardware and then pressing it once and then again a second or two later cancels the sound.

Try to press and hold the TO Config Button for three seconds.

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!

[AndrasN]

On 3/4/2025 at 12:43 AM, Speedbird721B said:

Are you only pressing the AP Diconnect once? Binding a disconnect button to my hardware and then pressing it once and then again a second or two later cancels the sound.

 

Is the button you use to disconnect the autopilot properly (the red AUTOPILOT DISC button on the sidestick) is configured in the Controls Settings to AUTOPILOT OFF or AUTOPILOT ON/OFF (might be TOGGLE AUTOPILOT, I am not in front of the sim).

If you set  that hardware button to AUTOPILOT OFF then one press should be enough (as it is in the actual aircraft) and the warning will stop after 4 cycles (as it should). I am not sure this setting is mentioned in the manual, I have not checked it as I am using the same setup as Fenix and this method was clearly specified in the Fenix manual. 

[jaybird]

On 3/3/2025 at 12:59 PM, Speedbird721B said:

Alvaro,

I like the idea of this post, but I think you need to investigate a little before reporting all of these as bugs or issues. I have no problems with contrails in 2020. The rain effect when wiping has been removed, but I believe ini have said they are working on implementing that. I don't have any issues with my AP Disconnect Sound. I press the Disconnect Button on my hardware twice and have never had problems. Are you sure the screen response is bad? Sometimes I need to click the screen once or twice for it to receive the input, but if you have your cursor on another screen, say the MailBox, and are trying to change MFD Settings, the cursor will need to jump to the MFD, resulting in a slight delay. Clicking which screen you want on the KCCU before inputting may help. The Beacon Light removing GPU can be changed in the OIS. Are you using the recommended Sensitivity Settings? I'm not saying the aircraft is perfect, and you raise a lot of valid points, but reading the manual, Discord, and this Forum can help with some of your issues. Fixes are coming.

There's enough false/mistaken reporting in these forums, just report your problems to Inibuilds, we don't need some intermediary...

[Alvariteus]

5 minutes ago, jaybird said:

There's enough false/mistaken reporting in these forums, just report your problems to Inibuilds, we don't need some intermediary...

This is the support forum.

[Alvariteus]

1 hour ago, AndrasN said:

Is the button you use to disconnect the autopilot properly (the red AUTOPILOT DISC button on the sidestick) is configured in the Controls Settings to AUTOPILOT OFF or AUTOPILOT ON/OFF (might be TOGGLE AUTOPILOT, I am not in front of the sim).

If you set  that hardware button to AUTOPILOT OFF then one press should be enough (as it is in the actual aircraft) and the warning will stop after 4 cycles (as it should). I am not sure this setting is mentioned in the manual, I have not checked it as I am using the same setup as Fenix and this method was clearly specified in the Fenix manual. 

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.

[Alvariteus]

On 3/5/2025 at 11:48 AM, AndrasN said:

Is the button you use to disconnect the autopilot properly (the red AUTOPILOT DISC button on the sidestick) is configured in the Controls Settings to AUTOPILOT OFF or AUTOPILOT ON/OFF (might be TOGGLE AUTOPILOT, I am not in front of the sim).

If you set  that hardware button to AUTOPILOT OFF then one press should be enough (as it is in the actual aircraft) and the warning will stop after 4 cycles (as it should). I am not sure this setting is mentioned in the manual, I have not checked it as I am using the same setup as Fenix and this method was clearly specified in the Fenix manual. 

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

[Martin Gavet]

I am still experiencing CTDs and have had to uninstall the A350 from MSFS despite redownloading the aircraft and clearing my WASM

[Marcocessna84]

56 minutes ago, Martin Gavet said:

I am still experiencing CTDs and have had to uninstall the A350 from MSFS despite redownloading the aircraft and clearing my WASM

Can you try to narrow the CTD down by looking into your Event viewer? This will pinpoint the actual cause. 

[Alvariteus]

On 3/3/2025 at 5:20 PM, Alvariteus said:

[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.

 

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.

 

[trisho0]

From MSFS2020, after the version 1.0.2 update the cabin still not modelled to see GSX pax seated. The A350 any model without the cabin is like flying a bird without feathers (lol). What about to copy/paste textures from A350 from MSFS2024. Is that possible? If so, any ideas or what files to pick?

Patricio Valdes

[balus]

17 hours ago, Alvariteus said:

 

 

- 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

 

 

Page 43 in the manual, turn off the AUTO GPU DISCO option.

I prefer it on, makes sense to me.

You may want to adjust your tone a little, you are coming across as demanding and agressive. You may or may not have some flight time, although I don't know how many hours are in an A350, but it is obvious that you aren't a programmer.

I've completed a dozen flights and I'm happy with the money spent, there are issues, yes, but I'm confident that they will be addressed.

Oh and I get more WASM problems with aircraft from another supplier that begins with P!

Edited Sunday at 05:40 AM by balus

[Alvariteus]

6 hours ago, balus said:

Page 43 in the manual, turn off the AUTO GPU DISCO option.

I prefer it on, makes sense to me.

You may want to adjust your tone a little, you are coming across as demanding and agressive. You may or may not have some flight time, although I don't know how many hours are in an A350, but it is obvious that you aren't a programmer.

I've completed a dozen flights and I'm happy with the money spent, there are issues, yes, but I'm confident that they will be addressed.

Oh and I get more WASM problems with aircraft from another supplier that begins with P!

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.

Edited Sunday at 11:47 AM by Alvariteus

[haza2]

Thank you for all of your feedback guys. Lets keep the chat friendly and constructive. A quote which is applicable here also from another team member.

 

It is a highly in-depth addon and we have a few WASM crash issues due to not everyone being on SU1 beta, and some complications with the Navigraph integration. These issues creeped in near the end of testing and as not present for the majority of testing. We are mostly stable now thanks to those who had certain issues reporting them clearly (all ones we did not see during testing). Its a complex aircraft and we aim to continue building on the great base we have to make this an even better addon. If you have specific, evidenced feedback or areas you do not like the best place to report these are on our forum where our team is looking at feedback, we will review and if its a bug it will be resolved. We are also planning some more dev streams to resolve some misconceptions and walk through some of the new technical elements we are adding. As mentioned above MORA and SND were added this week. Thank you for your business.

 

[nopixar]

6 hours ago, balus said:

Page 43 in the manual, turn off the AUTO GPU DISCO option.

I prefer it on, makes sense to me.

You may want to adjust your tone a little, you are coming across as demanding and agressive. You may or may not have some flight time, although I don't know how many hours are in an A350, but it is obvious that you aren't a programmer.

I've completed a dozen flights and I'm happy with the money spent, there are issues, yes, but I'm confident that they will be addressed.

Oh and I get more WASM problems with aircraft from another supplier that begins with P!

On the contrary. His post is absolutely brilliantly formatted and even opened with thank you to the Inibuilds team. Makes it easier to read and easier to see what’s been found/fixed. There was no need to you to add your happiness/what deem as money value to a bug post to compensate. There are hundreds maybe thousands of people out there happy with the captainsim 777. That’s brilliant for them. Enjoy your aircraft in peace and let people who have found bugs use the correct forum to bring them to the attention of the team. “Well it hasn’t happened to me” doesn’t mean that it’s not happening. A quick glance of the support forum/discord would’ve showed that. 
 

Well done to the poster for taking the time to format it I’m sure inbuilds appreciate the clarity, nothing worse than trying to trawl through random fluff to fix issues. 

[trisho0]

For the IniBuilds A350 with FS20 if no pax cabin then no flight, nothing to transport. The A350 not even for FSX sim and not even qualified for a Freighter model.

That's a shame!

 

Patricio Valdes

[balus]

10 hours ago, Alvariteus said:

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.

And yet you missed the first part of my post, the part that answered one of your complaints by simply reading the manual, you're welcome.

One of the problems with text based forums is that they are two dimensional and sometimes what one person considers friendly can come across as condescending and aggressive, especially when you demand 

" This bug (or"feature"?) should be removed asap. NOT YET TESTED "

your words, not mine.

Once again, you may want to consider your tone/approach.

Just as a suggestion, use ChatGPT or similar to rephrase the post in a friendly and formal manner, you might be surprised at the small changes made that affect how it may be interpreted by others.

 

Edited Sunday at 10:31 PM by balus

[Alvariteus]

3 hours ago, balus said:

And yet you missed the first part of my post, the part that answered one of your complaints by simply reading the manual, you're welcome.

One of the problems with text based forums is that they are two dimensional and sometimes what one person considers friendly can come across as condescending and aggressive, especially when you demand 

" This bug (or"feature"?) should be removed asap. NOT YET TESTED "

your words, not mine.

Once again, you may want to consider your tone/approach.

Just as a suggestion, use ChatGPT or similar to rephrase the post in a friendly and formal manner, you might be surprised at the small changes made that affect how it may be interpreted by others.

 

You are so funny.