- User Since
- Feb 5 2013, 12:47 PM (449 w, 1 d)
Jan 9 2021
I ran Thread Sanitizer (tsan) on Blender version
bc788929aa2bd259670a5562a1f403f25cad4625 (recent master) on macOS.
Jan 7 2021
Found the undo-experiments branch.
Jan 6 2021
This problem already existed when the undo speedup first entered Blender master, I could repro at the below change.
Let's say somebody would want to use git bisect to figure out where this problem started.
Nov 19 2020
Two suggestions that I was unable to find in the comments so far, based on that this looks like a race condition.
Oct 23 2020
Initialise tracking curve colors to a fallback color (black). Shouldn't ever become visible, but who knows?
Oct 15 2020
Closing in favour of D9218.
Oct 13 2020
The problem I really want to solve is that blue-on-dark-grey is hard to see:
Oct 12 2020
Jul 6 2020
Spaces added before "px" as requested by @Julian Eisel (Severin).
Jul 5 2020
@Sergey Sharybin (sergey), could you please review this for merging?
Jun 22 2020
@Aaron Carlisle (Blendify) what would be the easiest way for me to get this considered for merging?
Jun 12 2020
Jun 11 2020
@Sergey Sharybin (sergey), not sure if I should also change the number of decimals printed to one?
Jun 4 2020
Jun 3 2020
Here's what the new tooltips look like.
May 30 2020
May 14 2020
May 2 2020
Apr 30 2020
Not sure how on-topic this comment is, but with D3576 it would be possible to say how common these crashes are, which would help prioritize.
Apr 4 2020
Mar 10 2020
Thanks @Brecht Van Lommel (brecht) for the quick review!
Mar 7 2020
Mar 4 2020
@Jacques Lucke (JacquesLucke) your stack trace says eevee_draw_scene and looks kind of different from what I've been getting in /tmp/blender-2.82-crash.crash.txt (see above).
Here's the contents of /tmp/blender-2.82-crash.crash.txt:
# Blender 2.82 (sub 7), Commit date: 2020-02-12 16:20, Hash 77d23b0bd76f
Feb 29 2020
@paul szajner (szap), I think I know why "self" worked for you.
Feb 27 2020
Thanks for the clarification @paul szajner (szap)!
It works with your changes @Ankit Meel (ankitm).
Nope, doesn't work, and I don't get why, see below.
If we want to not hardcode the Blender version, we could go for the Blender version that has the highest number of samples over the last couple of months / the last 10000 samples / whatever makes sense.
@Ankit Meel (ankitm) were you able to repro using the provided instructions?
In LookDev / Rendered the ball is checkered:
Feb 26 2020
I'm on poetry 1.0.3.
@Patrick Mours (pmoursnv) except that the actual SQL is too much for me, I like the idea and I think it is an improvement on the current tables.
Feb 25 2020
Jan 25 2020
Today you learned :)
Dec 8 2019
FWIW I just downloaded the Uploading_Volumetric.blend and looked at it in Rendered mode in Blender 2.81a (press 'z' after loading it and click Rendered), and it was nicely cloudy.
Oct 10 2019
Awesome timing @Sebastián Barschkis (sebbas) :)
Oct 9 2019
And for context, here's where it was disabled: https://developer.blender.org/rB4494be513ac455b106b2cb9be119136a58212cd1
@Sebastián Barschkis (sebbas), will this change be in 2.81?
Sep 30 2019
One workaround that I was able to use with vanilla 2.8 was to:
- Up the global Frame Rate in the Output section from 24fps to 100fps.
- Multiply smoke Dissolve Time by 4 (I don't have "Slow" checked, not sure how Slow would affect this).
- Multiply the Smoke Cache End frame by 4.
- Render image 73 rather than image 19 (I tried 19*4=76 first, but 73 just happened to look better than 76)
Note also @Finn Bear (finnb) that the "Disable substeps for now" comment seems to be a red herring; it was in 2.79 as well...
Aug 27 2019
I don't see any docs, neither in this diff nor at
May 12 2019
Apr 10 2019
Mar 16 2019
Can confirm the fix as well, works like a charm now, thanks for fixing @Clément Foucault (fclem)!
Mar 15 2019
That was delivered quickly and totally answers what I wanted.
Mar 10 2019
Thanks for the update @Ray molenkamp (LazyDodo)!
Mar 9 2019
Another data point; if I switch to Cycles and render I get a foggy looking cube as expected.
Sep 20 2018
One alternative way of handling crash uploading could be to:
- Blender crashes
- Blender unconditionally stores a crash dump into a known location (without telling the user)
- Blender terminates (possibly without telling the user)
- User restarts Blender
- Blender sees the crash report from last run and does whatever its preferences say.
Sep 17 2017
Note that the thumbnail isn't that bad, the full-res version is though, please click on it!