• 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 Blender2MSFS support thread

Status
Not open for further replies.
I had try to follow the instructions bellow but the only output is a xml file. No bin, no glt, no texture folder with the albedo and emissive maps inside. Of course I enabled the option "Batch export LODs". When I had only one model into a only one Collection I had success. Is the collections names correctly? Inside each collection are the models names correctly? My model name is galpao. I need help. Best regards.
"
It is possible to use the extended glTF2 exporter to generate multiple models of different level-of-detail (LOD) in one go. For this, you need to organize your Blender scene in the following manner:

Each LOD model needs to be contained in a separate collection. Tha name of the collection needs to follow the pattern of x##, where ## is the identifying number of the LOD - e.g. x00, x01, x02, etc.

When opening the exporter, expand the section labeled "MSFS" and enable the option "Batch export LODs". The exporter will now automatically scan your Blender scene and export each of the x## collections in a separate object, called <modelname>_LOD##.gltf."
 

Attachments

  • lod_collections.jpg
    lod_collections.jpg
    79.8 KB · Views: 290
  • msfs_blend_file_name.jpg
    msfs_blend_file_name.jpg
    25.3 KB · Views: 299
Luis Vargas said:
I had try to follow the instructions bellow but the only output is a xml file. No bin, no glt, no texture folder with the albedo and emissive maps inside. Of course I enabled the option "Batch export LODs". When I had only one model into a only one Collection I had success. Is the collections names correctly? Inside each collection are the models names correctly? My model name is galpao. I need help. Best regards.
"
It is possible to use the extended glTF2 exporter to generate multiple models of different level-of-detail (LOD) in one go. For this, you need to organize your Blender scene in the following manner:

Each LOD model needs to be contained in a separate collection. Tha name of the collection needs to follow the pattern of x##, where ## is the identifying number of the LOD - e.g. x00, x01, x02, etc.

When opening the exporter, expand the section labeled "MSFS" and enable the option "Batch export LODs". The exporter will now automatically scan your Blender scene and export each of the x## collections in a separate object, called <modelname>_LOD##.gltf."
Click to expand...

Ok, I got it after change the Collections' name to x01, x02 and x03.
 

Attachments

  • lod_collections.jpg
    lod_collections.jpg
    45.8 KB · Views: 279
Can't get the exporter to work in any version except 2.9, I get a callback error when I try to enable it.

Small Correction: It only works in 3.90 ALPHA, doesn't work for me in any other version.
 
mustang60348 said:
Can't get the exporter to work in any version except 2.9, I get a callback error when I try to enable it.

Small Correction: It only works in 3.90 ALPHA, doesn't work for me in any other version.
Click to expand...

It would help if you attached the error to a message also.
 
mustang60348 said:
I have been using 0.37 in Blender 2.90 since it came out. I had to 'reset' my blender or I got that error.
Click to expand...

Yep, a few other users have reported similar issues. It was never tested with 2.90 though and the instructions have always been for 2.83. That said, he is going to try and make it work with 2.90, but this version does not.
 
mustang60348 said:
Trying to do LODs, it seems to export fine BUT when I compile it, it says can't load GITF listener on LOD01 and fails.
Click to expand...

Did you find what the problem is? I have the same error with v.2.83

glTFLister | Failed to load model: 'C:\Users\PackageSources\modelLib\Hram\Hram_LOD00.gltf'.
ModelLibLister | Failed to spawn the gltfLister for input file C:\Users\PackageSources\modelLib\
PackageBuilder | Failed to spawn lister for asset group mymodellib (type ArtProj)
 
Has anyone managed to get collisions working on blender objects? I'm using Blender 2.83.5 with the Blender2MSFS 0.36.1 plugin

I have a simple cube in blender (elongated to represent a building) I then add a material to the cube and set the MSFS Material Params to MSFS Standard and just set an Albedo Color.

I then ensure "Collision Material" is ticked and export making sure the following are ticked:

Selected Objects
Custom Properties
+Y Up
Apply Modifiers
UVs
Normals
Tangents
Vertex Colors
Materials

but when I import the model into the game I can still fly right through the cube.
 
BMW969 said:
Did you find what the problem is? I have the same error with v.2.83

