Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About oddo

  • Rank

Personal Information

  • Name
    Jonas Otto
  • Location
  1. Within a python node you can use all the text reading and writing abilities that python delivers. It comes with libraries for the most common formats whether you want to read line by line from a .txt file, sorted data from a .csv table or structured data like a .json or .xml. The python hom.hou module enables you to write the data as attributes to points.
  2. My Content doesn't posted

    I have been waiting for 6 days now and my first comment is still not approved. I wonder if this very comment will ever see the light of the day. This is not very helpful to anybody...
  3. Laptop for houdini

    I own a Razer Blade with the same CPU and Ram but a 1070 Max-Q. Houdini runs great without any hiccups but obviously it's not the fastest at rendering. For GPU rendering I mostly use an eGPU or our render servers in the studio. If you still haven't bought a laptop you can now get a Razer Blade with a 2080 Max-Q. Coming from using MacBooks for years the Razer is also the sleekest Windows laptop I was able to find.
  4. Hey James, Sorry to bring up this old topic but I am trying to achieve what you did there. Building pyproj for Houdini (preferably 17 but 16.5 would work too). Using my local python 2.7 I had to install Visual Studio 2008 build tools for python 2.7 but I was able to build pyproj as well as 1.9.6. Using C:\Program Files\Side Effects Software\Houdini 16.5.439\python27\python.exe setup.py build I can see the references to Visual Studio 14.0 but in the end I get an error. fatal error LNK1169: one or more multiply defined symbols found How did you manage to build it? //EDIT: I managed to build it and use it within Houdini. So in Case anyone stumbles upon this here is what I did: https://github.com/jswhit/pyproj/issues/149#issuecomment-436305206 this issue on github got me on the right track. The duplicate now comes as a standard with newer versions of C++. So deleting it as describes seems to be fine. I got the source tar for 1.9.6 build it like described above with houdini 17s own python version. This creates a build folder with the compiled library inside (pyproj-1.9.6\build\lib.win-amd64-2.7\pyproj). I coped that pyproj folder to a "lib" folder next to my hipfile and use it within a python like this: import sys import os libPath = os.path.dirname(hou.hipFile.path())+"/lib" if libPath not in sys.path: sys.path.append(libPath) import pyproj Hope this helps somebody.