All Activity

Hello, Forwarded to the team. Thank you

Hello, Forwarded to our art team. Thank you

Hello, Please refer to this statement regarding pop-outs. As of right now, it is still current;

Hello, I've prodded the team regarding the cargo variant FPS issue. Will lock this thread for visibility. Thank you and apologies for the inconvenience.

As it should in normal situations when there are no fuel leaks.

It’s still reading 0 kgs…..

So what's the issue with the calculation?

The iniBuilds support told me this: Hello, The developers believe this is an issue with the streaming of the product as this doesn't persist on locally downloaded version of the aircraft nor the iniManager PC version of the aircraft. They are going to check again when they are back in office on Monday.

I'm not sure if anyone else has this problem, but right after V1 the aircraft takes off like a rocket with minimal sidestick input. I can't pitch the nose down, it only starts an aggressive stall once it runs out of speed.

Dear all, I have an issue with the auto step climb feature. I programmed the step climbs in the FMC - I could see estimated times and altitudes, as well as S/C in the flight plan. Question - what is the altitude I set on the MCP? I assumed that I always set the current cruise altitude, and when step climb waypoint is reached, the plane will automatically change it to the new cruise level. Is that correct? Or do I have to enter the altitude "after" step climb? The reason I ask: When the plane was supposed to step climb, it simply told me "STEP DELETED" and did not do so. I ran out of fuel during my overnight longhaul and crashed.

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