richboy2307

Close the simulator if it is running. Navigate to your your FS20 WASM Folder: Steam: MS Store: 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-0x80000003 This 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!

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.

Hi @Eric Jeppesen 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!

Hi @LineDX 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. Should be fixed in 1.0.8 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). Thanks already logged and team is actively working on it. 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. Reported. Thanks!

Sorry for your issue, but team is aware of autosave alt capture logic issue and actively working on it. Thanks!

Thanks, issue is logged and team is actively working on it. 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 control Your 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

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

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!

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!