The A340 and A350 by iniBuilds are much better than the default A330, which still has several issues and could be so much better if Microsoft allowed iniBuilds to put all of their expertise behind it.
Please either ask iniBuilds to bring the A330 up to this standard, or allow them to release a premium version for purchase on their own.
Yeah we don’t need unfinished new local legends, famous fliers etc.
Current fleet is more than enough but most of the planes needs some love. A330 is a great plane and please let inibuilds improve it like engine blade animations, terrain radar etc
I’d love some improvements to the default A330 to be up to the standard of the A340.
This would be so awesome. MSFS should have at least one default aircraft that is truly payware-level. The ini A330 would be a perfect candidate.
That is what the A310 is.
My dream we want a330 study level
I would love (and absolutely pay for) an A330 at the level of the ini A340.
Well according to Jorg as per dev stream there is something like 70-90 aircraft being updated and fixed for SU4.
So we will see if this includes the A330 and the rest of the Inibuilds default fleet. Nothing in any beta builds so far, so unsure if we get to test these fixes or if they will just dump it all on us for the release candidate
A bit off topic but I just had to stop and say that this is pretty much a false impression.
Microsoft does not gatekeep iniBuilds here - just take a look at the Grumman Albatross discussion to find out that the developers of course are allowed to just improve their aircraft if they want to (Mike basically added new variants with drop tanks, an anchor and an old school cockpit variant to the existing aircraft without Microsoft stepping up to stop him. He even released a paintkit on flightsim.to)
I know that iniBuilds likes to point at Microsoft when it comes down to community wishes, but I think it’s more saying “ask Microsoft to place the order so we can create an invoice”. Not much more, but it doesn’t sound as nice as “ask Microsoft to add the feature. They have to decide.” 
For paintkits it’s IMHO the same story - ini releases paintkits for their own paid products on their own forums but not for the default aircraft. Why? Well, so you have to download their repaints through their manager (in which case there also is no plain white one…). So you have to create an account. So you may buy their products as you already have an account and the manager installed
I don’t blame them to do that but their way to communicate this is a bit shady. If other developers are free to add features to the default aircraft there is basically no restriction on them. If the changes needed are too time consuming to make as part of the usual maintenance within the existing contract it would be better to tell that.
Just my two cents.
I don’t think they gonna be part of the Beta. On Beta versions before the aircraft fixes outside of Working Titles and Asobos work were not part of the testing. Carenado, Nemeth, BlueMesh and iniBuilds fixes will most likely be part of the final release.
Not just asking for bug fixes here.
Ok, well consider this a request for Microsoft to allow iniBuilds to issue them an invoice then. If that’s what it takes. Or in, iBuilds can release a paid upgrade themselves
Would be nice if iniBuilds could sort out the 340 and 350 that we have paid for as a priority before making new aircraft like a premium 330.
agreed 
this would be nice.
I’m another in agreement with this. Let IniBuilds have full control over the A330 for better development and refinement.
I wish they can update their A330 like adding wing registrations, PW engines, and SATCOM or WiFi dome as most A330 operators have them.
I’d also like to add my vote to this. Please Microsoft/Asobo look at the great Inibuilds A340-300 and consider to order an updaten A330 from them. It should include more features and maybe even the PW engine variant. It could be sold in the marketplace for a small upgrade price.
Agree, a more refined A330 is the need of the hour. I especially wish to fly both the classic EIS1 A330’s, the mid MSN A330’s with 230-233t MTOW and the later build A330 Enhanced versions with the center wing tank activated. Also PW engine option too.
I’ve been experiencing WASM freezes with the A300, A310, and the A330 not only when trying to modify the STAR, but also when manually entering pilot-defined waypoints using coordinates or relative references into the MCDU, for example: XXXXX/046/12 (a new waypoint 12 nm away from XXXXX on a 046° bearing).
And even if the MCDU survives such an entry without freezing, the flight plan often gets scrambled, which is also visible on the ND where the route path becomes inconsistent or jumps around.
I don’t think I’m asking for too much “system depth,” because:
A) This is, in my opinion, basic functionality that should be part of any MCDU,
and more importantly
B) Inibuilds actually provides these features in the MCDU interface, so if they’re implemented, I think it’s reasonable to expect them to work without major bugs.
It’s honestly a real shame, because overall I really like Inibuilds’ products, they’re well modelled and enjoyable to fly. I’d switch to the fanboy camp in a heartbeat if they could finally get this part right.
I’d be fine with a premium version that comes at an extra cost, if that’s what it takes to get these systems working reliably.
There were changes to the A330 and other ini aircraft in the SU3 beta.
So that’s not entirely true, changes to the ini aircraft can show up on betas.