• 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 Problem using the new Asobo GltF exporter with Blender

Messages
9
Country
australia
Dear forum.

I've upgraded to Blender 3.1 and using V1.1.5 of the GltF Asobo importer/exporter.
I have used the Simple Scenery Sample supplied with the MSFS SDK to test the new exporter and it produces the following error

gltf error.jpg


The key line is
Calling operator "bpy.ops.export_scene.gltf" error, could not be found.

I've set up my export and textures path as per the tutorials and using either the Objects option or the Presets option.
The exporter generates the collection.xml file but fails to produce the gltF with the above error. My object is a simple cube with a single PNG texture.


If anybody can advise as to what may be causing this it would be a great help.

Thank you.

Mark
 
how does the Simple Scenery Sample and the Blender exporter mix together?

can you share your blender file to double check is everything is ok with it?

a very fast "tutorial"

 
Why do you install developments programs under "Program Files" ? (name with blank in the name)

A) Blender exist under ZIP release which can be installed in 1 mn where you want ... for example under a dedicaced partition F:\Prg
B) In place to install your plugin under F:\Prg\Blender-3.x\... you can also copy/paste the plugin under your personal environment:
C:\Users\"MyName"\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\...
As this you can "upgrade" easily your Blender version: just unzip the next "Blender3.X+1" archive on F:\Prg\Blender-3.x and ALL your plugin are operational.

* This method has only one problem : when an another version will be release as Blender 4.0 you shoud create an another directory F:\Prg\Blender-4.x ;)
 
Why do you install developments programs under "Program Files" ? (name with blank in the name)

A) Blender exist under ZIP release which can be installed in 1 mn where you want ... for example under a dedicaced partition F:\Prg
B) In place to install your plugin under F:\Prg\Blender-3.x\... you can also copy/paste the plugin under your personal environment:

As this you can "upgrade" easily your Blender version: just unzip the next "Blender3.X+1" archive on F:\Prg\Blender-3.x and ALL your plugin are operational.

* This method has only one problem : when an another version will be release as Blender 4.0 you shoud create an another directory F:\Prg\Blender-4.x ;)



What Is the problem about installation path?
That Is the default One from the default installer, and also the nne approved by Asobo in latest installation notes

(By the way, i find the portable version slower than the installed One)

Inviato dal mio Mi 9 Lite utilizzando Tapatalk
 
how does the Simple Scenery Sample and the Blender exporter mix together?

can you share your blender file to double check is everything is ok with it?

a very fast "tutorial"
Hi Mamu,

Thanks for your response!

I used the Simple Scenery file structure just in-case that was having any kind of influence on the result even though I suspected it had nothing to do with it.
I've created many projects with the old exporter and they compile fine using the old exporter.
None of them compile with the Asobo exporter so I wanted to start a clean project with a clean slate and simply used a single cube as the only object and embedded the whole lot in the simple scenery file structure.
I tried with and without a texture following the tutorial mentioned above.

I did however add in the old exporter into the script library prior to testing the Asobo one. I later removed the old exporter and replaced the first release of the Asobo Exporter with 1.1.5. Still no worky!
When I get home tonight I will re-installl Blender 3.1 and the the 1.1.5 Version of the Asobo Exporter and see how that goes.
I do however feel this might not be the solution.

regards

Mark
 
Hi Mamu, I've attached the project as requested. The blender file is in the PackageSources\modelLib\blender folder
Thanks

Mark
 

Attachments

Ok,

I uninstalled all versions of blender and add-ons.
I went through the registry and removed all references to blender
Re-Installed Latest Version of Blender 3.1 and the Asobo Importer/Exporter
And... Same Error.

Now i'm confused. :(
 
Ok,

I uninstalled all versions of blender and add-ons.
I went through the registry and removed all references to blender
Re-Installed Latest Version of Blender 3.1 and the Asobo Importer/Exporter
And... Same Error.

Now i'm confused. :(
Make sure you also have nothing here:

C:\Users\"MyName"\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\

Confirm that that the simple scenery Is not required for the export

Just open a new blend file, add some object, texture them and export

I can take a look at you blen only in the evening, i'm sorry

In the meantime, can you try installing a standalone (portable) version of Blender and add the exporter to that ?




