Alternatively, you might be able to do what you want by not using ICE instancing. Instead of using the Instance Shape compound on your original pointcloud, you might be able to create real, not instanced geo:
1. create an empty primitive polygon mesh 2. create a modeling ICE tree on it 3. get a 'Create Copies from Polygon Mesh' compound and connect its execute port to the ICE tree 4. drag in your point cloud and your geo to be copied per particle 5. connect them to the "Source Polygon Mesh Name" and "Point Cloud Name" ports If your instanced objects aren't using animation offsets and there aren't too many of them, or too many polygons in them, this might work well. Now you can snap to any point or surface on any of the copies of the mesh. On Tue, Oct 1, 2013 at 1:52 PM, Ed Manning <[email protected]> wrote: > Hey Tim -- > > if this is related to your earlier DOF control post... > > Instead of using an ICE approach, you could try the following, which might > be adequate: > > 1. create your ICE instance cloud > 2. create a null -- let's name it "null" for creativity's sake > 3. add your bokeh lens shader to the camera of choice > 4. set up an expression using the distance from the null to the camera > to set the Focus distance: > 1. right-click on the Focus distance animation icon in the bokeh > shader PPG > 2. choose "expression editor..." > 3. copy/paste this into the expression editor: ctr_dist_cam( null. ) > 4. click "Apply" > 5. Now you can move your null around the scene, and snap it to any > actual geo with the regular snapping controls, and keyframe the null > 6. If you include points in the snap-to options, you can snap the null > to the points in the cloud that's instancing your instance geo. As long as > the instanced objects aren't very big relative to your DOF distance range, > this may be accurate enough. > > hope this helps, > > Ed > > > > > > > > > > >
-------------------------- To unsubscribe: mail [email protected] with subject "unsubscribe" and reply to the confirmation email.
