- User Since
- Oct 26 2016, 12:41 AM (130 w, 2 d)
Thu, Mar 28
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?
Wed, Mar 27
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: