make your own 'emit location' by connecting to the 'on creation' port a closest location from your cached pointcloud to your newly created pointcloud getting & setting the point velocity
On 21 October 2014 15:59, Morten Bartholdy <[email protected]> wrote: > I also tried getting the PointVelocity of the cached pointcloud and use > that as direction vector for the Emit From Position but run into context > mismatch even if I try normalizing it so it should "just" be like any other > vector, so no go this far... > > > Morten > > > > > Den 21. oktober 2014 kl. 14:43 skrev Eric Thivierge < > [email protected]>: > > > Can you apply and Attribute Display prop to the cached point cloud to > > see if there are 'PointVelocity' values being read in by the cache? > > Will help you debug it by showing you it wasn't cached out. > > > > Eric T. > > > > On Tuesday, October 21, 2014 7:40:57 AM, Morten Bartholdy wrote: > > > I am emitting particles from a cached pointcloud and would like them > > > to inherit some velocity from the emitter particles. The inherit > > > emitter velocity node goes red, apparently caused by the compounds Get > > > PointVelocity from the Particle Emit Location. I did cache > > > PointVelocity on the emitter pointcloud, so I am not sure why it isn't > > > read. Is there a way to fix this? > > > > > > On a side note - I managed to emit from the cached pointcloud, but it > > > emits from point positions - I would like to emit from surface or > > > volume of the instanced geometry on the cached pointcloud. So far I > > > have not found a way to do this - is it possible directly or perhaps > > > via workaround? I tried emPolygonizer4 on the cached pointcloud in an > > > attempt to emit from that geometry but so far I have not got it > working. > > > > > > Thanks - Morten > > > > > >
