This is the place to take notes for on-going Pipeline, Assets & I/O meetings, before moving them to Meetings - Developer Forum . Please keep it as a clean, ready-to-use template for the next meeting.
Everyone is welcome on the Google Meet linked below every other Thursday, at 17:00 CET.
The meeting covers the pipeline & I/O module in a broader sense, including some topics hosted in other modules (e.g. some I/O python add-ons, or overrides and .blend file I/O from the Core module).
- Google Meet
- Previous meeting
- Next meeting
- Pipeline, Assets & I/O project
- Core project
- #pipeline-assets-io-module chat channel
- #core-module chat channel
Ongoing development for Blender 4.1 targets
- Python Hooks import: Micheal did not work on it yet. Since it is expected to be a fairly simple and straightforward change, he may try to squeeze it still for 4.1, if time allows.
PointInstancer: Micheal did some work on it, and thinks that it’s ready for final review and merge.
UsdGeomPointsas Point Clouds: Current status is unclear, it will most likely be rescheduled for 4.2 now.
- import of
GeometrySetfrom USD and Alembic: Jesse did some fixes and improvements, there are still some unknowns in this work (USD specs questions…). Probably safer to reschedule it for 4.2 at this point.
A loose rule was agreed on: if a patch is not (almost) ready by the end of next week (January 26th), it should be rescheduled for Blender 4.2.
As a reminder, Blender 4.1 will move into BCon3 (bug fixes only) on the 7th February.
Micheal asks whether Blender ShapeKeys can have some form of custom normals. USD can store “normal offsets” into its blend shapes. While Blender ShapeKeys do not store any form of custom normals currently, it could be possible to export the evaluated custom normals for each shape key?
Micheal raises the issue that the switch to Python 3.11 for Blender 4.1 release creates incompatibilities with Nvidia Omniverse work. But Blender follows the VFX platform, so 4.1 should be released with Python 3.11. Other DDCs should most likely also switch to Python 3.11 in the coming months anyway.
See also the synthetic task.
Micheal reports that Charles got some basic prototype working, he may demonstrate it at the next meeting.
This is about the basic support of export settings per collection, available for any external format (not the more advanced topics discussed in the previous meetings, specific to USD).
See also the design task.
The pull request is still WIP. Some UI/Operator aspects still need more work.
Some advanced features like ‘cascading settings’ for collection hierarchies are not implemented at all, but these are not required for an initial ‘test’ release of the feature.
The next meeting will be on Thursday 1rst February, 17:00 CET/Amsterdam time (your local time: 2024-02-01T16:00:00Z).
The provisional meeting agenda will be linked in the #pipeline-assets-io-module channel before the meeting.