<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Hi Lukas</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">this is great information thank you</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">will take a look at the source and try to figure it out</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">thank you</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 30, 2017 at 5:41 PM, Lukas Stockner <span dir="ltr"><<a href="mailto:lukas.stockner@freenet.de" target="_blank">lukas.stockner@freenet.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
I'm not sure how Houdini plugins work - I guess they're written in C++?<br>
You'll want to get rid of the XML step in between and link to Cycles directly.<br>
<br>
Cycles is basically split up into 4 "levels" (in the code: /blender/, /render/, /device/ and /kernel/ - all paths relative to the Cycles folder, which is intern/cycles/ in the Blender source)<br>
The first part is the Blender-specific glue logic, that's the one that you basically need to replicate for Houdini. The other three are independent of the underlying application, you can re-use those.<br>
<br>
So, my tips would be:<br>
- Set up a build environment where you can compile Cycles (without the /blender/ part) as a library and link it to your plugin.<br>
- Look at the Cycles API in /render/ (a good place to start is /render/session.h)<br>
- Look at how the Blender integration works - for setting up a Session and rendering, check /blender/blender_session.cpp and for syncing your data, check /blender/blender_sync.cpp<br>
- Write your own glue code that manages the Session and syncs the data from Houdini.<br>
<br>
Another example that you can check regarding how to call the "Cycles API" is the standalone renderer that you're probably using with XML files currently, it's in the /app/ folder.<br>
<div><div class="h5"><br>
Am 31.01.2017 um 01:27 schrieb Alvaro Castaneda:<br>
> Hi Everyone<br>
> I'm sure this list is full of amazing intelligent people and my questions might be a little silly but I just have to ask.<br>
><br>
> Any guidelines, tips or code I can look at for integrating Cycles into another app?<br>
><br>
> I'm trying to make it work with Houdini, in houdini the way renderer integrations work is really similar to who the Renderman for Blender works, basically you have 2 apps talking to each other.<br>
><br>
> right now I can write an XML from Houdini and launch Cycles and renders ok, the main thing I would like to implement is the interactivity part, making cycles live to changes from Houdini, any tips on how that is done?<br>
><br>
> thank you for you help for this wannabe developer<br>
><br>
> thanks<br>
><br>
><br>
</div></div>> ______________________________<wbr>_________________<br>
> Bf-cycles mailing list<br>
> <a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
> <a href="https://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">https://lists.blender.org/<wbr>mailman/listinfo/bf-cycles</a><br>
><br>
<br>
<br>______________________________<wbr>_________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">https://lists.blender.org/<wbr>mailman/listinfo/bf-cycles</a><br>
<br></blockquote></div><br></div>