Version 2.0.0-dev.3.4

[lexaknyazev]

2.0.0-dev.3.4

New Features

• Added support for KHR_materials_variants extension.

• Added support for new PBR extensions: KHR_materials_ior, KHR_materials_specular, and KHR_materials_volume.

• Added MESH_PRIMITIVE_ATTRIBUTES_ACCESSOR_UNSIGNED_INT validation error, fixes Vertex attribute with UNSIGNED_INT (5125) componentType is not caught by the validator #154.

• Added new vendor prefixes: ASOBO, CITRUS, CLO, OFT.

Bugfixes

• Fixed incomplete JSON pointers for out-of-range array elements.

• Web build is now usable from a local filesystem.

Integration updates

• Added exe-archive and web-archive tasks to generate release archives.

• Fixed test names for KHR_lights_punctual extension.

• Changed default severity of UNSUPPORTED_EXTENSION to Info, fixes Consider lowering the severity of UNSUPPORTED_EXTENSION #159.

[donmccurdy]

One suggestion, otherwise changes look good!

Might be worthwhile to check for the (disallowed) combination of PBR Next extensions with KHR_materials_pbrSpecularGlossiness or KHR_materials_unlit.

There's also an interaction with volume and transmission...

The volume extension needs to be combined with an extension that allows light rays to pass through the surface into the volume, e.g. KHR_materials_transmission

... but perhaps no point in testing for that case until the translucency extension is also available.

[emackey]

This is looking good so far. It will be great to have support for specular/ior/volume.

[emackey]

Looks awesome, glad to have variants added to the list too. Tested a couple things in VSCode, seems to work fine.

[lexaknyazev]

@donmccurdy

Might be worthwhile to check for the (disallowed) combination of PBR Next extensions with KHR_materials_pbrSpecularGlossiness or KHR_materials_unlit.

Since the previous release, these two extensions get flagged when used with any other material extensions.

[emackey]

I hope I didn't jump the gun here, but since this got merged, I published dev3.4 to NPM, built from commit 22a8b17.