Saving sequence as single mesh.

   1102   5   1
User Avatar
Member
3 posts
Joined: March 2020
Offline
Hi,
i am having a problem in rendering a frame sequence as one frame in houdini to alembic, what i want is to merge all frames of animation into one alembic file and remove the animation so the alembic sequence can be displayed as single mesh,instead of playing timeline and seeing different parts of geometry at each frame. For example i have sphere which is split into single poly at each frame i.e each poly is displayed at different frame number so when i try to export it into alembic all i get is same sequence of animation,but instead i want to merge all frames into one single mesh and remove animation so them mesh in alembic can be displayed as one regardless of frame number as if it is a single alembic file,i use a sop solver with merge node in it, but it cause ram issues because of density of polygons? any advice?
User Avatar
Member
8555 posts
Joined: July 2007
Online
you can use Trail SOP with trail length as long as your number of frames, following by Timeshift freezing the last frame

it would be similar to the soler approach though so if its super heavy maybe you will get similar issues
Tomas Slancik
FX Supervisor
Method Studios, NY
User Avatar
Member
3 posts
Joined: March 2020
Offline
tamte
you can use Trail SOP with trail length as long as your number of frames, following by Timeshift freezing the last frame

it would be similar to the soler approach though so if its super heavy maybe you will get similar issues

Hi,
Thank you for the answer, but this is even worse them manually saving files and load them at render time, only if there is an outside command line utility which allows merging of alembic files it would have been really helpful, but thanks for the answer anyway.
User Avatar
Staff
329 posts
Joined: July 2005
Offline
You might be able to partition the geometry into chunks without reaching your system's memory limits. Making the chunks as small as a single primitive will likely introduce a lot of additional overhead. Consider larger chunks. The attached .hip file demonstrates a few ideas that might help you move closer to your goal.

Attachments:
alembic-reorg.hip (143.1 KB)

User Avatar
Member
3 posts
Joined: March 2020
Offline
derrick
You might be able to partition the geometry into chunks without reaching your system's memory limits. Making the chunks as small as a single primitive will likely introduce a lot of additional overhead. Consider larger chunks. The attached .hip file demonstrates a few ideas that might help you move closer to your goal.

Hi,
Thanks for the files, but your file throw warnings upon opening, however file is working fine:

  • Load warnings for E:/alembic-reorg.hip

    Warning:

    /obj/geo1/rop_alembic1:

    Skipping unrecognized parameter "outputindexedarrays".


    /obj/geo1/rop_alembic2:

    Skipping unrecognized parameter "outputindexedarrays".


    /obj/geo1/rop_alembic3:

    Skipping unrecognized parameter "outputindexedarrays".


    /obj/geo1/unpack1:

    Skipping unrecognized parameter "dotransform".


    /tasks/topnet1:

    Skipping unrecognized parameter "savegraphattribs".
    Skipping unrecognized parameter "usedefaultlabel".
    Skipping unrecognized parameter "defaultlabel".
    Skipping unrecognized parameter "sep1".
    Skipping unrecognized parameter "regenerationtype".
    Skipping unrecognized parameter "evaluationtime".
    Skipping unrecognized parameter "customtime".
    Skipping unrecognized parameter "savescenefile".


    /tasks/topnet1/localscheduler:

    Skipping unrecognized parameter "pdg_usemaxtasks".
    Skipping unrecognized parameter "pdg_maxtasks".
    Skipping unrecognized parameter "pdg_waitforfailures".
    Skipping unrecognized parameter "pdg_workitemdatasource".
    Skipping unrecognized parameter "pdg_compressworkitemdata".
    Skipping unrecognized parameter "pdg_validateoutputs".
    Skipping unrecognized parameter "pdg_checkexpectedoutputs".
    Skipping unrecognized parameter "sepparm2".
    Skipping unrecognized parameter "sepparm3".
    Skipping unrecognized parameter "pdg_rpcignoreerrors".
    Skipping unrecognized parameter "pdg_rpctimeout".
    Skipping unrecognized parameter "pdg_rpcretries".
    Skipping unrecognized parameter "pdg_rpcbackoff".
    Skipping unrecognized parameter "pdg_rpcbatch".
    Skipping unrecognized parameter "pdg_rpcrelease".
    Skipping unrecognized parameter "folder6".
    Skipping unrecognized parameter "local_useminfreemem".
    Skipping unrecognized parameter "local_minfreemem".
    Skipping unrecognized parameter "local_minfreemempct".
    Skipping unrecognized parameter "local_enabletimeout".
    Skipping unrecognized parameter "local_maxtime".
    Skipping unrecognized parameter "local_handletimeout".
    Skipping unrecognized parameter "sepparm4".
    Skipping unrecognized parameter "local_enablemaxmemory".
    Skipping unrecognized parameter "local_maxmemory".
    Skipping unrecognized parameter "local_handlememory".
    Skipping unrecognized parameter "sepparm5".
    Skipping unrecognized parameter "local_skippackages".

User Avatar
Staff
329 posts
Joined: July 2005
Offline
EMwavelength
your file throw warnings upon opening

The file was created with Houdini 19.5. Warnings about unrecognized parameters are not unexpected if using a file with an older version of Houdini. None of the warnings should impact the behaviour of the example.
  • Quick Links