Jump to content
machinainfinitum

FBX EXPORT - DIFFERENT FILE FOR EACH FRAME

Recommended Posts

Hi brains ! Need help!
I've got a mesh (as an example I'll use pig head) and I'm using a "mesh slice" node to split it in different parts, using $F as index, basically every frame I see a different slice  of the pig.
Tried to export in fbx using rop fbx but can't find a way to create a different file for each frame.
I can export in obj and it works by saving each frame in a separate file "test$F.obj" but does not work with FBX rop, I always get only one FBX file.. Any idea ?
Thanks in advance, happy houdiniiiing !:D   

image.png

image.png

image.png

MeshSliceFBX.hip

Share this post


Link to post
Share on other sites

I thinks it's because this is the way FBX has been devised. basically FBX export animation in two ways :

- the most popular in game where you store animation with xform transform and bones + weight map.

- the other is  by exporting a vertex animation cache like the .abc format, in that case FBX export only one FBX file and store the animation in a file point cache .fpc

If you want to export per frame .fbx you just want to hack the way the format has been devised. 

 

it looks to be possible thought there is a scene by tomas here :

https://www.sidefx.com/forum/topic/54398/?page=1#post-349575

 

why do you prefer FBX over .abc for vertex cache file export ? 

why per frame ?

Edited by sebkaine

Share this post


Link to post
Share on other sites

Here's my take on it
It's not polished or anything, it just works.

Basically, it's a foreach loop, set to By Count, which is controlled by a frame range attribute.
Within the loop is a timeshift tied to the loop's iteration, as well as an FBX Export with the same loop iteration in the filename.
Finally, a python sop simply does a pressButton() on the FBX.
(The execution is handled through the Stop Condition of the loop. The subnet's Export button sets it to 0, force cook, then sets it back to 1)

Anyways here's the file (19.0.455), hopefully that helps.
export_separate_fbx_per_frame.hiplc

Cheers !

image.png.d5fc90d20e4e57246ebf5acf2c9366e6.pngimage.png.a9160fdcbfd47b2edcc8a444da57d97a.png

(I took that as a fun mini tool-building exercise, but sebkaine's link has a few other solutions that works just as well)

Edited by Alain2131

Share this post


Link to post
Share on other sites

Thanks everyone ! Got it working with Alain's setup, thanks for that :) 
Emmanuel  I need separate fbx because the mesh I'm slicing is around 60gb in size, can't create one unique abc or fbx for an easier file handling during import in Unreal Engine.
Cheers

Share this post


Link to post
Share on other sites

ahah 60GB into UE you definitly got a good reason. .abc suck in UE it looks that they still label it experimental features

https://docs.unrealengine.com/4.27/en-US/WorkingWithContent/Importing/AlembicImporter/

as it was already experimental 5 years ago, i guess it will stay that way forever before being replaced by usd. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×