removed sentences that were based on wrong assumptions.
- - -
I was considering purchasing a Houdini Indie license for my personal projects after having read trough the Houdini Indie FAQ.
https://www.sidefx.com/faq/houdini-indie-faq/#faq104
What I like to do is create OpenVDB files in Houdini Indie and then export them as .orbx to OctaneRender standalone.
In OctaneRender standalone I would then like to combine .orbx files exported from different software to one scene.
Currently I am confused if this is even possible with the Houdini Indie version.
To me it seems that the OctaneRender plugin imposes further restrictions on the workflow that are not mentioned at all in the Houdini Indie FAQ.
- - -
Houdini Indie FAQ:
https://www.sidefx.com/faq/houdini-indie-faq/
My impression was that the only technical limitation was the render size restriction:
What are the render restrictions for Houdini Indie?
When rendering image sequences, you are restricted to 4096 x 4096 pixels. There are not restrictions for still images. The image sequence restrictions apply to Mantra and any third party renderers supported by Indie.
Source:
https://www.sidefx.com/faq/houdini-indie-faq/#faq175
- - -
However in the Octane plugin release texts there are further limitations listed:
This plugin is also compatible with Houdini 15.5/16.0/16.5 Indie. In this case, the plugin will have a 4k limited resolution while rendering sequences, and the scene export and cloud rendering features disabled.
Source:
viewtopic.php?f=102&t=66348#p334840
Nowhere on the Houdini Indie FAQ it is mentioned that scene export and cloud rendering need to be disabled by 3rd party plugins.
- - -
Questions:
1) Are scene export and cloud rendering disabled so users cannot "work around" the " image sequence restrictions " or are these technical limitations?
2) Did SideFX explicitely ask Otoy to disable scene export and cloud rendering features or was this just a preventive measure?
3) Does Houdini Indie itself allow export of OpenVDB files?
- - -