- User Since
- May 29 2021, 11:40 PM (78 w, 6 d)
Jan 1 2022
This might be an OpenSubdiv problem.
No problem! I'll mark this as closed.
Dec 31 2021
I'm observing a similar issue, although I did not get that black area on the back: it just seems like the entire shirt is uniformly colored.
The add-on makes the length of each of the sides of the triangle proportional to the distance between the three points being measured.
I was able to replicate this, with one caveat -- I did not see an "Add Empty Symmetry Vertex Groups" option; perhaps that comes from an add-on?
Sorry, but the bug tracker is not for support requests -- all tasks opened here should be for bugs in Blender or one of its bundled addons.
I see two places where the layers are listed. One is in the Properties menu:
Whoops, forgot to do a make update. I can confirm that this has been fixed.
A debug/developer 3.1 alpha build immediately triggers AddressSanitizer when I open that file: P2690
Dec 30 2021
This was introduced by rB7e712b2d6a0d257d272ed35622b41d06274af8df
I can confirm this on the latest build from master. Working on bisecting it now, since it was fine on a pretty recent build.
Thanks for the report. Please check for the crash logs produced by Blender, as described here: https://docs.blender.org/manual/en/latest/troubleshooting/crash.html
I am unsure how to reproduce this issue on 3.0.0.
There is some relevant discussion in T64793
I can reproduce this with a variety of properties. I am unsure how to interpret the output; perhaps someone with more experience could chime in?
I was unable to cause a crash when trying the described steps. However, this might be related to T94506, where I can cause a crash.
Yes, I think this falls more under the "feature request" category. You can find more information here: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
I'll mark this as closed, since there has been no activity in a week (and because this is not a bug report, as Richard described).
It looks like the problem was that a keyframe of 360 degrees was acting like a keyframe of 0 degrees. However, I was unable to reproduce this.
The file is no longer available. You can drag-and-drop a .blend file directly into the text box for a comment to attach it, so please send it that way!
Just copying some stuff from the chat here:
Also confirmed on MacOS on the latest master build. This causes a segmentation fault, even in the debug/developer build; AddressSanitizer doesn't provide any information.
Thanks for the report. I cannot reproduce this crash on the 3.0 release when importing mp4s.
I was not able to replicate this on the 3.0 release (even with every bundled add-on enabled, in case one was relevant).
I can reproduce this on the latest build from the master branch, as well as in the 3.0 release.
Thanks for the report.
Thanks for the report. It looks like that the "Curve Endpoints" node never made it into the 3.0 release; instead, it was replaced by the "Endpoint Selection" node.
Thanks for the report! Please attach a minimal (remove as much stuff as possible) .blend file that's causing the problem. Even if it's happening with seemingly any setup, it will still be useful to have a specific example.
Can replicate on MacOS too. The similar "Edge Split" node in 2.93 does not cause a crash.
It looks like that, by default, it tries to name the file ".dxf". If you save without changing that name, it will wind up being a hidden file on MacOS and Linux.
Duplicate of T94482 ; closing
I cannot reproduce this on MacOS (with an M1 processor).
I spawned a Monkey object, added a Multiresolution modifier, and used it to subdivide five times. I then switched between edit and object mode a few dozen times. I saw a modest increase at first on MacOS, but it didn't grow forever.
I'm definitely seeing some differences between 2.93 and 3.0
A more striking example is to set the stroke method to Line, the spacing to 5%, and the "Adjust Strength for Spacing" checkbox to off.
Thanks for the report. However, this appears to be a third-party add-on that is not distributed with Blender. This bug tracker is for reporting bugs with Blender itself, or with add-ons that come with Blender.
Dec 29 2021
I cannot reproduce this in 3.0. I've attached a demo file that mixes two Principled BSDF nodes.
Dec 28 2021
Dec 27 2021
I am observing this on my M1 macbook. It gets worse as I add more editors -- with just the 3D viewport, it's practically a non-issue, but it gets pretty bad if I open lots of little text editors.
Dec 26 2021
I cannot reproduce this on the 3.0 release. If I make a vertex group, select some vertices, press "Assign", deselect all vertices, and press "Select", the vertices are selected.
You have attached conflicting files. The debug output states that it's from a 3.1 alpha build, but the system info file is from a 2.93.3 build.
Yes, this is being actively worked on. You can read about the progress here: T92212
I also get a segfault from the latest commit on master, rB28a8d434d53126c09ee795c5b8af129e3fc7521a
Dec 25 2021
Dec 20 2021
I've observed this before, and can reproduce the issue with that file.
Dec 15 2021
Can confirm, on both 3.0.0 and on a debug build of 3.1.0. Non-debug builds are getting an access violation.
I'm not seeing this on Windows 10 when running Blender 3.0.0. The default sphere scene loads after a moment. It also works fine on the 3.1.0 alpha.
Dec 13 2021
I can also observe this on my Linux laptop, which is using Intel integrated graphics. I was using a 3.1.0 lite build. The artifacting looks the same.
Dec 12 2021
The problem is that it's trying to run a script with the name of the Text object in blender. So, if the Text object is called "Text", it tries to run a script called "Text" (which does not exist).
Dec 11 2021
I can reproduce this on the 3.0 release, as well as in the 3.1 alpha.
I see the cause was already found in T93949, so that's good. I'm confused about how this is different from that issue, though.
I can reproduce this crash on both the current 3.0 release, as well as on a 3.1 alpha build.
Dec 10 2021
Dec 3 2021
Thanks for the report, but this is working as intended. The documentation for the Simple Deform modifier's Bend mode shows how it has no effect when using the X or Y axes: https://docs.blender.org/manual/en/latest/modeling/modifiers/deform/simple_deform.html
Dec 2 2021
Aug 26 2021
We will need more information. Are you exporting .fbx files from Maya and importing them into Blender? If so, then it's possible that Maya and Blender are expecting different units (centimeters vs. meters).
Jul 8 2021
I believe this is intended, albeit surprising: deleting the object just unlinks it from the scene. It still exists, just without any users.
Jun 25 2021
Ah, good find. I must've been scrounging around with the wrong keywords.