Jump to content

geneome

Members
  • Content count

    37
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Everything posted by geneome

  1. Painting with polygons

    Thanks rende! Just what I needed!
  2. sss with displacment without using ptc

    He's talking about PoinT Clouds. @kensonuken You could take a look at some old shaders like Mario's SSS shader found here. But you're first thougth about trying the Axis SSS shader might be a better start for what you are looking for (and it's newer). Why is the Axis shader not a concrete solution?
  3. Fantastic! Glad it was something easily fixed. Not a waste a time at all since I'm sure other users will run into the same thing. Now they can find the answer here
  4. Could you get the latest build (10.0.374) and see if you have the same issue (maybe some odd bug has since been fixed)? Your HD license will work on the new builds so no harm there. And if I may ask, how exactly are you rendering the image and selecting the resolution? Have you gone to your camera options and change the resolution under the View tab? Have you laid down a new Mantra node and under Properties > Output and changed the resolution there by checking the "override camera resolution" flag to see if that works? I know these questions might be insulting but we should explore all possibilities.
  5. Houdini Tutorials on Vimeo

    Definitely watching the wet map series!!! And if we're adding Vimeo channels maybe I'll through mine in as well: http://vimeo.com/channels/57559
  6. Op_Id output

    I think what might be the issue is that you are missing the addition of vm_generate_opid (Mantra 10.0 > Output > Generate Op Ids for objects) to your Mantra node. If you're interested, I did a little video on this which might help.
  7. Painting with polygons

    I'm not understanding Mike's tip - I can't seem to get this effect to work that way. Could someone post a screen cap of the VOPSOP or a hip?
  8. A fanboy pic

    Beautiful! THANK YOU!
  9. A fanboy pic

    I would love a high res version so I can make this beauty my background. Got any handy (or currently rendering)?
  10. Where Can I Get HQueue

    HQueue is still in beta and is available in the Linux builds only (there's an option for it in the installer). I remember that it was supposed to come out of beta in July but maybe they've hit a few snags (or maybe I haven't noticed that Windows and Macs have it now). It will come with Houdini (so free in a sense) but Apprentice users will find little use in it due to the limitations. There is of course the HQueue Help Page, but HQueue itself has some help sections on it's actual use.
  11. Linux

    I'm not going to be the one start the which Linux distro is better, but I can say that I've been using Fedora (currently 11) with Houdini and it works. I suppose that's what's most important - a working Linux distribution that works with Houdini, and I'm sure there are several that work just fine. I will say that Fedora has regular updates and is backed by Red Hat.
  12. od[force] Houdini 11 Wishlist

    A retopology tool (or set of tools) would be a nice addition unless there's some great sop setup that can do a good redrawing of points on a model that I haven't found (anyone know of one?).
  13. The lighting model in the frontface box is so the front_side_light is contributing to the color of the shader (i.e. it gives the grid a green tint). As long as we're asking questions I have one of my own Jason. You note: "Please note that you must turn off "Ensure Face Point Forward" in the Lighting Model VOPs." This only applies when the normals of the grid are pointing away from the torus. When they are pointing towards the torus (I rotate the grid 180) it doesn't matter if "Ensure Face Point Forward" is on or off. So I suppose the question is: Am I right about that? If so, when using this technique is the orientation of the normals something you always need to think about or not worry about it and just uncheck "Ensure Face Point Forward" if it's not working?
  14. From my last posts (1, 2) one could discern that I had some sort of goal in mind. Well, I did, but after about a week of trying to figure it out I keep hitting a wall so it looks like I'll see if yet another post might lead someone to answer my cries. On a Vista 64 machine I have a device whose SDK is a COM dll. The dll comes in both a 32 and 64 bit version, so both are on my machine. I have a python script that can poll the data from the device and running it in IDLE with a 32 bit Python 2.5.4 and comtypes 0.6.0 I can poll data from the device - so it works! I can see everything I do on the device printed nicely in IDLE. But in Houdini (9.5.379 32 bit) with comtypes added to it's python directory, when I run the same script using either the python shell, making a python operator type, or even using the script sop, I get an error. Specifically: "AttributeError: 'module' object has no attribute [COM method]". The fact that it's throwing an error regarding an attribute in the dll makes me think that it's at least seeing the dll. This is reinforced when I turn off the device, both IDLE and Houdini post the error which says it can't find the device. So maybe this just will not work in Houdini. Maybe throwing in Python COM modules into Houdini just pushes the intended use of Python in Houdini too far. But what I would like to understand is why everything works beautifully in IDLE but when I have all the right ingredients in Houdini it doesn't work. Could it possibly be some issue with the permissions Python has in Houdini to access other parts of my machine? Or could it be an issue like 32 bit Houdini is looking at the 64-bit dll (which doesn't make sense to me if the 32-bit Python can see the right dll and work. It's a shame I can't get it working since it always has seemed that I'm really close to getting this device working in Houdini. It seems that Houdini can feasibly get device information (1, 2) without going a beyond-my-power HDK route.
  15. RESOLVED: Python COM Access Restricted In Houdini

    My thoughts exactly, that's why I wasn't paying any attention to what was actually in the comtypes folder. Big lesson learned on my part in this case.
  16. RESOLVED: Python COM Access Restricted In Houdini

    Figured it out - but this will be embarrassing on my part. And it actually makes me feel kind of silly wasting so much time trying to find work-arounds for what I thought was a bigger issue. But since I posted about it I am obligated to post the resolution: The comtypes module in Houdini wasn't compiled! (SYmek: You may begin laughing) I had no .pyc or .pyo files anywhere. And that was it, after I compiled everything using the Python compileall module in Houdini itself (along with adding my own _ctypes.pyd) it all worked out. Now I can get Houdini's command window to print the data from the device just fine. Now I need to see if it's feasible to get this data into Houdini beyond printing to a window, but that is for another day. And if I get anythin usable out of it I'll be sure to post about it.
  17. RESOLVED: Python COM Access Restricted In Houdini

    Small update: SYmek got me thinking about Houdini's Python version 2.5.2 and the one I have this working on (2.5.4). I took a look at the release notes from the Python 2.5 releases and it seems that there were a few fixes to the ctypes module after 2.5.2 was released. This might be the issue, so when I get a chance I'm going to do some module replacement to Houdini's ctypes with a 2.5.4 version to see if it's that easy to resolve my issue. Fixed since 2.5.2 (the first one is a big red flag to me):
  18. RESOLVED: Python COM Access Restricted In Houdini

    In Houdini I ran the ctypes test (Houdini 9.5.379\python\lib\ctypes\test\runtests.py) and got the following: find_library('c') -> None find_library('m') -> None ---------------------------------------------------------------------- Ran 349 tests in 0.141s (0 modules skipped) Unavailable resources: SEH, printing, refcount OK EDIT: BTW, I needed to add _ctypes_test.pyd from my python 2.5.4 install to Houdini.x\python\lib to get the tests to work. EDIT EDIT: I get the same result when I run the ctype test in Python 2.5.4.
  19. RESOLVED: Python COM Access Restricted In Houdini

    Nonsense! I'm always glad to hear from you The IDLE I've been using is Python 2.5.4 and Houdini uses 2.5.2. So yes, it's a different version. Houdini's python is compiled by SESI, and their python distribution comes with ctypes as a module which the comtypes module I added relies on. The one oddity is that though Houdini has a ctypes module it was was missing _ctypes.pyd so I took that from my python 2.5.4 version and put it in Houdini.x\python\lib (where a bunch of other pyd files are). Without _ctypes.pyd the script was complaining it couldn't find it (since the ctypes module _init_.py (in both Python 2.5.4 and Houdini) imports some things from it. Once I added it Houdini seemed to see _ctypes.pyd and import from it. Actually that never even crossed my mind, I'll run a ctypes test and post back. Everything I've been using has been compiled on VC8, so that shouldn't be an issue. I have run into things compiled on VC9 returning an error in Houdini, and the error usually notes that's the issue (e.g. MSVCR90.dll not found).
  20. No Python Libraries In Houdini?

    I noticed that Houdini comes loaded with *most* of Python, but it is strangely missing the library (*.lib) files. In Python proper they are found in the "libs" folder. Some of python's built-in modules use them, and that's still the case with those that come with Houdini. I tried to add them myself by creating a "libs" folder in Houdini's python folder but they weren't recognized. I'm correct in that they are not included right? Does anyone know why? More importantly, does anyone know how to add them to Houdini?
  21. No Python Libraries In Houdini?

    I think I figured out my problem. It wasn't the _ctypes.lib that's being called but the _ctypes.pyd. Houdini doesn't have it and neither does the 64-bit Python 2.5. So either I'll need to work on compiling my own 64-bit pyd for ctypes or go to 32 bit Houdini and copy the _ctypes.pyd from the 32-bit Python install and throw it in the ctypes folder (which worked). I thought I could take the 64-bit Python 2.6 _ctypes.pyd and use it but it's throwing an error because it's compiled with VC9.
  22. I want to bring in a python module into Houdini. This module is set up with multiple folders with various files (a package) so that I can import them like import myCoolModule.thisFolder as X or import myCoolModule.thatFolder as Y The HOM docs state:
  23. Accessing Packaged Python Modules

    This helps a great deal. They are generic modules so it seems that placing them in PYTHON_PATH is the way to go. Thanks SYmek!
  24. `outlight()`

    I gather you got the hip from here? If so, the `outvar()`_`outlight()` was a custom expression of Peter's: So it's not a built in feature of Houdini, but still a very useful expression!
  25. My Rigging journey

    Yes, yes, yes I would be first in line to download it!
×