Practical Info
This is a weekly video chat meeting for planning and discussion of Blender Eevee/viewport module development. Any contributor (developer, UI/UX designer, writer, …) working on Eevee/viewport in Blender is welcome to join.
For users and other interested parties, we ask to read the meeting notes instead so that the meeting can remain focused.
- Google Meet
- Next Meeting: November 21, 2022, 11:30 AM to 12:00 PM Amsterdam Time (Your local time: 2022-11-21T10:30:00Z → 2022-11-21T11:00:00Z)
Attendees:
- Jeroen
- Clement
- Omar
- Miguel
Metal backend
- Reviewed some patches, reviewing/development will be slow the upcoming weeks due to availability constraints.
Multi view
- Multiview support for the new draw manager has been added.
- Test cases needs to be added to validate its working, before using it with the shadow mapping code for Eevee-next.
Viewport compositor
- Some bug fixes have been done.
- Dalai and Pablo did an UX proposal to make sure that even when the project isn’t finished it can be part of a release. The implementation should be prioritized, but would not make it to 3.4 as we are already in BCon3.
- Documentation should also be looked at. Perhaps a single entry explaining how to enable and what the limitations are.
- Nodes in the Vector/Distort category will be handled next. Tracking nodes needs more attention as it is uses CPU processing from the tracking module. Unclear if this can be used in the current form.
Blender 3.4 release
- Team is focused on bug fixing.
- NVIDIA volumetric firefly issues (for the Heist project)
- Depth of field glitches when active camera isn’t a camera object. Currently undefined experience is expected. This effects Eevee-next and Workbench-next.
- Shader Codegen performance regressions when using cascade bump/noise nodes.
- AMD compiler crashes.
Debugging
- Idea to add comments to the codegen in order to track better what generated code belongs to which node/socket/attribute. Unclear how to enable/disable it Proposal will be made.