rsmith6621a Posted Sunday at 07:24 PM Posted Sunday at 07:24 PM Yesterday, something went buggy with my SIM. When I would attempt to load a flight it wouuld hang at the Start Flight menu and the circle in the corner would just spin and never load into the airport. After several try's to find a fix, I went ahead and did a repair and reset then I started to rebuild my sim back to its pre incident state. This morning, I uninstalled the A-350 and reinstalled it as it was not showing in the aircraft menu. After the re-install the A-350 is not showing up when I I am in the aircraft selection menu, but it is showing up as installed in my MSFS 2024 Community folder. What am I missing and what can I do to get it to show up. Thank you
IniJamir Posted Monday at 04:06 PM Posted Monday at 04:06 PM Hello, How long was the loading taking, initially the A350 can take about 5-10 minutes (seen on my system) to fully initialize following first time installs/reinstalls, and updates, was this a first time launch or repeat? Additionally, It is possible that the aircraft is not being detected in the IniManager itself. When you install the aircraft, do you use addon-linker or any other 3rd Party Link Programs? You can attempt to clear the IniManager Cache: To clear the iniManager cache, close the application and delete the contents of the local and roaming AppData folders: %localappdata%\iniManager and %appdata%\iniManager. You can also clear aircraft-specific WASM caches by navigating to %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\ and clearing related folders. Let me know if either of these help resolve the situation, thank you.
Solution rsmith6621a Posted Monday at 11:41 PM Author Solution Posted Monday at 11:41 PM Hello IniJamir. In the past 5 years I have always pointed all of my installs to E:\Microsoft Flight Simulator 2024\Community. It seems since I have done a reset I need to point it at another location that being C:\Users\****\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community. This seems to have fixed the issue. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now