A350 iniBuilds - catastrophic release as never seen before

[LRBS]

57 minutes ago, lwt1971 said:

Such is the way in the current world of software
 

Some people have a problem with this. Instead of evolving and striving for the better, we tend to accept the wrong direction. 

58 minutes ago, lwt1971 said:

 if a user buys blindly on release day and then complains about bugs then that's the user's problem IMO. 

When developers make such lofty claims (I'm speaking in general) about their product, and customers find out that it was just a sales gimmick, I can't see this as a user problem. 

 

 

I understand that customers have varying levels of knowledge and expectations. However, it is poor practice to release something with so many bugs in the hope that a few will not notice. Where is the pride and expertise of the programmers?

 

I believe we're at fault for not expressing our dissatisfaction and for enabling this situation enough.

[RJC68]

Sorry, no issues here, at least 10 flights of around 2 to 3 hours duration and a 15 hour flight, none of which with a single crash.

Edited March 10 by RJC68

[Simon_C]

4 minutes ago, mpo910 said:

Enormous pressure on the devs who need to fix asap....(they released the first 2 updates in just one week! and the bug-fix list was huge.....is that ALL tested well? hmmmmm....

Customer support already written several times they slept less and monitor support forums almost 24/7!!! Due the issues.....thats as shame they need to work this way BECAUSE the delivery was not good (that COULD raise stress-level within the inibuilds company as well.....FULLY home made issues and NOT needed at all)

And this is how you ruin the company.

[lwt1971]

3 minutes ago, Simon_C said:

My tolerance for bugs is very high, if I adopt early. Which I did. And I tolerate every bug in the A350.

 

I do not tolerate advertised but missing or not working features. And these are not bugs.

Great, well do what you must to vent/voice your intolerance for missing or not-working features despite not wanting to wait and finding what was missing vs not, what was working vs not 🙂 🤷‍♂️
 

[mpo910]

1 minute ago, RJC68 said:

Sorry, no issues here, at least 10 flights of around 2 to 3 hours duration and a 15 hour flight, none of which with a single crash.

Thanks for sharing. Did you use TCAS on and injected traffic? I have read TCAS is one of the reasons people have freezing gauges...

 

[Simon_C]

1 minute ago, mpo910 said:

Thanks for sharing. Did you use TCAS on and injected traffic? I have read TCAS is one of the reasons people have freezing gauges...

TCAS... as in, being on, not standby?

[mpo910]

3 minutes ago, LRBS said:

I believe we're at fault for not expressing our dissatisfaction and for enabling this situation enough.

🙂

Indeed...that is way I decided to share my thoughts and experiences with this one here.

And I do not expect others to be on my side....but to communicate...and share...

 

[mpo910]

2 minutes ago, Simon_C said:

TCAS... as in, being on, not standby?

I have read they suggest to leave it completely off in the KCCU (FMS - SURV Page - OFF).

That is a work around for one of the freeze reasons.

Edited March 10 by mpo910

[Farlis]

6 hours ago, mpo910 said:

, because we paid almost EUR 80 for this "state of release".

You mean 90€. After exchange rate and taxes that 89.99 was the price I paid. That's a higher price than a PMDG aircraft.

Let that sink in for what you get.

Edited March 10 by Farlis

[LRBS]

25 minutes ago, lwt1971 said:

t's up to the user to believe them or not..
 

I'm sorry, that's such a ridiculous statement. Should we not trust them now? 

When a software is full of bugs, and they claim to be such a good software that's misleading the customer for a quick profit.  

[Farlis]

5 hours ago, Ricardo41 said:

Nobody is forcing anyone to buy this on release day. 

Wait 6 months or longer until the bugs are fixed. 

So are we at that point in software development now were we have to simply by default wait half a year until a software product is polished after release and simply stop buying upon release?

This is ridiculous.

[Simon_C]

8 minutes ago, mpo910 said:

I have read they suggest to leave it completely off in the KCCU (FMS - SURV Page - OFF).

Mmmm yeah, right... no, I always have it on, since I did pay €90 for one of the most expensive addons ever (does not top FSLabs A320 in P3D, which was I think about €150, however that was also commercial sim). And it IS a mostly used feature, even by youtubers who tested the aircraft.

5 minutes ago, Farlis said:

Let that sink in for what you get.

Sinking is a good word 😄

Edited March 10 by Simon_C

[mpo910]

1 minute ago, Farlis said:

You mean 90€. After exchange rate and taxes that 89.99 was the price I paid. That's a higher price than a PMDG aircraft.

Let that sink in for what you get.

inibuilds knew their product would sell well as they are the first to release a A350. 

And I know how they deliver their praised high level of detail product...

That is settled down now....and next time they need to wait a bit more for my money.....just to be sure I do not ealry adopt so many issues 😉 

[lwt1971]

2 minutes ago, LRBS said:

I'm sorry, that's such a ridiculous statement. Should we not trust them now? 

When a software is full of bugs, and they claim to be such a good software that's misleading the customer for a quick profit.  

In order to ensure that an add-on or sim platform meets the level of quality *you* seek, best to wait rather than buy blindly on release day or the initial early days isn't it?. Otherwise yes, you are completely going on the words of the developer aren't you? What the developer considers sufficient release quality for initial release may or may not be the same as what you seek.

Do you have the ini A350 btw?
 

[mpo910]

2 minutes ago, Farlis said:

So are we at that point in software development now were we have to simply by default wait half a year until a software product is polished after release and simply stop buying upon release?

LoL

Seems so....and as EVERYONE will wait six months and the company delivered "bad quality" six months ago.....those bugs need another 6 months till discovered and fixed....so it is a good suggestion to wait one year LoL (irony off again).

No of course that what he suggested or stated is not the way to go...

At least not for me. But use forums like this and on their own website CAN help a liitle bit. We need to use our possibility to communicate and if needed to raise pressure this way.

BUT: Always respectful! 

Most of the time it is NOT a developer (role) issue.....but the SALES who ad pressure and  make strange decisions about release dates.....and lots of devs are not in a role to decide WITH sales.....sales often rules....TOP DOWN.

And yes....that way you ruin a company in long term. As people at development and customer support are getting the "worse" feedback and pressure to fix....now even in a shorter period as normally would be done...

IniBuilds has grown very very fast.....what we see here is totally clear where this comes from.....the processes and structures aren´t alligned with the company size and market size yet....that needs time and inibuilds needs to reflect that.