connomar
Resource contributor
- Messages
- 265
- Country
Yes it does, many thanks.
-
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 MSFS Asobo Official Blender exporter
- Thread starter rhumbaflappy
- Start date
- Messages
- 353
- Country
I don't understand how to export the lods. With the old plug-in, I hadn't problems to export it, but with the new plug-in yes. See the photo. Some advice? I'don't see lod_01, lod_02 and lod_03 files in my folder.
UPDATE: I were able to create bin e gltf Lod files, but now my problem is how to create only an xml file.
UPDATE: I were able to create bin e gltf Lod files, but now my problem is how to create only an xml file.
Attachments
Last edited:
- Messages
- 872
- Country
With that setup,
Un-tick group by collections
Rename your meshes as
Castello_LOD01
Castello_LOD02
Castello_LOD03
Click Reload lods (sometimes take several clicks)
Export
You Will end up exporting 3 glTF and 1 xml with the three lods
ciao!
Inviato dal mio Mi 9 Lite utilizzando Tapatalk
Un-tick group by collections
Rename your meshes as
Castello_LOD01
Castello_LOD02
Castello_LOD03
Click Reload lods (sometimes take several clicks)
Export
You Will end up exporting 3 glTF and 1 xml with the three lods
ciao!
Inviato dal mio Mi 9 Lite utilizzando Tapatalk
- Messages
- 872
- Country
Now that you have changed your setup
Rename the collections as
Castello_LOD0
Castello_LOD1
Castello_LOD2
Leave the group lod by collections SELECTED
click Reload lods
You can now select all the 3lods, assign them their minSize and Export
At this time, you Will end up with a single .xml called Castello.xml including the 3 lods
----
In pratica, l'exporter crea nuovi xml in base al nome degli oggetti (o delle collection). Se trova lo stesso nome ne cerca eventuali lod in base al prefisso suffisso _LOD0, LOD1 oppure _x0, x1 etc
Le regole che segue il nuovo exporter sono le stesse del exporter di 3ds max
Multi-Exporter
docs.flightsimulator.com
Inviato dal mio Mi 9 Lite utilizzando Tapatalk
- Messages
- 353
- Country
ok if you have base color, but if you have trasparent texture? I Applied Alpha Blend, and alpha clip to a trasparent texture in png format, but I see the trasparent black on msfs2020.
another question I have day\night problem, I solved with modelconverter, but it isn't possible having day\night cycle applied on blender and have this problem. If I use emission texture in blender I see it in my object.Is It normal this? IF I see my object in ms2020 without modelconvert, I see night texture during the day.
another question I have day\night problem, I solved with modelconverter, but it isn't possible having day\night cycle applied on blender and have this problem. If I use emission texture in blender I see it in my object.Is It normal this? IF I see my object in ms2020 without modelconvert, I see night texture during the day.
Last edited:
FoxtrotScenery
Resource contributor
- Messages
- 86
- Country
So you have a texture for the base colour that has transparency if I understand it correctly?
If that's the case, use the image in the "Base Color" slot:
Then set the "Alpha Mode" to "Blend" and keep the "Base Color" setting above that setting (so not the image!) as white:
As far as I know that should work
- Messages
- 353
- Country
Hi Foxtrotscenery, many thanks. I will try it.
UPDATE: it worked!
Last edited:
- Messages
- 72
- Country
1. Create your different LOD models and group them in separate collections. Name these collections with the main name (Hangar) and append the appropriate LOD suffix (_LOD0, _LOD1 and so on to each one).
2. Open the Multi-Export tab and set the Settings to the location of where your textures should go, your copyright and what to export.
3. Go back to the Multi-Export Objects tab and set it as shown:
3a. Grouped by Collections checked, Show Hidden Objects optional(not important now). You will see your LODs grouped by the main name of the objects.
3b. Generate XML checked
3c. Open the Folder dialog and point to the folder in your project you want to export to.
3d. Make sure all the LOD collections you want to export for this model are active.
3e. Check the box next to the LOD entry.
3f. (important!) Make an entry in the LOD value box for each LOD model. The last one can remain 0 (This seems to mean the Sim will decide when to stop displaying the lowest LOD model.) Later you can adjust these values, but for now start with maybe 8 for a hangar. What the number means is that that model will stop being drawn when a sphere enclosing it is less than, in this case, 8 percent of the vertical view field of your screen. For long models like bridges, you may have numbers as high as 1000 meaning when the surrounding sphere is less than 1000 percent of your vertical screen height, go down to the next lower LOD.
4. Click Export and go check the destination for an XML and a .GLtf and .bin for each LOD model you had selected.
5. Open the .xml file and note that there is an MinSize entry for each LOD.
6. Each model needs a GUID to uniquely identify it in the simulator. If there was no GUID at all (like this is your first export), it will be generated. If it was there from a previous export of this model, it will not be overwritten. If you click Overwrite GUID, though, a new GUID will be written, and you'll have to start over on your placement and other stuff as you place and adjust the model.
Note: If you get an error on Export, check first that you've got all the collections active. If already have your GUID and XML, and you only want to export one of the LODs, uncheck the MultiExport LOD items you don't want to export BUT uncheck the Generate XML or you'll clobber the other LODs in the XML. In this way, you can hide the other LOD collections and work on one LOD at a time. Note also that this exporter is, IMHO, a wonder over the old one for working with LODs.
I apologize for the laughable hangar design, but I threw something together in ten minutes to illustrate this procedure.
HTH. Let me know if you need more pictures.
2. Open the Multi-Export tab and set the Settings to the location of where your textures should go, your copyright and what to export.
3. Go back to the Multi-Export Objects tab and set it as shown:
3a. Grouped by Collections checked, Show Hidden Objects optional(not important now). You will see your LODs grouped by the main name of the objects.
3b. Generate XML checked
3c. Open the Folder dialog and point to the folder in your project you want to export to.
3d. Make sure all the LOD collections you want to export for this model are active.
3e. Check the box next to the LOD entry.
3f. (important!) Make an entry in the LOD value box for each LOD model. The last one can remain 0 (This seems to mean the Sim will decide when to stop displaying the lowest LOD model.) Later you can adjust these values, but for now start with maybe 8 for a hangar. What the number means is that that model will stop being drawn when a sphere enclosing it is less than, in this case, 8 percent of the vertical view field of your screen. For long models like bridges, you may have numbers as high as 1000 meaning when the surrounding sphere is less than 1000 percent of your vertical screen height, go down to the next lower LOD.
4. Click Export and go check the destination for an XML and a .GLtf and .bin for each LOD model you had selected.
5. Open the .xml file and note that there is an MinSize entry for each LOD.
6. Each model needs a GUID to uniquely identify it in the simulator. If there was no GUID at all (like this is your first export), it will be generated. If it was there from a previous export of this model, it will not be overwritten. If you click Overwrite GUID, though, a new GUID will be written, and you'll have to start over on your placement and other stuff as you place and adjust the model.
Note: If you get an error on Export, check first that you've got all the collections active. If already have your GUID and XML, and you only want to export one of the LODs, uncheck the MultiExport LOD items you don't want to export BUT uncheck the Generate XML or you'll clobber the other LODs in the XML. In this way, you can hide the other LOD collections and work on one LOD at a time. Note also that this exporter is, IMHO, a wonder over the old one for working with LODs.
I apologize for the laughable hangar design, but I threw something together in ten minutes to illustrate this procedure.
HTH. Let me know if you need more pictures.
Last edited:
- Messages
- 683
- Country
Thanks 
Hi
do you know when Asobo, will integrate "officialy", in the SDK Documentation, the "Blender Plugin", with all the chapters
(as they did for 3DSMax plugin),
if i well understood, last SDK interview, they talking about that will be happens right?
but, SU10 arrive, and i not see any "Blender Plugin Chapter"
do you know when Asobo, will integrate "officialy", in the SDK Documentation, the "Blender Plugin", with all the chapters
(as they did for 3DSMax plugin),
if i well understood, last SDK interview, they talking about that will be happens right?
but, SU10 arrive, and i not see any "Blender Plugin Chapter"
- Messages
- 72
- Country
Only if it gets you going in the right direction and didn't insult your intelligence. Remember, mikeat.at, when we fixed the batch LOD xml generation in the original. This new one makes working with LODs a breeze. I'm thinking of supplying that hangar to Asobo for a generic. I won't even charge them for it!
- Messages
- 683
- Country
No you didn't insult my intelligence.. Learning or attempting too. Thanks for your expertise @PhysicsTeacher
BobM.
BobM.
- Messages
- 3
- Country
I have been unable to find a solution to the following error I am receiving in MSFS when building a package that includes a model with 8 point lights.
"required extension not supported: KHR_lights_punctual"
Are there additional steps that need to be taken or is this feature currently not working? Thank you in advance for your help if you are able to provide it.
"required extension not supported: KHR_lights_punctual"
Are there additional steps that need to be taken or is this feature currently not working? Thank you in advance for your help if you are able to provide it.
- Messages
- 872
- Country
- Messages
- 3
- Country
Thank you for the response @mamu
I will try that again but it seems like I only get the error when I export with that option checked.
I will double check this when I get a change to get back to the project. Thank you for the suggestion
- Messages
- 3
- Country
So I tried again with checking the 'Punctual Lights' box. I exported as usual and got the same error. Unchecking the box resulted in no errors, but also no point lights in sim.
I redownloaded the plugin and tried again and got the same error.
Here are shots of the options selected for the point lights themselves (if that has anything to do with it) And the error message when I try to build the package to import the new model.
I redownloaded the plugin and tried again and got the same error.
Here are shots of the options selected for the point lights themselves (if that has anything to do with it) And the error message when I try to build the package to import the new model.