Inviato dal mio Mi 9 Lite utilizzando Tapatalk
 
@Mikea.at,
I pratice like this because I use 3 different versions of Blender: one to be compliant with X-Plane, one for FSX-P3D and the last to MSFS.
But everyone is free to do as they wish, simply AvalonWeb has problems and the purpose of a forum is to try to help people who are seeking help :cool:

@mamu,
When you're on the retreat, time doesn't matter (40 years as Admin/Developer at THALES).
The fact that this is the default path and recommended by Asobo, is in my humble opinion not an valid argument ;) Over the last 2 years, I have been very disappointed in the way they have developed.
When you develop for Microsoft simulators you use a lot of software and a number of them were made in the MSDOS constraint time with names without any blanks that had to respect the 8+3 character rule. The simpler the better.
That said, this is just an opinion on my part and everyone does as they please.

@avalonweb:
Your concern comes from the way you have defined your path to the Output directories: //..\Output\ (your syntax is incorrect).
By using the directory icon (to the right of the input field for the Folder) and browsing the tree to the desired directory, the export works fine.

PS: For more information, I recommend opening the Console (Windows menu - Toggle System Console) which gives more information on how the export is going.
 
Hi Lagaffe,
Again I appreciate your input and have already taken your advice about the use of the C:\Users\"MyName"\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\. I think that's an excellent way of organising the scripts and that's how I'm using mine.

The path created was done using the method you suggested. I also experimented with manual paths.
The xml file is being created in the path I've defined using all methods. But the error still persists and no gltf is created.

I will try the console and report back my findings

kind regards

Mark
 
Hi Lagaffe,

Console output:
Error: Python: Traceback (most recent call last): File "C:\Users\micro\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 171, in execute MSFS_OT_MultiExportGLTF2.export( File "C:\Users\micro\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 45, in export bpy.ops.export_scene.gltf( File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py", line 132, in __call__ ret = _op_call(self.idname_py(), None, kw) AttributeError: Calling operator "bpy.ops.export_scene.gltf" error, could not be found location: <unknown location>:-1
 
Hi Mamu

In response to your recommendation. I downloaded Blender Portable. Saved it to a USB Key and added the Asobo Importer/Exporter to the USB Key.
I tried it on my development machine and it failed with the same error.
I took it to my old laptop (very slow machine) and it worked just fine!

So there must be a machine level configuration in error somewhere. As I said, the old exporter works just fine on the Dev machine.

I would love to know if there are any other insights?

I really appreciate the responses I've got so far :)
Mark
 
Some ideas in bulk:
- do you have the "." as decimal separator ?
- have you select your cube before exporting ?

My steps:
- I have downloaded an other time your example
- unzip it under T:\Tmp
- I launched Blender 3.1.2 (plugin 1.1.4) browse and open you test.blend
- in the OutLiner, I change "Orphean Data" for "ViewLayer" (Cube is selected)
- in the plugin, at the right of Folder parameter, I click on the icone, browse directories and choose my outptut: currentlys the path indicated no change from your default (your previous choice )
- I export it

Here the contains of System Console:
Read prefs: P:\Users\Lagaffe\AppData\Roaming\Blender Foundation\Blender\3.1\config\userpref.blend
Read blend: T:\Tmp\PackageSources\modelLib\blender\test.blend
'Z:\Prg\Blender-3.1\3.1\python\lib\site-packages\extern_draco.dll' exists, draco mesh compression is available
11:42:45 | INFO: Starting glTF 2.0 export
11:42:45 | INFO: Extracting primitive: Cube
11:42:45 | INFO: Primitives created: 1
11:42:45 | WARNING: More than one shader node tex image used for a texture. The resulting glTF sampler will behave like the first shader node tex image.
11:42:45 | WARNING: More than one shader node tex image used for a texture. The resulting glTF sampler will behave like the first shader node tex image.
11:42:45 | INFO: Finished glTF 2.0 export in 0.023940086364746094 s
The glTF created can be easily be visualized under MCX.

To be sure, I have update my plugin 1.1.4 in 1.1.5 under Blender 3.1.2: I have the same results :cool:
 
This is the response I got from Boris that did the trick.

1649850562382.png

Some ideas in bulk:
- do you have the "." as decimal separator ?
- have you select your cube before exporting ?

My steps:
- I have downloaded an other time your example
- unzip it under T:\Tmp
- I launched Blender 3.1.2 (plugin 1.1.4) browse and open you test.blend
- in the OutLiner, I change "Orphean Data" for "ViewLayer" (Cube is selected)
- in the plugin, at the right of Folder parameter, I click on the icone, browse directories and choose my outptut: currentlys the path indicated no change from your default (your previous choice )
- I export it

Here the contains of System Console:

The glTF created can be easily be visualized under MCX.

To be sure, I have update my plugin 1.1.4 in 1.1.5 under Blender 3.1.2: I have the same results :cool:
Thanks for the unbelievable support from you guys. Had I not disabled the shipped glTF import add-on. The problem would never have occurred. Hopefully this thread will help others.
 
Thanks, Boris, for the solution above, I cannot get this to work at all in Blender 3.2. I DO have the latest blender-io-msfs 1.1.6. I can get it to work without any errors in Blender 3.1, but not 3.2. All of the required add-ons are enabled.

Just wondering if anyone else is having this issue? I've uninstalled and reinstalled Blender 3.2, and the add-on and have the same issue. I cleared out config files and everything for Blender 3.2 before reinstalling it so that it was a "fresh" copy of Blender. Then installed the add-on per instructions.

Bottom line of log file says it cannot pickle image object.

Anyone else have this issue with 3.2?

Thanks in advance,

TB2
 
Last edited:
Hi TB:

Uh-oh... now I've gotten my self into a 'pickle'. :yikes: :laughing:

https://www.yourdictionary.com/pickle

https://docs.python.org/3/library/pickle.html


Sorry I was not more explicit elsewhere in my posts, by raising the possibility that since Blender 3.0 apparently was the version available when the "Asobo" exporter was last updated, we may have to await an update from the developers of that "Asobo" Blender exporter for full compatibility with Blender 3.1 and beyond (aka "et.seq.").

https://en.wiktionary.org/wiki/et_seq.


I'll see if I can find anything about an add-on for Blender that enables live preview of MSFS glass tint color in Blender workspace.

NOTE: IIUC, according to the latter video by "MyPhysical World" at 7:40...

Blender 3.1 is required to enable viewport preview of glass translucency /color etc. :pushpin:

GaryGB

IIUC, Blender 3.1 et seq. requires use of the Asobo MSFS Exporter add-on.

Good Luck ! :)

