Can confirm whenever multires is used and smooth() is involved (Smooth Brush, Mask Smooth) -- cannot reproduce using anything else...
Sun, Oct 14
Sat, Oct 13
Fri, Oct 12
Ah, sorry, looks like my initial bug report was misleading.
Just click on the minus next to vertex color data and that deletes it.
As far as I'm concerned, the only two issues are (1) the annoying warning message that just keeps popping up, and (2) the fact that now with vertex color data added I have to keep enabling dyntopo all the time. Personally, I've never really needed vertex painting, and I feel that with the modern PBR workflow that everybody uses these days, vertex painting is becoming less and less important.
Unfortunately these 2 features contradict each other on a fundamental level so this is the way it has to be...
Sat, Oct 6
Thu, Oct 4
Wed, Oct 3
Tue, Oct 2
note: I am unsure about the usage of WM_keymap_add_item [as opposed to using WM_keymap_verify_item], but apparently veryfing would find an entry already and would thus not work...
Tue, Sep 25
I can confirm this issue.
Mon, Sep 24
I wanted to bring this issue up again. Noticed the same behavior. And it seems many other people are having massive performance issues with multithreading too.
Tue, Sep 18
Please Do not set priority of tasks yourself, especially not to high priorities!
Sep 12 2018
Sep 7 2018
Sep 5 2018
I have attached the blend file. When I open that file, select the console which already has the command typed in, and press ctrl + space, blender crashes.
Please attach the blend file that crashes.
After downloading the latest version of Blender (Hash 265ec400ab1) and running in factory mode, the error no longer occured. However with the default settings that I had set up, the error did occur. I have attached the printed error as a text file in case it is still of interest.
Sep 3 2018
Cannot reproduce either. Please:
- Try to re-download and re-install Blender.
- Try the latest build from our buildbot.
- Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
- Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).
Cant redo the crash w/ 2.79 release, master 7ff1750218bf3c2ef4c57f9ea4a12b738f4b7264 or blender2.8 ad68470d447dfb3864ed3e159dc0951bbf8547c6
Aug 23 2018
Confirmed, also affects 2.8… Not sure whether this is actually a bug, or a limitation of current code though…
This is a WIP, is in the next in the list in context of multires actually.
Aug 16 2018
Hi there—I wanted to let you know I took at a look at this bug. I ran into this issue originally when going through the blender cloud game asset tutorials. There are a couple things going on here in the latest blender. I was able to fix one miscalculation for tris but ran into a blocker with quads.
Aug 15 2018
Well, yes, they should, as long as 'Alpha' setting just below blend mode is enabled… Disabling it will lock the alpha channel. Thanks for the report, but no bug here.
Can confirm the issue, but not so sure we can do much about that, this looks to me very similar to the terminator problem in rendering… @Campbell Barton (campbellbarton) or @Brecht Van Lommel (brecht) may know better?
Aug 14 2018
Ah actually, we already have that reported…
Ah, yes, it is indeed impossible for Blender to load packed PSD (because underlying library OIIO does not allow reading images from memory, only from files…). You probably loose your images after some undo/redo action.
Thanks for the report, but unfortunately there is not much we can do here, PSD is not an open format, so it’s not really easy to fully support.
@Campbell Barton (campbellbarton) uh, this is actually again the infamous 'operator started from toolbar has no View3D context info' issue… we already had that bug in other cases, but never actually saw how that was fixed. ;)
Aug 13 2018
Made some requested changes.
I also removed the vertex normal code. Now everything is simpler.