When the button in the 3D Viewport header is pessed to render the 3D Viewport contents, ordinary armature bones are not rendered. Paths and custom bones are rendered, but ordinary octagonal bones disappear.
Description
Description
Event Timeline
Comment Actions
I'm assuming that this is in svn-trunk, and that this used to work ok for you.
Is there any grease-pencil drawing anywhere?
Comment Actions
This is in 2.47 RC 2 for Windows. In 2.46, armatures were visible in renders made with the viewport render button.
There is no grease-pencil. To be sure, I tried this on a brand new .blend with nothing but a default cube and an armature bone, and the bone does not render.
Comment Actions
This is in 2.47 RC 2 for Windows. In 2.46, armatures were visible in renders made with the viewport render button.
There is no grease-pencil. To be sure, I tried this on a brand new .blend with nothing but a default cube and an armature bone, and the bone does not render.
Comment Actions
Hmm... can't reproduce this error here (windows, svn-trunk) using the drivers on this machine. However, when running using MesaGL as the OpenGL renderer, I can replicate this bug.
Comment Actions
Just for the record, I discussed this further on IRC, and noted that octohedrons, b-bones, and envelopes do not render, but custom bones and sticks do render.
My computer's graphic card does not support GLSL. Aligorith tested using MesaGL and was able to reproduce the bug.
Comment Actions
Confirmed error here, osx 10.3. System didnt change for years, and has rock stable opengl.
It works fine in older blender ;)
Comment Actions
There was an issue introduced after this bug report where armatures wouldn't render at all in the opengl render irrespective of the graphics card. This was fixed.
However the original bug is probably still not fixed, since I only reverted the behavior from before. I tried redoing it in the official 2.47 and 2.47-static version, and latest svn, but no luck. This was with both nvidia drivers and MesaGL, version 1.4 (2.1 Mesa 7.0.3-rc2). So I'm assigning this back to Joshua since he was able to redo.
Comment Actions
I think I've finally found that this is a driver issue.
Mesa-7.0.4 had this problem, but it was resolved in Mesa-7.2.
Closing now!
Comment Actions
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.