All Activity

All of the improvements we made for performance have been applied to both the 2020 and 2024 versions of the aircraft. None of the changes we made for the sake of performance were 'only' applied to 2024.

1.1.8 2024 version receives NICE fps, meanwhile 2020 version still BAD.

Plane configured correctly, ECAM Memo green for take-off, after takeoff by engaging the AP the plane does a hard bank to the right and enters into stall and then crash as no controls are responsive.. the second time when it happens to me. For sure was not following the flight plan... by banking hard right.

IniBuilds. Please fix this issue!

At 13 mile final on the ILS to 22L at Helsinki, full flap was deployed once the ac slowed beyond the reqd speed. At a similar time a engaged APP as LOC was established. As I did this the auto-throttle disconnected (which I didn't notice as a VFE warning also came on), the aircraft lost speed and almost entered stall until the aircraft corrected itself. Speed indications stuck on the PFD at 120knts despite the ac accelarating as TOGA selected. Stby inst indicated increasing speed. Autopilot re-engaged (by me) then entered a side to side rocking motion before I decided to eject (lol). I've only had the 350 for a week and think it's good but clearly some issues still to sort.

And after loading into the last Autosave again it works again very very well.

Good Day, i´ve got an WASM crash during my cruise from RCTP to YBBN without doing anything or pressing something, just cruising. Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH WASM Error: WASM: Error -239 / ffffff11 WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) Specs: Intel Core i9-9900K, Nvidia GeForce RTX 4080 Super and 32GB Ram of your system. last autosave.bin

I've tried many flights with the v1.0.5 on SU4 and all of them result to a WASM Crash with the red gauges. I can't complete even a single flight. Most of the time when manipulating the MCDU for normal stuff. It's really annoying to start a flight and being stress about a crash at any Time. Until next update I won't reinstall the aircraft as it is just not playable. Hopping for a Hot Fix soon. Regards Quote

The developers are silent on the reports, that's all.

I have the same problem today rout RJAA-PHNL. I'm stopping flying this plane and switching to the PMDG. I've never had any problems with it, everything's great.

@iniSteven I've tried many flights with the v1.0.5 on SU4 and all of them result to a WASM Crash with the red gauges. I can't complete even a single flight. Most of the time when manipulating the MCDU for normal stuff. It's really annoying to start a flight and being stress about a crash at any Time. Until next update I won't reinstall the aircraft as it is just not playable. Hopping for a Hot Fix soon. Regards

Could be nice to get an answer from Ini here 🙂 Or at least get a reason why they don't want to implement it

Hello, I'm runing on Su4 with the 1.0.5 and I can't just play with the aircraft. Getting WASM crash at any time even when loading from the gate. Addon broken at this time, I won't reinstall until next update.

I don't understand why the MCDU don't load my flight. Simbrief is loaded.

After being accepted by OBBB I received the notification of current ATC unit. When I close it however, the current ATC unit is not displayed on the DCDU. I am on version 1.0.5. Shouldn't there be the text?: CURRENT ATC: OBBB BAHRAIN RDR

Same here today. This happens again and again and again. It's almost impossible to end a flight. It happens completely randomly. No other aircraft, such as the Fenix, Headwind 330, or the A320 Neo/A380 (fly-by-wire), have such problems, and they are significantly cheaper or even free!

Hello, try set beacons off then on after set strobes on. This works for my A340.

Now, if I was to take the wings from the latest paintkit models (V1.0.1) from here: https://forum.inibuilds.com/files/file/3322-inibuilds-a340-airliner-paintkit However, all the models are glitched and make the whole aircraft invisible. You can see they are invisible and none of the textures work properly when you change all the models to the latest paintkit models. Therefore, IniBuilds needs to update the paint kit models to correctly fix the models to show textures and the models. Most people probably missed the wings decals being an issue as they won't be looking at that when creating liveries.

If I was to take the wings from the latest paintkit models (V1.0.1) from here: https://forum.inibuilds.com/files/file/3322-inibuilds-a340-airliner-paintkit The wings work, however they don't display the nessercary decals. Such as there are not the wingwalker lines on the top, as well as stencils around the wing. Also to mention to the topic that there is no Under Wing Reg assigned to the wing. Therefore, it does not show....

So, I believe I found the issue to the problem.... I've been using the wing models from a IniBuilds livery (let's say the Virgin Atlantic one, doesn't matter which specifically), however the IniBuilds liveries models do not use the A343_WINGREG_ALBD.PNG file, as the under wing registration is from the LIVERY_ALBD.PNG file (or whatever it uses). I reverted back to the old wings from the first release (V1.0.0) and found that everything works fine, however, as expected, the decals on the top of the wings and around certain areas are not correct as it's not using the latest Livery.xml.

I am seeing pink texture boxes around the airport KJFK

Hello, Since v1.0.5, the addon is not usuable. i'm getting random WASM crash at every flight. I'm not the only one. We need an Hot Fix. Thank you.

Aircraft: A350-900/-1000 Version: 1.1.8 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Not related Specs: 9800X3D, RX 9070 XT 16G, 64G RAM Autosave File: Not related I don't use Navigraph, I enabled BTV by entering a stopping distance in the system. After touch down, BTV activated as normal, but as I apply manual braking and hence disabling the autobrake, the "Autobrake Off" callout was not heard. This had been an issue for me for a long time.

After spawning mid-air (necessary due to WASM crash... different issue), configuring the aircraft and enabling autopilot in NAV mode, the plane rocks / rolls left to right. Seemingly it keeps overcompensating. Please see below video. I'm not fully excluding wrong user input but if that were the case I would expect some kind of warning. https://gofile.io/d/AqvApL