• 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 Building / Exporting, no changes on final package. (SOLVED)

Messages
237
Country
us-newyork
Hello everyone,

I'm using the latest SDK release as of November 11, 2022 v.0.20.3 for MSFS. I attempted to see the changes I made to my scenery with the SDK and after building the package, and viewing it in the sim, no changes were displayed.
So, I can see my changes only during SDK mode but not after exporting/building. I build the package both ways, inside the sim with SDK and outside with fspackagetoo.exe. Each time expecting to see a different result in game on separate sim-loading-cycles.

The changes I made were utilizing polygons and creating grass areas, as well adding default trees, and default Asobo 3d trees too. What is my folder missing that it's not building?

Thank you.
 

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,427
Country
us-wisconsin
If you eixt the sim, copy the package to Community, and restart the sim, does it show as expected?
I have found polygons often do not show in the DevMode after reloading the project. I have to use the development camera, elevate to the stratosphere and dive down to near ground level before the will show.
 
Messages
237
Country
us-newyork
If you eixt the sim, copy the package to Community, and restart the sim, does it show as expected?
I have found polygons often do not show in the DevMode after reloading the project. I have to use the development camera, elevate to the stratosphere and dive down to near ground level before the will show.
When the package is pasted in the Community, and then I start the sim, it doesn't show as expected. It shows an older version.

So, these are basically grass areas I placed using polygons.

I'm also looking for that file we were told not to include in our builds. I forgot the name of it. Maybe you know what I'm talking about. @rhumbaflappy
 
Messages
18
Country
us-illinois
Hello everyone,

I'm using the latest SDK release as of November 11, 2022 v.0.20.3 for MSFS. I attempted to see the changes I made to my scenery with the SDK and after building the package, and viewing it in the sim, no changes were displayed.
So, I can see my changes only during SDK mode but not after exporting/building. I build the package both ways, inside the sim with SDK and outside with fspackagetoo.exe. Each time expecting to see a different result in game on separate sim-loading-cycles.

The changes I made were utilizing polygons and creating grass areas, as well adding default trees, and default Asobo 3d trees too. What is my folder missing that it's not building?

Thank you.
Have you tried changing the visibility order of the polygons?
 
Messages
18
Country
us-illinois
I did change the visibility order of the polygons. But it's not only the polygons not showing, also added Asobo objects don't show up either.
I would delete the folder inside package and build your entire project again. It looks like is reading an old data.
 
Messages
237
Country
us-newyork
I would delete the folder inside package and build your entire project again. It looks like is reading an old data.
I did that as well, multiple times actually. There's a file, in the SDK project folder, which is not allowing to process the new items to the final build package.
 
Messages
18
Country
us-illinois
You probably did this but ill ask anyway, did you delete the project folder from your community folder?
And do you get any errors?
 
Messages
237
Country
us-newyork
You probably did this but ill ask anyway, did you delete the project folder from your community folder?
And do you get any errors?
Tried this. Brough the package back in, and saw an old version. SDK isn't building the new information I've implemented. :confused:
 
Messages
18
Country
us-illinois
Tried this. Brough the package back in, and saw an old version. SDK isn't building the new information I've implemented. :confused:
Check the asset group names and path to make sure they are set correctly , also make sure when you export the project the names are correct for the xml file and all other files. Other than that i have no idea whats wrong
 
Messages
237
Country
us-newyork
Check the asset group names and path to make sure they are set correctly , also make sure when you export the project the names are correct for the xml file and all other files. Other than that i have no idea whats wrong
okay, I will check on that when I cycle in MSFS today. Thanks
 
Messages
237
Country
us-newyork
Hello there, anyone else has any suggestions? I've returned to this project, and I am still unable to view the work done on the airport. Thanks.
 
Messages
237
Country
us-newyork
Solved. The package was a copy that was transferred to another drive when I moved Dropbox to an external drive and it kept using the same directories with the exported builds. I went to the package of it's birth drive location and now it works well like it should. Thank you guys.
 
Top