glTFLister | Failed to load model: 'C:\Users\PackageSources\modelLib\Hram\Hram_LOD00.gltf'.
ModelLibLister | Failed to spawn the gltfLister for input file C:\Users\PackageSources\modelLib\
PackageBuilder | Failed to spawn lister for asset group mymodellib (type ArtProj)
Click to expand...

I was using 2.9, switched to 2.83.6 and the problem went away. Make sure you use collections called x00,, X01, X02 and so forth and make sure you select Batch Export LODs, that's what worked for me.

After you export you should have the same number of .gitf files that you had collections, and each one should be able to be opened in a viewer, I use 3d viewer from the MS Store.
 
Thestonefox said:
Has anyone managed to get collisions working on blender objects? I'm using Blender 2.83.5 with the Blender2MSFS 0.36.1 plugin
Click to expand...

If you go back a few pages here, you'll eventually find a short conversation about this. I think this is mainly an issue on my end, as I haven't incorporated collision gizmos yet. I am not 100% sure how all of this works. On the one hand there's the "collision material" tick box, which should add the extension as expected. However, there's also a bunch of node-extensions to define "gizmos" solely for collisions. It appears to me that those gizmos should be used for object collision in a scenery, while the collision material could be used for something else - like UI? I really don't know yet.
I will find out eventually and add that function to the toolkit, this just hasn't been a priority for me at the moment.
 
Vitus said:
If you go back a few pages here, you'll eventually find a short conversation about this. I think this is mainly an issue on my end, as I haven't incorporated collision gizmos yet. I am not 100% sure how all of this works. On the one hand there's the "collision material" tick box, which should add the extension as expected. However, there's also a bunch of node-extensions to define "gizmos" solely for collisions. It appears to me that those gizmos should be used for object collision in a scenery, while the collision material could be used for something else - like UI? I really don't know yet.
I will find out eventually and add that function to the toolkit, this just hasn't been a priority for me at the moment.
Click to expand...

Yeah I think you may be right about the collision material being used for UI. According to the SDK docs it says:

`When checked, meshes with this material will have collidable faces. This can be used to create precise colliders, for example for mouse interaction. Use this with low-resolution meshes. `

So I'm guessing that means it has something to do with panel interaction. But saying that the SimpleScenery sample in the SDK, if you look at the Light_Sample gltfs they have the

```
{
"ASOBO_tags":
{
"tags":["Collision"]
}
}
```

set and that light sample model is collidable too. I don't see anything else in their gltf that would denote collidable though so maybe its something within the .bin file that is being exported from 3dmax?

P.S. I tried just adding that `"tags":["Collision"]` manually to my file and it didn't seem to make any difference, still couldn't collide with stuff.
 
A total noob here: I have a strange problem - I can't make the LOD changes show when I load the project into MSFS. When I export with correct collection names, LOD files geneate OK, XML shows them too, but I don't see any changes in Project Editor, and FPS hit doesn't change with distance. I copied model twice and added Decimate modifiers (0.3 and 0.5) to create lower poly LODs for Google Maps captured mesh. Named everything correctly. But it doesn't show the lower ones. In Blender lower LOD look horrible (on porpose, so I can spot it) but it doesn't appear in MSFS Project Editor. I tried default minsize in XML: 8-4, 25-15, 250-150, and I don't see lower LODs showing. My areas are large - 10 city blocks or so. Any idea what am I doing wrong? Also sometimes if I add objects they keep not showing up in MSDS Project Editor, but that I guess is not the exporter problem. I open project -> Build package -> load BGC into editor and new stuff is often not there... Sometimes it is. Just mentioning it in case it may be related. But new LOD are in, I see them mentioned in the console. They just do not show...
 
Are there any restrictions on models and textures? I have simple low-poly models without problems, but more complex models cause glTFLister | Failed to load model:
 
Hello Roman.
Seem that the Export LOD don't export correctly all LOD. I have some trouble with 2.83.
Try to export each LOD separtly (by showing only the LOD you want to export before exporting).

Change manualy values before compiling. I have almost correct LOD viewing with LOD like that :
<LOD ModelFile="blablabla_LOD00.gltf" minSize="5"/>
<LOD ModelFile="blablabla_LOD01.gltf" minSize="2"/>

Values must be probably attapted. It's seem that like in FsX, it's depending of the size of the object.
 
Status
Not open for further replies.
Back
Top