- Brecht Van Lommel (Blender)
- Jeroen Bakker (Blender)
- Patrick Mours (NVIDIA)
- Stefan Werner (Tangent)
- Max Dmitrichenko (Intel)
- Jeff Amstutz (Intel)
- Agreement to move time to 5pm to accommodate attendees in west coast USA. This time slot works for everyone in attendance. If it doesn’t work for anyone else, let us know and we may move it again. The other option would have been 3pm.
- Due to holidays there will likely be less attendance in the next few weeks. Next weeks meeting on December 15 will go ahead. For December 22 we’ll check if it’s useful in the meeting next week. The week after that, December 29, there will definitely be no meeting.
- OptiX: shader ray tracing is in master, CPU + GPU rendering is under review. For baking we’ll use the CUDA kernels, so that at least this functionality is also available when OptiX is selected. That makes OptiX nearly feature complete, the only thing missing is branched path tracing which is planned to be replaced anyway. The notice about OptiX being experimental will be removed.
- OpenVKL: Jeff asked about the conditions needed to be met for support for this to be accepted. Points to the usefulness in scientific visualization, and support for features like unstructured volumes and particle volumes. Brecht is still unsure if this extra library dependency and associated cost is something we should have in Cycles, as the aim so far has been to make Cycles work for animation rather than scientific use cases, and prefers to keep the focus on that.
- Stefan mentions hdCycles is going forwards as explained in the previous meeting notes, and that he will have some patches to fix bugs in core Cycles.
- Eevee AOV and Cryptomatte are in master. Jeroen looks into further Cryptomatte improvements, like a Python API for accessing the hashes (topic).
This is a weekly video chat meeting for planning and discussion of Blender rendering development. Any contributor (developer, UI/UX designer, writer, …) working on rendering in Blender is welcome to join and add proposed items to the agenda.
For users and other interested parties, we ask to read the meeting notes instead so that the meeting can remain focused.