- User Since
- May 24 2016, 1:39 PM (56 w, 3 d)
Thanks for your answer, Vuk. I didn't even know that one could find every single pixel of an image in the Outliner... crazy ;)
I don't know if this helps in any way but if I enable the new dependency graph (--enable-new-depsgraph) the scene load time goes from several minutes to a mere 5 seconds.
The Outliner performance problems persist though.
Thanks Corey for having a look at this. I hope you find something to improve this as it's a major bottleneck here right now.
Wed, Jun 21
Fri, Jun 9
I just tried if this new fix also gets rid of these artifacts but it doesn't: https://developer.blender.org/T51681
Tue, Jun 6
Wow! That looks great. I don't have much time to test all kinds of combinations but following the repro steps in this bug report gave me the results I expected:
Thu, Jun 1
Wed, May 31
Yes, I noticed that too. The bundled EXR environment seems to be a tough one. The tiny sun disk is at something around 50000 RGB!
But on the other hand I want / need the "power" of this sun to give me bright highlights and sharp shadows, clamping would be my last resort.
I wonder why Branched PT isn't giving me artifacts.
Confirmed. I was just about to report it here as well ;)
Tue, May 30
Sorry, can't help you because I don't know what kind of modifiers you try to apply or what your scene looks like but I can translate that German term to English for the other 99% of users here:
Sun, May 28
Fri, May 26
I'm afraid something went wrong here. I get an instant crash of Blender as soon as I start tracking, no matter if I use Autotrack or a single manually placed tracker.
The latest Buildbot build that doesn't contain this commit is not crashing.
Wed, May 24
All fine here. Latest builds. Win x64.
May 22 2017
At least with the current Buildbot builds Alembic export always crashes as soon as I use "Simple" or "Interpolated" children no matter what I set the "Display" amount to.
I can confirm it with the very latest Buildbot build.
May 19 2017
There seems to be a syntax error in line 40 of filter_features_sse.h
May 17 2017
No, sorry, no backtrace. I'm not a coder, I'm just glad I can compile Blender myself ;)
I justed tested it again and found that my own VS2015 builds and the official Buildbot VS2015 builds crash while the VS2013 builds from the Buildbot don't.
This EXR coming with this scene is known to contain NaNs. Saving it to HDR format "fixes" this. But even saving it as a new EXR (I tried 16bit half-float with ZIPS compression) got rid of the black boxes.
If you load the original environment EXR into Natron it displays a yellow warning that it replaced some NaNs with white.
May 16 2017
According to the build number in the splashscreen, yes.
And the bmesh_bevel.c source also contains the latest changes.
Thanks for taking care of this. I just compiled the very latest master and the Blenderman.blend still crashes Blender here.
May 10 2017
May 5 2017
All 2.8 Buildbot builds also crash.
May 4 2017
You're a wizard! Thanks for this very quick fix!
May 3 2017
Apr 13 2017
OMG! It crashed in my own latest build and it still crashes in the current Buildbot builds but it looks like Sergey just fixed it while I was typing the bug report!!!
Apr 12 2017
Ah, that's good to know, Sergey.
Mar 31 2017
The Blenderman file is still crashing all the Buildbot builds on opening while official 2.78c can open it. Is this a regression of some sort?
Mar 7 2017
Feb 20 2017
I just compiled the latest version and the fix is working perfectly! :)
Feb 18 2017
Jan 13 2017
Jan 9 2017
Dec 14 2016
Dec 2 2016
Nov 23 2016
Wow! Thanks for your quick help! :)
Jun 21 2016
May 24 2016
Wow! That was fast! :D