Hair particle system and OpenCL issue on AMD 7870 (possible driver related) #49019

Closed
opened 2016-08-05 11:04:24 +02:00 by soulfire · 37 comments

Tested with latest build 5.8.2016.
Driver: Crimson 16.7.3

Hair PS is connected with OpenCl issue on AMD 7870. (GCN1, Pitcairn).
Reproducing steps:

  1. Cube with hair PS is on scene (not in camera view)
    amdpremtest.jpg

  2. Render result:
    amdtest1.png

  3. Cube with hair PS is on scene (not in camera view) with restrict rendering
    amdpremtest2.jpg

  4. Render result (renders fine):
    amdtest2.png

Conclusion: If object with hair PS is on scene, there are some shading issues.
test_hair_ps_1673.blend

*Tested with latest build 5.8.2016.* Driver: Crimson 16.7.3 Hair PS is connected with OpenCl issue on AMD 7870. (GCN1, Pitcairn). Reproducing steps: 1) Cube with hair PS is on scene (not in camera view) ![amdpremtest.jpg](https://archive.blender.org/developer/F332956/amdpremtest.jpg) 2) Render result: ![amdtest1.png](https://archive.blender.org/developer/F332957/amdtest1.png) 3) Cube with hair PS is on scene (not in camera view) with ***restrict rendering*** ![amdpremtest2.jpg](https://archive.blender.org/developer/F332965/amdpremtest2.jpg) 4) Render result (renders fine): ![amdtest2.png](https://archive.blender.org/developer/F332961/amdtest2.png) Conclusion: If object with hair PS is on scene, there are some shading issues. [test_hair_ps_1673.blend](https://archive.blender.org/developer/F332962/test_hair_ps_1673.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @TomG

Added subscriber: @TomG

Added subscribers: @Sergey, @mont29

Added subscribers: @Sergey, @mont29

@Sergey maybe you have hardware to check this issue? :/

@Sergey maybe you have hardware to check this issue? :/

Tested on W8000 (which is also GCN 1.0) on Windows 10 and freshly re-installed 16.7.3 driver and can't reproduce the issue.

Questions:

  • Does the issue happen with previous Blender releases (2.76, 2.77a) ?
  • Does the issue happen with previous driver versions?
  • Does the issue depend on tile size?
Tested on W8000 (which is also GCN 1.0) on Windows 10 and freshly re-installed 16.7.3 driver and can't reproduce the issue. Questions: - Does the issue happen with previous Blender releases (2.76, 2.77a) ? - Does the issue happen with previous driver versions? - Does the issue depend on tile size?
Author

In #49019#384926, @Sergey wrote:

  • Does the issue happen with previous driver versions?

Yes

  • Does the issue depend on tile size?

No. I tried with lower tile size and the same happens.

  • Does the issue happen with previous Blender releases (2.76, 2.77a) ?

This is render result with 2.76, 2.77a with the same file. It seams that light is not computed right. Render is not the same as with 2.77.3
{F333074}test_hair_ps_1673_276_277a.png

> In #49019#384926, @Sergey wrote: > - Does the issue happen with previous driver versions? **Yes** > - Does the issue depend on tile size? **No. I tried with lower tile size and the same happens.** > - Does the issue happen with previous Blender releases (2.76, 2.77a) ? This is render result with 2.76, 2.77a with the same file. It seams that light is not computed right. Render is not the same as with 2.77.3 {[F333074](https://archive.blender.org/developer/F333074/test_hair_ps_1673_277a_hp.png)}![test_hair_ps_1673_276_277a.png](https://archive.blender.org/developer/F333071/test_hair_ps_1673_276_277a.png)

Added subscriber: @brecht

Added subscriber: @brecht

Thanks for the tests, but i still can't reproduce the issue. And for bugs like this it is crucial to be able to reproduce it in order to fix..

@brecht, maybe you can reproduce the bug?

Thanks for the tests, but i still can't reproduce the issue. And for bugs like this it is crucial to be able to reproduce it in order to fix.. @brecht, maybe you can reproduce the bug?

No, I couldn't reproduce this bug, tested with an R9 380 on Windows.

No, I couldn't reproduce this bug, tested with an R9 380 on Windows.
Author

Thanks. Than it's probably driver issue with AMD 7870.

Thanks. Than it's probably driver issue with AMD 7870.

Added subscriber: @s12a

Added subscriber: @s12a

Occurs on AMD HD7770 (GCN 1.0) on Windows 10 64bit and AMD Crimson drivers 16.8.1, using Blender 2.77a but only when hair is enabled and when the experimental GPU Rendering feature set is also enabled.

example.png

Here is a simple scene I can share where the problem easily shows.

example2.jpg

20160809-simplescene-hairbug.7z

Occurs on AMD HD7770 (GCN 1.0) on Windows 10 64bit and AMD Crimson drivers 16.8.1, using Blender 2.77a but only when hair is enabled and when the **experimental** GPU Rendering feature set is also enabled. ![example.png](https://archive.blender.org/developer/F334763/example.png) Here is a simple scene I can share where the problem easily shows. ![example2.jpg](https://archive.blender.org/developer/F334770/example2.jpg) [20160809-simplescene-hairbug.7z](https://archive.blender.org/developer/F334772/20160809-simplescene-hairbug.7z)

Added subscriber: @Alirion-2

Added subscriber: @Alirion-2

I have reported this to AMD's driver team aswell.

If helpful i could provide a Teamviewer Access to a GCN 1.0 System.

I have reported this to AMD's driver team aswell. If helpful i could provide a Teamviewer Access to a GCN 1.0 System.
Author

OpenCL error (-61): CL_INVALID_BUFFER_SIZE in clCreateBuffer
OpenCL error: CL_INVALID_MEM_OBJECT in clEnqueueWriteBuffer(cqCommandQueue, CL_MEM_PTR(mem.device_pointer), CL_TRUE, 0, size, (void*)mem.data_pointer, 0, NULL, NULL)

Today it took about 4 minutes to cancel the render.
With 2.76b, Cycles cancels render almost immediately. Scene had about 100 000 faces.

I think it has something to do how driver operates the GPU memory.
Flushing the memory takes ages.

> OpenCL error (-61): CL_INVALID_BUFFER_SIZE in clCreateBuffer > OpenCL error: CL_INVALID_MEM_OBJECT in clEnqueueWriteBuffer(cqCommandQueue, CL_MEM_PTR(mem.device_pointer), CL_TRUE, 0, size, (void*)mem.data_pointer, 0, NULL, NULL) Today it took about 4 minutes to cancel the render. With 2.76b, Cycles cancels render almost immediately. Scene had about 100 000 faces. I think it has something to do how driver operates the GPU memory. Flushing the memory takes ages.
Author

This comment was removed by @TomG

*This comment was removed by @TomG*
Author

Today's build didn't crash but hair rendering is still fault. I post console log if it helps.
Is it possible to implement test variables for console log to detect this issue's source ?
test_1682.png

test_1682.blend

hair1.JPG

hair2.JPG

Today's build didn't crash but hair rendering is still fault. I post console log if it helps. Is it possible to implement test variables for console log to detect this issue's source ? ![test_1682.png](https://archive.blender.org/developer/F337894/test_1682.png) [test_1682.blend](https://archive.blender.org/developer/F337895/test_1682.blend) ![hair1.JPG](https://archive.blender.org/developer/F337896/hair1.JPG) ![hair2.JPG](https://archive.blender.org/developer/F337897/hair2.JPG)
Author

There is issue with Interpolated mode. In the process of rendering, Blender freezes with Interpolated mode. I captured the screen when it froze.
hair int6.JPG

t1.blend

There is issue with Interpolated mode. In the process of rendering, Blender freezes with Interpolated mode. I captured the screen when it froze. ![hair int6.JPG](https://archive.blender.org/developer/F354483/hair_int6.JPG) [t1.blend](https://archive.blender.org/developer/F354485/t1.blend)

That's weird, we did not do any explicit fixes for the hair. Could be the commit which changed the internal data layout tho.

For the freezing, did you try setting tiles to some really low value (like 64x64) and rendering few samples (like, 1 sample, if that works 10 samples..) ?

That's weird, we did not do any explicit fixes for the hair. Could be the commit which changed the internal data layout tho. For the freezing, did you try setting tiles to some really low value (like 64x64) and rendering few samples (like, 1 sample, if that works 10 samples..) ?
Author

In #49019#390364, @Sergey wrote:
That's weird, we did not do any explicit fixes for the hair. Could be the commit which changed the internal data layout tho.

Whatever you changed in this release, please keep it.

For example, first 2.78 RC1 build rendered this (Crimson 16.8.2 hotfix 2):
t1hair.jpg

t1hair_s.jpg

As subdivision level of the mesh goes up, there are more tesselation artifacts if the hair is present on the scene.

Fiji and Polaris cards didn't have this issue, only 7xxx series. Could it be connected with GPU memory and internal data layout which you said you changed?
Or maybe is on behalf of AMD's 16.8.3 drivers.

For the freezing, did you try setting tiles to some really low value (like 64x64) and rendering few samples (like, 1 sample, if that works 10 samples..) ?

Thank you. I'll try.

> In #49019#390364, @Sergey wrote: > That's weird, we did not do any explicit fixes for the hair. Could be the commit which changed the internal data layout tho. Whatever you changed in this release, please keep it. For example, first 2.78 RC1 build rendered this (Crimson 16.8.2 hotfix 2): ![t1hair.jpg](https://archive.blender.org/developer/F355170/t1hair.jpg) ![t1hair_s.jpg](https://archive.blender.org/developer/F355172/t1hair_s.jpg) As subdivision level of the mesh goes up, there are more tesselation artifacts if the hair is present on the scene. Fiji and Polaris cards didn't have this issue, only 7xxx series. Could it be connected with GPU memory and internal data layout which you said you changed? Or maybe is on behalf of AMD's 16.8.3 drivers. >For the freezing, did you try setting tiles to some really low value (like 64x64) and rendering few samples (like, 1 sample, if that works 10 samples..) ? Thank you. I'll try.
Author

@Sergey I did't set up the GPU compute properly.
The issue is still there in the build 9.9.2016 with 16.8.3.
t2.png

I tried various tiled sizes:
default, 64×60, 512×512 and the same weird shading is present.

@Sergey I did't set up the GPU compute properly. The issue is still there in the build 9.9.2016 with 16.8.3. ![t2.png](https://archive.blender.org/developer/F356896/t2.png) I tried various tiled sizes: default, 64×60, 512×512 and the same weird shading is present.

Added subscriber: @Jns_76

Added subscriber: @Jns_76

I have the same problem with HD7950.
Driver: Crimson 15.12 (сan test with latest version if needed)

blender-2.78-rc2-windows64
GPU:
untitled1.png

CPU:
untitled.png

Blender 2.77a (2016-04-05) hash: abf6f08
GPU:
untitled1_old.png

CPU:
identical to GPU

I have the same problem with HD7950. Driver: Crimson 15.12 (сan test with latest version if needed) blender-2.78-**rc2**-windows64 GPU: ![untitled1.png](https://archive.blender.org/developer/F362231/untitled1.png) CPU: ![untitled.png](https://archive.blender.org/developer/F362233/untitled.png) Blender 2.77a (2016-04-05) hash: abf6f08 GPU: ![untitled1_old.png](https://archive.blender.org/developer/F362236/untitled1_old.png) CPU: identical to GPU
Author

@Jns_76 please test newest drivers
http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64
16.9.1

Also, report to AMD http://www.amd.com/report because apparently Fiji and Polaris cards are not affected with this.
AMD is reworking issues from the latest versions of drivers so it's better to give feedback.

Please, test this file https://developer.blender.org/T49371
I think this 2 issues could have some connections because if you have more subdivision levels (standard or new adaptive microdisplacement), there are more tesselation artifacts/render result is darken.

@Jns_76 please test newest drivers http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64 16.9.1 Also, report to AMD http://www.amd.com/report because apparently Fiji and Polaris cards are not affected with this. AMD is reworking issues from the latest versions of drivers so it's better to give feedback. Please, test this file https://developer.blender.org/T49371 I think this 2 issues could have some connections because if you have more subdivision levels (standard or new adaptive microdisplacement), there are more tesselation artifacts/render result is darken.

In #49019#392438, @TomG wrote:
@Jns_76 please test newest drivers

Installed. Now everything is broken. Great.
whql-win7-64bit-radeon-software-crimson-16.9.1-sep13

blender-2.78-rc2-windows64
sun strength-50
untitled rc2 hair_on sun_50.png

Blender 2.77a (2016-04-05) hash: abf6f08
sun strength-50
untitled 2.77a hair_on sun_50.png

Blender both versions
sun strength-1
untitled 2.77a hair_on sun_1.png

I don't even sure how to report this...

> In #49019#392438, @TomG wrote: > @Jns_76 please test newest drivers Installed. Now everything is broken. Great. *whql-win7-64bit-radeon-software-crimson-16.9.1-sep13* blender-2.78-**rc2**-windows64 sun strength-50 ![untitled rc2 hair_on sun_50.png](https://archive.blender.org/developer/F363053/untitled_rc2_hair_on_sun_50.png) Blender 2.77a (2016-04-05) hash: abf6f08 sun strength-50 ![untitled 2.77a hair_on sun_50.png](https://archive.blender.org/developer/F363055/untitled_2.77a_hair_on_sun_50.png) Blender both versions sun strength-1 ![untitled 2.77a hair_on sun_1.png](https://archive.blender.org/developer/F363057/untitled_2.77a_hair_on_sun_1.png) I don't even sure how to report this...
Author

Added subscriber: @bliblubli

Added subscriber: @bliblubli
Author

Testing t1.blend with Catalyst 16.9.1
CPU render ttcpu.png


GPU render with blender-2.78-78c380d-win64 build (you can see weird shading on sphere and in viewport comparing to CPU render)
tt1.png
************/*With @bliblubli build https:*uploadfiles.io/90e0707ou
you can see strange tesselation shading on sphere is gone. But render is too dark still.
tt3.png
************///
Could you implement bliblubli's OpenCl code? It solves tesselation shading when hair PS in on scene.

Testing [t1.blend](https://archive.blender.org/developer/F370821/t1.blend) with Catalyst 16.9.1 CPU render ![ttcpu.png](https://archive.blender.org/developer/F370812/ttcpu.png) ************ GPU render with **blender-2.78-78c380d-win64** build (you can see weird shading on sphere and in viewport comparing to CPU render) ![tt1.png](https://archive.blender.org/developer/F370814/tt1.png) ************/*With @bliblubli build https:*uploadfiles.io/90e0707ou you can see strange tesselation shading on sphere is gone. But render is too dark still. ![tt3.png](https://archive.blender.org/developer/F370819/tt3.png) ************/// Could you implement bliblubli's OpenCl code? It solves tesselation shading when hair PS in on scene.
Author

Still black screen and hair PS issue with blender-2.78-3e460b6-win64.zip and Crimson 10.1 on AMD 7870.

Still black screen and hair PS issue with blender-2.78-3e460b6-win64.zip and Crimson 10.1 on AMD 7870.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Please try again with latest build from builder.blender.org/download

Please try again with latest build from builder.blender.org/download

Added subscriber: @fablefox

Added subscriber: @fablefox

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Fable Fox self-assigned this 2017-05-04 08:41:03 +02:00
  1. No news in over a week... closing
  2. Last version tested was in Oct 2016.
1) No news in over a week... closing 2) Last version tested was in Oct 2016.

Added subscriber: @RenatoMeneses

Added subscriber: @RenatoMeneses

I'm getting the same issue when I try to render hair in 3D view, but it render well in final render.

My system: Rx 480 + Rx 470

It happens in each one alone and with both together with or without Crossfire:

OpenCL error (-61): CL_INVALID_BUFFER_SIZE in clCreateBuffer

I'm getting the same issue when I try to render hair in 3D view, but it render well in final render. My system: Rx 480 + Rx 470 It happens in each one alone and with both together with or without Crossfire: OpenCL error (-61): CL_INVALID_BUFFER_SIZE in clCreateBuffer
Member

@RenatoMeneses can you please create a new bug report?

@RenatoMeneses can you please create a new bug report?
Here you go: https://developer.blender.org/T51755
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#49019
No description provided.