richboy2307

Hi everyone Thanks for your reports. Our team has investigated the issue, from what we are able to see is that the connection is still open from our module (data is continually transmitting, and being listened to hence why control inputs work), however their module stops rendering the display in such instances. We have also raised the same with WINCTRL (previously WW) for further investigation on their end. We are hopeful a solution can be found soon. Temporary solution is toggle between Cpt or Co-Pilot side in SAP whenever you notice this. Thanks for your patience meanwhile!

Thanks logged.

Hi If you're airborne, the option only appears whenever you are not in NAV lateral mode. So you can, for example, set current HDG and pull HDG knob first, then you will be able to activate the secondary flightplan. Thanks

Hi, The accepted format is WPT/ALT in LSK L1, so try DATOK/410 for example. After you start climbing to the FCU selected ALT, it updates the CRZ ALT to the FCU alt as long as its higher than current CRZ ALT. You also get an FMS scratchpad msg "NEW CRZ ALT FLXXX" as seen here. The temps however you may need to adjust on your own. 2026-01-19 22-57-25.mp4 Thanks!

Glad to hear. There is no option to disable that at the moment but suggestion is noted for the team. Thanks!

That sounds like network issues with simbrief servers, if its taking that long for a download to complete. But anyways, as long as it works for you 👍

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!