All Activity

Hi, thanks you for your reply To clarify: I do not have any third-party addons, liveries, or visual modifications installed I am only using the Inimanager. The issue occurs only on the A350. All other aircraft I own have fully functional exterior lights from the cockpit view. Please let me know if you need any additional information or tests. Best regards, Danny

Of course, enjoy!

Ahh - it was the default EGGP that was still sitting there. Many thanks for the help - now sorted! Cheers Mike

Hi, It sounds like something might not have initialized correctly during the first load. Go ahead and clear the WASM folder via the steps below as well as verify that the livery selected is up to date. Let me know if this helps. Thank you.

Thanks for your suggestion! Although there is no assignment in the MSFS control options, now I figured out it's something in SPAD.neXt triggered the A/THR when I move the right throttle. I don't see anything mapped in SPAD.neXt but running MSFS without SPAD.neXt does make the problem go away. Now I just need to spend some time to figure out why.

Hello, This issue is known. A little more information; The same was reported on A310 and taken by Asobo as a sim bug, basically the click spot boundaries have become too small / scale incorrectly with zoom levels in SU5. Move closer or zoom in if you're having troubles for the time being. Thank you.

i had this and selected the no cabin option (and deleted WASM) and it returned, although the pfd is messed up now, might start a seperate thread though

I haven't flown the A340 in a month or two, and now it feels like the brakes are half on all the time. I need between 40 and 45% throttle just to taxi at a normal speed. A takeoff roll planned to be around 10,000 feet with FLEX thrust took 14,000 feet at TOGA thrust. Not having any pedals, I use a button on a joystick assigned to the in-game BRAKES variable - they are either on or off. Parking brake acts normally. Any suggestions? I did not have this problem before and I changed nothing on the config. C.Falk Lexington KY

Hello, I have a problem that when I engage the autopilot on airbus a350 1000. When I engage the autopilot it follows the flightpath but the Altitude Hold light comes on at whatever altitude the aircraft is it. For example, if I set the altitude to FL33 and autopilot engaged at say 5,700 feet to follow the flightplan, the Altitude Hold and Auto Thrust come on once autopilot is engaged and the aircraft will follow the flightpath. However the aircraft stays at 5,700 feet and will not climb at per Simbrief. Altitude Hold cannot be disengaged. I've even set a key for "Toggle Altitude Hold" on my joystick and this does not work. I've also gone through and turned off AI assistance as advised but this doesn't help with the problem. Cannot turn off Altitude Hold without disengaging the autopilot. Please help Regards Rod

I’m having an issue installing my A350 into my MSFS2024 community folder. Every time I try to install on the default simulator path to the community folder (by clicking on the “Scan for Simulator Path” which does show the path which logically means that Inimanager recognises it), I get an error “ENOENT: no such file or directory, mkdir ‘<Path to the community folder>’” I’ve uninstalled, deleted the Inimanager folder in Appdata\Roaming to ensure clean reinstall and restarted my PC but the same issues arises when I try to reinstall. I even ran the Inimanager on Administrator to see if it can install and tried alternative downloader but to no avail. Anyone has a solution for this?

I'm having the exact same issue. Plane is unusable as of now.

Thanks, its helped!!!

Hi Danny, Having owned the aircraft on Xbox and then transferring the license to PC should have had no affect on your PC installation whatsoever. That being said are you using liveries from the manager or from a 3rd party provider? I've been using the A350 v1.2.5 with no issue seen with lighting so far. Is this occurring on any other aircraft you own or just our A350. Let me know, thanks.

Hello Inibuilds team, I am writing to report a persistent issue with the exterior lights on the Airbus A350. While the lights are visible and functioning correctly in External View, they are completely invisible when I am in Cockpit View (no light splash on the ground or illumination of the environment). Please note that this issue appeared recently; everything was working correctly prior to this. Specifically, I have noticed that the Wing Lights are working, but the Nose Taxi, Nose TO, and Landing lights are not functioning at all from the cockpit perspective. Context & Steps Taken: Platform: PC (Inibuilds store version). Background: I originally owned this aircraft on Xbox and recently transferred my license to PC using the system provided by iniBuilds. Addons: I do not have any light enhancement addons or visual mods installed that could interfere with the aircraft's lighting system. Installation Issue: Even though the transfer was successful and I can download the aircraft, the A350 does not appear under "My Products" in my account dashboard. Troubleshooting performed: I have deleted and reinstalled the aircraft multiple times and cleared the WASM folders, but the issue persists. Observations: I’ve noticed that this specific bug (lights invisible from the cockpit) was a known issue on the Xbox version. Since I transferred my license from Xbox and the problem started recently, is it possible that the build I am downloading is still flagged with console limitations or missing PC-specific effect files? Could you please look into this and check if my account/license transfer is correctly linked to the PC version? Best regards, Danny

with the basic career mode aircraft, we just don’t have any regional jets to make getting to the bigger passenger jet more affordable in career mode

Hi guys, thank you for replying the post. I use Navigraph latest AIRAC cycle on SU5. I was also on SU5 beta before the final release. I did OPIS-OPFA flights 5 times since the update and this issues happened 4 out of 5 times. It also happened on another city pair as well. It was long haul do could not replicate it. I normally clear the WASM folder contents wash time there is sim update or ini update. The way I clear the Wasm folder is I delete the files in the wasm folder not folders as they contain terrain, navdata, simbreif. Do I need to delete everything in the Wasm folder including the sub folders? I will try to record a video and post it next time. The routing is OPIS-28R-BELKO1K-ENRIR1A-ILS Z-03R FL230 GS Intercept alt 2500. I have a few addons from FS2020 but mostly turned off in addon manager. But will try turning off if there is any left to see it it is package order issue. As said before never had this issue before. Regards

I've passed this along to the team.

So It was the nav data in the end, but definitely a unique case. 😅 You called it! I only responded that as long the sim was up to date that the nav data shouldn't be your issue because the aircraft will just use whatever the sim has instead of its own aircraft specific navdata. Anyway well done, Hope you enjoy all the approaches. 🙂

Are you using Navigraph Navdata in the Simulator? Then it is most likely the package_order_hint problem. There was a similar issue a few days ago. Please look at the Navigraph Forum for details. Long story short: you are using old MSFS2020 addons lacking for the package_order_hint entry in the manifest.json. This disturbs other addons, although the critical addon itself works flawlessly.

If you open the scenery_config.json file with notepad++ and go to the Custom VDGS section, does it say it's disabled?

So I had an issue with the aircraft following INS and GPS or VOR I would take off, and the plane would not follow the flight plan put in by SimBrief and manually added to the INS or Gps The aircraft would get stuck in a right-hand turn and would not climb i tried so many different things, from unplugging my joystick and throttle quadrant this made no diffrence i tried to remove the plane and install it again . so i then opened simapppro. I checked and updated all firmware, recalibrated the joystick, and it then started working again.

Hi, are you able to upload a vide the next time this happens, I have flow 350 a couple times since release of v1.2.5 and have yet to encounter this issue or seen it reported. Has this happened more than once or have you been able to reliably reproduce it. Were the airports default or 3rd party? Additionally have you cleared the WASM folder since these issues began occurring or even reinstalled the aircraft as something might have been corrupted during the update or with the rollout of SU5. Let me know if this helps. Thank you.

Clear the WASM and then try with the default livery and then load in somewhere like GVAC that doesn't have much going on around it. Let me know if this helps

Wait for the Update to drop on Marketplace...