- User Since
- Oct 18 2005, 12:13 AM (709 w, 1 d)
Mon, May 13
Mar 18 2019
Upstream issue: https://github.com/KhronosGroup/glTF-Blender-IO/issues/358
Mar 4 2019
@Tobias Heinke (TobiasH) In the import/export section, the lowercase "if" was intentional, to match the formatting of the rest of the section. The way this section is structured is a little odd, as each heading is considered part of the sentence that follows it. Probably this whole thing needs a rewrite at some point, but putting a capital letter there doesn't seem to be the correct solution.
Mar 1 2019
@Julien DUROURE (julien) Can we add this? Thanks!
Feb 28 2019
Feb 27 2019
@Julien DUROURE (julien) There should be some new images that go along with this change, can you check?
Jan 4 2019
Issue copied upstream: https://github.com/KhronosGroup/glTF-Blender-IO/issues/205
Dec 13 2018
@Ivaylo Gogov (ivaydesign) glTF version 2.0 does not ship with raw shaders, as they are not very portable between different platforms (WebGL, OpenGL, Vulkan, Direct3D, Metal...). Often a shader is very deeply paired with the inner workings of the particular rendering engine it's used by, and can't meaningfully move between engines even on the same platform. glTF 1.0 had WebGL shaders and was tied specifically to the WebGL platform for this reason, but in glTF 2.0 the shaders have gone away, replaced by PBR (Physically Based Rendering) and a set of well-defined texture maps that enable a wide range of physically plausible materials. Thus, glTF 2.0 enjoys platform-independence and engine-independence.
Dec 6 2018
@Ivaylo Gogov (ivaydesign) In the past few days there have been major improvements to the export settings, but unfortunately a serious bug has crept in with the "Save Settings" feature. I believe this will be fixed in the next few days.
Nov 24 2018
Hi all, may I ask a process question here? I'm curious what's the best strategy to keep development efforts synchronized between here and the Khronos GitHub repository. I believe the plan is for issues and patches to continue to be managed on GitHub, unless we create administrative problems in so doing.