Jump to content

Search the Community

Showing results for tags 'missing frames'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering + Solaris!
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Name


Location


Interests

Found 2 results

  1. I left a TOPs network rendering some camera angles, but it's stopped with missing frames in one of the sequences (1-112 where it should be 1-144) Dirty and cook returns done. The caveat is I have 'Cook frames as single work item' on for post-processing nodes (ffmpeg and then some python in this case), when I deselect this I get all the frames and it picks up. How can I get it to check the frames, discover which are missing and pick up where it left off? OR would it be better to let it cook individual frames and then group the output by filename and push that into ffmeg?
  2. I'm trying to sim waves lapping up onto large rocks jutting out of an ocean. The sim appears to be working. However, when I write out to a bgeo sequence, some of the files have low byte counts, and are correspondingly missing when you play them back. This was simmed on a machine with 24 processors and 20GB of ram. I'm going to try to increase memory to see if this fixes the problem. But it would be helpful if the hip file could write out more informative diagnostic information. How would one go about doing this? As the geometry rop doesn't inherit any log info from the source DOP. thanks devilsRock.waveSim.h16p5p378.v007.hipnc
×
×
  • Create New...