Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ColinCohen

  • Rank

Personal Information

  • Name
  1. The Last Buddha

    This is my first nearly completed project using Houdini, which was used roughly equally with LW, as well as a couple of post tools. http://cc600.com/video/buddha.mp4
  2. Mdd Reader

    As I said, LW looks at the world backward. That is, x,y,z in Houdini = x,y,-z in LW. For example, I've created a complex road system in Houdini, part of which gets smashed. I imported both parts into LW. I then did the DOPs in Houdini and exported the .mdd file using the original script. But .mdd file caused the geometry to appear on the opposite side of the z-axis in LW. So I negated the z-coordinate in eetu's script and all was well. It should be noted that if all you're looking at is one piece of geometry, you might not even realize it was flipped, as you'd have no reference point. But with multiple pieces, it'll become very obvious. LW's rotational system is also different than yours. Fortunately, you don't have to deal with that with .mdd files. But if you guys ever decide to write a .mot file exporter (for motion paths) as I recently did, you certainly will.
  3. Mdd Reader

    I've used my modified versions of these scripts in production extensively in the last month. They work very well besides that offset issue, which is very easily worked around. LW looks at the world backward. All I had to do was negate the z-coordinates in eetu's script and everything worked perfectly. Edward, I saw that other thread. I'm not sure there's anything I can add, but if you have any questions about the .mdd format, feel free to ask them. I know it pretty well -- I've even written custom C plugins that read and write them.
  4. Houdini 9.5 is here. First Impressions?

    Looks like an excellent upgrade. I read here that v8 had an IPR system, but they hadn't time to incorporate it into v9: http://www.sidefx.com/index.php?option=com...p;highlight=ipr Does anyone know if it's still planned?
  5. Houdini to Lightwave pipeline?

    Blender creates a velocity file that's used by its vector blur compositing node. The file's not documented, so I had to backward engineer it from the C code (and possibly not %100 correctly.) When the point counts were consistent from frame-to-frame, it worked -- but if the mesh got more dense, the points that didn't exist in the previous frame would have nonsensical velocities.
  6. Houdini to Lightwave pipeline?

    What you're describing is, I believe, how RealFlow works in LW. I once tried doing that with Blender, but I couldn't get consistent velocity vectors from Blender when the point count difference was significant. But I did update that Python script so that it would create the velocity endomorph. If you'd like, I'll post my modification here -- that should take you a little closer.
  7. Houdini to Lightwave pipeline?

    If you're feeling ambitious, there's a Blender python script for exporting object sequences to .lwo. It shouldn't be too difficult to convert it to Houdini (which uses Python as well.) You could then convert your surfaces right inside the script. And if you're feeling really ambitious, there's a section in the Houdini help describing how to write your own custom importer. You might find it useful to know that Houdini exports its groups in .obj files, which are read into LW as parts. So, by using the Parts -> Surfaces command, you can transfer your Houdini group names to LW surface names. By the way, LW will not create motion blur on an object sequence (unless something's changed recently.)
  8. Mdd Reader

    Here you go (I didn't want to post it without your permission.) I haven't yet fixed issue #3. ee_mdd_reader_05.zip
  9. Warning On Start Up (solved)

    Go to the Control Panel, run System, and on the Advanced tab you'll see a button for setting environment variables.
  10. City Engine

    And it seems there will be a non-commercial version as well.
  11. Mdd Reader

    I've found some small issues with writer. These relate to using the native .mdd reader in LW8; they may not be issues with Point Oven or with other readers. 1. I had to flip the z-axis in the script. 2. The last exported frame disappears in LW. It seems the reader in LW expects an extra record at the end. I appened one, and that fixed it. 3. If the exported range is in the middle of the timeline, it seems to be offset by a frame. For example, if I want to export from frames 400-450, I need to export from frame 399. Thank you for this very useful asset.
  12. Archway Asset

    Steven, I can't seem to reproduce the circle bug. Could I trouble you to post a .hip file? And what version number of Houdini are you running? I'm creating an Arabesque city for a short film I'm making. Thus all the archways. I'll post it here in a few months when I have the first WIP done. I've been surprised how many buildings have arched windows and/or doorways, even here in LA. So hopefully it will be of general use as well.
  13. Archway Asset

    Thanks for the feedback (and the bug reports) -- it's much appreciated. I've updated the file in the original post with the fix.
  14. potbelly pig

    Very much looking forward to seeing the .hip file. I'm new to Houdini too and just assumed I would have to continue to do this type of modeling outside of it, but maybe not.
  15. Archway Asset

    I've had to create a lot of arched doorways and windows for my current project and decided to create a digital asset and release it. If you use it and find problems, please let me know (I'm pretty new to Houdini so I might've missed something.) Thanks. archway.zip