Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Darkster

  • Rank

Personal Information

  • Name
  • Location
    Cape Towm, South Africa

Recent Profile Visitors

710 profile views
  1. Capture to disk and Mplay

    So I contacted support and asked them about this, and they said that Flipbooking sends the images directly to mplay via network sockets, and that the docs are out of date (the -s spool directory command and the $HOUDINI_TEMP_DIR for viewwrite aren't used anymore). That means viewwrite won't save any images to disk, no matter how nicely you ask it. And there's no alternative, you can't have mplay playing back the images while saving them to disk. In short, this can't be done, you either can use mplay or save to disk, not both.
  2. wxPython Crashes with multiple instances

    Thanks for taking a look. At the moment it's not much of a issue, it's just very annoying when it happens. Normally I force the GUI window to always stay on top, so this issue is normally not a problem, but it's easy to forget you have a GUI open if it's minimized or you don't have always.
  3. Hi guys, When I try to run a wxpython GUI (like the one below) it crashes Houdini if I run it twice without closing the original. I'm using the method described in the docs to run it in a separate thread so it doesn't lock up Houdini. I've tried using a wx.SingleInstanceChecker(), but I'm not sure how to properly integrate it into my scripts. Has anyone encountered this problem before and/or have any solutions? Test code: I'm running Linux Centos 6 & Houdini 13.0.376 Any help would be appreciated.
  4. Capture to disk and Mplay

    Hi guys, I'm trying to create a capture and write out a image sequence to disk while viewing it through mplay as it renders via python. I'm currently using viewwrite, it can write to disk no problem, and it can capture to mplay ok, but it can't do them together. Apparently when using ip or md as the output it's supposed to write the images to $HOUDINI_TEMP_DIR, but it doesn't create any files. I've tried changing the path and using the -s spool directory augment, makes no difference. Also tried using a openGL ROP, but same result. Does anybody know of another method, or a way to get this to work? Any help would be appreciated. I'm running Linux Centos 6 & Houdini 13.0.376 if it helps. Thanks
  5. Scene Specific Variables

    I would like to avoid creating additional nodes. While it should load properly and store data nicely, it's a extra node floating around which the user can then delete or break. (unless there's a way to hide the node) I'll do this in the meantime though, until a better solution arises.
  6. Scene Specific Variables

    Is there a way to store scene specific variables? If I use environment varaibles, they persist across the houdini session and are visible when I create a new scene. Another problem, if I create a geometry node, and put this bit of code in the Python Source Editor (so it runs when the scene is opened) import hou parm = hou.parm("/obj/geo1/file1/file") print parm.name() It gives me a "`NoneType` object has no attribute name" error. It looks to me like it's trying to find a parameter before it exists. Is there a way to make the script run AFTER the scene has been cooked? I need to evaluate some parameters & store their values in scene specific varaibles so I can compare the values next time I open the scene. (I'm creating a version manager which, when the scene is opened, checks if there any new versions in the folder the parameter is looking at)