Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About saml

  • Rank

Personal Information

  • Name
  • Location
    Sydney, Australia
  1. emittingFluids

    Hey, You need to wire the merge after the solver for the static geo to act as a source. Cheers, Sam. fluidEmission_2.hipnc
  2. Baking Point Clouds from RSL

    Thanks Alan, that fixed the problem. I hadn't included the channels in the AOV's.
  3. Hi, I am unable to generate a point cloud file from an RSL shader within Houdini to be used for SSS. I may be using the wrong workflow but when I render out my RIBs from the renderman ROP, the RIB file is created successfully but it is not generating the .ptc file. The shader I have applied to my geometry to bake out a .ptc file is as follows: Are there any specific settings I have to apply in Houdini for ptc's? Thanks in advance for any assistance to resolve this! Sam.
  4. Install HDA from python module

    Thanks again for the assistance! I have now resolved the problem. Although the strings both appeared to be identical yet only the explicitly defined string worked with the hou.hda.installFile() method, using the type() function on the path variable I discovered it was of <type 'unicode'>. I converted the path variable to a string using the path = str(path) command and now it executes successfully! Cheers, Sam.
  5. Install HDA from python module

    Thanks for the speedy reply SYmek! I hadn't thought to use those os module commands too, they are very useful. When testing isfile against the path it returned a false boolean. I got rid of the extra quotes and isfile now returns a True result, but the same initial error arises, so there must still be an underlying problem with the path string... Code: Output: As a test I tried to force the path to be a string using: path = "".join("%s" % path) This still resulted in the same initial error. Maybe there is some kind of other string conversion I need to do? Thanks again for your direction.
  6. Hi, I am developing a python script and have come across an issue with the hou.hda.installFile() module and I am wondering if anyone can shed some light on how I can resolve it. The following are two scenarios, one which works and the second which calls an exception and fails unfortunately I need the second one to work ==Scenario 1== The following was executed in the python shell within houdini and works with no issues: ==Scenario 2== This is a snippet of the code I have used in my python module which I have imported into and run in houdini: The path output in the console from the print command appears exactly the same as the first scenario "C:/Documents and Settings/Administrator/My Documents/RSL/rel/watermelon.otl" however, fails with the following exception appearing in the houdini console: When I substitute the "path = re.sub..." attribute with a direct path to the otl it works successfully even though the string appears exactly the same in the print statement of the path. It seems there is an issue with the type of attribute being generated but I am unaware of the best approach to solve this. Any help would be much appreciated!! Sam.
  7. Hey, I'm not sure if this is exactly what you are after as the scale is not driven by the scale value of the box object, but instead uses the pscale attribute to control the transform scale of each box as it reaches its apex. The scale is set to 1 in Y until it reaches its apex and then scales from 1 to 5 over a period of 10 frames. It does not use the timewarp node, but achieves the same results. HTH, Sam. TimeWarp_02.hipnc
  8. Hi, the print node works fine for nodes in most VOP networks, however in my case it doesn't appear to work with VOP SHOPs. Is anyone aware of another method of printing data anywhere along a VOP tree within a shader? I have a VOP VEX Surface SHOP and am trying to print a Pz value. Is anyone else experiencing this issue? Cheers for any help! Sam.
  9. wxPython in Houdini 9.5 OSX

    Hey Graham, thanks for your response! I never did find a solution to this. I'll take a look at the python Cocoa bindings next time.
  10. wxPython in Houdini 9.5 OSX

    Hi, I have just downloaded and installed the ansi version of wxPython for OSX. When running a basic wxPython script using the default Python 2.5.2 install on OSX it works fine. I then proceeded to copy the "wx" folder of the newly installed wxPython over to my $HFS/houdini/scripts folder, and attempted to execute the same script within Houdini using its inbuilt version of python, I receive the following error: I'm unsure if this is the correct workflow for executing wxPython scripts within the OSX version of Houdini, but I had no problem using this method running a previous version of Houdini in Windows. I very much appreciate any advice as to how I may solve this issue. I don't know if the latest version of the wxPython binary for OSX is compatible with the Houdini 9.5 OSX version of Python or if I am simply using the wrong binary or taking the incorrect approach. Thanks in advance for any assistance! Sam.
  11. Hey Jae, I was having a similar problem, where my zDepth channel didn't appear to display any depth values. I found that if you lower the Gain/White Point in the zDepth image plane in the render options and then render it out and bring it into COPs, you can then wire it into a Levels COP as Spencer said and then lower the value of the second output level until your image begins to show some depth values. I was rendering out single .pic files as opposed to separate images. As far as I know using Pz from the top view will still display the depth correctly as it appears to compute the z value from the origin of the camera as opposed to World view. Correct me if I'm wrong though as I am pretty new to Houdini. Cheers, Sam.