- User Since
- Apr 11 2016, 1:11 PM (262 w, 1 d)
Mar 8 2021
Mar 4 2021
Feb 22 2021
Dec 18 2020
I've changed hardware since this report. Unfortunately I was experiencing too many visual bugs and driver crashes using the open source AMD drivers with the 5700XT while working in Blender.
Dec 11 2020
Nov 22 2020
Can confirm this behavior with a Radeon 5700XT on Ubuntu 20.10 (also Mesa 20.2.1) with building from source 7bab87c119f4. Same thing happens when trying to enable an addon that imports numpy.
Nov 1 2020
It doesn't occur during rendering, only when loading all the assets before the actual rendering starts. When the render starts (ie. tiles start calculating), the speed of that part is the same. The trees are all geometry so there's no transparency being used in the materials.
Oct 27 2020
Just tried 2.90.1 and it's fine, so I might have mixed up Blender versions while testing initially, sorry about that.
Oct 22 2020
I've been having the same issues with shaders that don't have transparency as well, it feels like the object you're working on (shading, particles etc) will randomly disappear in the rendered view. This happens for me in 2.90.1, 2.91 Beta and 2.92 Alpha (master)
I'm using a AMD Ryzen CPU (3990X), maybe it's NUMA related?
Oct 21 2020
Oct 13 2020
I ended up getting around this by using a normal particle system with physics set to none, but afaik this problem still exists.
Oct 5 2020
Might be something to do with the open source amdgpu drivers on Linux specifically then? Because the same thing happens on Xubuntu as well with the same hardware and drivers.
Oct 4 2020
Sep 21 2020
Sep 8 2020
Aug 20 2020
No problem, here's a link to the files: https://cloud.mantissa.xyz/index.php/s/PmfJLaNHqzewPwr (1.7GB)
If you want the tree scene as well, I'll have to share it directly, as it has assets I can't link publicly.
Aug 19 2020
Just had some time to check 2.80 and 2.79b to compare and it looks like this behavior goes pretty far back.
I did some quick testing in 2.82 and 2.81 and the behavior seems present there as well. I can have a look at 2.79 once I have some time to see it the problem exists there as well.
Aug 17 2020
Aug 16 2020
Aug 6 2020
Jun 28 2020
May 20 2020
May 18 2020
Did some additional testing with different linux distros to complete the picture.
Same results occur with Pop!_OS, Solus & Fedora 32, all using Nvidia driver version 440.82, with the same hardware as the original report.
At least we know it's not something OS specific, might even be hardware related.
May 15 2020
For reference, I'm running a 1st gen Threadripper CPU with 16 cores, which might be why we're experiencing similar behavior.
I'll try the same on Pop_OS and see it it persists, so we can get some more info, although with it being based on Ubuntu I'm not expecting massively different results.
May 13 2020
Running blender with --debug-cycles, these are the messages it spits out when everything hangs:
Yeah, it's with CUDA in my case.
May 7 2020
Apr 22 2020
Switching to CUDA 10.1 will solve this. As the docs state 10.1 is currently the supported version.
Apr 18 2020
Mar 23 2020
Mar 17 2020
Feb 28 2020
Feb 21 2020
Feb 19 2020
Jan 30 2020
Jan 28 2020
Dec 29 2019
Dec 22 2019
Dec 17 2019
Dec 14 2019
Dec 10 2019
Dec 9 2019
Dec 4 2019
Nov 6 2019
Oct 25 2019
Oct 13 2019
Sep 20 2019
Sep 16 2019
I made a comment about this on the DevTalk forum: https://devtalk.blender.org/t/vertex-weight-color-overlays-in-the-viewport-in-object-mode/6414
Also made it in to a proposal on RCS: https://blender.community/c/rightclickselect/1Cdbbc/
Jul 26 2019
Jul 8 2019
No worries, I got it from the splash screen to begin with.
After resetting everything I can think of I've found that opening an existing file causes it to work correctly.
Creating the setup from scratch however, causes the behavior, so it looks like it's only when the setup is first made in the scene.
I've tried it a few times now and this behavior is repeatable on my machine.
Just tried again today with the latest buildbot: d19d0ff99e61
Problem still persists for me.
Jul 4 2019
Tried a new build, the issue persists for me on Xubuntu 18.04.
Jun 30 2019
Jun 16 2019
May 31 2019
May 30 2019
Can confirm Dynamic Paint isn't working correctly in 2.80.
Both files attached are the same setup, one in 2.79 and the other in 2.80.
Tried both Weight and Color modes, but no results in either in 2.80.
Setup works as expected in 2.79.
May 29 2019
OpenAL tends to mess with some of the other PulseAudio devices when starting Blender, causing recordings to get garbled or internal sample rates to get mixed.
This can happen during streaming sessions or whilst having other audio editing applications open.
I tend to set it to "Null" so it doesn't interfere with the other open applications.
Found the issue while reconfiguring from scratch, changing the Audio Device in the preferences to "Null" halts playback.
I've updated the description to reflect the issue more clearly.
May 28 2019
That works fine on my end.
Just tried resetting my preferences real quick and then it works again.
Maybe it's something I've set up in my startup file / preferences?
I've attached a scene where it's not working with my current setup together with my user prefs and startup file.
Only changed some basic preferences and some UI, so it looks like something I've set up a specific way.
Apr 8 2019
I tend to use the World texture panel for procedural textures I use in the Compositor. The Brush or Line Style categories don't quite fit, maybe renaming World to Compositing might be useful?
Apr 7 2019
Mar 28 2019
Mar 21 2019
Mar 6 2019
Feb 27 2019
Feb 20 2019
Feb 13 2019
I've elaborated a bit more on this issue in a devtalk post, as not to clutter the bug tracker too much.
Here's the full post for anyone interested: https://devtalk.blender.org/t/opensubdiv-issues-with-large-and-complex-meshes/5534
Feb 12 2019
Feb 4 2019
Dec 4 2018
Nov 29 2018
Oct 30 2018
Jul 2 2018
Nov 18 2017
Aug 21 2017
I've pinned it down to Radeon ProRender, my mistake.
Didn't realize I'd installed it on both my machines already, once removed the behavior goes away.