richboy2307

Hi @KLEE330 Thanks for getting back. Right so your Simconnect connection is not working properly OR the addons are not able to write to your work folder. The OIS/EFB are not WASM so have their data cached elsewhere in the sim's browser instead of the work folder for WASM modules. As I mentioned, we haven't made any changes on our end that would affect the behavior, and we're unable to reproduce the issue on any of our systems running SU4. In this case, you should try running the simulator as an administrator with elevated permissions, verify that the work folder isn't set to "read-only," or adjust your Windows UAC settings to see if that resolves the problem. Additionally, you might consider repairing or reinstalling your simulator files to rule out any issues that may have occurred during the initial SU4 update process. Thanks!

Thanks for your suggestion, shared with the team. As for the GNS530, that is based on actual L1011-500 retrofit configuration: (Click to enlarge image)

Thanks, logged.

Hi @MeesM Is this happening consistently? Is it only at certain airports or everywhere? Can you try to service these engines via the EFB Maintenance page to see if it resolves the issue? Additionally, ensure you have disabled assists such as Auto-Mixture: If you continue to have an issue, please share some screenshots of your overhead, main engine displays and pedestal for reference. Thanks

Hi @KLEE330 That is odd, there have been no changes made to the FMS SB Import functions since launch so its unlikely to have been caused by updates. Try the following: Re-input your Simbrief ID (numbers only) but using the on-screen keyboard of the EFB instead (you can enable it in the settings). Run the sim as admin. The plan is requested via SimConnect to SimBrief and then downloaded into your "work" folder, which is a temporary folder that could be restricted by Windows UAC. Running the sim as an admin may help if access permissions are causing the problem. You could also manually monitor the files in the "work" folder to see if they are in-fact being downloaded/updated. Namely the Simbrief.json file and the .fpl file in the flightplans folder found there. Work Folder Paths Try running with an empty community folder to rule out any addon conflict. While this is rare, occasionally some addons can affect Simconnect behaviour, which in turn could be causing your issue. You can test this quite easily by temporarily renaming your existing Community folder to _Community, then running the simulator to test. To restore, simply close your sim, delete the new Community folder and rename _Community back to Community. Hopefully one of the above resolves your issue. Please let us know how you fair. Thanks!

Hey @Hny Have you tried to calibrate your throttles via the OIS? Guide here:

Hi @Rob K You can try the following: Re-enable it via My Library within the sim. For more information, see: https://flightsimulator.zendesk.com/hc/en-us/articles/17373373933340-How-to-enable-disable-and-download-content-in-the-simulator OR Manually activate it via the Content.XML file. The relevant entry is as follows (note: the important bit is the status should read "Activated") The file can commonly be found here - MS Store: C:\Users\[Your Name]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ Steam: C:\Users\[Your Name]\AppData\Roaming\Microsoft Flight Simulator 2024\[Your Steam Username Folder]\ Thanks!

Update: FSimStudios CYYC and VerticalSim KPVU - FS2024 compatibility updated on the store and on iniManager.

Hey @Arty57 Thanks for the update. Forwarded to the team. For what it's worth, I could calculate on Lbs the marketplace version as well, so maybe the issue was the EFB/WASM hadn't updated properly and a fresh install (via iniManager) resolved it. Anyways we'll investigate. Thanks! Update 1: As far as we can ascertain, the issue is resolved as of v1.0.7 update. If you are having issue, please try a fresh WASM compile or re-install the aircraft.

@Roders Thank you for your time and for sharing your concerns. I understand your frustration, we genuinely do our best to address WASM crash issues because our goal is to provide a smooth experience. That said, these crashes can be difficult to reproduce, if at all, so every bit of information you provide is incredibly helpful! Thanks for the additional information; it was very helpful. Still no WASM crash, but I did notice the unusual ND line drawing/flickering behaviour, which could be another clue. Perhaps the WASM crash happens eventually whilst the PFD/ND system was re-drawing paths from memory. Thanks, noted with regards to DISCON as well. In the meantime, try performing all the actions through the F-PLN page instead (see video below)? Seems to work better in this instance (though there is no DISCON between AMIKI and CI14 initially still). If you encounter the WASM crash again, please let us know. We'll keep working with this in the meanwhile. Thanks! 2026-01-16 07-01-45.mp4

