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

thanks john! I read it, but there nothing about how to handle custom attributes. Is there a way to us a default attribute to importing some custom attributes?

Hi,

another question regarding HEngine in Maya: is it possible to import particles (nParticles in Maya) with custom attributes? I have a float attribute for lightemissio. Or is it possible to use a default attribute an mapping it inside Maya?

thanks.

hi John,

big thanks for fast reply the maya guy told me, there are no Cd attrib with v. seems to be the attribe rename sop don't work. I have an output node to force to cook everything above. Maybe he have to press the synce or recook(Hengine in Maya) button to get the attrib rename to work? ..he only see the attrib that bake in the caches.

Hi,

we have some problem to read the v attribute in Maya with Engine. In the hda we have an output, where the v attribute exist. But not in Maya with Hengine. Is this not possible? ..we tried to

If its make sense I could send the hda with an meshfile.

Thanks, Tom.

…with the opencl tab checked (houdini sparse pyro solver) its falling back to non-sparse version. Its only sparse solving on CPU for now.

love it. here smile is somehow inspiring.
….and my kids love it, too.

i experienced the same. i guess bgeo, fbx and abc have more modern exporter, then i.e. obj, ply, 3ds etc. are very slow…

Hi,

if have no succes to switch the for each block iterator (index_in/length_in) to float. It alway iterate only over integers. How could I iterate over float value (like in to old for each block, i could switch between float and integer)

thanks. Tom.

hey,
1. attrib promote: uvs from vertrx to points
2. subdivide the mesh
3. attrivop: bind uvs -> uv texture vop -> diplace along normal vop

comming out quite nicely. I like how the face coming down. Now I want to see the animation

Try to increase the constraints on the grain solver. The constraints works like how much layer can stacked one over another. So if you have 20 constraints, the solver can stack 20 particllayer. I am not sure if its 100% right…
But if you increase the resolution, you have much more „stacked layer“ to solve in stable way. so you have to increase the constraints much higher which cost a lot of simtime.

So my approach is to use low particle count as possible. Then I would upres the sim with point replicate SOP or you could use the vel field from the grainsim to drive some dumb particles(high count).

i could cry! …thats not released yet!! pure awesomeness!!! thanks to the dev team and the hole sesi crew.

i also not understanding, why a company is allowed to spam with self promoting posting and a single artist not allowed to…

^^ “seems like it could be cool, but I had a look and I'm not touching it again”

i had the very same experience. for me the biggest issue is how to distributing/managing jobs on my cpu threads.

i think it could be great, but it needs better usability.

i guess you have write inside backticks: ´detail…´. a string needs this to know when it have to evaluate an expression.

thanks for posting your 2990wx experiences and for then indepth answers
i also would deciding between 2950 and 2990. what I also interested in is heavy ram load(geometry) with mantra. also how it would perform with pyro/flip with low seperation size(ram heavy simulations). most render benchmark a very lightweight.

thanks for your motivating words