Page MenuHome

OpenCL issue and motion blur (AMD 7870 Pitcairn)
Closed, InvalidPublic


Crimson 16.10.3

When rendering

without motion blur checked
render result is non-visible.

Checking Motion Blur and rendering again, gives correct render.

Also, you can see difference between rendering times.



Event Timeline

soulfire (vejn) added a comment.EditedNov 28 2016, 10:40 AM

I have now installed Crimson 16.10.4 and it takes to long to render.

Vuk Gardašević (lijenstina) triaged this task as Normal priority.Dec 5 2016, 8:15 AM

Can't reproduce. Could you please try a daily build from and report back wheather you still see the issue?

soulfire (vejn) added a comment.EditedDec 6 2016, 3:44 PM

Crimson 16.11.5
Still the same issue (rendered without motion blur).
Also, what I found if you render without motion blur and then check motion blur, render kernels are loading as if for the first time.

This is probably related to a specific GPU architecture / family of cards.

I could not recreate it with Bonaire R7 360, Win 7 64 bit with driver 16.8.3 on Blender Build 8ce6de3

soulfire (vejn) added a comment.EditedDec 6 2016, 4:13 PM

I found something else:
If I render with Progressive refine, black screen is not present only weird shading on sphere:

If I render with Progressive refine + Motion blur, it renders OK (the same as with motion blur). Only with Progressive refine, it renders slower.

Maybe this will be enough to find the source of the problem.

@Vuk Gardašević (lijenstina) , @Mai Lavelle (maiself) should I open new thread for todays build for this ?

Error with todays build and new Crimson Relive drivers

AMD R9_290, AMD GPU Pro 16.40 driver, Linux x64
Blender 2.78a, 2-78-bd42987 (20 dec)

'ps test.blend' rendering ok for me with any combination of 'motion blur' and 'progressive refine' options. And it takes quite a token amount of memory, just about 30 - 50Mb (looking at 'Frame | Time | Mem' string after render).

Mai Lavelle (maiself) closed this task as Invalid.Feb 3 2017, 1:24 AM

Without being able to reproduce I can only assume this is a driver bug. You should check you have the latest drivers and try lowering the tile size.