- User Since
- Oct 26 2016, 12:41 AM (242 w, 11 h)
Wed, May 19
May 10 2021
My mistake, it seems the error is caused because nor is unused in the fragment shader, which leads to normalMatrix to be removed in the vertex shader. This can be closed now, sorry.
Nov 21 2019
@Bastien Montagne (mont29) So basically the solution is to move the panel out of the Properties editor or write a modal (timer event perhaps?) according to the docs... Any chance of having a way to manually force to update the depsgraph info for Properties editor in the future without resorting to the https://docs.blender.org/api/current/info_gotcha.html#can-i-redraw-during-the-script hack?
Nov 16 2019
@Bastien Montagne (mont29) I tested it but it seems that even with bpy.context.view_layer.update() the wrong behavior can still be reproduced, am I missing something? Also I don't understand why it works when the operator is called directly with and without the manual update and when called from a panel it doesn't.
Ok thanks, I will keep that gotchas' page in mind, and ask before in those pages when possible.
Nov 14 2019
Nov 13 2019
Aug 2 2019
@Demeter Dzadik (Mets) I tried for a while but couldn't reproduce the issue so far, thanks!
May 13 2019
Thank you, it seemed like the opencl package wasn't installing correctly when installing the driver, after some config I got it working and Blender detects my gpu for gpu rendering!
I had the same problem with the 18.50 version of the driver but I didn't report this before because I didn't have time to do so.
blender-2.80-427c75e4c20b and AMD gpu pro 19.10 driver installed, I'm unable to reproduce the bug anymore!
Mar 28 2019
With a "recording", do you mean a screen recording? please elaborate this.
And with the "system memory profiler" part, will the System Monitor of Ubuntu do the job?, or do I need another tool?
Mar 27 2019
I installed the latest version of AMD gpupro driver: amdgpu-pro 18.50-725072, and I am still able to reproduce the crash.
I installed the latest version of AMD gpupro driver: amdgpu-pro 18.50-725072, and I am still able to reproduce the error.
Mar 25 2019
Jan 31 2019
Jan 15 2019
Jan 14 2019
Jan 13 2019
Oct 8 2017
Upon testing i can confirm the issue is no longer present in that version. Thank you.
Oct 7 2017
Nov 20 2016
Well without motion blur the render time of a random scene is 19.28 seconds while the time with motion blur is 68.7 seconds. Although the low render time might be because of not rendering any object.
Tom, I tried checking motion blur as you said and GPU rendering worked as usual. That workaround seems to be doing the job.
Nov 4 2016
Done. Still the same results, no object renders with gpu :/
Sorry I don't understand what you mean with that question. I loaded factory settings, and then I tried to render the default startup file's scene.
Nov 1 2016
Oct 30 2016
Hi, I was wondering if you could help me; I manually replaced the wrong line in the kernel_projection.h file. That made projection gpu rendering work again, although this time when I try to render a final image, blender throws no error, but renders a blank image, without any object, only the color of the surface background. Secondly, in the other file (kernel_shader.h), seems to be different with the file you shared with the changes: