We have no idea why the sim is unable to compile. You could check that you have enough free disk space. Nobody has resolved this yet nor fully understands what it means. You could try reinstalling the game but there is no promise that helps.
Ok i found it but its only camera definitions. I have no idea why my throttle on my T1600 doesnât work for this heli. I tried all kinds of sensitivities settings and bindings, emptied my community folder, created a new profile. etc. the slider goes down, but then pops right back up like thereâs conflict somewhere. I have no idea where. I pressed fadec and tired both engines on and off, an a cold start. Yikes I give up.
It worked when the ordinal had the propeller binding so I guess theres a setting saved somewhere. Sorry I canât use this fun plane.
We have no idea why the sim is unable to compile. You could check that you have enough free disk space. Nobody has resolved this yet nor fully understands what it means. You could try reinstalling the game but there is no promise that helps.
Blockquote
A big thank you for this answer, with 300 GB available on the hard drive dedicated to MSFS I donât think I will run out of space for this installation.
When to reinstall the simulator to not be sure of the final result, I prefer to wait.
Maybe a solution will be found in the future or a future update of MSFS will solve this problem.
Many other users are having the same problem, so maybe a talented boy among them will have the solution.
In the meantime the beautiful bird will stay in the hangar with a tarpaulin to protect the cell
A possible cause could be a too long path/filename for some files located inside the community folder. Some users ran into this issue with other mods. This is more possible in the case you have installed your game in the default folder instead of a custom location at a low folder level.
It is still possible to move the main game folder (where you find âcommunityâ and âOfficialâ) by backuping the community / official folders and uninstalling / installing the game. During installation, you need to stop the process after a few minutes, and put back your backup. Then, at relaunch, the game is installed.
A possible cause could be a too long path/filename for some files located inside the community folder. Some users ran into this issue with other mods. This is more possible in the case you have installed your game in the default folder instead of a custom location at a low folder level.
It is still possible to move the main game folder (where you find âcommunityâ and âOfficialâ) by backuping the community / official folders and uninstalling / installing the game. During installation, you need to stop the process after a few minutes, and put back your backup. Then, at relaunch, the game is installed.
Blockquote
Thanks for the advice appreciated, but these uninstall / install procedures are not guaranteed and with my very slow connection it discourages me from engaging in this process.
I donât think the path to the âCommunityâ folder is long with FS2020 (F : ) MSFSPackages \ Community \ destroyer121-h-135.
It seems to me that it is as short as possible ⊠anyway thank you very much for the help.
Indeed, your path is quite short, so definitely not the cause.
The procedure I described to change resources directory works for sure (I did it 3 times for different reasons); but you must have another fast disk to store the backup during the âpseudo-installationâ process.
Maybe you have a mod interaction (as there is with Kinetic assistant). You could try to remove temporarily the others mods in /community to see if it works better ; or remove the folder named âdestroyer121-h-135â in your FS appdata folder (if you did not try that already) :
C:\Users\YourName\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages => it will be re-created at launch.
So I summarize:
1 I kept in the Community folder only the âdestroyer121-h-135â folder as well as another folder called âfs-base-ingamepanels-lnmâ (probably a folder related to LittleNavMap)
2 I deleted C: \ Users \ MyName \ AppData \ Local \ Packages \ Microsoft.FlightSimulator_8wekyb3d8bbwe \ LocalState \ packages \ âdestroyer121-h-135â which was recreated when MSFS started.
3 I created a flight with the cold H135 in the parking lot and immediately after activating the batteries, I found the same conditions, namely the inability to fly.
See captures:
Cold and Dark:
Try to do like me activate the engine and other at the same time and wait for everything to turn green and then you can take off without any problem and at ocasions you lose everything but it comes back without losing the control of the helicopters me it works
Please be more specific with: âactivate the engine and others at the same timeâ. What is meant by other? Does this refer to âcoald startâ?
Personally, I think the problem has a deeper cause regarding WASM which is referred to earlier!
Thanks for your post
My god⊠so many versions⊠I Icanât keep up !
I donât know how many you are to work on this, and how much time you spend, but the result is impressive !
Anybody notice, aircraft after some banks, can dive to the ground with no way to stop it. Not sure if this could be adjusted, older version did not do thisâŠ