Expose object node in XML API #8
No reviewers
Labels
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: blender/cycles#8
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "howetuft/cycles:caustics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Object node is not currently exposed in XML API (see
https://devtalk.blender.org/t/cycles-standalone-caustics/32861/2).
At now, Object nodes are only implicitly created when Mesh nodes are
read. This prevents users of the XML API from accessing features that
are dependent on this node, in particular caustics.
This commit implements the following solution:
Add a function for reading Object XML nodes
Provide the XML Read State with an object property, which allows to
set the current Object for state’s sub-nodes.
When creating a Mesh, if the object of the Read State is set, use that
object rather than creating a new one. Otherwise, follow the previous
behaviour (implicit creation).
An example scene is also provided, illustrating how caustics can be
rendered using this functionality.
Thanks for the patch. From a quick look this looks okay. Let's wait for Brecht for final approval though.
Thanks.
I'm unsure how long we will keep the XML file format alive, at some point I would like to remove it in favor of USD. But as long as that is not a complete replacement we can keep doing improvements like this.
Cycles Standalone - Expose Object node in XML APIto Expose object node in XML APIThank you!
I'm attached to the XML API beyond reason, but I must be one of the only ones ;-)
USD (or glTF?) is likely to be the future, however: it would be a sensible move.