Thanks for explanation Brecht. I'll pass this on to the renderfarm and see what they can do.<div><br></div><div>Cheers!<br><br><div class="gmail_quote">On Tue, Oct 9, 2012 at 7:00 PM, <span dir="ltr"><<a href="mailto:bf-cycles-request@blender.org" target="_blank">bf-cycles-request@blender.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Bf-cycles mailing list submissions to<br>
<a href="mailto:bf-cycles@blender.org">bf-cycles@blender.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:bf-cycles-request@blender.org">bf-cycles-request@blender.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:bf-cycles-owner@blender.org">bf-cycles-owner@blender.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Bf-cycles digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Multi-GPU tiling support? (Brecht Van Lommel)<br>
2. UV, not working well in OSL Script node (Dalai Felinto)<br>
3. Re: UV, not working well in OSL Script node (Brecht Van Lommel)<br>
4. Re: UV, not working well in OSL Script node (Lukas T?nne)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 8 Oct 2012 12:49:12 +0200<br>
From: Brecht Van Lommel <<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>><br>
Subject: Re: [Bf-cycles] Multi-GPU tiling support?<br>
To: <a href="mailto:bf-cycles@blender.org">bf-cycles@blender.org</a><br>
Message-ID:<br>
<CAKFUgC35A0qT+zkLftyALvh=<a href="mailto:HGMZ5bn31gsWr0-EtzuEjPGJEQ@mail.gmail.com">HGMZ5bn31gsWr0-EtzuEjPGJEQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Yes, 6x6 tiles should allow 36 GPU's to work on the same image. But<br>
even before the tiling multi GPU was already working. So more likely<br>
it has something to do with the configuration or Cycles not<br>
recognizing the GPU's. Cycles should by default use all GPU's except<br>
for the one used for display in case of multi GPU. So if this is a<br>
dual GPU system that might be the problem that causes only one of the<br>
two to be used.<br>
<br>
This script can be used to print which GPU devices is used and which<br>
settings are available, if you have some way to run.<br>
<a href="http://www.pasteall.org/36025/python" target="_blank">http://www.pasteall.org/36025/python</a><br>
<br>
Ideally the render farm should set things up such that the user<br>
preferences are already saved with the right configuration.<br>
<br>
Brecht.<br>
<br>
On Mon, Oct 8, 2012 at 3:54 AM, Andrew Price <<a href="mailto:redbytex@gmail.com">redbytex@gmail.com</a>> wrote:<br>
> Hey all, I sent this yesterday but I'm not sure it went through, so I'm<br>
> sending it again (sorry if you get it twice).<br>
><br>
> Does tile rendering allow for multiple GPUs to work on the same image? Eg. 6<br>
> x 6 tiles, allow for 36 GPUs to work on the frame simultaneously.<br>
><br>
> I'm creating a few animations with Cycles and have been using the renderfarm<br>
> RenderFlow to render them. So far we have only been able to get one GPU to<br>
> work on one frame at a time, but we're not sure if this is normal.<br>
><br>
> Thanks for your help.<br>
><br>
><br>
> --<br>
> Regards,<br>
> Andrew Price<br>
> <a href="http://www.blenderguru.com" target="_blank">www.blenderguru.com</a><br>
><br>
> _______________________________________________<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>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 8 Oct 2012 23:19:09 -0700<br>
From: Dalai Felinto <<a href="mailto:dfelinto@gmail.com">dfelinto@gmail.com</a>><br>
Subject: [Bf-cycles] UV, not working well in OSL Script node<br>
To: <a href="mailto:bf-cycles@blender.org">bf-cycles@blender.org</a><br>
Message-ID:<br>
<<a href="mailto:CAGjvzG3XN8EpNWgmpkMr7jCe7by1txPBczKsDqU8P0Lnt1JE9w@mail.gmail.com">CAGjvzG3XN8EpNWgmpkMr7jCe7by1txPBczKsDqU8P0Lnt1JE9w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi there,<br>
<br>
I'm testing the OSL node (in lukas' branch) and I noticed that u,v is<br>
not getting the information from Blender.<br>
See file <a href="http://www.pasteall.org/blend/16845" target="_blank">http://www.pasteall.org/blend/16845</a> or image:<br>
<a href="http://www.pasteall.org/pic/38655" target="_blank">http://www.pasteall.org/pic/38655</a><br>
<br>
The test shader source is very simple:<br>
####<br>
surface<br>
example_shader_1<br>
(<br>
output closure color fora = 0<br>
)<br>
{<br>
fora = color(u, v, 1.0) * emission();<br>
}<br>
####<br>
<br>
Any clues on whether it's a todo in cycles, or something in the "OSL<br>
script" node implementation?<br>
Thanks,<br>
Dalai<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 9 Oct 2012 08:41:23 +0200<br>
From: Brecht Van Lommel <<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>><br>
Subject: Re: [Bf-cycles] UV, not working well in OSL Script node<br>
To: <a href="mailto:bf-cycles@blender.org">bf-cycles@blender.org</a><br>
Message-ID:<br>
<CAKFUgC0nCji9-dh0wB8a+JvyTLMLyF=<a href="mailto:1tTZ8wvWidM2-esOkcA@mail.gmail.com">1tTZ8wvWidM2-esOkcA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
The sphere looks correct to me. The u,v values here are like the<br>
Parametric output in the Geometry node (barycentric coordinates in the<br>
triangle), not a UV layer. If the plane has that material assigned too<br>
that would be a problem, but otherwise don't see the bug.<br>
<br>
For the UV layer though, there is a bit of a design issue here. Cycles<br>
only exports mesh data layers when they are requested by the shader<br>
(to save memory and export time). However for an arbitrary OSL shader<br>
I don't know how to determine automatically if they need such<br>
attributes.<br>
<br>
Brecht.<br>
<br>
On Tue, Oct 9, 2012 at 8:19 AM, Dalai Felinto <<a href="mailto:dfelinto@gmail.com">dfelinto@gmail.com</a>> wrote:<br>
> Hi there,<br>
><br>
> I'm testing the OSL node (in lukas' branch) and I noticed that u,v is<br>
> not getting the information from Blender.<br>
> See file <a href="http://www.pasteall.org/blend/16845" target="_blank">http://www.pasteall.org/blend/16845</a> or image:<br>
> <a href="http://www.pasteall.org/pic/38655" target="_blank">http://www.pasteall.org/pic/38655</a><br>
><br>
> The test shader source is very simple:<br>
> ####<br>
> surface<br>
> example_shader_1<br>
> (<br>
> output closure color fora = 0<br>
> )<br>
> {<br>
> fora = color(u, v, 1.0) * emission();<br>
> }<br>
> ####<br>
><br>
> Any clues on whether it's a todo in cycles, or something in the "OSL<br>
> script" node implementation?<br>
> Thanks,<br>
> Dalai<br>
> _______________________________________________<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>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 9 Oct 2012 09:17:12 +0200<br>
From: Lukas T?nne <<a href="mailto:lukas.toenne@gmail.com">lukas.toenne@gmail.com</a>><br>
Subject: Re: [Bf-cycles] UV, not working well in OSL Script node<br>
To: <a href="mailto:bf-cycles@blender.org">bf-cycles@blender.org</a><br>
Message-ID:<br>
<CANhmeOi5Bxvd=3a8dN7gyR-9r7B5v2V4vZeA2=<a href="mailto:48FRPx6BcA8Q@mail.gmail.com">48FRPx6BcA8Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Had a little discussion with Dalai about how to make sure such shaders<br>
are still portable to non-cycles renderers. Apart from the brute-force<br>
solution (always request UV in the OSL script node), we came up with<br>
two options:<br>
<br>
1) Use a generic "Vector" input, like other nodes. This has the<br>
advantage of being flexible, but is not as simple as using u/v globals<br>
directly.<br>
<br>
2) Use shader metadata to encode cycles attribute requests:<br>
<br>
surface<br>
example_shader_1<br>
[[ string attributes = "UV,SomeCustomAttribute" ]]<br>
(<br>
output closure color fora = 0<br>
)<br>
{<br>
fora = color(u, v, 1.0) * emission();<br>
}<br>
<br>
Still this second approach would only work when actually writing the<br>
node *for cycles*. Using a shader from other render engines which<br>
doesn't have this request feature/limitation would still not work<br>
without manual fixing ...<br>
<br>
Maybe it should be added as an option on user level: Simple checkbox<br>
list in advanced options (sidebar) to enable UV and other requests.<br>
Not very elegant though.<br>
<br>
On Tue, Oct 9, 2012 at 8:41 AM, Brecht Van Lommel<br>
<<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>> wrote:<br>
> The sphere looks correct to me. The u,v values here are like the<br>
> Parametric output in the Geometry node (barycentric coordinates in the<br>
> triangle), not a UV layer. If the plane has that material assigned too<br>
> that would be a problem, but otherwise don't see the bug.<br>
><br>
> For the UV layer though, there is a bit of a design issue here. Cycles<br>
> only exports mesh data layers when they are requested by the shader<br>
> (to save memory and export time). However for an arbitrary OSL shader<br>
> I don't know how to determine automatically if they need such<br>
> attributes.<br>
><br>
> Brecht.<br>
><br>
> On Tue, Oct 9, 2012 at 8:19 AM, Dalai Felinto <<a href="mailto:dfelinto@gmail.com">dfelinto@gmail.com</a>> wrote:<br>
>> Hi there,<br>
>><br>
>> I'm testing the OSL node (in lukas' branch) and I noticed that u,v is<br>
>> not getting the information from Blender.<br>
>> See file <a href="http://www.pasteall.org/blend/16845" target="_blank">http://www.pasteall.org/blend/16845</a> or image:<br>
>> <a href="http://www.pasteall.org/pic/38655" target="_blank">http://www.pasteall.org/pic/38655</a><br>
>><br>
>> The test shader source is very simple:<br>
>> ####<br>
>> surface<br>
>> example_shader_1<br>
>> (<br>
>> output closure color fora = 0<br>
>> )<br>
>> {<br>
>> fora = color(u, v, 1.0) * emission();<br>
>> }<br>
>> ####<br>
>><br>
>> Any clues on whether it's a todo in cycles, or something in the "OSL<br>
>> script" node implementation?<br>
>> Thanks,<br>
>> Dalai<br>
>> _______________________________________________<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>
> _______________________________________________<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>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<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>
<br>
<br>
End of Bf-cycles Digest, Vol 18, Issue 4<br>
****************************************<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br>Andrew Price<br><a href="http://www.blenderguru.com" target="_blank">http://www.blenderguru.com</a><br><div style="display:inline"></div><br>
</div>