As per the title, I have been unable to get this mod to install correctly. I am posting screenshots of:
I have re-downloaded the mod several times, and re-extracted it using both 7-zip and windows file explorer unzip feature.
Any help is greatly appreciated. Thanks.
Not sure if related, but curious why your path has Microsoft.FlightDashboard_xxx vs Microsoft.FlightSimulator_xxx (not in front of my own computer, but I’m pretty sure the latter is how my path is set up).
That’s the path, as I understand it, for a MSFS installation via Steam.
This (Install Instruction for FBW A32NX) also applies here, just with the folder you have (workingtitle-g3000). Possibly look for other airplanes / nav systems (e.g. WT CJ or G1000NXI) installs which might interfere and temporarily remove them.
flybywire-aircraft-a320-neo folder into your community package folder.It is located in:
C:\Users\[YOURUSERNAME]\AppData\Local\Packages\Microsoft.FlightSimulator_<RANDOMLETTERS>\LocalCache\Packages\Community.flybywire-aircraft-a320-neo folder into your community package folder.It is located in:
C:\Users\[YOUR USERNAME]\AppData\Roaming\Microsoft Flight Simulator\Packages\Community.That worked! Thank you!
Does this mean that all mods should go into this folder?
C:\Users\steve\AppData\Roaming\Microsoft Flight Simulator\Packages\Community
Should my mods reside in both folders?
Yes all mods in this folder and only this, not the other.
Glad it worked. Have fun.
Ha! I was editing my response the same time you were responding.
Should the mod files reside in both folders?
Thanks again for your help.
No. See my edit.
If you could mark my post as the solution so others with the same problem know quicker where to look.
No. This folder should be left alone. Addons must be put into:
your drive (c,d,e whatever you installed it):\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Community
Thanks for your response. In retrospect, I think it was a mistake to purchase MSFS through Steam, mainly because of the conflicting info found by google search as to where the Community folder is located. I found many online references that said that after a Steam install you should put mods into:
User > AppData > Local > Packages > Microsoft.FlightDashboard_randomnumber > LocalCache > Packages > Community
For me this didn’t work; however, the Community folder location suggested by SierraHotel2873 did work (thanks again!). So I have an installation with two different Community folders, only one of which works for Mods.
I do not have a SteamLibrary folder. But I do have:
LocalDisk (C:) > Program Files (x86) > Steam > steamapps > common > MicrosoftFlightSimulator > Packages
However, there is no Community folder located there. I can only assume that during a Steam MSFS installation, the creation of the Community folder(s) is based on some other variable, possibly something unique to my system.
I greatly appreciate the comments of this Forum’s participants, without whom I’d still be trying to figure out why my mods don’t work!
The correct Steam path is C:\Users\YOUR USER NAME\AppData\Roaming\Microsoft Flight Simulator\Packages\Community
But the path is hidden, so you must first set explorer to show hidden files.
And I strongly recommend that you use Add On Linker, then it will be much easier to organize everything.
Thanks. I always set file explorer to show hidden files as well as extensions. I’ve heard of Add On Linker but hadn’t tried it because I only have about 4-5 files in my Community folder. I’ll give it a shot since I’ll likely add more mod content going forward.