Hi, Ragdoll addon fails to enable on both Blender 5.1 and 5.2 LTS (Windows) with:
RuntimeError: Error: No module named ‘ragdollc’
On 5.1 I get a full traceback:
File “…\bl_extension_ops.py”, line 1504, in execute
cmd_batch = self.exec_command_iter(is_modal)
File “…\bl_extension_ops.py”, line 2598, in exec_command_iter
self.exec_legacy(source_filepath)
File “…\bl_extension_ops.py”, line 2731, in exec_legacy
bpy.types.PREFERENCES_OT_addon_install.execute(self, bpy.context)
File “…\userpref.py”, line 830, in execute
bpy.ops.preferences.addon_enable(module=mod.name)
RuntimeError: Error: No module named ‘ragdollc’
On 5.2 I only get the bare “No module named ‘ragdollc’” message, no traceback - not sure if that’s meaningful or just less verbose logging.
My guess is this is the same kind of issue as the 4.3 break last year (RNAMeta) - Blender 5.1/5.2 moved to Python 3.13, up from 3.11, so the compiled ragdollc binary probably needs a rebuild for the new Python ABI.
Is a Python 3.13 build in progress? Happy to test a patch build if one’s available. Thanks!
Hi @Apraxas, thanks for reporting this. Ragdoll currently supports Blender up to and including version 5.0. No date yet for when 5.x will receive support.
@marcus do you have any estimate on when we might see support for 5.2?
It won’t be anytime soon, on our grand schedule of things it’s near the bottom of priorities right now.
We’ll continue to keep Ragdoll patched for Blender 5.0 and below until then.
Oh that’s a bummer. Blender releases versions super often, so it is understandable that keeping ragdoll updated for every version is a lot of work.
Still, staying behind the update cycle this much makes ragdoll unusable for a lot of folks who already moved to newer versions.
Would it be a good idea perhaps, if keeping ragdoll updated all the time is too much, to only release ragdoll updates for blender to coincide with major LTS versions, such as 5.2, while skipping over the minor ones?
This way the update burden wouldn’t be as high while also supporting the people who stick to major LTS releases for long term projects, so they can use the addon throughout that blender version’s life instead of waiting super long for it to only be supported by the time other 2 or 3 versions have already come out.
We do support 4.5, which is also an LTS release until 2027.
Thanks for the response. Do you know if there’s any quick and dirty way to get the existing version working with 5.2?
The issue is that Ragdoll is a compiled Python extension, and those are compiled per Python version. Blender since 5.0 updated their embedded Python interpreter and thus would require a newly compiled version of Ragdoll in order to work. If you can find a way to have Blender run on Python 3.11 then loading the Ragdoll extension may work. Depending on whether there also were backwards incompatible updates to their Python API (which are frequent).