Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Lucavfx

  • Rank
  • Birthday 01/01/2007

Personal Information

  • Name
  • Location
  1. Quick question, what's the command line tool to merge two tiled rendered frames together (using the rop tiled render option)? Cheers
  2. Hi Martin, Thanks for the heads up, I asked sidefx support as well and was told they're not developing it. I suppose I'd still like to know if H16 would provide the capability for users to build their own cryptomatte compatible aovs.
  3. Hi, I'd like for my dept to adopt it: Has progress been made to export cryptomatte aovs in mantra? We can help beta testing / trialing if needed. Please let me know Many thanks Luca
  4. Thanks Graham that helped quite a bit
  5. Thanks, I'm getting closer now. The problem is that as in the case of image plane parameters they're specified as vm_channel_plane# however python param and parmTemplate calls expect parameter names to be explicit (i.e. vm_channel_plane23). Setting the conditionals dict to explicit parameters does not seem to apply in this case
  6. Hi, I'd like to access the 'Hide When' parameter field in 'Edit Parameter Interface' via python. The idea is to access this field and store a string such as "{ showmoreinfo == 1 }". Is there a way to easily do this? I searched and found workarounds which involve calling the hide method i.e. hou.parm('/out/mantra1/vm_lightexport_scope21').hide(1) but this result in an inefficient system requiring hoops to achieve what I want. Any ideas? Thanks Luca
  7. ROP Operator Submit Houdini2Deadline

    I've had thinkbox adding a variable called IGNORE_INPUTS ( i think that's how it is called, I'm not in front of my PC) years ago to resolve this issue, no need to edit any deadline installation python files! this is what I use in my submitToDeadline to prevent any rop from cooking any of its inputs. obviously this would require you to handle the rop dependencies manually via code. this is handy if you intend building your own dag algorythm for parsing the rop branch. that's what submitToDeadline does internally. L
  8. Update: I passed the overridden variable HOUDINI_OTLSCAN_PATH by adding it to hq_sim and I can see it is set correctly in the client -as seen from the client properties log- however the client doesn't load otls from the ~/USERNAME/houdini/14.0/otls
  9. Hi, we're looking into hqueue and noticed that hqueue clients don't inherit the environment or the otl paths. i.e. otls stored on ~/houdini14.0/otl are not made available to the client. (I'm having a look at the hqueue docs but can't find anything regarding this. Also manually adding the otl_scan_path variable in the hqueue rop and submitting a job doesn't seem to pass the variable to the client on the farm.) Is there a way to configure hqueue so that clients would launch a specific wrapper? or simply inherit the current environment including otl_scan_path? Thanks for your help L
  10. Completed Asset: SubmitToDeadline

    Cool! I'm going to release an update in a couple of weeks and also dropping the price quite a lot for the compiled version and introducing a more expensive otl with exposed source code. I'll let you know as soon as the new versions are out on orbolt.
  11. ROP Operator Submit Houdini2Deadline

    Thanks for the nice words, I think it is placed at a very competitive price for small/middle sized studios (the cost for the time of a pipelineTD building something similar would be many times higher). BTW it is now live at the orbolt website https://www.orbolt.com/asset/Simultools::submitToDeadline Have you tried using the environment variable DEADLINE_PATH to construct the path to the deadline executable? that env variable should always be present whether you have a local installation of the deadline client or a remote installation. That is pretty much what I use in my olt.
  12. 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
  13. ROP Operator Submit Houdini2Deadline

    Hi Igor, I tried it and it seems to error on the groups/pools fields and on submission (I'm on Linux). Funny timing, I've been developing a houdini to deadline submitter for quite some time, it's called submitToDeadline and is going to be made available real soon (stay tuned!). SubmitToDeadline supports all common rops, multiple submissions and complex dependencies, bypasses etc. It's quite similar in features to the proprietary solutions seen at highend vfx studios in London (but simpler to use): http://simultools.com/submittodeadline Video illustrating the main features can be found here: https://www.youtube.com/watch?v=iJNoxD1hvI8 Thanks L
  14. hqueue dependency

    very useful, thanks. Do you know by any chance know if it possible to specify children inside children jobs so to create more complex arrays of dependencies?
  15. DOP sopsolver not evaluating over time

    That's a good option for this particular case, thanks for your replies. L