[Bf-cycles] osl node

Lukas Tönne lukas.toenne at gmail.com
Wed Oct 24 00:24:01 CEST 2012


Great :)

Maybe with the compile function being part of render engine API we can
get rid of the global shader update tag easier now (marked as a XXX
hack).

The refresh time is also quite annoying still. The lagging UI was what
i tried to fix with the patch for device cancelling, which turned out
to be too unstable ([1], [2]). If individual shader updates can reduce
this UI lag sufficiently that would also be ok.

[1]
http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=50528

[2]
http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=50696

On Tue, Oct 23, 2012 at 11:59 PM, Brecht Van Lommel
<brechtvanlommel at pandora.be> wrote:
> Hi,
>
> I did some changes, making the node a generic shader script node
> instead of OSL script. It was mostly renaming and code refactoring to
> avoid the cycles specific operator. I'll continue tomorrow and look
> closer into the update system. I also have some plans to make cycles
> only reload individual shaders when you edit them, instead of all, to
> shorten refresh time after tweaking values.
>
> Brecht.
>
> On Sun, Oct 21, 2012 at 9:36 PM, Dalai Felinto <dfelinto at gmail.com> wrote:
>> Hi Brecht,
>> I updated the todo list and git pushed my latest changes here:
>> http://wiki.blender.org/index.php/User:Dfelinto/OSLNodeTodos
>>
>> If you need one big patch with "lukas et al" changes you can get it here:
>> https://dl.dropbox.com/u/3292898/Patches/12.10.21-cycles_osl.diff
>> (this is more for someone else willing to try it, I know you can get
>> it from git directly)
>>
>> Small note: I can't get the osl node to compile when running from
>> xcode. It works in Jen's computer, so dunno. So for the time being I'm
>> compiling with cmake+make. The error I get is
>> http://www.pasteall.org/36460
>>
>> Also, there are different fronts of work. On one end there is polishing to do:
>> * we need to improve the update system, and how the compile operator
>> is called (right now it can be called from both Text Editor and the
>> Node panel, so it's a bit of a mess) .. and we need to get a nice way
>> to update all scripts using the same text.
>> * a md5 or more robust way of checking if the file changed (something
>> that blender could have in a low level if I may say) (instead of the
>> timestamp).
>> * proper error messages/handling when recompile fails.
>> * . . .
>>
>> Another is OSL patching:
>> * basically implement support for string stream i/o
>>
>> If I find the time I will probably look at the OSL patch todos first.
>> So don't be shy in tearing up the current "blender" code apart. And I
>> will try to be online at night and morning in case you have questions
>> (pacific time), that should help.
>>
>> Thanks,
>> Dalai
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-cycles
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles


More information about the Bf-cycles mailing list