• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Save to Community File

Messages
7
Country
unitedkingdom
Just tried to rebuild EGCC and although it will save it when build is pressed it comes up with the box saying saved in community file but nothing appears there. this has been working ok since before recent update. I have found it however in the packages section of the EGCC project file. WTD
 
May I ask how?

Since the recent update, the build does not work anymore here. When trying to build the project, MSFS automatically starts (never did that before) and in the dos-window the failure "provided project definition file does not exist" shows up.

The pop-up "copy to community folder?" does not do anything. Can't find the file in the packages section of project file either.
 
I presume you have redirected ADE content to the new fs base generic airports file. Make sure you have updated the ADE installation to the latest as instructed in the first two hot file releases and it should work . I had missed one of the updates.
 
The pop-up "copy to community folder?" does not do anything. Can't find the file in the packages section of project file either

It is recommended to turn off the Copy to Community Folder option. I believe (hope) this was documented somewhere as an issue. This means you manually add the built package. I think someone recommended using Addon-Linker (is that what it is called?) which I believe allows you to set up folders outside your community folder where packages can be placed. Perhaps someone will confirm this (or otherwise.

https://www.fsdeveloper.com/forum/threads/ade-2020-alpha-21-hotfix-4.454244/page-3#post-899709 post #42
 
Yes, Addon Linker allows you to put your mods somewhere else and then it creates symbolic links to them inside you community folder. The main advantage is that you can place you addons where you want and you can easily select/deselect them (even make presets) to load with MSFS.
 
It is recommended to turn off the Copy to Community Folder option. I believe (hope) this was documented somewhere as an issue. This means you manually add the built package. I think someone recommended using Addon-Linker (is that what it is called?) which I believe allows you to set up folders outside your community folder where packages can be placed. Perhaps someone will confirm this (or otherwise.

https://www.fsdeveloper.com/forum/threads/ade-2020-alpha-21-hotfix-4.454244/page-3#post-899709 post #42
Jon, I do not have the copy to community folder option enabled but as others have posted the build is failing with error "Provided project definition file does not exist."
 
"Provided project definition file does not exist."
This is a consequence of attempting to build a package using "fspackagetool.exe," since the most recent update. It is an error on the part of Asobo and until it is fixed, there is no way to compile packages without activating the "build" function within DevMode. I do not know if ADE can access the build function without calling fspackagetool.exe, that would be the only workaround, until it is fixed.
 
This is a consequence of attempting to build a package using "fspackagetool.exe," since the most recent update. It is an error on the part of Asobo and until it is fixed, there is no way to compile packages without activating the "build" function within DevMode. I do not know if ADE can access the build function without calling fspackagetool.exe, that would be the only workaround, until it is fixed.
Thank you Rick for the helpful point to solution. I first tried running fspackagetool.exe from the console (DOS Prompt) but it died the same way as if it were called by ADE. I opened MSFS and turned on Developer mode, loaded my project xml in the ADE20 Projects location and then did a BUILD & EXPORT to place the compiled project in the appropriate Packages folder. First time I had a few minor errors to clean up but second time worked like a charm.

So many thanks.. no longer dead in the water with my improvements to KHOU Hobby.
 
Last edited:
I do not know if ADE can access the build function without calling fspackagetool.exe, that would be the only workaround, until it is fixed.

No - it calls the fspackagetool
 
Back
Top