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

Workflow when updating a gltf object in scenery

Messages
20
Country
australia
Hi there
I have recently tried my hand at MSFS scenery again and trying to get to grips with the system. I am creating a custom object using Blender and have successfully imported it into my scenery. With the object being work in progress, I do update it often to see if it still works within the scenery (long bridge object). I find that every time I export the gltf from Blender, I have to open MSFS, go into dev mode, build the project, exit MSFS entirely, and launch it a second time to get the sim to detect my new custom object.
Having to launch the sim once to build, exit, and launch it a second time to view the results of my new gltf object is very time consuming.
My project is outside of the Community folder. Is there a better way of doing things or is this just the way it is?
 
I put a shortcut to FSpackageTool.exe into each project folder, so when I add or edit an object I just drag the project xml file onto the shortcut to rebuild without having to load the sim.
 
Wow, thanks a lot for that. So no need to clean the build or anything - will this method automatically detect the new version of the gltf file and build it into the package?
 
Nice trick.

Still, I'm not sure if I understand the question.

Usually the Objekt will show immediately for me. No need to restart sim with the normal editor either.

I make changes on an object in blender, re-export it and 1 sec later the new version of the object will show.

At least before Update....now nothing at all shows... But that's another thing
 
I find that if you make changes to an existing object in a project and export that object from Blender while the project is loaded in the Scenery Editor in Devmode, then the changes to the object will show up in the sim within seconds, without having to recompile the project. But if it is a new object that has never been used in the sim before, then I find that you do have to compile it at least once, then close and reopen the project that contains the object, before you can select the object for insertion into your scene. This should not require a restart of the sim. Just use FSpackageTool.exe on the project XML file, or use the Rebuild All command in the Project Editor. My experience is based on version 0.10 of the SDK. Don't know if any of this changed in version 0.12.
 
jup. Thats how it was. New objects needed a fresh load into the project but already placed objects, at least when guid and name etc didnt change, it appeared same second when the model was changed.

Sadly it seems those times are over for a handful of ppl.... Didnt find a way without to have to restart the whole sim to make things appear. Or even populate the Scenery dropdownlist....

I may try that other way that was mentioned here.
 
maybe the small changes still work. Im not sure. Probably everything still works, as long it doesnt need a rebuild. In this case one forst has to place the output package into community folder again...
 
Back
Top