-
Posts
1521 -
Joined
-
Last visited
-
Days Won
79
Content Type
Profiles
Forums
Downloads
Posts posted by richboy2307
-
-
Hi @cuttorz
Apologies for the delay.Please reach out to Direct Support with reference of your original order transfer request: https://inibuilds.com/pages/contact
Thanks!
-
I believe the same WASM crash was reported by you on the Discord as well. So we will follow-up there directly:
https://discord.com/channels/535246634448191499/1369346404874588282/1378721954890125533
For context, we tried multiple times now across different systems, with multiple different revisions to the SEC F-PLN (Rwy, Appr, TAR and many combination of it thereof). Working fine for us (see video attached on discord). Not able to reproduce the WASM crash as yet.If you're getting consistent repro with the above autosave file (or other crash files), a video like below would help along with the autosave file to try and get reproduction of the issue. Add it to the linked discord thread itself. Thanks.
-
Hi @braganca
The aircraft is not underperforming, rather the sim is giving you bad weather data at that moment, specifically temperature. Note the ISA Temperature Deviation of +53c (!).
The engine cannot provide enough thrust at such high temperatures at altitude, and is performing as it should in the current conditions.
When this happens, try to cycle your live weather. Thanks!
-
Hi,
We have some testers who have used this aircraft in VR primarily since pre-release (both sims) without any major issues, even going in-and-out throughout longer flights.
There is a known sim limitation specifically in VR or when using headtrackers/camera shake addons (like FSRealistic) that affects the accuracy of hit registration of mouse clicks on the MFD, which is being worked in FS24 SU3 Beta based on user reports.
Please confirm that the aircraft is functional in 2D, if not, try to clear your WASM folder and launch directly onto a runway on first load to ensure proper WASM compile.
Thanks! -
Thanks, shared suggestion with the team.
-
2
-
-
Hi @GuangDu The manual is attached here, and also in the Resources/Documentation folder inside the aircraft package (Community Folder) :
You need to ensure the weapon is armed first. Thanks
-
@ykeyre The threshold is 80kts. It only triggers if ABRK is disengaged above 80kts.
22 hours ago, ykeyre said:auto brake is disengaged above 40 knots ground speed,
Thats what we had it as originally, but we had SME information that 80kts it the more standard option so it was changed to reflect that.
-
1
-
-
@DoubleP99 @Finster2308 What are your system specs? It genuinely sounds like using the 4x time compression you are running out of CPU resources, and as a result performance suffers to the point where the aircraft is no longer controllable by the autopilot.
Not something we can fix, just limitation of the way computation works. On my 5800x3D, 3090 I can run 4x fine on both sims, although better in FS24 than FS20 due to architectural changes on the backend.
If during 4x you're managing less than 20fps (its not a hard limit, but a rough guideline), then you can expect instabilities.
Thanks!
-
As of iniBuilds A350 Airliner update v1.0.11 (MSFS 2024), some necessary changes have been made to the folder structure in preparation for the ULR update. This affects the Cabin variants specifically, meaning that your previously saved custom camera configs (Cameras.cfg) may not load automatically on first load of this version.
You can restore your Camera config by copying it over to the new folder as follows:
-
Locate your Presets folder at the path listed below:
Quote
Steam:
%APPDATA%\Microsoft Flight Simulator 2024\SimObjects\Airplanes\a350\presets\inibuilds
MS Store:
%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\SimObjects\Airplanes\a350\presets\inibuilds
-
There will be up to 6 folders. Your old Camera config is stored in the 'a350-1000/config' or 'a350-900/config' folder for -1000 or -900 Cabin variant respectively.
-
Copy the Cameras.cfg from the Old folder to the to the New folders - 'a350-1000_default_cabin/config' or 'a350-900_default_cabin/config' for -1000 or -900 Cabin variant respectively.
QuoteNote:
- You may need to restart the sim for changes to take effect.
- Saving new custom camera will overwrite the previous file.
- It is recommended to keep back-ups of your original file for safe-keeping.
-
Locate your Presets folder at the path listed below:
-
- Close the simulator if it is running.
-
Navigate to your your FS20 WASM Folder:
Steam:
Quote%APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600
MS Store:
Quote%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600
-
Delete all the contents of this folder. This folder and its contents will be re-generated next time you load into a flight with the aircraft.
Note: This will reset your EFB Throttle Calibration and EFB Settings so they should re-done the next time you load into the aircraft.
-
Yes we have tried flying into and out of EGLL. For most of you having this issue, I presume you are on SU2 Beta? If so, thats likely due to the new memory management that actively culls objects from memory as part of performance/stability optimisations.
You may revert to SU1 or adjust your settings on SU2 beta to lessen the memory demand, and thereby the instances of this happening. Its not a scenery issue in that sense, and if the sim is doing the above too aggressively, it is for sim code to resolve.
Thanks!
-
Sweet. if you have any further question regarding your transfer request (after submitting it), feel free to reach out to Direct Support: https://inibuilds.com/pages/contact
-
Hi,
That is odd, seems like corrupted data. You could try reinstalling it (disable then renable via MyLibrary)
We'll look into it if can reproduce it. Is this happening at every airport or only specific ones?
Thanks!
-
Hi @K2rockall
Unfortunately there is not much in the logs there, however judging by the Exception code: 0x80000003 in the first screenshot, perhaps you can try the solution suggested there: https://forums.flightsimulator.com/t/app-could-not-start-exception-code-0x80000003This appears to be a general sim issue due to missing dependencies rather than something A350 specific per se. If you continue to have issues, I recommend reaching out to MS Support as well with your logs for suggestions.
Thanks!
-
Hi,
The KJFK Enhanced upgrade is exclusive to purchases via the iniStore for the moment.
We'd like to offer similar upgrade pricing paths via the FS2024 Marketplace, however still awaiting such functionality for it so not possible at the moment.
If you're on PC and want to avail the discount pricing sooner than that you may
- Transfer your 2020 Marketplace purchase to iniStore via an Order Transfer: https://forms.inibuilds.com/order-transfer
- After successfully transferred, purchase 2024 KJFK Enhanced via the inStore using the same account that has 2020 JFK + use discount code KJFK- UG on checkout.
Note: This will move your 2020 KJFK to iniStore permanently, and it will no longer be available via the Marketplace.
Thanks!
-
1
-
Hi
There is no way to link purchases, however you should still be able to download liveries into your community folder. Just make sure the right path is chosen in the iniManager settings (click on your name top-left corner).
You can also drag and drop other community liveries downloaded elsewhere into your community folder for use with A350.
Thanks.
-
Just a follow up on your report. Can you please provide screenshots of how your axis is setup within the FSUIPC AXES & ASSIGNMENTS & CALIBRATION window? Both the assignments tab and also the calibration.
I'm assuming the Paddles are the TWCS type, wherein they are a single axis? If so, how are you assigning it to brakes as an axis? Do you have it assigned to both LEFT BRAKE and RIGHT BRAKE in FSUIPC, then you have manually set the MIN / MAX values of the axis? And is the issue that both brakes are being pressed or just that its not "zero-ing" brake pressure in the centre?Thanks!
-
1
-
-
Hi @LineDX
On 4/9/2025 at 5:02 AM, LineDX said:1. In fs2020 T.O.THS is always out of range at cold and dark startup even after following the above mentioned instructions.
On 4/15/2025 at 7:48 PM, LineDX said:please review the autosave file with TO THS showing out of range with all batts on and external power connected.
I've even tried loading into your autosave file but not seeing this (though as mentioned noted your issue). Will see if can be reproduced on any testers systems but in any case I don't expect this to be a major bug. Even if you are getting that on spawn it shouldn't affect flight at all as the aircraft mainly re-trims after engine start as you have mentioned.
For anyone else reading this thread, this automatic trimming will usually happen after you have done the following:- Update your weights via OIS LOADSHEET page (SET ZFW and SET FUEL)
- Fill in the FUEL & LOAD Page of the FMS (especially ZFWCG) with new values
- After engine start, observe automatic re-trim to the managed trim value.
- Troubleshooting: In case it does not set the correct value, DISARM and then ARM your ground spoilers again to trigger the auto-trim process again.
On 4/9/2025 at 5:02 AM, LineDX said:2-When open offset menu, the drop down list does not disappear after clicking the items. You have to press the ESC button after selections for lists to disappear.
Should be fixed in 1.0.8
On 4/9/2025 at 5:02 AM, LineDX said:6-The ac did not capture the ALT constraint during managed climb mode. Example, departing OPKC BADUL1 DEP. KC509 has an ALT cap FL070 but it did not capture and continued to climb just like OP climb when the AC was in fact in Managed CLB. It was maintaining the managed speed though.
7-Did not capture the STAR constraint ALT/FL during managed DES. VDEV more than 2500ft thus unable to capture the GS altitude of 3000ft set on FCU. Happening on MIMAL1 ARR and ILS36RZ for OPLA.
As for VNAV in general, team is working on a larger update to the logic that will improve VNAV calculations and ALT CSTR compliance. This will come in a future update (1.0.9 at the earliest, though may be later as its still undergoing refinement and testing process).
On 4/9/2025 at 5:02 AM, LineDX said:1-The TCAS does not generate any TA/RA even when traffic is visible. Even the aircrafts don't change the shape/color when comes in close proximity.
Thanks already logged and team is actively working on it.
On 4/9/2025 at 5:02 AM, LineDX said:2-switch the TCAS from TA/RA mode to standby and then back to TA/RA mode does not clear ECAM notification.
The TCAS STBY ECAM can be triggered by any of the following,
‐ Select STBY in the TCAS mode option list on the SURV CONTROLS page of the MFD, or
‐ Select STBY in the XPDR mode option list on the SURV CONTROLS page of the MFD, or
‐ Set the ALT RPTG button to OFF on the SURV CONTROLS page of the MFD.
As its status is controlled by more than just the TCAS mode (TA/RA), probably what happened in your case is as follows
- You set the TCAS mode from TA/RA to STBY
- The ALT RPTG button also automatically set itself to OFF (by design)
- You set the TCAS mode from STBY back to TA/RA
- The ALT RPTG button remained OFF (by design)So ensure none of the following are set STBY or OFF to make the ECAM disappear.
On 4/9/2025 at 5:02 AM, LineDX said:3-When change the MACH speed in the CRZ mode from managed to selected. The ETA does not change in the CRZ tab in PERF section. It's bug. MACH.78 and M.88 has the same ETA for the T/D which is 94miles away. This can't be right.
Reported.
Thanks!
-
1
-
On 4/20/2025 at 4:41 AM, felipeturbay said:
reloaded the flight via the autosave option but the aircraft is unable to capture the cruise altitude with VNAV since the compete vertical profile is not longer there.
Sorry for your issue, but team is aware of autosave alt capture logic issue and actively working on it. Thanks!
-
1
-
-
8 hours ago, C. Schaffhausen said:
I tried to resume my flight by loading the Autosave. However, the ALT*/ALT/ALT CRZ function does not work, the aircraft would overshoot the target altitude and keep climbing/descending.
Thanks, issue is logged and team is actively working on it.
2 hours ago, FelixM said:Autothrust is also not working for me
Please confirm after reloading your autosave that
- A/THR is enabled on the FCU
- Your throttle axis is in the CLB detent
- FMA reads SPEED / MACH / THR IDLE / THR DCLB depending on phase of flight as an indication of thrust controlYour hardware input of primary flight controls, particularly throttle axis prior to loading the autosave can affect the status of that control after reloading. Hardware inputs will override the autosave variable always (same as it does in active flight).
Thanks!
-
Since v1.0.6 update of the iniBuilds A350 Airliner, the Taxi Camera Lights are only operational on aircraft that have such lights installed; and when specific conditions listed below are met.
Taxi Camera Lights - ON vs OFF
(Click to enlarge image)To Enable Taxi Camera Lights
You must ensure all of the following:
- Under OIS Equipment Settings > Taxi Camera Light is set to ON; and
(Click to enlarge image)- TAXI pushbutton on EFIS CP is set to ON; and
(Click to enlarge image)- NOSE LT switch is set to TAXI or T.O.; and
- Main Landing Gear (MLG) is on the ground
QuoteNOTE: FS2024 Users - The OIS Equipment setting - Taxi Camera Light may be controlled by your airline configuration file that comes included with the installed livery.
(Click to enlarge image)
To manually override, you may edit the LiveryConfig.cfg file included in the livery package and ensure it reads INI_OPTION_TAXI_CAM = 1 accordingly. The changes will take effect after sim restart.
(Click to enlarge image)For more information on the Livery Config file, see
-
1
-
Since v1.0.6 update of the iniBuilds A350 Airliner, the Taxi Camera Lights are only operational on aircraft that have such lights installed; and when specific conditions listed below are met.
Taxi Camera Lights - ON vs OFF - FS20
(Click to enlarge image)To Enable Taxi Camera Lights
You must ensure all of the following:
- Under OIS Equipment Settings > Taxi Camera Light is set to ON; and
(Click to enlarge image)- TAXI pushbutton on EFIS CP is set to ON; and
(Click to enlarge image)- NOSE LT switch is set to TAXI or T.O.; and
- Main Landing Gear (MLG) is on the ground
QuoteNOTE: FS2024 Users - The OIS Equipment setting - Taxi Camera Light may be controlled by your airline configuration file that comes included with the installed livery.
(Click to enlarge image)
To manually override, you may edit the LiveryConfig.cfg file included in the livery package and ensure it reads INI_OPTION_TAXI_CAM = 1 accordingly. The changes will take effect after sim restart.
(Click to enlarge image)For more information on the Livery Config file, see
-
No need to apologise. We're all learning new things about the A350 each day as its such an incredibly familiar yet different aircraft with new procedures, systems and technologies.
Thanks!
-
2
-
-
Just do this or any other flight as normal. In case it happens again please provide the autosave as well as the WASM crash report as we'd love to resolve these issues however it is impossible to do without getting proper reproduction of it on any tester or production systems.
It is equally difficult to verify the efficacy of any fix implemented based purely upon "guesstimation" if we can't reproduce the errant scenario to test on.
Thanks for your patience and understanding!
How to - Change between Cabin Variants via the Aircraft Selection Menu
in FAQs
Posted
Overview
The iniBuilds A350 Airliner for FS2024 (PC) now comes with additional Cabin Packs that you can download via the iniBuilds Store and soon via the Marketplace (PC). Once installed, you can choose one of the many custom airline cabins to use with any compatible livery of your choice via the Aircraft Selection Menu.
Changing Cabin Variants
Now you can return to the Free Flight menu and select Start Flight to use the selected Cabin variant of the iniBuilds A350 Airliner.
Compatibility with Custom Cabin Textures
You can use any cabin variant with any installed livery for that aircraft type (-900 or -1000) as they share the same exterior models (e.g. Cathay Pacific -900 Livery with a Qatar Qsuite Cabin option).
However, if your installed livery comes with additional cabin customizations/textures, they may conflict with the Cabin Packs. In such instances please use the "Default Cabin" variant to continue enjoy those customizations.