FS#51364 - [blender] Fails to do antialiasing with Cuda

Attached to Project: Community Packages
Opened by Miguel Espada (ridli) - Thursday, 13 October 2016, 17:01 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 31 October 2016, 16:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
current blender package 17:2.78-1 uses a cuda kernel that fails to do antialiasing on cycles gpu render pathtracing mode. I've tried at least a couple of gtx 970.
According to what I've seen on blender dev pages, this bug ocurred at some point of the 2.78 development but it's solved on the release. I've tested the current tar.gz package from blender.org and it's right indeed.

Additional info:
blender package 17:2.78-1

Steps to reproduce:
pdf document included
   arch bugreport.pdf (972.7 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 31 October 2016, 16:22 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 16 October 2016, 04:58 GMT
Hang on, so what's the problem with our packaging? If it's not fixed in the upstream package that we use, we'll have to wait for a new upstream version.
Comment by Miguel Espada (ridli) - Sunday, 16 October 2016, 10:41 GMT
But the current blender.org package is ok. Did you take another upstream source? or maybe it's the upstream cuda package or libGL/libGLU package that it's compiled against?

I could confirm that if you extract the cycles addon from the blender.org distribution package "../2.78/scripts/addons/cycles" and overwrite the one installed from the arch repository package "/usr/share/blender/2.78/scripts/addons/cycles", the cuda antialisaing works fine.

Despite all this, I think that in current package state has to be marked as broken or something similar because due to this it could cause strong headaches on any environment and losses on professional ones.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 24 October 2016, 01:44 GMT
This might be fixed after the blender rebuild is moved from the boost rebuild in staging.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 30 October 2016, 03:35 GMT
Works for me now.
Comment by Miguel Espada (ridli) - Sunday, 30 October 2016, 10:40 GMT
Yes, it works flawlessly now.
Great!
Comment by Miguel Espada (ridli) - Sunday, 30 October 2016, 20:52 GMT
test: https://www.youtube.com/watch?v=kBPsroIENtY

Loading...