Export multiple fbx files
2193 4 2- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
- tamte
- Member
- 8772 posts
- Joined: July 2007
- Offline
- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
- JoseDGarcia
- Member
- 2 posts
- Joined: June 2019
- Offline
In case if anyone is curious, TOP's manage to do this, but before Top's I set up the geometry by using connectivity to create attribute class for each piece, then attribute wrangle @class += 1; follow by a blast with group @class='@Frame' to isolate pieces to a frame, then TOP's net with a FBX export, set to frame range, 1 to max pieces, in my case it was 107 pieces.
Edited by JoseDGarcia - May 4, 2022 15:06:31
- freule
- Member
- 8 posts
- Joined: Feb. 2019
- Offline
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!
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!
Edited by freule - April 16, 2024 20:15:22
-
- Quick Links