All Activity

Other than the immersion of the fan blades now just at a stand still I have zero issues with the A350. Just praying for a fix!

I receive announce of pushback during take-off. 😒

Hi, thought this would be the best place to ask this question… I saw via email update that the iniBuilds A340 aircraft will soon be available to download on iniManager. Will it be possible to transfer A340 marketplace orders to iniManager using the transfer request at that time?

Same Issue here as well. Anyone know how to fix this?

I'm curious. I removed one of the "LIVERY_ALBD--" files (as one does) from one of the liveries from inimanager and I got some insight on I presume the "texture and modeling techniques to bring crisp textures and detail at even the closest distances" that were mentioned in the Paint Kit Manual. Something that I can't find anywhere is what determines the placement of these I suppose "blank" areas that get filled in with a decal or solid colour, any info about it in the manual, nor have I come across any third party liveries that use this technique either. Is there anywhere I can learn more about this? How someone can use this in their own livery, if these blank areas can be edited or removed after the fact on an existing livery etc?

Never mind the quality - first, we need fan blades that move that show the engines are working. This is a real immersion killer this now.

I install it, fly it. But it keeps showing up as not installed.

I just moved from X-plane 11 to X-plane 12 and downloaded the latest A300 for X-plane 12. This plane has some issues but I can´t see any support for this plane for X-plane in this forum. So is this plane no longer supported and abandoned?

True I got the a350 from inibuilds and there is a lot of lacks in quality I know the cabin thing but come on also someone in another form contacted inibuilds support and they said they were working on it

Hello, I just purchased the A350. I love this aircraft, but I thought the product was stable. First flight without any problems. Second flight: orange screens lit up (WASM)... and on the third and fourth flights: it was impossible to initiate a descent (T/D). If I engage vertical descent on autopilot... nothing happens, it maintains altitude. I fly the A320 (Fenix) regularly and don't encounter this problem. Can you help me with this T/D and autopilot issue? Maybe I'm missing something, but I don't understand why the autopilot doesn't respond when I switch to V/S manually.

Hey! To activate the alternate, you usually need to go to the F-PLN page, click on any waypoint in your active route (usually the top left LSK), and you should see an 'ENABLE ALTN' or 'ACTIVATE ALTN' option. Just a heads up - this will usually insert a discontinuity and then your alternate airport will appear at the bottom for you to set up the approach.

I deleted and reinstalled the plane but this message still appears, see photo. I can delete the WASM folder over and over again but the message persists. Is there any way to make the plane usable because at the moment it's just a waste for 69 euros?

you havn't stated that have you deleted your wasm folder after the last update, is the main reason for these type of issues

Hello, just approved your message. Did you get sorted?

I believe sound improvements are underway, but I really hope you'll make the gear operation sounds more realistic. This volume level is a defining characteristic of the A350. First, here's a reference sound for gear up. Next, here's a reference sound for gear down. The volume should be increased to the point where you might mistake it for a bug. Those who dislike loud sounds can simply adjust it in the settings. I just want the sounds to match reality. By the way, the timing for playing the gear drop sound during rotation is off again. I thought it was fixed for a while, but it's back to the original...

A340 releasing on ini manger on the 15th.

Also, to add: with the current configuration, it looks like the GSX VDGS screens conflict with the ones that come with the stock scenery. I experimented with this at gate 14, which gave me a purpleish looking number on the screen and info from what looks like the GSX screen. Scenery index clearing did nothing. Looks like there is some sort of issue with configuring this properly in the app.

Well it works 100% in FS24

Got to love the fact that I spend another 50 euro's on the compatible version and this is the support you can expect.

Doesn't look like there's any changes in 1.0.2 for this.

Looking for a solution too of this issue too. looking at this thread it is obvious that they don't care much. All other complex airliner I purchased work fine using controller in VR but not this one. More $$ to in the fire.

lol it works!

Hey @garett_09@aj_chugh Thank you for your report. That is unusual; based on the FROM/TO combinations I could identify from your screenshots, I haven't yet encountered similar issues. Nevertheless, please send us the Simbrief OFP PDF for the route where you're experiencing this problem. It could assist us in better reproducing and diagnosing the cause. You can find your OFP in PDF format on Simbrief Dispatch: This is OTHH-KLAX for example even with steps as computed by Simbrief, all automatically imported. So that is why we believe there has to be something specific in certain plans that may be causing it. OFP: OTHHKLAX_PDF_1767977506[1].pdf Thanks! OTHHKLAX_PDF_1767977506[1].pdf

Hi, Even after the 1.2.0 update, the accuracy of the flaps sound seemed not to have improved (or even worse). The suggestion was not being taken. And we still have the weird looping sound. With the current stability of the aircraft, I believe the team can start prioritising improving the immersive environment, including the passenger's perspective as well. Please consider this, even though it may further increase your workload. Thank you! (Same user coz I lost my ac)

Found the problem.. Parking brakes command on my joystick was also programed do shut down all engines.