Tom Freitag

Thanks jsmack for your answer. Since the pointcloud represents a rbd sim every point has its own unique piece. Yes there is no real instancing happening but at the end I don't want to write out every frame with the heavy geo. SO the lighting department will only get the pointcloud (with instancefile attribt look to the static geo).
I only write the ptnum to instancefile for faster debuging. At the end in it will named "piece`@ptnum`.rs"

I looked to houdini documentation (instancing) saying:
----------
Note

You can set the Instancing Limit on the Geometry tab of the 3D View Display Options dialog to the maximum number of OpenGL primitives that can be instanced before some instances start being replaced by the Stand-In Geometry. This prevents the graphics card from being overrun by a huge amount of rendering which could halt or reset the graphics driver. Setting this to zero will always use the stand-in geometry.
--------

But it doesn't help. But why to the hell the "instancefile" triggering the viewport, when there is only a stupid unique number(as string) per point (instancefile). Can I say to viewport don't do it ?

Hello,

I have a really strange bug. When I create a string attribute "instancefile" on a (animated or static) pointcloud, houdini is freezing for minutes and the gpu running full of memory. Now the strange thing is: If I call it other then "instancefile" it works fine..
Try this: scatterpoints 30.0000pts -> attribute create SOP (attribute name: instancefile type: string value: $PT or `@ptum`)

Right now I found a silly solution. When its freezing, the GPU running full. If I closing the viewport everything went smooht. But its not a solution. Any Ideas?

thanks, tom

thanks, it works now.
tom