• 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 ADE HF5 can't compile anymore

downscc said:
Jon, I changed my project path from e:\ADE20 Projects\ to simply e:\ADE20 and running fspackagetools.exe creates the airport without my user model. It persists in throwing an error on the model asset with the error message including this: "Input: E:\ADE20 Projects\.... etc.

I cannot find where this latent reference exists. I deleted the model information and re-did the User Model Manager but something is still referencing the old pathname. Ideas?

UPDATE: Holy Moly, it took some time and a lot of "well let's try this, and let's try that" but I've removed the latent references to the old path name. Under the project root directory (in the projects folder) there is a folder _PackageInt with a number of sub-folders including some that are nested. The solution I found was to delete ALL files in the _PackageInt folders/subfolders but DO NOT delete any folder. Just delete files. Started working as good as new with new project folder name.
Click to expand...

Hi Dan:

Thanks for the followup. :)

I'm curious if you would be willing to post some step-by-step details of your troubleshooting methods cited above, for those of us who prefer to use ADE instead of DevMode GUI ? :scratchch

Since ADE does not (yet ?) offer a "Clean" feature as is available via DevMode GUI, it would be helpful to know more about this.

In particular, could you explain what "Started working as good as new with new project folder name" ...and in what application ?


Thanks for sharing your discovery with us, as many of us are with you in preferring ADE over DevMode. ;)

GaryGB
 
Last edited:
Gary: My troubleshooting wasn't structured and I hit a lot of cul de sacs. This all started where I read a post by Jon that indicated the compiler (fspackagetool.exe) was truncating a path that contained a space. So I changed my path from e:\ade20 projects to e:\ade20 and then found that the compiler would compile the airport object but threw an error for the model asset, this error message indicated it was looking for the asset in the old path.

I looked for anything that referenced the old path instead of the new path. Nothing in the PackageSources did that, including the bin/gltf/xml/png files that are the model source. The User Model Manage kept throwing an error as well because it kept looking for the old path. I never found the path name in any file that was in the _PackageInit folders but I noticed the data was encrypted in some kind of binary format. On a wild ass guess I deleted those files, put the model files back into the respective folders and successful run user Model Manager (this compiles the model bgl only) successfully. Now I was able to compile the project including the modellib and create a project package.

My method of using fspackagetool directly is to put a copy of it in the project root directory, along with a shortcut to cmd.exe (the console window). Thus, I can open the console window and launch fspackagetool directly.

After I got the compile working using the console, I then found that using the Build menu command in ADE would also work. My approach was to troubleshoot using the console window and not ADE to eliminate ADE as the problem.
 
Last edited:
Thanks Dan. :)

I had not yet tried looking in the 3D model *.BIN file for a URI path with a Hex viewer.

I guess either a 3D model URI path is OK or not; and if not, one must "clean" that source and the files in the __PackageInt folders.

Perhaps Jon will add a "Clean" option to ADE 2020 for 2-Way Editing in the future ? :wizard:

GaryGB
 
downscc said:
Jon, I changed my project path from e:\ADE20 Projects\ to simply e:\ADE20 and running fspackagetools.exe creates the airport without my user model. It persists in throwing an error on the model asset with the error message including this: "Input: E:\ADE20 Projects\.... etc.

I cannot find where this latent reference exists. I deleted the model information and re-did the User Model Manager but something is still referencing the old pathname. Ideas?

UPDATE: Holy Moly, it took some time and a lot of "well let's try this, and let's try that" but I've removed the latent references to the old path name. Under the project root directory (in the projects folder) there is a folder _PackageInt with a number of sub-folders including some that are nested. The solution I found was to delete ALL files in the _PackageInt folders/subfolders but DO NOT delete any folder. Just delete files. Started working as good as new with new project folder name.
Click to expand...
Hi. Tried the "Holy Moly" with my simple mod of LFMP. Did not work. No new files were written into the folders under _PackageInt. I do hope somebody can solve this or find a workaround that I understand.
 
I don't get error messages anymore, but I don't get builds either. Just the message box "Package built" (after "This may take some time" which it doesn't anymore).
 
Sueede said:
I don't get error messages anymore, but I don't get builds either. Just the message box "Package built" (after "This may take some time" which it doesn't anymore).
Click to expand...
Note I wrote that I removed latent references to the old path name, for example a ModelLib reference existss in PackageDefinitions\<projectname>.xml file. There were a couple of others as well that I've forgotten but your project root directory contains user-model-list.dat that I deleted while trying to make the user model manager work. This process wasn't easy which is why it earned a holy moly.
 
My workaround:
Before compiling MSFS has to be closed.

I drop the airport project .xml file on to the fspackagetool.exe in the MSFS SDK folder (no need to rename folder to one without spaces). The package is created (compiled) in the right ADE projects folder.

After hitting enter and closing the console window as well as the MSFS splash screen with the error message.

I can use the ADE tool (Alt-C command) for copying the package into MSFS Community. After having copied a new package to any other folder (like Addons Linker) manually a first time, ADE Alt-C command copies the projects to that new location,

Of course I also have to shut the console window and MSFS splash screen that tells me something is wrong. Then I start MSFS the proper way.
 
Last edited:
You must log in or register to reply here.
Back
Top