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
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
|
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 |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 31 October 2016, 16:22 GMT
Reason for closing: Fixed
Monday, 31 October 2016, 16:22 GMT
Reason for closing: Fixed
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.
Great!