<div dir="ltr"><div><div><div><div><div><div><div><div>Hi,<br></div>according that threads participants, AMD 14.1 drivers have a working implementation...<br><a href="http://blenderartists.org/forum/showthread.php?254521-A-good-news-for-AMD-ATI-Graphic-cards-owners/page61">http://blenderartists.org/forum/showthread.php?254521-A-good-news-for-AMD-ATI-Graphic-cards-owners/page61</a><br>
<br></div>With that in mind, any developer thats adding features to cycles should now consider using conventions and code suitable enough to work on both CUDA and Opencl Capable devices.....<br><br></div>Bare in mind that INTEL,NVIDIA and AMD use opencl.....<br>
<br></div>Getting things a step closer to multi-platformness should be an objective for blender cycles.....<br><br></div>As well focus on opencl bug reports(commencing February 1st 2014)<br><br></div>And finally optimizations for the opencl implementation of cycles...<br>
<br></div>Peace out<br><br></div>PS can cycles developers review the following quote, and possible reflect this on the cycles code/kernel.....<br><br><div><i><b>So, in the end, for practical purposes pretty much only the basic features already enabled by default will work.<br>
<br>
These are the features I really haven't been able to enable in any way:<br>
<br>
__LAMP_MIS__ --> doubles the OpenCL kernel build time, PC hangs or Blender crashes when the render starts<br>
__CAMERA_MOTION__ --> errors in console<br>
__HAIR__ --> needs #__MULTI_CLOSURE to not end up in console
errors, but makes Blender crash when compiling the OpenCL kernel
otherwise
</b></i><div><div><div><div><div><div><br>Peace<br></div></div></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 3 January 2014 14:31, <span dir="ltr"><<a href="mailto:emmi.spammi@t-online.de" target="_blank">emmi.spammi@t-online.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I'm also following the developement/fixing of the ATI issues. It seems<br>
to work. I can render on my AMD Pitcairn.<br>
However it is much slower than my CPU (which was not the original<br>
intention ;)).<br>
<br>
I would be interested in any news of performance improvements.<br>
<br>
Best regards<br>
<br>
Emanuel<br>
<br>
PS: CPU: Intel i5-4570 (3,2GHz); GPU: AMD Radeon HD7850 1GB<br>
<br>
<br>
<br>
Am 03.01.2014 14:24, schrieb Gottfried Hofmann:<br>
<div class="im">> Check this threa, especially the last few pages:<br>
><br>
> <a href="http://blenderartists.org/forum/showthread.php?254521-A-good-news-for-AMD-ATI-Graphic-cards-owners" target="_blank">http://blenderartists.org/forum/showthread.php?254521-A-good-news-for-AMD-ATI-Graphic-cards-owners</a><br>
><br>
> Seems like there is hope for AMD users...<br>
><br>
> On 01/03/2014 02:12 PM, Geo A wrote:<br>
>> Are there any news regarding cycles being compatible with AMD cpus or<br>
>> ATI gpus sooner or later?<br>
><br>
<br>
</div><div class=""><div class="h5">_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
</div></div></blockquote></div><br></div></div>