Skip to content

Blender 2.92 fixes & video-texture-source component
Compare
Choose a tag to compare
@netpro2k netpro2k released this 19 Apr 22:25
· 1155 commits to master since this release
v0_0_9
4baaeb4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release adds support for the video-texture-source component and fixes issues exporting material components in Blender 2.92. As with all updates, we will only be supporting the latest version of Blender since this addon integrates heavily with the built in GLTF exporter which changes with each update to Blender.

image

To use the new video-texture-source component, add it to a Camera node, then add a video-texture-target component to a material, selecting the camera as the "source node" in the component properties. At runtime the texture for the material will be replaced with a rendering from the camera, mapped to the entire UV space.

When exporting make sure to "Include > Cameras" in the export settings. The Camera's properties such as FOV and near/far clip will be respected in Hubs. Note that the framing rectangle in Blender is based on the render settings, so if you are trying to get a particular framing, you should set your render resolution to the same as your video-texture-source texture resolution.

The implementation of this on the Hubs side is still a bit in flux and may change. The camera is currently unable of rendering itself, and currently does not capture your own head.

Incidentally also:

  • Added support for nodeRef type in component properties, allowing components to reference other nodes (optionally requiring specific components)
  • Added support for specifying a label for component properties, overriding the name displayed in the Blender UI
  • Fixed handling of default values for enums
  • Fixed exporting of vec4 properties
  • Fixed default value for shadowMapResolution on light components
Assets 2
Loading