I’m on linux using blender 4.2.4 LTS portable and I have the ragdoll core runtime and plugin setup, the steps I followed was the manikin ragdoll setup tutorial by making the markers and assigning/connecting them and then recording the simulation. But the entire time the capsules didn’t appear when assigning the markers and after running the simulation and using the manipulator tool it wasn’t showing the capsules either.
Hi @Beefysam211, welcome to the forums!
Do you mean you could never see any Markers or anything Ragdoll-related in the viewport at all? You ran through the steps from the tutorial “blindly”, and managed to get a recording out of it?
Sounds related to rendering. Were they any messages or error upon loading the plug-in? Or upon assigning that first Marker? If possible, it would be great to see what it looks like when you first open Blender and assign that first Marker.
Oh, but you were able to use the Manipulator tool? You saw the Ragdoll UI etc.? Just not the Marker shapes in the 3d viewport?
Thank you for the welcome.
So like I can access the ragdoll dropdown menu to assign and record etc but I cannot see the capsules and when choosing the manipulator tool I cannot make capsules either and the extra UI that shows in the manipulator doesn’t appear either. So I assume it’s a UI and world viewport capsule rendering issue.
Unclear. Both the 3D capsules and 2D viewport HUD is rendered separately from the rest of Blender, with OpenGL 4.3.
If possible, it would help to know:
- From the video, it looks like a Linux distribution. Which one?
- What is the GPU, and how recent are the drivers? OpenGL 4.3 is not new, so it’s unlikely an issue of age
- From the terminal, what command is used to launch Blender?
- Once launched, are there any messages in that terminal that relate to Ragdoll?
arch linux running open source radeon drivers running on an integrated gpu.
Running blender through the terminal and recording the output while assigning capsule markers gave me multiple errors like this but I couldn’t see any errors related to the manipulator UI
Ragdoll failed to init OpenGL renderer: could not load gl_fxaa.vert/fragFAILED TO COMPILE FRAGMENT SHADER: gl_fxaa.frag
here’s the whole file
To me it seems like ragdoll fails to initialize its opengl renderer for the capsules, and for the manipulator tool UI I think the python api is not calling the blender UI buttons
Like I’m supposed to be viewing this UI and capsules but I cannot see these elements like in the tutorials
That seems to be it, that error message means the GPU and/or drivers are incompatible the hardware requirements of Ragdoll. There’s not much we can do here unfortunately, the hardware requirements for OpenGL 4.3 is from 2012 and we can’t support versions older than that without sacrificing on visuals and performance.
But like my system has is running OpenGL 4.5
This is for OpenGL EGL
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.3.3-arch1.2
OpenGL core profile shading language version: 4.50
This is for OpenGL GLX
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.3-arch1.2
OpenGL core profile shading language version string: 4.60
Hm, in that case it sounds like some specific incompatibility with Ragdoll and that GPU and/or driver. We can’t reproduce it on our end so it’s very difficult to debug. Are you sure there are no other messages in the terminal, surrounding that one error message? Sometimes you could see a line number, that would help us identify which specific OpenGL call isn’t supported on your machine.
Yeah the line numbers are in that pastebin link I posted
FAILED TO COMPILE FRAGMENT SHADER: gl_fxaa.frag
0:24(27): error: no function with name 'texture2D'
0:24(27): error: type mismatch
0:24(17): error: no matching function for call to `dot(vec3, error)'; candidates are:
0:24(17): error: float dot(float, float)
0:24(17): error: float dot(vec2, vec2)
0:24(17): error: float dot(vec3, vec3)
0:24(17): error: float dot(vec4, vec4)
0:24(17): error: double dot(double, double)
0:24(17): error: double dot(dvec2, dvec2)
0:24(17): error: double dot(dvec3, dvec3)
0:24(17): error: double dot(dvec4
FAILED TO LINK SHADER:
error: linking with uncompiled/unspecialized shader
Vertex path:
gl_fxaa.vert
Fragment path:
gl_fxaa.frag
Ragdoll failed to init OpenGL renderer: could not load gl_fxaa.vert/fragFAILED TO COMPILE FRAGMENT SHADER: gl_fxaa.frag
0:24(27): error: no function with name 'texture2D'
0:24(27): error: type mismatch
0:24(17): error: no matching function for call to `dot(vec3, error)'; candidates are:
0:24(17): error: float dot(float, float)
0:24(17): error: float dot(vec2, vec2)
0:24(17): error: float dot(vec3, vec3)
0:24(17): error: float dot(vec4, vec4)
0:24(17): error: double dot(double, double)
0:24(17): error: double dot(dvec2, dvec2)
0:24(17): error: double dot(dvec3, dvec3)
0:24(17): error: double dot(dvec4
Bingo! Sorry I didn’t see that pastebin link (unsure how I could have missed it).
This is enough to work with. I can’t guarantee when we’ll have a look at this, but this looks solvable. Will post back in this thread once we’ve sorted it.
Thank you for paying attention to this bug, kudos to the development team for coming this far in the development stage of ragdoll dynamics.