10 minutes ago, JYW said:

...

But as said above, the weakest point for me was the sound.   Ini really need to get a better sound developer. This suffers from all the same weaknesses - sound wise - as the A300.   The engine sounds (from in the cockpit) are really, really, poor.   This sound weakness will really hold ini back, as the issue migrates from one plane to the next.

...

The sound (particularly on the flightdeck) is one of the biggest immersion factors for me.  Without decent or convincing sound, the experience tends to be a little thin.  

People seem to forget the beta they released first time around before being pulled was a few months out of date. Not sure if the same thing has been done.

6 minutes ago, carlanthony24 said:

People seem to forget the beta they released first time around before being pulled was a few months out of date. Not sure if the same thing has been done.

I can't think of any reason why they'd deliberately put an old version out to beta.   The purpose of beta would be for beta testers to test their potential release candidate, ready for next Tuesday's SU15 launch.

I really wish that was the case - because it's not in good shape at the moment - but I can't see it.

Did a take off flew a bit, ended the flight, and deleted/uninstalled…

Went back and flew the 182RG down to Punta Gorda from Tampa - much funner!

9 minutes ago, JYW said:

I can't think of any reason why they'd deliberately put an old version out to beta.   The purpose of beta would be for beta testers to test their potential release candidate, ready for next Tuesday's SU15 launch.

I really wish that was the case - because it's not in good shape at the moment - but I can't see it.

They did just that when it first came into beta. It said in airport data that it was an alpha build and it was a few months out of date something like that. Purely down to how long it takes to get through microsoft testing I believe was the reason Ini did say, same reason it takes so long for PMDG products to get through.

Edited March 23, 20242 yr by carlanthony24

52 minutes ago, Fiorentoni said:

The A300 was bugged on release

Not for me. I did several flights with the launch version with no issues.

You have to remember not everyone was effected by some of the bugs. That's why they took so long to nail them down.

  

50 minutes ago, Fiorentoni said:

The A310 as of now (SU14) doesn't even work anymore but crashes on loading (from what I've heard).

I was talking about at release. You even said that word in the post I quoted.

Edited March 23, 20242 yr by Tuskin38

3 hours ago, jcomm said:

You mean... graphically wise, right?

Yes.

7 minutes ago, carlanthony24 said:

and it was a few months out of date

It was a week, not months.

7 hours ago, omarsmak30 said:

MCDU freezing is really a critical bug, I didn't even do anything (just selected the runway) and the plane is dead 🤔. 

These are issues they're having with the A300 - MCDU crashes, Simbrief import crashing the box, fall out of the sky, and CTDs, so unsurprising the A320 which probably shares the same base code for a lot of things is running into the same issues.

25 minutes ago, Tuskin38 said:

I was talking about at release. You even said that word in the post I quoted

You're right, my bad. The A310 was alright on release.

55 minutes ago, mspencer said:

These are issues they're having with the A300 - MCDU crashes, Simbrief import crashing the box, fall out of the sky, and CTDs, so unsurprising the A320 which probably shares the same base code for a lot of things is running into the same issues.

Really???! I mean I don't care about their A320Neo (God bless FBW) but I feel sorry in advance for the A350 which most likely will have the same garbage 

41 minutes ago, Fiorentoni said:

You're right, my bad. The A310 was alright on release.

Honestly the A310 is actually okay not bad, I fly it often. It had some issues in SU14 but in 15Beta, actually works with no issues (at least for me) but of course the obvious bugs like the VNAV is sometimes a bit off but got used to it

1 hour ago, Tuskin38 said:

It was a week, not months.

Not sure but from what I remember being said it was longer than that since the version number was way out also.

2 hours ago, JYW said:

I had a 'A320 fest' today, flying short legs in the Fenix, FBW and the INI A320.

Order of greatness

1. Fenix A320

2. FBW A320 NEO

3. Ini A320 NEO

.....no real surprise there.  I did find the INI was... ok... not terrible.  I do actually like their cockpit textures... maybe even a little more than the Fenix. 

But as said above, the weakest point for me was the sound.   Ini really need to get a better sound developer. This suffers from all the same weaknesses - sound wise - as the A300.   The engine sounds (from in the cockpit) are really, really, poor.   This sound weakness will really hold ini back, as the issue migrates from one plane to the next.

The only other real issue I had was with the wonky VNAV and poor speed management, as covered by others above.

For Xbox users it has it's place.  But on PC would I ever choose to fly it, above the Fenix or FBW?   ...doubtful.

I did exactly the same thing today with exactly the same results and rankings, except…I had forgotten just how GOOD the FBW is. Their EFB sets the bar for all who follow. 
-B

iniBuilds is really hurting their reputation by releasing something like this. Not a good look.