Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Days Won


Community Reputation

44 Excellent

About goldleaf

  • Rank

Contact Methods

  • Website URL http://vimeo.com/user866299

Personal Information

  • Name Chris
  1. If you run houdini from the Terminal, you might get more information. With Houdini installed in the standard location, open the Terminal and run: cd /opt/hfs16.0.633;source houdini_setup;cd --; houdinifx --foreground Hopefully, that'll give you more information when it crashes.
  2. Got it, thanks Mark
  3. Does anyone know whether or not a fisheye projection is possible to write for the viewport? I'm looking around on behalf of a friend, and I think it might be possible, from perusing the HDK, but can't tell for sure. If anyone knows whether this is possible or impossible, either way, it'd be great to know. Thanks!
  4. What version of OpenVDB are you linking against, the one that ships with Houdini 16, or from Github? And there have been some HDK/OpenVDB changes in the logs; I'd try using 16.0.557 or later if you can.
  5. You need to put it in backticks, and use a single-dot for the current node: `opname(".")`
  6. Yeah more ram/HD space the better, if your motherboard can support it. For your current setup, you can totally get used to using Houdini just fine; obviously keep in mind you won't be winning any benchmarks, but for just getting started for as inexpensive as possible, you're pretty close to having something decent to start with; I would replace your graphics card with a 6GB GTX 1060, for $250 USD (I use one on a 2560x1440 screen, works great). Also, I've found that older 12-16 core (24-36 thread) workstations can be found on eBay for pretty good prices, and are a cost effective way to acquire cpus for heavier sims/renders. Often times these machines can support anywhere from 96GB to 256GB of ram too. I also use Linux Mint. Good luck!
  7. if you need to save disk space, you might find it useful to convert large particle sets / point clouds into Points VDB and saving that VDB primitive to disk in your bgeo. Haven't tested rigorously but seems promising.
  8. http://www.openvdb.org/download/openvdb_particle_storage_2015.pdf
  9. The initial data for DOPs simulations requires .sim files. For FLIP (and maybe some other solvers), technically you could probably use a bgeo as the source, giving it some initial velocity and such based on that frame of a sim; but you're not actually resuming a sim, you're starting a new simulation, and it may not match up very well since it's an incomplete snapshot that doesn't have the whole state of the system like the .sim files would have. *edit* what vtrvtr said
  10. Yeah that's awesome they added it; I switch between left/right handed mice/stylus and backspace its great. There is also a Left Handed Menus option, to move the menus to the left side of the cursor instead of the right side, if you prefer that.
  11. Definitely sounds like a bug, though I haven't hit it; I'd submit it pronto.
  12. Try the Group Expression SOP with: @numvtx > 4 Group features were broken up to be easier to support/expand, and to make it easier to work with groups. Many of the features crammed into the Group SOP were difficult to find/use. Hope that helps!
  13. Yep, that's what I was curious about! Glad to know it's in there! Thanks @Sepu
  14. Thanks @Atomthat's great! Does RedShift allow variations when instancing lights?
  15. I too am curious, its good to see AMD surging in the right direction