The wind uplink to the FMGS isn't working - it just comes up with zeros everywhere. Is this a bug or something I'm doing wrong?

Unfortunately it reports "ERROR" like the serial (which I've copied from the Aerosoft One through the dedicated button) doesn't work.

I've opened a ticked in the system (no reply yet); do you know if there is a fix/walk around to enjoy the plane?

Thanks in advance for your support

I do love this bird and with the updates it's progressing nicely. This is very much a Toliss thing but can you please stop the interconnection between the ACPs? Selecting the volume or other controls on one ACP does not change the settings on the other ACPs in the real aircraft. It's really amateurish, default aircraft fare that sort of thing. Toliss' aircraft in Xplane do it and it's really naff.

Cheers all

This one is using original msfs camara.

This one is using chaseplane.

the new WINCTRL RMP panel is not working with the A340-600.

When will this be the case?

Thanks & BR

However, the current 3D model doesn't have ADF antennas. I’ve heard that Aerosoft is updating the 3D model, and it would be great if they could include ADF antennas (preferably with an option to select the number of ADF antennas to match the real aircraft).

I thought it was a wasm problem, but that does not do anything.

Anyone else has the same problem and knew how to fix it permanently.

It takes sometime more than 20 minutes to get the plane decent on the ground. (If I didn't decide to take another plane who works flawless or the simulator crashes before I solved it, when I use this plane. But that is a different problem :-) )

Absolut terrible

Thankfully I was able to get through the activation failure by clearing the WASM folder, but this then means that throttle calibrations need to be redone, Navigraph logins re-authenticated etc.

There must be a better way, in fact we know there is, other addons don't have to go through this laborious process during updates.

On every single flight I fly, the TLR VREF and the MCDU VLS don't match. It's not an occasional glitch, it happens consistently. I'm attaching two screenshots from one representative flight (EDDF-OERK) that illustrate this clearly, but the same pattern shows up every time.

Screenshot 1 (EFB - Landing Performance page):

• LW (T) = 229.0t

• Weight Variant set to Standard (not HGW) — this matches the aircraft profile I use in SimBrief, which is also set to Standard

• EFB computes VAPP = 147kt

Screenshot 2 (MCDU - PERF APPR page, same moment, same flight):

• Landing conf selected: FULL

• FMGC VLS = 142kt

The EFB's own math checks out internally: 142 (VLS) + 5 (wind correction) = 147 (VAPP shown). So the EFB is being consistent with itself.

The problem is the TLR. Cross-referencing the TLR's landing distance table (visible in the screenshots) for LDW 2280 (i.e. 228.0t, closest bracket to the 229.0t landing weight used), the VREF listed is 148kt. That's a 6kt gap against the FMGC VLS of 142kt for what should be the same landing configuration and weight.

This isn't a one-off - I've seen the same pattern on every flight I've logged, with the gap ranging roughly 4-8 kt (TLR VREF always higher than FMGC VLS, never the other way round). For comparison, on the Fenix A320 I fly regularly, TLR VREF and FMGC VLS are generally very close (within a knot or so) - nothing like the consistent multi-knot gap I'm seeing on the A346.

What I'm trying to figure out:
I honestly don't know which value is "correct" here, and I don't expect this forum to be able to verify SimBrief's internal TLR calculation. So rather than asking "which one is a bug," I'm curious about the practical side:

• For those of you flying the A346 regularly - has anyone else noticed the TLR VREF and FMGC VLS not matching like this?

• And if so, which value do you actually trust and use for VAPP?

Screenshots attached for reference. Happy to share more data points from other flights if useful.

Setup info:

• Sim: MSFS2024 Sim Update 5.1

• Aircraft version: v1.0.4 (but same behavior observed since v1.0.0)

• This happens regardless of arrival airport or landing weight.

Thanks!

Today I had the same problem but activating gives an error. Maybe I exceeded the number of activations but activating everytime was annoying but this error keeps me from using the plane.

Anyone has a solution for this problem?

I have reinstalled the A340-600 twice with a fully cleared WASM folder, I have reinstalled my simulator and I am running the latest GPU drivers and windows 11 version. I have exhausted all the options I can think of by myself. 

I have attached comparison screenshots: the ToLiss A346 panel shows the incorrectly illuminated switch (marked with a red arrow), while reference photos from the real aircraft show the unlit switch (marked with green arrows).

Thank you for your amazing work on this aircraft, hope this helps to make it even more accurate!

• The logo lighting is faulty. It’s supposed to switch on automatically with the navigation lights and when the gear is down, but it stays off.

• Cabin lighting is faulty from the ECO section of the cabin onwards. Well, they’re paying too little; the neon tubes have probably been removed as a cost-saving measure.

• The emergency exit signs aren’t lit.

• Have we somehow lost the seatbelt and no smoking signs?

• CTD when using the taxi cam if it’s dark outside (Video on request).

You will need to uninstall the aircraft through Aerosoft One and then reinstall by choosing Install Experimental Release in your library.

The downgrade is also available to Contrail users.

I would like to say that when on VATSIM and using Vpilot (MSFS2024, v. 1.0.3 of the aircraft) pressing Ident on the TCAS/ATC panel in the pedestal, does not activate the relevant button on Vpilot. Is this a bug?

Thank you,

Sorry! I saw now that it seems to work. Just needed bigger clouds obviously. So I can enjoy my favorite aircraft even more.

Only thing missing: WINCTRL RMP not working yet. Other WINCTRL peripherals work.

I am running MSFS 2024 latest version with updated aerosoft A340, I also use chaseplane.

1. If I zoom out too much the aircraft sounds cut out. I can still hear wind noise. In the Virtual cockpit.

2. Would it be possible to have the route download option with out the INIT A or INIT B info download - so just the route.

3. Can you have the BARO sync between CAPT and FO but make the STBY independent.

4. Option to sync the two EFISs / FDs / LS buttons.

Thank you again for a great product!

Cheers,

Anyone knows how to fix this. It did work in the past