blender: 4.3.2 -> 4.4.0 #391594
blender: 4.3.2 -> 4.4.0 #391594
Conversation
Blender is now using a fork of OpenCOLLADA. They have done so since 4.2, but in the upcoming Blender 4.4, Blender will fail to build with the original and needs this fork. This fork “removes everything (a lot!) that is not actually needed by Blender” and so is likely not suitable for use by other projects (of which there are a few within Nixpkgs). See more in [upstream README][1]. [1]: https://github.com/aras-p/OpenCOLLADA/blob/4526eb8aaa6462c71fbedd23103976c151a01c50/README.md
Changelog: https://developer.blender.org/docs/release_notes/4.4/ Diff: https://projects.blender.org/blender/blender/compare/v4.3.2..v4.4.0 - Blender now needs its fork of OpenCOLLADA to build successfully - Blender is now bundling assets with the release tarballs again, so go back to single src - Blender changed Draco location so we can have it work out-of-the-box and don’t have to move the Python dir around anymore; see upstream faaa12a10131b93757a8395f3448040436981e5f - Other patches we backported are now applied and unneeded - Blender added Pipewire support, but it’s off in their release builds currently so turn it off as well
|
The package builds fine, but I found some visual glitches (on switching workspace occasionally some icon gets drawn really big possible at the mouse cursor position for a split second, and on the sculpt workspace the icon for brushes are messed up) and one crash when trying to assign a texture to the default cube to test texture painting. Edit: stdout of my testrun: >>> result/bin/blender
[W][23:33:14.272851] pw.conf | [ conf.c: 1204 pw_conf_load_conf_for_context()] setting config.name to client-rt.conf is deprecated, using client.conf
register_class(...):
Info: Registering key-config preferences class: 'Prefs', bl_idname 'Blender' has been registered before, unregistering previous
register_class(...):
Info: Registering key-config preferences class: 'Prefs', bl_idname 'Blender' has been registered before, unregistering previous
Warning: Missing Textures (or linked), detected!
Warning: Missing Textures (or linked), detected!
Warning: Missing Textures (or linked), detected!
Warning: Missing Textures (or linked), detected!
Error: nu::shell::core_dumped
× External command core dumped
╭─[entry #48:1:1]
1 │ result/bin/blender
· ─────────┬────────
· ╰── core dumped with SIGABRT (6)
╰────F.or context my system info: |
| hash = "sha256-LCU2JpQbvQ+W/jC+H8J2suh+X5sTLOG9TcE2EeHqVh4="; | ||
| }) | ||
| (fetchgit { | ||
| name = "assets"; |
There was a problem hiding this comment.
Maybe my crash and glitch came from missing some assets?
There was a problem hiding this comment.
It’s in the commit message, but the assets are now bundled in the release tarball. The only difference is the release tarball doesn’t have Git-specific files like .gitattributes.
| @@ -201,6 +172,7 @@ stdenv'.mkDerivation (finalAttrs: { | |||
| "-DWITH_OPENIMAGEDENOISE=${if openImageDenoiseSupport then "ON" else "OFF"}" | |||
| "-DWITH_OPENSUBDIV=ON" | |||
| "-DWITH_OPENVDB=ON" | |||
| "-DWITH_PIPEWIRE=OFF" | |||
There was a problem hiding this comment.
Is there a specific reason, why we want no pipewire?
Or could we make this optional, same as jack?
There was a problem hiding this comment.
Just saw your note in the commit message, sorry for not looking there first.
Still an option might be nice to have, no?
There was a problem hiding this comment.
Personally don’t really want to support something that upstream doesn’t support (src). It’s an outstanding todo item, IMO, to more properly consume Blender’s own release config in our packaging so we make fewer deviations.
There was a problem hiding this comment.
I see, with that It sure makes to wait for upstream defaulting to ON.
Yea I have seen that briefly (I didn’t get a crash, though), but I haven’t yet done full testing. Need to compare with Blender’s own build to see if it’s a packaging or upstream issue. |
|
Actually I’m seeing the workspace switch icon flashing on 4.3.2 as well, so I don’t think it’s an issue with the upgrade, but possibly some dependency update that’s happened in the interim. |
|
So, both visual glitches happen as well on my sons machine with Garuda Linux, also he is on Wayland, while I am running X11. I'll see if there is an upstream issue for this. Furthermore, I wasn't able to reproduce the crash as well. |
|
I'm seeing a visual glitch in the grease pencil asset icons. They are all the same icons. When hovering or selecteng, the correct icon for the hovered/selected item the mouse is over is shown. But the icons right of the cursor change to the selected/hovered icon and left of the mouse the items stay the same as before. Can someone confirm this glitch? |
|
Yes, that's exactly the glitch I am seeing on the Sculpting workspace. I also found an additional detail in the flashing icon glitch: it is the last icon of the tool menu to the left. When the tools are hidden (e.g. by pressing I can confirm both glitches on |
|
At least the glitch with the brush thumbnails seems to be an issue in MESA 25.0.0 and should be fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34091 |
See individual commits for details.
I’m on the fence about making the OpenCOLLADA Blender fork top-level, especially as Blender expects to remove it in v5.0 later this year anyway. Thoughts welcome.
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.