aothms
commented
7 years ago Ok, perfect, feel free to disregard this change, it's just sth trivial to make our example [1] render well.
Question: are you able to use glTF V2 in your pipeline, and thus use xeogl's new glTFModel component? Note that it's not backwardly-compatible with glTF V1.
I think so, I just convert a trivial collada file using the standard collada2gltf converter.
BTW at some point, I'm going to circle back and update BIMSurfer to use the latest xeogl, since the API changes are fairly minimal with regard to BIMSurfer (mainly about storing all the components in a xeogl.Model rather than a xeogl.Collection, which got removed from the engine since then).
I saw that, would be great to get in sync again. Anything special in terms of new features? :)
[1] http://opensourcebim.github.io/BIMsurfer/docs/example_glTF.html
xeolabs
Hi Thomas! I actually rewrote the glTF loader to support glTF V2.0: https://github.com/xeolabs/xeogl/blob/master/examples/js/models/glTFModel.js
And I'm about to merge the rename-opacity-to-alpha branch into master, which will fix transparency for glTF, and will change the way transparency is managed within xeogl.
Question: are you able to use glTF V2 in your pipeline, and thus use xeogl's new glTFModel component? Note that it's not backwardly-compatible with glTF V1.
BTW at some point, I'm going to circle back and update BIMSurfer to use the latest xeogl, since the API changes are fairly minimal with regard to BIMSurfer (mainly about storing all the components in a xeogl.Model rather than a xeogl.Collection, which got removed from the engine since then).