gawain presents problems when particle #50935

New Issue

Dalai Felinto · 2017-03-13T12:40:03+01:00

Dalai Felinto commented

2017-03-13 12:40:03 +01:00

In Blender 2.8, the particle drawing code seems to be stressing the gawain buffer allocation.

If you open the file: bug-particles-draw-28.blend
And play around with it (e.g., rotate the view), you get:

The file is simply a cube with 50,000 particles displayed as circles.

In Blender 2.8, the particle drawing code seems to be stressing the `gawain` buffer allocation. If you open the file: [bug-particles-draw-28.blend](https://archive.blender.org/developer/F508370/bug-particles-draw-28.blend) And play around with it (e.g., rotate the view), you get: ![bug-circle-partcles.png](https://archive.blender.org/developer/F508368/bug-circle-partcles.png) The file is simply a cube with 50,000 particles displayed as circles.

Dalai Felinto commented

2017-03-13 12:40:03 +01:00

Changed status to: 'Open'

Dalai Felinto commented

2017-03-13 12:40:03 +01:00

Added subscriber: @dfelinto

Mike Erwin was assigned by Dalai Felinto

2017-03-13 12:40:29 +01:00

Dalai Felinto commented

2017-03-13 12:40:29 +01:00

Added subscriber: @fclem

Antonio Vazquez commented

2017-03-13 13:09:45 +01:00

Added subscriber: @antoniov

Antonio Vazquez commented

2017-03-13 13:09:45 +01:00

I can confirm this bug in Windows 10 compiled in VS2015 64bits, but it's something that I have seen not only using particles.

Sometimes, I get weird results using differents GPUs, but it's not easy to determine when or why. Lately, with last versions the error doesn't appears as easily as before, but it's not solved yet.

I can confirm this bug in Windows 10 compiled in VS2015 64bits, but it's something that I have seen not only using particles. Sometimes, I get weird results using differents GPUs, but it's not easy to determine when or why. Lately, with last versions the error doesn't appears as easily as before, but it's not solved yet.

Mike Erwin commented

2017-03-13 21:43:54 +01:00

No problems on Mac, tested on Intel and NV. Trying Windows next...

Mike Erwin commented

2017-03-13 22:58:52 +01:00

After more testing -- zoom/rotate viewpoint, run animation -- I'm still not seeing this problem.

Windows 10, VS2015 on Intel 520
Windows 10, VS2017 on AMD FX-9800P

On what GPUs do you see the problem? Does debug vs. release build make a difference?

After more testing -- zoom/rotate viewpoint, run animation -- I'm still not seeing this problem. Windows 10, VS2015 on Intel 520 Windows 10, VS2017 on AMD FX-9800P On what GPUs do you see the problem? Does debug vs. release build make a difference?

Clément Foucault commented

2017-03-14 04:23:56 +01:00

We tested on Debug build + Linux + Nvidia (Closed source driver) and the bug is happening on 2 machines: My laptop (GTX960m) and Dalai's desktop (Some Quadro). Will try release build.

Dalai Felinto commented

2017-03-14 10:44:50 +01:00

It has the same problem in Release build (Linux)

Renderer: 'Quadro K6000/PCIe/SSE2'
Vendor: 'NVIDIA Corporation'
Version: '4.5.0 NVIDIA 375.26'

I get the problem as soon as I open the test Blender file.

It has the same problem in Release build (Linux) Renderer: 'Quadro K6000/PCIe/SSE2' Vendor: 'NVIDIA Corporation' Version: '4.5.0 NVIDIA 375.26' I get the problem as soon as I open the test Blender file.

Dalai Felinto commented

2017-03-14 12:26:45 +01:00

I tried in a Linux box with a highend ATI and it doesn't happen either.

Renderer: 'AMD Radeon (TM) Pro WX 7100 DUO Graphics'
Vendor: 'ATI Technologies Inc.'
Cersion: '4.5.13468 Compatibility Profile Context 16.60.3'

I tried in a Linux box with a highend ATI and it doesn't happen either. Renderer: 'AMD Radeon (TM) Pro WX 7100 DUO Graphics' Vendor: 'ATI Technologies Inc.' Cersion: '4.5.13468 Compatibility Profile Context 16.60.3'

Mike Erwin commented

2017-03-14 15:52:31 +01:00

Thanks for the info! I suspect this is a buffer alignment/padding issue. I'm talking to someone from NVIDIA tonight (local C++ meetup) and will ask him for details.

@antoniov do you see this only on NVIDIA?

Thanks for the info! I suspect this is a buffer alignment/padding issue. I'm talking to someone from NVIDIA tonight (local C++ meetup) and will ask him for details. @antoniov do you see this only on NVIDIA?

Antonio Vazquez commented

2017-03-14 18:59:33 +01:00

@MikeErwin Tested in Windows 10 GTX660 and get the error in Debug and Release compiled with VS2015 64bits. The compilation was without CUDA support in Cycles.

Vendor: NVIDIA Corporation
Renderer: GeForce GTX 660/PCIe/SSE2
Version: 4.5.0 NVIDIA 376.53

What can I do to provide you more information?

@MikeErwin Tested in Windows 10 GTX660 and get the error in Debug and Release compiled with VS2015 64bits. The compilation was without CUDA support in Cycles. Vendor: NVIDIA Corporation Renderer: GeForce GTX 660/PCIe/SSE2 Version: 4.5.0 NVIDIA 376.53 What can I do to provide you more information?

Dalai Felinto commented

2017-06-08 16:04:59 +02:00

@fclem are you still running into this? In my current computer (Ryzen + AMD 480) the problem is gone.