Just in case anybody wonders how to do it without uv's, in case you are doing some proceduraly textureing, add a rest position node before any animation takes place, kind of the same but you won't have to create uv's - Max Rodas

ajz3d

not sure if anything changed since then, but if .fbx still doesnt support per frame export as different file

Just checked, and I couldn't export FBX "Render Frame Range" to separate files with the ROP FBX Output SOP, so it appears that things didn't change much. The animation is written into a single file.

@HenDaSheng, if you're not constrained to FBX files at this point in production, the best format for this kind of task would be Alembic.

Otherwise, if you need to use FBX, but don't want to use TOPs, you can write a Python script (a shelf tool for example), that would:

1. Create a ROP FBX Output SOP.
2. Link its input to currently selected SOP.
3. Set the "Output File" to /path/filename.$F4.fbxor something like that, depending on your file naming convention and the frame range you want to render.
4. Set other FBX settings.

Then, in a loop for every 10th frame:
1. Press "Save to Disk" button.
2. Move the timeline +10 frames.
3. Go to 1. Rinse and repeat.

And, after the loop completes its cycle, destroy the FBX output node.

坦特
I don't have better answer for you, maybe just example using TOPs
https://www.sidefx.com/forum/topic/54398/#post-351084 [www.sidefx.com]
not sure if anything changed since then, but if .fbx still doesnt support per frame export as different file I'd consider TOPs the most straightforward and you even can chose which frames or even just wedge the parameters on your object directly instead of animating, etc

does it need to be .fbx?

kentin
Oh great, houdini as so much ways to do things, glad you find one !
With my file you can see another one!
Have a good day

HenDaSheng

肯廷
Hey,

You can't access an attribute outside a wrangle by just typing @attribute, with few exceptions (like group expression...).
It should be a little vex expression to access to point, detail, vertex or primitive attribute, for example in your case : point(0,0,"exit_div",0) * 10.

If you want a deeper understanding of this, this is the template for this expression that you can find in the doc : point(surface_node, point_number, attribute, index)

It's "0" for the surface node because your attribute is set on the node you edit, but if you want to access an attribute outside, you can replace "0" by an absolute, or relative path like this : point("../attributepromote1",0,"exit_div",0) * 10.

Hope it will help you!
Have a nice day.

Thanks for your help, it's a bit hard for me, I'll look into it.
I tried to write in this way, and it did solve the error, but the Divisions are still the same result.

肯廷
Hey,

You can't access an attribute outside a wrangle by just typing @attribute, with few exceptions (like group expression...).
It should be a little vex expression to access to point, detail, vertex or primitive attribute, for example in your case : point(0,0,"exit_div",0) * 10.

If you want a deeper understanding of this, this is the template for this expression that you can find in the doc : point(surface_node, point_number, attribute, index)

It's "0" for the surface node because your attribute is set on the node you edit, but if you want to access an attribute outside, you can replace "0" by an absolute, or relative path like this : point("../attributepromote1",0,"exit_div",0) * 10.

Hope it will help you!
Have a nice day.

坦特
scatter on static geo
then attribute interpolate P N and up from deforming geo

also note it's important to have both, N and up attributes to get stable rotation, not just N
(alternatively you can also use orient or transform attributes)

HenDaSheng


I try to place the instance on the dynamic grid, the problem now is that the instance keeps shaking, how can I fix the position of the instance?

Thank you for your help!