Package Details: blender-as-py-module 2.93.3-1

Git Clone URL: (read-only, click to copy)
Package Base: blender-as-py-module
Description: A fully integrated 3D graphics creation suite, to be used as Python module. Useful for programmatic/batch rendering.
Upstream URL:
Licenses: GPL
Submitter: jagot
Maintainer: jagot
Last Packager: jagot
Votes: 3
Popularity: 0.000000
First Submitted: 2016-11-13 18:21 (UTC)
Last Updated: 2021-08-31 10:08 (UTC)

Latest Comments

1 2 Next › Last »

jagot commented on 2022-07-25 08:09 (UTC) (edited on 2022-07-25 08:10 (UTC) by jagot)

Sadly, I have not had the time to test.

You could try bumping the version number on this line and see if it compiles:

If not, the PKGBUILD probably has to be tweaked to be in line with the main package:

b0o commented on 2022-07-23 11:22 (UTC)

Is this working for Blender 3.x?

jagot commented on 2021-08-31 09:24 (UTC)

So that's what was missing, thanks! 800e6b7b1091

PumpkinCheshire commented on 2021-08-31 08:35 (UTC)

Hi, it seems you have not refreshed the .SRCINFO file since 2.80. My aur helper insists on updating this package every time even it is already the latest version.

Could you please refresh the .SRCINFO?

makepkg --printsrcinfo > .SRCINFO


jagot commented on 2020-09-10 14:05 (UTC) (edited on 2020-10-03 10:24 (UTC) by jagot)

I've updated to version 2.90.0, but running the example quoted below, I get a SEGFAULT:

$ python -c "import bpy ; bpy.ops.render.render(write_still=True)"
/run/user/1000/gvfs/ non-existent directory
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
zsh: segmentation fault (core dumped)  python -c "import bpy ; bpy.ops.render.render(write_still=True)"

This was when running on a remote desktop via SSH, so that could possibly be the culprit. I've checked that the fix was included in 2.90.0.

EDIT: Just tested this on a laptop, and can confirm that it works.

DarioP commented on 2020-05-25 10:35 (UTC)

Wow, they already fixed it. I am impressed! I have compiled with:


And the segfault is gone. I also confirm that openjpeg2 seems good.

DarioP commented on 2020-05-24 18:36 (UTC)

Yeah, I also tried 2.82a and even trunk, no difference. Reported upstream:

jagot commented on 2020-05-24 18:06 (UTC)

I can confirm that I also see the segfault, even with 2.82a (which I just pushed).

DarioP commented on 2020-05-24 15:02 (UTC)

Does it work for you? I can build it fine and import the module, but I get a segfault as soon as I try:

$ python -c "import bpy ; bpy.ops.render.render(write_still=True)"

as suggested here:

I changed the dependency openjpeg for openjpeg2, which is in extra instead of AUR. Same result: builds fine but segfaults on the command above.

jagot commented on 2020-03-01 16:04 (UTC)

Updated to 2.82, Python 3.7 => 3.8, added Optix support.

I have not actively used this package myself since a while, so it would be useful to have some test scripts checked in, that tests the functionality, maybe against a reference render? Drop me an email if you have any suggestions.