2025-02-03 Viewport & EEVEE Module Meeting

Practical Info

This is a weekly video chat meeting for planning and discussion of Blender Viewport & EEVEE module development. Any contributor (developer, UI/UX designer, writer, …) working on Viewport & EEVEE 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: 17 February 2025, 11:30 AM to 12:00 PM Amsterdam Time (Your local time: 2025-02-17T10:30:00Z2025-02-17T11:00:00Z)

Attendees

  • Clement
  • James
  • Jeroen
  • Miguel

Module

Overlay

  • [#52 - WIP: Overlay: Add tests - blender-test-data - Blender Projects] Added render tests for Overlay engine. The initial tests is generated from possible UI options using a python script. There around 2000 permutations. We still need to decide if we want to store the generated blend files on the tests/data folder or not. The decision will be made during the review as we would like to have some inputs from other as well.

Metal

  • [#133830 - Fix #129571: Metal: Broken texture atomic workaround - blender - Blender Projects] The workaround for atomic textures could make out of bound writes. Fixing this apparently also fixed the hang on the build bot. The code will be reviewed t check all cases are covered.
  • [#133818 - Metal: Add native tile input to workarounds - blender - Blender Projects] For the future we should add more Metal workarounds to --debug-gpu-force-workarounds as that made it easier to track this issue. Some workarounds are stored distributed in the code and requires some reorganization to make this happen.
  • Workaround for raster order group does restart the existing rendering scope and keep the state of the initial rendering scope. When starting the second rendering scope it performs load operations and can clear the results of the first rendering scope, which is not correct. This might be related to support the legacy platforms (Black cube). There seems like an undefined behavior here. This needs more investigation but is considered an high prio issue.
  • It is being discussed to support Apple Intel until 4.5 LTS. For 5.0 and onwards it can work, but it might break due to new developments. If this happens we should rely on community support. Main reason is that fixing driver issues on these platforms do not meet the quality/expectation Blender needs. Currently development time is burnt to discuss, investigate and fix these issues, what won’t allow us to focus on adding value for other users.

[!NOTE]
Next week there will be no meeting. Blender 4.4 Beta will start and we will focus on fixing high prio bugs and detailing designs.

5 Likes