Jump to content

vtrvtr

Members
  • Content count

    213
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    9

vtrvtr last won the day on April 22

vtrvtr had the most liked content!

Community Reputation

81 Excellent

1 Follower

About vtrvtr

  • Rank
    Initiate

Personal Information

  • Name
    Vitor
  • Location
    Brazil
  1. Script to resume crashed render

    Yes. All of them, I think. Beware that the free version on Deadline does not work with PDG because it uses a commandline submission instead of a Houdini submission. But normal Houdini submissions works fine.
  2. Script to resume crashed render

    That's basically what render schedulers are for. Tractor, Deadline, Hqueue etc.
  3. Aligning geometry to torus surface

    The easy way is to use MOPs Without it, check this hip odf_copytotorus_orient.hipnc
  4. Can't reproduce your exact situation without the rest of the setup, but the Point Generate SOP, which I suppose is implemented reasonable well in C++ should be a good enough comparison in terms of a high limit. 2e+07 points is basically instantaneous on my machine, 0.006 secs on the monitor to be exact. Even Point Jitter SOP all those points is just 0.1 secs. Are you sure you're not being betrayed by the viewport? Usually the viewport is by far the biggest slowdown when it comes to changing geometry. Also, VEX is very decent in terms of speed, but you might want to try the HDK itself. You can easily without all the compiling hassle with inlinecpp
  5. implicit cast vector to float? [solved]

    AFAIK there's no vector comparison in vex. What you are doing is just comparing the first element of the vector. Depending on your needs you can use length to get the magnitude of the vector and compare them instead. Either that or you can write your own function to compare the vectors in a way that suits your needs.
  6. Modifying built in viewer states?

    No, I was just using the shell Yeah, apparently the OnCreated callback (which is wrongly named OnCreate on that page btw) is called before the polybevel itself enters its state I guess your best bet is put a hotkey or shelf that changes the state when you use it. You could also make a wrapper HDA around polybevel.
  7. Modifying built in viewer states?

    I didn't actually went through doing something elaborated, but it seems to me I can enter a different state fine while selection polybevel import stateutils sv = stateutils.findSceneViewer() sv.currentState() >> polybevel::2.0 sv.setCurrentState("some_state") sv.currentState() >> some_state
  8. (SOLVED) Import nodes from file using Python

    You can merge hip files with hou.hipFile.merge https://www.sidefx.com/docs/houdini/hom/hou/hipFile.html
  9. You can change the visualization to box or points. You can also press D on a viewport and change the option in the Optimize tab that dictates how many polygons you want in the viewport, which will change the visualization anyway If they are not in the viewport all the time, you can also cull them manually by using a simple volume equivalent to the camera's frustum and a blast node.
  10. Custom Solver

    Since you can write and read attributes, you "can" do it in python, but it will be awfully slow. VEX would be a better alternative, but yet it isn't what the language was really made fore. The HDK is for sure the correct way to do it. In fact, one the examples of the HDK is a snow solver. You can find it in $HFS/toolkit/samples/SIM/SNOW_Solver.*
  11. Run script in Command Line tools with Python

    Sure, here's a hip. The code is all inside the pythonscript node. It's the following: import os.path as op import subprocess hython_path = op.join(hou.expandString("$HFS"), "bin", "hython") hrender_path = op.join(hou.expandString("$HFS"), "bin", "hrender.py") hip_path = hou.hipFile.path() subprocess.Popen([hython_path, hrender_path, "-e", "-d", "mantra1", hip_path]) As for importing hou, it's not very straight forward. Besides adding the path to the .py file to your current python path, you need to also add the $HFS/bin folder to your PATH variable in order to correctly import the custom houdini C libraries. As described here http://www.sidefx.com/docs/houdini/hom/commandline.html subprocess_hython_odf.hip
  12. Run script in Command Line tools with Python

    If you want to render the files sequentially, you can do the same you did in that .cmd, but in python. Something like hou.hipFile.load(file1) rop = hou.node(path_to_rop) rop.render(args) hou.hipFile.load(file2) rop = hou.node(path_to_rop) rop.render(args) ... If you want to to spawn new processes to render your files, you can call hrender using subprocess subprocess.Popen([path_to_hython, path_to_hrender, hrender_args]) And, of course, you can write a specific custom python script to suit any other needs
  13. Run script in Command Line tools with Python

    Is there a reason you're not rendering using python directly? You can check inside $HFS/bin/hrender.py or render.py for some examples. If your usage is simple, those scripts would be enough for you to use directly
  14. Pyro source Wedges TOP

    I think your doubt is how would the pyro load difference sources. You might be able to do that directly in tops with some clever usage of switchs, maybe some python. But I figure the default workflow is to cache your sources and use a File SOP do read them back. After that it's just another normal wedge. See file. pyro_simple_wedge_odf.hipnc
  15. Pyro source Wedges TOP

    I'm not sure I understand what you mean. Do you want an item for each source? Like this sh
×