I was using Blender2MSFS Exporter, but now I installed fresh Blender 3.2 and
the official Asobo Blender Exporter from GitHub. I was able to migrate
materials and see MSFS material parameters populate, however I have problems:
On export I see no XML file with GUID etc. created, and no option to create one like the old exporter had. What am I doing wrong? I see .gltf and .bin files and texture files in specified …/texture/ folder.
How do I structure the Blender file to export LODs? I see no options for that either.
I only see “gltf 2.0” in Blender export - it does have “MSFS Etensions” checkbox which I enabled. Is this the correct exporter? I installed and activated as described on the GitHub page.
I get an error if I select “custom properties” checkbox". What options should be selected?
Unfortunately the GitHub page only has installation and material migration
instructions. There is no documentation that I can see about how to actually
use the exporter, what options are available and what are they for.
You don’t export with File/Export but you need to pop up the N panel, you will
find the main exporter plugin May I suggest this little tutorial? https://youtu.be/NMiYmCspuOs About Lods setup, of you are familiar with the
“former” exporter, simply chance the collection names from x0, x1 and so on
with YourObjName_LOD0, YourObjName_LOD1 and so on, where YourObjName will be
the name of your glTF file, In the export settings, first tab, make sure you
select group by collections then reload LODS, you can change also the minSize
of each Lod
yes you export from the main file export menu - and select the gltf 2 option -
ASOBO has extended the existing Khronos code for MSFS, The N one is for multi
export.
Thank you! This is the next best thing for a manual. Now that I got the naming
right, it seems to be working. Haven’t tested in the MSFS but at least all
files are generated now and make sense.
That’s right, however 1st OP issue was no .XML via File/Export glTF 2.0 he’s
right, that way no .xml is not created with current plug-in version. We all
know that the single model .xml is quite easy to handmade, but since
multiexport is perfectly capable of exporting single models and their .XML, it
is my preferred choice for pretty much everything (and a single mnemonic
export workflow, rather that different ways to export single and multi
models!) Being an extension of Kronos gltf 2.0 exporter is very good design
idea, but has some weakness One of them is it can not override gltf 2.0 specs
E.g. there is a 3d here regarding emissive Msfs supports glTF emissive over
1.0 to enhance bloom, gltf 2.0 specs doesn’t, so every value the plugin ships
to Kronos parser is clamped to gltf 2.0 specs (max 1.0), manual mod to the
gltf file is still needed By the way, in the beginning the GitHub was
excitingly active. Has been a more than a month without news/bug/issues
fixing. M.me@SonantAlpaca promised the plugin will be shipped
with su10, it is going to be delayed @pepperoni you did a wonderful job with
that, keep up the good work! The Blender foundation is a sposored by
Microsoft, will be awesome that Msfs, it’s latest masterpiece, will officially
support is ASAP!!
You are right, I misread the OP. We are working on resolving the issues that
have been posted to the ASOBO git issues page. Glass, has_sy(i)metry
(spelling) and emissive>1.0. Things just have to be tested and get ASOBO
approval. Other issues, may be more complicated, and also need ASOBO approval.
I have little experinece in Blender, so I hope this makes some sense. What are
the chances of Asobo re-exporting all their base, and Premium/deluxe planes,
with the “Unique Identity Bit” set when the Model is exported. The sim
supports “Sub-Models”, but to use them , the base model would seem to need to
be exported with that :“Unique Identity Bit” set. Currently, No Asobo Planes,
or any other 3rd part planes (I have seen), have been exported with that bit
set, so for all those aircraft, the addition of a Sub-Model is not possible ?
If this is not the case, please can we have a better description of how to use
Sub-Models in the SDK. Sub_model option potentially opens up some great
opportunities, but it appears to be very limited, without the base Model being
exported correctly to support them.