Blender 2.91 support and more components!

• Update to support Blender 2.91, namely fixing lightmap export. This version of the exporter will NOT work with older versions of Blender. If you need to keep using 2.83 you should use the old version of the exporter. Versions in between 2.83 and 2.91 may work with one or the other, but are not considered supported.
• Fix nav-mesh component not exporting properly. You should now be able to specify custom nav meshes by adding the nav-mesh component to a mesh. You probably also want to add the visible component to it, to prevent it from showing up (though having it be visible could be useful for debugging).
• Add background, fog, audio-settings, image, video, audio, link, and visible components (thanks @rawnsley for the PRs!). The media elements have issue when being used in non-scene gltfs. We will need to fix this on the Hubs side.
• Some misc code cleanup of hacks no longer needed due to gltf exporter updates.

Component UI Improvments

A bunch of miscellaneous cleanups and improvements to component interface

• cleanup components UI + make component properties collapsible
• add nav-mesh, uv-scroll, and waypoint as default components
• fix exporting vec properties
• add support for enum properties
• add support for image properties
• support for description, subType, and unit annotation on properties
• support for grouping components into categories
• fix python warnings about "attributes" usage on dynamic classes

Fix bone components

The last release assumed a later version of the gltf exporter (that will actually be shipping with Blender 2.9) which broke the exporting of components on bones. This release fixes that for 2.83.

Add support for MOZ_lightmaps and Blender 2.83

This adds support for MOZ_lightmap exporting and upgrades to be compatible with Blender 2.83 (it is NOT backwards compatible with 2.82, or more specifically the GLTF addon that ships with 2.82)

To export a lightmap, create a MOZ_lightamp node from the Add > Hubs menu and hook up a image texture to the Lightmap input. Use a UV Map node to control what UV set should be used for the lightmap, as you would any other texture in Blender.

Note that fore use in Hubs, you currently MUST use the second UV set, as ThreeJS is currently hardcoded to use that for lightmaps. This will likely be fixed in the future so the exporter does not enforce this.

Support for Blender 2.8.2

• Updated to support Blender 2.8.2 and gltf-blender-io shipped with it
  • Updated to use the gltf-blender-io user extensions API for most hooks.
• Ability to add components to bones

v0.0.1

Initial Commit