[Bf-cycles] Dso api in Cycles
stewreo at gmail.com
Tue May 15 15:20:03 CEST 2018
other than OSL support, there is no customisation API for Cycles. At the moment, there is no support for procedural primitives of any kind. Cycles supports triangles and hair curves/ribbons. The built-in support of subdivision surfaces and displacement is a view-dependent tessellation that is performed prior to the actual rendering process.
In theory, it should be possible to extend Cycles with any kind of ray/procedural intersection. Procedural objects would need to be able to return bounding boxes, respond to ray hit queries and be able to fill out a data structure with intersection point, UV coordinates, derivatives, object ID etc after an intersection. A full integration would include CUDA and OpenCL code paths, which may be hard when your procedural relies on disk caches or dynamic memory allocations.
> On 15. May 2018, at 15:05, Nicolas Chaverou <nicolas.chaverou at golaem.com> wrote:
> Hi there,
> I looked over the Cycles documentation and its roadmap but could not found the answer;
> We'd like to check the feasibility of creating a DSO plugin for Cycles which could create delayed geometry at render time; Does anyone know what if Cycles has such an API for this ?
> +33 (0)2 99 27 21 44
> http://www.golaem.com <http://www.golaem.com/>
> Bf-cycles mailing list
> Bf-cycles at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles