babybus

Weirdly the -900 works just not the -1000. Very strange!

You shouldn’t need to do any of this. ini used to be my one of my favourite developers. After the botched release of the A350 and the decision to not make products for 2020 they’re quickly falling down my list.

I’ll give this a go. Thank you. Seems ridiculous for a £70 add on.

Glad it’s not just me.

The latest update seems to have broken the aircraft again for me. It was CTD'ing when loading in. I then removed everything from community folder apart from A350 and it worked. I then added everything in with no liveries and it works. I then add the ini liveries back in and I get the CTD again.

Perfect, thank you! Did a search but couldn't find anything.

Hi Eddie, I narrowed it down to the liveries. If I have all the liveries installed it crashes however if I only have a few it works. Hope that helps.

The calculation doesn't seem to be working.

No comment from ini?

I still haven’t resolved this issue. Please can someone help?

{ "dependencies": [], "content_type": "AIRCRAFT", "title": "A350 Airliner", "manufacturer": "Airbus", "creator": "iniBuilds", "package_version": "1.1.2", "minimum_game_version": "1.38.2", "release_notes": { "neutral": { "LastUpdate": "VERSION 1.1.2 RELEASED JULY 15, 2025\\nv1.1.2c", "OlderHistory": "" } } }

On 2020 or 2024? How would I know?

Cleared WASM, uninstalled and reinstalled. No luck! Still CTD loading in. Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Exception code: 0x80000003 Fault offset: 0x0000000001f0ffe2 Faulting process id: 0x2790 Faulting application start time: 0x1DC0514ED340FC8 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: 89c91ec3-74f1-43e7-a586-0ca899a95a6a Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

I have uninstalled and reinstalled with no luck. Keep getting a CTD with the A350!

Hello, I am unable to uninstall the aircraft via the ini manager. I have manually deleted the aircraft files. Now 2024 version shows uninstalled however 2020 doesnt. Please can you tell me what I need to do? The aircraft has been unusable for me since the last update so I am hoping a re install will fix this.

Thank you. Really shouldn’t have to do all this. Not impressed.

I can't even uninstall the product. ini has really dropped the ball! Not impressed.

Hello, I have never had to do that before. Would you mind explaining how I clear the WASM folder and also if it will affect any of my other add ons?

Every time I load in any A350 variant or livery I get a CTD during the loading process. File below! This has only been since the last updated. Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Exception code: 0x80000003 Fault offset: 0x0000000001f0ffe2 Faulting process id: 0x3F4C Faulting application start time: 0x1DBFA0C29252D92 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: 19009dbd-ed76-46f0-bd9b-82f7fa193623 Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

Hello, I was really excited for this aircraft however I am left disappointed. If I could get a refund I would! Lets hope with updates this improves. I have been a loyal ini customer for a long time, however I am starting to get really frustrated at the lack of quality control. Here is a list of issues I have found. 1. Anti Collision switch makes no sound 2. XPNDR 2 doesn't show any FL just stays as 000. 3. Comms don't connect to V Pilot. 4. Prop levers stopped responding too axis input - will test further with other aircraft incase it is my setup. 5. Autopilot Alt Button doesn't engage, just flashes 6. Attitude roll wheel doesn't respond. Need to disconnect AP to level off. 7. Sounds are very disappointing. 8. It would be good if the course neadle automatically jumped to the next track from the TDS GTN. I know slightly unrealistic but would be a nice help! 9. Spray Panel is present in all variants.

Hello, I was wondering when the F406 will be released and wanted to confirm that it will be available for 2020 as well?

Is it possible to have some support please?

For some reason whenever I load up the manager it always tries to update PHNL and VABB even though they’re up to date?

2024-07-22 16-39-57.mp4

Just departed EGGW to EGNX. Was climbing through FL100 to FL120 and just done a direct too UPDUK. I was clearing out the way points when all the systems just froze. Screenshot attached. Aircraft flew normally with manual thrust and control however nothing else would work but the altimeter. Photo attached.