Jump to content

Search the Community

Showing results for tags 'deadline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • 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

Found 8 results

  1. Ocean - no displacement with Deadline

    Probably a stupid question but i'm not a mantra user... I'm currently rendering an ocean in Mantra on our farm with Deadline. I've written out the ocean spectra, foam etc and everything renders correctly on my box. I'm then submitting an IFD generation job and a mantra job (frame dependent on the IFDs) however it renders without any displacement on the ocean...
  2. Greetings! To anyone using Deadline for rendering Mantra, could you advise what your successfull workflow is, please? I have a couple of questions about the HoudiniSubmitToDeadline parameters that I can't find definitions for in any docs. This url is the most useful: https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User Manual/manual/app-houdini.html Q1 - machine limit & Mantra Threads defaults are 0. Do I need to change this value, or is zero ok? Q2 - "Submit Houdini Scene" is OFF by default. Is this correct? Q3 - "Ignore Inputs" is ON by default. Which inputs is it referring to?? It's currently only rendering successfully if I DONT generate .ifds first, which is obviously not correct. I am ticking on "DiskFile" in the Driver tab of /out/mantra1 Disk file = $JOB/ifds/$HIPNAME/mantra_$F4.ifd Shared Temp storage = $HIP/ifds/storage Local Temp storage = $HOUDINI_TEMP_DIR/ifds/storage I launch Render->SubmitHoudiniToDeadline Pool = 3d group = None ROP to Render = Choose = /out/mantra1 Under MantraExport Submit DependentMantraStandalone Job is checked ON Pool = 3d group = None 2 tasks are submitted, which is normal. First task generates .ifds again (I think this can be avoided by select SkipFilesThatExist in /out/mantra1 IMAGES tab Second task is supposed to write .exrs but fails. Yes, the folder is writeable. Pipeline are looking into the error: INFO: Process exit code: 1 2018-01-05 17:14:03: 0: An exception occurred: Error: Renderer returned non-zero error code, 1. Check the log for more. 2018-01-05 17:14:03: at Deadline.Plugins.PluginWrapper.RenderTasks Any pointers gratefully received. Many thanks, Olly : )
  3. Hello All, I have scoured Solid Angle and Thinkbox support for answers to how to setup Deadline to generate ASS files to render them on Deadline farm. When I try to get Deadline to generate both, it fails out miserably. When I generate the ASS files locally (with VDBs correctly pathed) I get the error: [ass] line 76: /obj/FIRE:volume.shader: unresolved reference to '/obj/FIRE/shopnet/arnold_vopnet/volume_collector2' Unfortunately, I can't upload project file for active show, but any links or tips would be greatly appreciated. Thank you
  4. Networks sims using Deadline or HQueue

    hey guys, So I got a new workstation this week, and i'm trying to setup my old system as a render/simulation node. I did get mantra rendering to work using deadline, but simulations aren,t working for some reason. I'm getting this error (see attached image) I also tried HQueue, but all my jobs keep failing there. HQueue does see both my computers, but it immediately fails when I submit a job (either render or sim) I'm on windows and I'm using Houdini Indie. Any ideas?
  5. Render Farms

    Hello, I'm looking to find out what off the shelf render farms people prefer currently for production; likes and dislikes? Short background: We need to use our nodes for Houdini, Max, Maya, fume, and a few other software. Currently about ~100 nodes, and we don't have a dedicated render farm technician so the most hands off, off the shelf is the best. I have experience with Hqueue, Rush, Deadline, and Qube, so I am looking for any additional off the shelf software, too beyond those. Thanks -Ben
  6. Hi, I've completed and uploaded to the orbolt store my rop otl submitToDeadline . Who is it for: If you’re a Houdini freelancer or a mid-sized studio and you are looking to use Houdini on the renderfam in the most productive and painless way, and your renderfarm is managed with Thinkbox’s Deadline software then SubmitToDeadline is for you. What is it: SubmitToDeadline is a self contained python houdini digital asset, it is quite powerful and handles all sort of dependencies automatically. It basically has similar features and functionalities of proprietary solutions seen at big vfx studios. Features: -Self contained Houdini Digital Asset -Automatic handle of all sort of dependencies -Solid algorythm to traverse networks and build accurate dependencies -All common rops are supported (currently excluding ‘fetch’) -Dependencies on a per-job basis -Mantra rops are submitted as two jobs (ifd and mantra) -Mantra sub-job dependencies on a per-frame basis Video: https://www.youtube.com/watch?v=iJNoxD1hvI8 Webpage: http://simultools.com/submittodeadline Orbolt page https://www.orbolt.com/asset/Simultools::submitToDeadline
  7. Advantages: 1. Can work with other ROP nodes. As Example it can be called from Wedge ROP for automatic multi job submission. (for different takes or for automatic parameter change). 2. May submit any ROP node. DYNAMIC_ROP or GEOMETRY_ROP. Not only Mantra ROP. 3. All Submit Settings Saved in scene file and are the attributes of the scene. You may open this scene after some yars and don't need remember some attributes which was rendered a scene in the last time. Also not needed to save submit setting in other places. Installation: 1. put otl-file: houdini2deadline_v01.otl in standart user houdini otl storage: on Windows: %USERPROFILE%/Documents/houdini13.0/otls) on Linux: ~/houdini13.0/otls 2. save python script houdini2deadline.py anywhere 3. open Houdini and navigate /out 4. open tab-menu and choose Farm->Houdini2Deadline 5. in Parameters of houdini2deadline node "Program" field set correct path to houdini2deadline.py python script (by default this field set to "$TOOLS/scripts/python/houdini2deadline.py") 6. May set this settings as default with "Gear" menu on node. Or change default values via RMB->Type Proprties...->Parameters Tab select desired parameter, go "Channels" tab and set default value. This is beta version. Any bug report and suggestions are welcome. houdini2deadline_v01.otl houdini2deadline.rar
  8. I'm trying to launch my Mantra renders from within the Houdini GUI. But, I've had no luck. I followed ThinkBox's instructions (and their script is named incorrectly) to install the menu button. And it doesn't work, no error, just nothing. http://www.thinkboxsoftware.com/deadline-5-houdini/ Any ideas? I think I'll probably just have to code up something myself. Sigh.
×