Jump to content

symek

Members
  • Content count

    1,839
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by symek

  1. Ubuntu will work minus graphic card drivers (better to switch to default video driver at old machine). Windows probably won't (at least it never was with Win7).
  2. Afaik HDK doesn't expose any headers for Mantra's camera, but you might take a look into lens shaders, like ASAD lens shader (v_asadlens shop) to control camera projection.
  3. kwargs in python shell ?

    print hou.node("/obj/myHDA").hdaModule().kwargs
  4. Is OpenCL 2.0 Faster than HFS OpenCL?

    You can always confront your imagination with reality measuring Houdini's performance in both cases. I wouldn't be surprised if lso OCL 1.2 code could run faster on OCL 2.0 driver. Aside of language's changes, new versions usually evolves compilation for better vectorization (I also imagine that dynamic parallelism might be used for work stealing).
  5. Maybe they have been bought?
  6. On a single computer, right? I don't see why not. You can always open multiply session of Houdini on a single computer without consuming license. Moreover, if you start hbatch on a computer used already by Houdini, it will not consume another license too. Shorty speaking Houdini will always consume a single license on a single node what ever number of processes are running on it given previously accounted license is sufficient to run new process (HoudiniFX + Houdini Core + hbatch running at the same time will consume single license, while hbatch + Houdini Core + Houdini FX, will except three distinct licenses...).
  7. Because it's just right*. * - written on a glorious MacBook Pro (13-inch, 2016, Two Thunderbolt 3 ports)
  8. Rendering slow

    CPU usage is low, probably because rendering takes a small part of the time, more is export geometry and disk operation. Go with Redshift or OpenGL render.
  9. Command Houdini on Phyton

    Yes, Houdini has an excellent (best in industry imho) support for Python scripting. Houdini Python module can be imported to regular Python session, or used inside Hython, which is like regular Python interpreter with builtin Houdini module. With Python you can do everything Houdini can offer (some omissions can be found but don't relate to anything important). Some references for you: Opening and inspecting scene: http://www.sidefx.com/docs/houdini/hom/cb/hipfile Accessing hou module from regular Python: http://www.sidefx.com/docs/houdini/hom/commandline General intro: http://www.sidefx.com/docs/houdini/hom/intro Full API docs: http://www.sidefx.com/docs/houdini/hom/hou/_index
  10. Parent as Selected

    parent = thisNode.parent() if parent: parent.setSelected(True) Checking if parent exists in your code makes me suspicious about your goal though. Are you actually interested in hierarchy selection or network selection? Above code returns a network which contains a node: so for /obj/geo1 it will return /obj. For the ancestors nodes you have to use parents = thisNode.inputs()
  11. Rendering IFD files

    OK, that's a good reason for using IFDs (unless you can install HQueue there, which simplifies this task a lot). Google says for Windows looping command would look like bellow, but I don't know a thing about MS shell. for /r %i in (*) do mantra -f %i Actually there seems to be bash for Windows these days too, lol.
  12. Rendering IFD files

    Neither of that. Single IFD file contains a single frame definition, but you can't write ocean.$F.ifd as $F is Houdini's specific variable. You need to loop over files. Depending on a OS you're running on this gonna be simple expression like (Linux): for file in `ls *.ifd`; do mantra -f $file; done You typically have some sort of script for doing such things. Why you're trying to render from IFD file? If you'd like to render from a command line on a single computer, you may take a look on hrender script provided by SESI. It will take a hip file and render specified ROP from command line. No need to export IFDs (IFDs are mostly useful for render farms, and funcy production render orchestration...)
  13. Broken Mosaic Node?

    Could you attach frame sequence making you trouble? Another thing is that Cops are sensitive to image resolution change in sequence. Are those files all the same?
  14. Rendering IFD files

    mantra -f /path/to/ifdfile.ifd <optional image.pic> By default mantra will use ROP settings embedded in IFD file, but you can overwrite them in command line like: mantra -j8 -Va -f /path/to/file.ifd image.exr All of this is explained in a first link my first post.
  15. Broken Mosaic Node?

    Seems to be working here. Are you sure your frames are correct. Maybe some frames are busted, and COPs can't open them? (it's 100x512pix)
  16. Rendering IFD files

    Once IFD file is on disk, you don't use Mantra ROP, but render with command line: http://www.sidefx.com/docs/houdini/render/batch#mantra Also on a wider context: http://www.sidefx.com/docs/houdini/render/ifd_workflows hth, Szymon.
  17. Boujou import problem

    IFAIR you can merge them all into one geometry as points with a single ObjectMerge SOP, and wildcards in the path. Every Null Object has a point inside it. Something along the line: /obj/Boujou_fbx/somesubnet*/null*/point1
  18. Installing Nuke plugins linux

    I'm not even sure if Nuke NC can import custom plugins, last time I checked, it didn't use any compiled stuff.
  19. Substance Painter to Principled Shader

    What texture format did you exported in?
  20. cant rename node with variable

    Not sure if this is related, but you have a bug in second line, since selectedNodes() returns a tuple, so you can't call children() on that. Also setName() can throw an exception if name isn't correct, like empty string, so most probably your getChildrenName has some issue.
  21. @numpt vs npoints (VEX vs Hscript)

    Whatever you put into wranglers they are VEX script statements, whatever you put into parameters they are Hscript expressions statements (or Python's ). Both can do similar things (like giving you a number of points in a SOP), but they cannot be mixed or used exchangeably. Different languages, different purposes, different places of appliance, notably with some amount of overlapping functionalities likes functions for querying geometry, generators of random numbers etc.
  22. Random values for material inputs

    Did you put $PT inside material parameter? If so, it won't work as $PT is a local variable meaningful only in SOPs' context. If you wan't to drive saturation per point, you have to create an attribute in SOPs, and bind it to shader parameter. Or use something what is available in shaders, like uv, prim number etc.
  23. Refreshing COPs operators has been buggy in recent versions of Houdini. Promote Texture Name parameter outside material network while it's in default value (Mandril.pic), then - being outside shader natwork - change Mandril.pic into Cops' path. It should start magically work. hth ps pink color is Mantra's secret way to inform you that the texture is missing. You can customize this via HOUDINI_DEFAULT_TEXTURE_COLOR env. variable.
  24. Compositing- increase canvas area

    WindowCOP?
×