Hi @Roders Sorry to hear about the WASM crash, and thank you for reporting it. The team will be investigating further. Although I haven't been able to reproduce this crash myself, I did notice some discrepancies with the VNAV calculations after applying the changes you mentioned, which might provide a clue. To help us better to reproduce the WASM crash, Are you experiencing a consistent WASM crash when performing this action (based on the attached autosave)? Did you make any modifications to the flight plan prior to this autosave? Thanks!

Glad to hear that. Will lock the topic now. Thanks for your patience and understanding!

Hi @Arty57 Please include screenshots of the EFB calculation you're running. Also attach the OFP in case you're doing it direct from import so we can investigate further. Thanks!

Hi @Jun56 Apologies for delay in response, hopefully you have resolved it already by now by following the suggestions in the other threads here. If not, please ensure the following: Uninstall/Disable other LOWI sceneries via Content Manager (FS20) / My Library (FS24). This includes Gaya/Asobo LOWI as well as any other 3rd party sceneries. Clear your scenery indexes and then restart the sim.Thanks

Hi Yes after the A340 is available via iniManager, you will be able to request an order transfer via the form. Thanks

Hi, Thanks for your suggestion. However, sorry that is not possible as the Marketplace is the only platform through which additional content is distributed for MSFS 2020/24 on both consoles (XBOX/PS5). There is no other way around it with the locked ecosystems of consoles. Thanks!

Hi Please reach out via Direct Support with your request. Thanks!

Hey @Mandretti Sorry to hear that. Try again now? Could have been some activation issues server side due to high demand. If the issue persists, I recommend contacting our store team through Direct Support. Please include screenshots of what you're experiencing on both the iniManager and TFDi application for reference. Be sure not to share any of these screenshots publicly to protect user information. Thanks!

The profile is not part of the uploaded package. We've already asked the dev to rectify this ASAP. You can also reach out to the dev here https://www.facebook.com/people/Sim-Design-Group/100066783410216/ for any other scenery-specific enquiries. Thanks for your patience meanwhile. Thanks!

Hey Thanks for your patience. We've verified that the correct file should be iniBuilds-a350-900-DAL-6DN, and that it is being downloaded into the FS20 community folder, so it should work properly in your sim now. The install status should also be detecting correctly. Thanks!

Hey Thanks for your patience. If you purchased the A350 through the MS Marketplace (either for FS2020 or FS2024), you can submit an Order Transfer request using this form. Just follow the on-screen instructions to upload proof of ownership screenshots, If you can't find the exact order number, any 4-digit number will do. You’ll receive updates on the status via email. Once approved, you can install the A350 directly into your community folder using iniManager (for FS2020 or FS2024). Just make sure to uninstall the marketplace version via Content Manager (FS2020) or My Library (FS2024) to prevent any conflicts. If you have any further questions or concerns, you can contact us via Direct Support. Thanks!

Hi @Jackmill Although I cannot speak for other stores, at iniBuilds Store, '2024 Compatibility' normally must be explicitly confirmed by the Vendor (i.e., the product developer) directly to our store team. Anyways, regarding those 2 sceneries I will forward your request to our store team. In the meanwhile, you can install them into your FS2024 folder by - Copying them from your 2020 Community folder OR - Under iniManager settings, define your FS2020 Community Folder path as your actual FS2024 Community folder path instead Thanks!

Hi, Thanks for your patience. That is not an issue, as recent Sim Updates have altered what needs to be indexed versus what can be stored in the rolling cache. As a result, not all scenery will have this data generated in the future. Thanks!

Hey @garett_09@aj_chugh Thank you for your report. That is unusual; based on the FROM/TO combinations I could identify from your screenshots, I haven't yet encountered similar issues. Nevertheless, please send us the Simbrief OFP PDF for the route where you're experiencing this problem. It could assist us in better reproducing and diagnosing the cause. You can find your OFP in PDF format on Simbrief Dispatch: This is OTHH-KLAX for example even with steps as computed by Simbrief, all automatically imported. So that is why we believe there has to be something specific in certain plans that may be causing it. OFP: OTHHKLAX_PDF_1767977506[1].pdf Thanks! OTHHKLAX_PDF_1767977506[1].pdf

Thanks, will have a look. For anyone else also coming across this, please also attach your latest 2 autosave files for when it happened so we can load into the same scenario to compare. For more info on Autosaves, see below FAQ post: Thanks!