- User Since
- Nov 29 2003, 10:15 PM (824 w, 3 d)
Jul 11 2019
I noticed this UI bug as well just yesterday. The radius values should probably be removed from the Transform panel in Bone Properties. Also, when in Pose mode, the order of properties in the 3D Viewport's Transform panel is inconsistent with the Bone Properties one as well. The Rotation Mode drop-down should probably be bumped above Scale in Bone Properties so it better matches the 3D Viewport's sidebar.
Jun 13 2019
I'm not entirely sure I agree that this isn't a bug. It's certainly a workflow regression when compared to the behavior in 2.79.
Jun 10 2019
@edwin hernandez (juanito49) Ah... I missed that. For me, disabling that option allows me to make the selection, but it takes two clicks for the object highlighting to move.
Confirmed here with a build from today (hash: 8aa87972cac3). Easy to reproduce (though I'm not sure how Lock to Object is relevant).
Jun 4 2019
Feb 19 2019
Dec 13 2017
Confirmed on Arch Linux with a build from today (hash: 4838512e7d4)
Nov 9 2017
Little workaround that might give a some insight to this bug:
Oct 13 2017
May 20 2016
I can confirm that the behavior isn't quite as I would expect it to be. For instance, in the example .blend file, in order to get the bones' z-axis to point in the positive Y axis, I need to put the 3D cursor either very low in the global z-axis or quite a bit into the negative (crossing the center line) in the x-axis. The attached images should show that.
Apr 27 2016
Mar 1 2016
Following up, kevindietrich's patch works for me. No crash after applying it.
Feb 25 2016
Sep 8 2015
Maintenance for this add-on is being done on GitHub: https://github.com/Fweeb/blender_render_music
It *is* being kept up to date. Currently it's maintained on my GitHub account: https://github.com/Fweeb/blender_spritify
Still works here. What is the specific error that you're getting?
Jul 16 2015
@Gary Thomas (garythomas128) are you using the version of the add-on that ships with Blender 2.75a? I just tried it in both 2.75a and a build from the latest commit in master and everything seems to work just fine for me. You should see the Return to Original File button on the Tool Shelf within the Relations tab.
Much appreciated @Bastien Montagne (mont29). I just recompiled and tested. No crashes now. Thanks!
Just did some additional checks and it's not about the image size. It's specifically about bit-depth I think. The attached image is a 16-bit PNG (generated by Blender, BTW) and it consistently crashes Blender for me in thumbnail view on the File Browser.
Jul 15 2015
Apr 30 2015
Just rebuilt and checked. Looks like those commits fixed it. Thanks.
Apr 29 2015
Nov 9 2014
Oct 13 2014
The reason for writing this patch is because I have actually been writing Add-ons as part of book writing and documentation on Blender. Personally, I don't see "addons" as being particularly distinctive from a branding perspective (i.e the reason for phabricator's namings); it appears to be more of a mistake/typo. And, yes, Dyntopo is in the interface, but I'm pretty sure that nearly all user-facing strings for subsurf are written as "Subdivision Surface" in the UI.
Oct 2 2014
Jun 4 2014
It seems this issue rises as a result of having .blend files that link to assets in one another. That is, A.blend has an object, "1" that is linked from B.blend. And B.blend has an object, "2" that is linked from A.blend. It's kind of a circular linking scenario.
Apr 4 2014
Feb 3 2014
Ah... nevermind. User error. It's not in the main presets where I expected it to be. I first have to choose something such as H.264 or MPEG (or just about anything in an AVI container). From there, I can change the container and codec in the Encoding panel.
In the Movie section of my File Format dropdown, I have the following options:
IIRC, don't Macs have native Quicktime support while other platforms only rely on FFMPEG? If that's the case, that might explain why you see it and I don't.
Jan 3 2014
Probably best to close this report. The crash doesn't happen on Factory Defaults. And after reconfiguring all of my settings (themes, addons, etc.) with the Factory Defaults as a base, the crash hasn't returned.
I was able to sanitize a test file... it seems the issue partially has to do with the size of the finished rendered image (rendering at 50% resolution does not yield a crash). The strange thing, however, is that this file has worked fine in Blender since the 2.69 release and only seems to have started crashing recently.