Source:

'The A340 Airliner v1.0.10 update focuses on improving operational accuracy and refining several core aircraft systems, with a range of fixes across flight guidance, FMGS behaviour, MCDU functionality, and navigation handling. Updates address issues affecting waypoint selection, fuel flow logic, datalink messaging, and various flight deck indications, helping ensure smoother and more consistent day-to-day operations.

This update also includes improvements to ground handling integration and visual corrections to the aircraft model, alongside an audio pass restoring missing cockpit interaction sounds and refining cabin ambience, with the addition of a new noise-cancelling option within the EFB.

This update can be downloaded via the iniManager.

V1.0.10
SYSTEMS ⚙️
FIXED Flight director movement on departure refined
FIXED Reference thrust indication changes to climb thrust on lifts off
FIXED Company Message memo on despite all messages viewed
FIXED Cannot delete or modify OPT step properly
FIXED Issue with SEC FLT PLN interaction
FIXED Inability to display an NDB on the FIX INFO page
FIXED DDRMI compass card should also show TRUE heading when selected
FIXED MCDU Datalink status page
FIXED Negative EFOB values overflowing off screen
FIXED GND CTL pushbutton on the overhead panel stays illuminated for too long
FIXED Use default radio frequencies on load (122.80/121.50)
FIXED WX messages can't be deleted from ATC Message log
FIXED Font sizing issue on Route RSV
FIXED PFD speed bug flicker with manual vAPP speed
FIXED Fuel flow is immediate, even before start valve opens.
FIXED EIS1 setting auto trim value
FIXED Waypoint selection screen not showing for duplicate station when manually entered

ART 🎨
FIXED Nosewheel floating above ground-contact point incorrect

EFB📱
FIXED GSX boarding values now match planned weights

SOUNDS🔊
FIXED ACU sounds in cabin
FIXED Space Key on MCDU(s) has no CLICK Sound
ADDED Added noise cancelling option in EFB

iniBuilds Team ❤️'

Edited March 6Mar 6 by MrLamb

Thank you for the update.

I’ll give it a try. The A340 remains one of most favorite Airbus airliners in MSFS.

Already downloaded. Install and flying it right now VHHH/RJAA.  Love the plane so much but the MCDU screen still continues to randomly freeze (buttons continue to work) and that is all on ini. It seems it has to do with the instrument popup panels and ini grouping multiple instruments into one panel as opposed to a one to one ratio. One to one is how Fenix and FSLabs code their planes. Fenix and FSLabs have full and flawless integration with WinCTRL(winwing) devices including their MCDU, FCU and EFIS.  Ini?  Eh…not so much.

I have pretty much every aircraft Ini has produced.  Many of their sceneries.  I am a loyal and valuable customer who just wants to enjoy his wonderful iniBuilds a340-300 with systems that work 100% as much as possible.  Five 9’s as they say.

Ini needs to up their game on this.  It is frequently discussed on their chat and support forums. This screen freeze is darn near guaranteed if you fly the plane with WinCTRL gear and software.  Ini needs to own this, or at least acknowledge its existence and provide an owner of the flaw, Ini or WinCTRL. And yes, I have raised these same topics on the above mentioned chat and support forums.  Deaf ears for the most part.

Respectfully,

-B

Edited March 7Mar 7 by btacon

17 minutes ago, btacon said:

 It seems it has to do with the instrument popup panels and ini grouping multiple instruments into one panel as opposed to a one to one ratio...

The drawing of the displays has literally nothing to do with the variables the plane sends to SimAppPro. 

Is that so.  How?

Edited March 7Mar 7 by btacon

Definitely adding this to the hangar. 

Still no separate pop out displays? It's unfortunately a dealbreaker for me. 😒

V1.0.10 not yet available on the marketplace, only v1.0.9 is available.

Edited March 7Mar 7 by Avance

If I have the Fenix and the A350 what gap would this fill? Considering getting it as well

1 hour ago, Avance said:

V1.0.10 not yet available on the marketplace, only v1.0.9 is available.

Thanks I was going to ask that.  I hadn’t been given a reason previous to migrate my purchase over to the Inibuilds store, but here it is.

I did SCEL-LEMD yesterday (at 4x speed), and it flew fine, no issues.

12 hours ago, btacon said:

Already downloaded. Install and flying it right now VHHH/RJAA.  Love the plane so much but the MCDU screen still continues to randomly freeze (buttons continue to work) and that is all on ini. It seems it has to do with the instrument popup panels and ini grouping multiple instruments into one panel as opposed to a one to one ratio. One to one is how Fenix and FSLabs code their planes. Fenix and FSLabs have full and flawless integration with WinCTRL(winwing) devices including their MCDU, FCU and EFIS.  Ini?  Eh…not so much.

I have pretty much every aircraft Ini has produced.  Many of their sceneries.  I am a loyal and valuable customer who just wants to enjoy his wonderful iniBuilds a340-300 with systems that work 100% as much as possible.  Five 9’s as they say.

Ini needs to up their game on this.  It is frequently discussed on their chat and support forums. This screen freeze is darn near guaranteed if you fly the plane with WinCTRL gear and software.  Ini needs to own this, or at least acknowledge its existence and provide an owner of the flaw, Ini or WinCTRL. And yes, I have raised these same topics on the above mentioned chat and support forums.  Deaf ears for the most part.

Respectfully,

-B

I have to agree. I love this plane, but I hate the way that they grouped all instruments into 1 panel. It should be individual pop outs. I submitted a ticket about this matter, but they will not change. So I've hangered the A340 and will be skeptical on my next Ini aircraft purchase. I'll wait and see what Tolis/Aerosoft has to offer/

Hi:

We should always keep one distinction in mind.

Among the premier developers of our (MSFS) SIM today, only PMDG and iniBuilds have subjected their development (and validation) process to the inherent constraints of the standard MSFS software architecture and Marketplace installation paradigm.

Fenix and FSLabs rely on their own external applications that run independently, but alongside the simulator. I do not know we’ll ever see their products in the Marketplace, and that’s a pity.

It’s not that iniBuilds still cannot (should not) match such refinements of Fenix and FSLabs, but it’s not a fair comparison. There is always more flexibility in proprietary solutions.

With that said, having never adopted XP, the last time I flew an A340 in the SIM (an airplane that’s dear to me), that too a barely acceptable version of it, was from Wilco feelThere decades ago. So, this one here stands apart from that minimal rendition, and I’m appreciative and much grateful. 

Of course, I look forward to continuous updates and improvements of this A343.

The standard A343 has never frozen in my many flights with it, but just once with the A340 VIP edition.

Edited March 7Mar 7 by P_7878

14 hours ago, Stavros said:

The drawing of the displays has literally nothing to do with the variables the plane sends to SimAppPro. 

Thank you Stavros for an opportunity to retract my incorrect theory of root cause.  I have been more fully informed by ini and feel far more hopeful for a quick resolution.  Blue skies,

-B

3 hours ago, Shomron said:

If I have the Fenix and the A350 what gap would this fill? Considering getting it as well

The A340-300 is an older Airbus.

It´s a longhaul Aircraft, but can be used on high density routes, just like the A350, which represents the most modern generation of Airbusses.

The A340-300 cockpit looks and works very much like the Fenix A320 CEO.