Yep it can be.
If you want to trigger the evaluation by rendering instead of through a
script, then having an empty mesh might make a difference, but it shouldn't
as the renderer still has to query the empty geometry to find out if it is
empty, forcing the evaluation.
On Wed, May 6, 2015 at 1:54 P
Thanks for posting your workaround Leonard. I haven't had a chance to check
out your solution but can the geometry even be an empty polygon object?
On Wed, May 6, 2015 at 5:32 AM, Leonard Koch
wrote:
> The solution to this problem is to have the splice operator output onto
> the PolygonMesh port
The solution to this problem is to have the splice operator output onto the
PolygonMesh port of a dummy object, one that doesn't have anything to do
with the cloud we're pulling the data from. To then force evaluation in a
session without a viewport we just need to access the geometry of that
dummy
Yeah, we had the same problem but for us it was for rendering. We had
put our SpliceOp on a Null and since Arnold was never pulling the null
data, the operator was never evaluated and it didn't render. So we put
the Splice Op on a mesh, a very tiny sphere that was being passed to
Arnold so the
Thanks Jason.
Yeah that is interesting information. I had already figured that part out
though (see my response to Renaud).
It is very neat though to see it all described in detail.
We're now having this weird issue of splice not being able to pull ice
attributes when forced to evaluate this way.
On 05/05/15 9:15, Leonard Koch wrote:
We're running splice in Softimage to render out a
pointcloud using a renderer written in KL.
Sounds cool!
Would this help? (see related tip)
from here: http://softimage
We're running splice in Softimage to render out a pointcloud using a
renderer written in KL. So the renderer lives in an operator on the
pointcloud.
When we open this scene using xsibatch the splice operator doesn't get
evaluated.
Just like any other part of the scene wouldn't. Because it doesn't
7 matches
Mail list logo