GaryGB

Apparently the developers of the "Asobo" Blender exporter have not yet updated their code for Blender 3.2 et seq., as only Blender 3.1 may still have 'some' code compatibility with the "Asobo" Blender exporter.

https://developer.blender.org/T99504


I suggest watching this Repository on GitHub for any updates:



IIUC, there has been no actual "Asobo" exporter functional code commits to the "Asobo" exporter GitHub Repository since this:

https://github.com/AsoboStudio/glTF-Blender-IO-MSFS/commit/b2c04f29114700b55c72449830768fff1ca4b5f8

"adding all files
Luca Pierabella committed on Dec 13, 2021"

However, according to a report by Lagaffe, an initial commit was "empty"; eventually the functioning code was updated February 2, 2022.

https://www-pilote--virtuel-com.tra...tl=en&_x_tr_hl=en&_x_tr_pto=sc&_x_tr_sch=http


Perhaps a Flight Simulator 'Repository Suppository' might "get things moving" again ? :rotfl:


Hopefully, this MSFS exporter will be supported by "Asobo" on an ongoing basis that keeps pace with the rapid succession of Blender updates.


Considering the new features and breaking changes released since Blender 3.1, a "Asobo" exporter update is urgently needed.


I hope this does not become yet another piece of "Palindromic Abandonware" ...as has occurred with other Blender exporters.




In the mean time, as we are forced once again to "make do with what we have since FS' developers last threw us a bone", perhaps Lagaffe might offer some additional insight for us here at FSDevloper (in English), as to what, if anything, we may do with the "Asobo" exporter and a designated numeric version of Blender:

https://www-pilote--virtuel-com.tra...tr_sl=fr&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=sc

https://www-pilote--virtuel-com.tra...tr_hl=en&_x_tr_pto=sc&_x_tr_sch=http#p1084599


GaryGB
 
Last edited:
Back
Top