• 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.

MSFS Packaging Errors

Messages
51
hey guys,
So im working on a plane, have bben for the past few weeks. As a starter, i decided to use the naming convention of the SimpleAircraft sample, so i wouldnt have to rename every single files and folders. Its been working perfectly, i've built the package maybe 30 or 40 times , to test things and to update de 3D model in sim. Always used the package tool thats in the SDK folder. Since this morning, i get this error, and as far as i can see, the Gltf are not getting packaged, so neither are the json (manifest, layout). I have done nothing that i havent done before, meaning pushing few vertices around, adjusting some textures etc. I cant put my finger on why its happening. Thanks for your help :)

 
Messages
118
Country
unitedstates
It is hard to tell what is happening because we cannot see the errors that happened above the lines in your screenshot. Scroll up in your Command window. There should be errors that are preventing your gtlf from compiling.
 
Messages
926
Country
australia
In my experience, the package tool doesn't tell you what errors there are when it compiles a model. The only clue is the "Output path does not exist" for the gltf which tells you it hasn't compiled. If the model hasn't compiled it usually because I haven't exported all the parts hierarchy or there is an animation without a matching name in the xml.

First debugging step for me would be to select a single part in your model and export that and see if that compiles. That's where I would start.
 
Messages
51
In my experience, the package tool doesn't tell you what errors there are when it compiles a model. The only clue is the "Output path does not exist" for the gltf which tells you it hasn't compiled. If the model hasn't compiled it usually because I haven't exported all the parts hierarchy or there is an animation without a matching name in the xml.

First debugging step for me would be to select a single part in your model and export that and see if that compiles. That's where I would start.
Spot on, i actully spent a night disabling collection one by one, exporting, compiling etc until i find whats going on. Turns out its my altimeter gauge that somehow decided to brick the whole model. Trouble is, i can see nothing wrong with it. Anyway, probleme solved :)
And i can confirm most of the time, the packaging tool doesnt really give you an obvious red line pointing you to the problem.
 
Top