EDIT: Ok I figured it out. Apparently the "0" doesn't count as input (which now that I understand it totally makes sense). So I replaced with the actual path and it worked. Thanks!
For some reason I can't get the @name attribute as a file output as I can in a regular, single-frame ROP FBX Output.
This output code works perfectly in the regular FBX Output node (but it doesn't render frame range):
But inside the Topnet the exact same code doesn't work:
I'm exporting different geometries with very different asset names, so I wanted to use the @name attribute from the geometry. I didn't want to use a generic "building_$F" (which works just fine).
Any clues on how to do that?
Thanks!
Found 7 posts.
Search results Show results as topic list.
Technical Discussion » Export multiple fbx files
- freule
- 7 posts
- Offline
Technical Discussion » Attrib Create Value not overriding Default value?
- freule
- 7 posts
- Offline
vicvvsh
"active" is a point integer attribute, not a float attribute. Try change type in attribcteate SOP and you get what you want.
Yes, but weirdly enough, it works as float too in the 2nd example.
I remember trying switching to integer and getting the same error, but now I tried it again and indeed it works, thanks!
npetit
active should be an int attrib - if you switch the attribcreate SOP's type to Integer in your first example, it works as expected.
in a wrangle you can doi@active = i@group_groupexpand2;
Yup, tried again and it works, thanks!
Technical Discussion » Attrib Create Value not overriding Default value?
- freule
- 7 posts
- Offline
Thanks for the answer!
I'm aware that the AttribCreate node has to create the attribute for all the points. In my first gif I was assuming that it would create a default value of 1.0 for ALL the points and assign the value of 0.0 only for the selection. The visualizer and the spreadsheet show that correctly (black as 0.0 --> inactive). In short, I wanted only the red tip to jump out.
Your wrangle works great and I understand the issue, but I'm still confused on why the spreadsheet shows the correct values for the points but fail to exclude them from the simulation.
It's not a big issue, but thanks!
I'm aware that the AttribCreate node has to create the attribute for all the points. In my first gif I was assuming that it would create a default value of 1.0 for ALL the points and assign the value of 0.0 only for the selection. The visualizer and the spreadsheet show that correctly (black as 0.0 --> inactive). In short, I wanted only the red tip to jump out.
Your wrangle works great and I understand the issue, but I'm still confused on why the spreadsheet shows the correct values for the points but fail to exclude them from the simulation.
It's not a big issue, but thanks!
Technical Discussion » Attrib Create Value not overriding Default value?
- freule
- 7 posts
- Offline
Getting this small issue with the Default/Value of the Attribute Create node adding the "active" attribute to a geometry for a RBD Bullet Solver simulation.
Creating the attribute as 0.0 and setting it to 1.0 seems to work fine. But creating at 1.0 and setting it to 0.0 for some reason is ignored by the RBD bullet solver, and despite the attribute value being correctly set to 0.0, all pieces are included in the simulation.
Am I doing anything wrong? Did I misunderstand the function of the "default" and "Value" on the Attribute Create node? Or is this a bug?
Thanks!
Creating the attribute as 0.0 and setting it to 1.0 seems to work fine. But creating at 1.0 and setting it to 0.0 for some reason is ignored by the RBD bullet solver, and despite the attribute value being correctly set to 0.0, all pieces are included in the simulation.
Am I doing anything wrong? Did I misunderstand the function of the "default" and "Value" on the Attribute Create node? Or is this a bug?
Thanks!
Houdini Indie and Apprentice » PolyBevel Limited by surrounding edges?
- freule
- 7 posts
- Offline
Hey yeah, that second option does work way better! Thanks a lot, really appreciate it!
It is somehow weird that Houdini doesn't have that option by default, since this seems to be a very desirable way of chamfering edges, specially for organic models.
Thanks again!
It is somehow weird that Houdini doesn't have that option by default, since this seems to be a very desirable way of chamfering edges, specially for organic models.
Thanks again!
Houdini Indie and Apprentice » PolyBevel Limited by surrounding edges?
- freule
- 7 posts
- Offline
Houdini Indie and Apprentice » PolyBevel Limited by surrounding edges?
- freule
- 7 posts
- Offline
Hi,
I'm trying to chamfer some edges in a cactus model and add the chamfer intensity as a parameter in the subtool.
Problem is, when being divided the edge is either overlapping the smaller connections or limited by the minimum distance.
I've attached the same procedure in 3dsMax, for comparison, which is what I wanted.
Is there an easy way to make the Polybevel behave like this? I've changed all the configurations but nothing seems to do the trick.
Thanks!
Fernando Reule
I'm trying to chamfer some edges in a cactus model and add the chamfer intensity as a parameter in the subtool.
Problem is, when being divided the edge is either overlapping the smaller connections or limited by the minimum distance.
I've attached the same procedure in 3dsMax, for comparison, which is what I wanted.
Is there an easy way to make the Polybevel behave like this? I've changed all the configurations but nothing seems to do the trick.
Thanks!
Fernando Reule
-
- Quick Links