All Activity

Good afternoon. After purchasing the A350 and downloading iniManager, I keep getting stuck on this screen when trying to install the A350. Sometimes clicking the download button causes iniManager to crash unexpectedly. Is there any solution to fix this issue?

Oh yes, my ears also hurt.

In the V1.03 update, the BOD DIS has been limited to 3 digits instead of 4 digits for some reason. There should be 4 digits to allow 1000's of NM to be added to monitor the TOD along the flight plan route from the departure point. FCOM example of PMS flight setup page. IN V vs, in the sim... limited to 999.

3 - fuel and weight at FL 350 4 - crz at FL350 - N1 reading 81% - at this weight at M0.83 it should be at about 85% N1 5 - I really can't see how at MTOW this plane can comfortably reach FL350 The VS often would go down to 500 - 1000 fpm at heavy weights. Please check this with someone who has flown the real -500

@IniJamir In V1.03 The deceimal point has been moved instead of fixing the placment of the number. The decimal should be in the centre and the below should show as 04.76

Here are some pics from v1.0.3 1 - At 23 800' and climbing at 2000' fpm - this was at a TOW of 505 000lbs (basically MTOW) 2 - At 33 800' climbing at 1400'fpm at M0.82

After version 1.0.3 the standby power system is and shows UNARMED through the UNARMED light and the DC standby bus fail light on the electrical panel. The switch is clearly in the ARM position. If I put the switch in ON, the system works fine.

I noticed this in version 1.0.2 and there is the same issue in 1.0.3. When aligning the INSs and inputting the position into all 3 of them when the selector is in POS, all is well. However after pushing back with the INSs in NAV and having sen the OFP to the INS through the paper flight bag, the position is wrong. Essentially I can't naivgate using the INS. The aircraft thinks it is half a degree to the west of the actual position. This causes the aircraft to fly offset of the track, even though I haven't programmed it for offset. I can't even update the position because after I press INSERT the second time after inserting the Longitude, the value just jumps by itself again back to a value around half a degree to the west of the actual position. Essentially I can't tell the INS my actual position, it just overrides it to a wrong position. I didn't have this issue in previous versions of the aircraft. I also used RMT on all 3 units when inserting the OFP from the paper flight bag. I have to use the GPS unit to navigate which works perfectly fine. After inserting the waypoints into the Garmin unit you can clearly see on the map that my actual real position is to the west of the desired track of my flight plan. The INS doesn't know where it is.

A350 Nose Wheel Steering Not Responding (MSFS 2024) Description: The nose wheel steering is not responding at all in the iniBuilds A350. What I tested: Axis correctly assigned to "Nose Wheel Steering Axis" Axis input works (confirmed in sensitivity screen) Reinstalled the aircraft completely No conflicting bindings Other aircraft (A320/A330) work correctly Result: The nose wheel does not move at all, even with: Parking brake released Aircraft powered Throttle applied Conclusion: The aircraft is not reading the steering axis.

Hi After 1.2.5 this still not fixed. After touchdown, the pitch trim should: 1. During a touch and go, the pitch trim will automatically move to the takeoff position, based on the aircraft CG. 2. After landing, the pitch trim will move to 0,8° (maintenance position) when the speed goes below 30 kt. Currently, in both case the pitch trim stays UP 7.0 deg.

Hi, even after filling GW, Fuel and OAT in the flight init page of the PMS on the ground, I get OPT flight level as 888. This looks to me like a regression bug, not present in the previous versions.

Hi, FL360, all packs on, the cruise level set on the tape, but the pressure gauge shows 0 ft cabin altitude and probably over the gauge max scale delta p. Also the cabin temperature is quite low, below 20 F.

Update II 22 April 2026: Came here again to report that the new version 1.0.11 is the FIRST VERSION I have ever flown successfully using SimApp Pro. I just completed a 4.5 hour flight KPDX to KIAD using SAP 1.16.94. No lockups, no freezes. In approximately 500 hours of flight time previously this has never happened. This is very good news for those who don’t have or don’t wish to use alternatives like SPADNext or Mobiflight. Hats off to ini for this release! YMMV TANSTAAFL Blue skies, -B

good morning, after the new update, I immediately started testing, on the ground at the gate no problems, taxiing to the runway no problems, Take off no problems, during climbing the PC started stuttering and very heavily even, many addons disabled, such as ActiveSky - VRAAS - REX ATMOS, but the problem remained, any suggestions?

As title says (new in latest update 1.0.3) Using the provided checklist steps for power-up, the wrong UNARMED light comes on. IMO Pls recheck also AC/DC Fail lights ... JetNoise

Hi everyone, I’ve just updated to v1.2.5 and completed a few flights. I noticed several issues that seem to be new or persisting. I would appreciate it if these could be fixed in the next update. • Autopilot Disconnect Sound: When the AP is disconnected, the alert sound stutters or is momentarily interrupted. • LNAV / Direct-To Issue: When executing a "Direct-To," the aircraft does not follow the LNAV path correctly and turns in an unexpected direction. • Autobrake Disarm Voice: The "Autobrake Off" callout is extremely quiet (like a whisper) and hard to hear. • TCAS Reset on Takeoff: On my second flight, even though TCAS was set to ON/TA-RA, it automatically switched to OFF upon rotation/takeoff. • Company Message: The "Company Message" notification still does not disappear as expected. Thank you for your hard work on this project!

Hi @IniSteve - this seems like a relatively easy fix to swap these nodes. Do we know if it's likely to happen soon? AI trying to route via the above taxiways doesn't make it, making 08R departures a bit of a mess. Did we also work out what is actually changed with the BGL's switched with the 'North Runway Active?' The BeyondATC Discord is frequently seeing people raise issues with AI and debugging confirms these nodes not linking to the right runway (or that the runway in the nodes isn't correct!) is playing up. Seems to be quite a bit of disapointment with the quality of the ini product if something quite simple as renaming the runway in the node data is still left to be fixed over 2 months later from when I demonstrated the issue.

I've passed this along to the team, a video would still be very helpful if one can be added, if not I can try to get one tomorrow myself. Thank you

As jetsetuk said, I have the same issue. I did a couple patters trying different techniques including button pressed and illuminated, as well as NOT pressed and lights not illuminated. I can only manually deploy the spoilers in the air (speed brake). Once I touch down, nothing happens, regardless of thrust reverse or not…also, on touchdown, manual deployment using key bind doesn’t work. The ONLY way I can deploy spoilers after touchdown is to use the mouse and physically drag the spoiler lever. interesting note, after engine start, right before taxi on my control surface checks, the keybind works for deployment of the spoilers. 🤷‍♂️ really hoping this can be pushed towards the top of the priority list for the next update.

I'll pass this along to the team, thank you 🙂

Are you able to send a video of the below issue happening? Either a google drive link or youtube will work. Thank you

Hi Inibuilds, not yet had chance to fly the new update for the A350 but I will give it a good flight tomorrow. I've just noticed that the 2 buttons when clicked don't have a animation , I realise its not a biggie but thought I'd report it to you Video :

There is a click spot on the Radar Altimeter to the right of the ADI that will extinguish the DH lamp.

FO side clock hour hand is black under instrument light with no flood lighting And if you click by the label on the FWS CARGO COMPARTMENT extinguisher guards, the label disappears never to return. The guards work fine. Example below shows one missing after clicking. All the other guards seem fine.

On my last flight v1.0.2 the capt side decision light was permanently on.