Eddie

Hi, Please try force re-download of the affected streamed content.

Hi, Thank you, passed on to the team. 🙂

Hello, Yeah there's definitely something not right here. I have, like mentioned, tried what you mentioned but it seems something is making the simulator ignore the chock logic entirely. Have you tried using the A300 in an empty community folder to rule out any potential conflicts? Thank you

Hi, Apologies for not getting back to you. Been a very very busy month for us and all we ask is for your understanding. I've tried reproducing the issue and haven't come to the same conclusion. The chocks won't engage in your instance due to the aircraft already being in motion, which is obviously a problem. Either way, the team has been made aware despite not being able to reproduce and will be addressed in a future update. Again, apologies for the very delayed followup. Thank you

Hi there, Apologies for the inconvenience. The team is already aware of this 🙂

Hi there, Thanks for the report. I've passed this on to the team 🙂

Hi, yep. We've noted this. Looking into it for a future update! 🙂

Hi, From what I understand, this impacts all content that is locked within the simulator including standard, deluxe and premium content. So nothing third party as that will be installed locally unless the developer chooses to use the streaming functionality as well (not sure how that will work if the product is sold on a third party marketplace). Microsoft has already made a statement regarding this issue and are working towards something that will make the community happy. Thank you

This seems to be a known sim issue. You can try force re-"downloading" the streamed files:

Hello, Try clearing you "work" folder for respective aircraft you're having issues with. That is found here: Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\ MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\ Thank you

Not yet. I believe once the marketplace is available, you'll be able install things locally.

Hi there, Thanks for letting us know. Passed on to the team! 🙂

Hello, Thanks for the report, passed on to the team.

Hi, Due to the nature of the encrypted/locked files Microsoft have shipped, it is not possible to access the base files and make liveries off of them. There are requests for paintkits/access on the MS forums. Until they get addressed, I have no answer to your question. Hopefully sooner than later we'll see liveries start popping up once/if file access is granted. Thank you

Please check the ThrottleData.ini file (open with Notepad). Check for specifically [throttle] reverse_on_axis = true If it says false, change it to true as above. Reverse thrust should then work after a sim restart. ------------------------------- The ThrottleData.ini file can be found in the respective aircraft's work folder at the following paths. For e.g. the A400M's work folder will be inside ...\microsoft-aircraft-a400m\work at the below paths: FS24 Work Folder Paths Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\ MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\

Hi there, I'm able to get all lights working properly. This is most likely due to the server issues not streaming things correctly yet. I understand the frustration; hoping all issues are resolved sooner than later. Thank you

Hi Pablo, Message above yours indicates that this is indeed an issue on our end. The team is aware and will hopefully be fixed next update. Apologies for the inconvenience and thank you for your patience.

Hi, My last reply is the most up-to-date information regarding this. We are still looking into lessening the occurrence of WASM crashes. With our next A300 update, we are hopeful they will reach close to 0. We understand it's taken a long time but we'll get it out to you as soon as possible. Once again, apologies for the inconvenience and wait. Thank you

Hi there, Steam users are still required to use Microsoft services to connect to the game, as such, everything such as settings, purchased items through the in-game marketplace etc are stored in the MS cloud. If you purchase any product on 3rd party websites, such as ours (inibuilds.com), your product will be available, in this case, on our iniManager. If you are asking if the B1 will be available in the in-game marketplace, it will as soon as Microsoft has cleared it all good to be pushed onto the marketplace. We have already sent it to them. Hope that clears things up! Thank you

Hi there, Make sure you have uninstalled the default Asobo LOWI from the Content Manager. That will certainly cause conflicts. If that is already done, please make sure photogrammetry is set to ON. Thank you

Hi Sam, Just to double check, have you installed the GSX profile we provide through the iniManager? Thank you

Hi, As mentioned, this is mostly out of our control. The update is not a simple "patch fix" that can be pushed through the content manager. It needs to be pushed as a sim update and that is something I assume Microsoft is reluctant on doing when it comes to smaller patches (note this is just my assumption). Regardless, we are at the mercy of Microsoft and when they would like to distribute the fix is entirely up to them; that way we cannot provide any dates or schedules, and I doubt they would be able to either. I am hoping it is sooner than later though! Thank you for your understanding!

Hi, Glad to hear. Enjoy flying! Thank you

Hi Maverick! Apologies for the late reply. Must've missed this post. Anyway! Try to check the maintenance options, to see if it might be a wear and tear issue. If not, try to run A300 without any addons to rule out any potential conflict. Additionally, you can try to clear the work folder: Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 The simulator will recompile those files (same as first time launch) next time you load the a320neo. Thank you

Hi! No worries at all. From what I know, any potential conflicts were resolved with 1.1.2 of the 787-9 so it may be worth to double check if you are indeed on that version, just incase. Other than that, I'm not really sure what the culprit could be. You can try clearing the contents of the "work" folder for the A320. You can do that by locating the folders here: A320neo Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo The simulator will recompile those files (same as first time launch) next time you load the a320neo. Thank you and I hope this resolves the issue!