0.9.14 is released today.
Notch is now VR ready. (Read below)
As part of this process we’ve made some major improvements to rendering performance which will benefit projects across the board, not just those made for VR.
Other new features:
- Native HAP / HAPQ read support
- A new generation of Meshing Node for particles and other procedurals, with hugely increased resolution & performance, and reduced memory footprint
- New Field Lighting node now supports lighting of 3D fields with multiple omni and spot lights and shadows
- Clone to Mesh now supports cloning to mesh surfaces or edges
- Output feed configuration improvements including visualisation in editor
- Connection Monitor Window - visualise status of network editing & OSC connections
- Workarounds for bugs in latest NVIDIA drivers allowing support of GeForce 1080
360 Video Rendering
Builder now offers the ability to render both monoscopic and stereoscopic 360 VR videos utilising the new ‘VR 360 Camera’ node. Simply add this camera into your 3D scene, configure, render and then playback on your YouTube, Cardboard or your preferred VR headset/app.
If you need to preview the scene on a headset before exporting you can utilise the Oculus Rift directly from Builder CG/Pro (see below).
Oculus Support : Part I
We’ve introduced initial Oculus Rift Consumer support with VR Headset Camera node. You can output directly to the headset from Builder Pro while you edit, or from exported standalones for a final deliverable (requires Builder Pro and Playback).
This is just our initial release of headset support, so expect to see new features and a more tightly integrated workflow in upcoming releases.
If you’re planning on executing production projects with Oculus Rift please get in touch to discuss your project, workflow and specific licensing arrangements: info@notch.one