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.

bandini

Members
  • Content count

    274
  • Joined

  • Last visited

  • Days Won

    9

Community Reputation

87 Excellent

3 Followers

About bandini

Contact Methods

  • Website URL http://adamswaab.com

Personal Information

  • Name Adam
  • Location Los Angeles, CA
  1. I'd like an option in the Tree View to show objects in a hierarchy view. I want to have a maya outliner-style view or C4D object list view, just for /obj level objects (or subnets). I'd like to be able to organize them how I want and have the option to sort them alphabetically, if desired. I still want timeline markers...
  2. Looks like this is a bug. It has been reported and logged.
  3. Thanks, Ben. That's pretty much what I thought. I don't usually make HDAs of materials. I tend to use the prebuilt ones, then open them up and add what I need, promoting the appropriate new parameters as necessary. It's a matter of convenience for me to not have to rebuild the interface. So, now on to some other perplexing stuff. I'm trying to figure out why I get artifacts when using a principled shader inside a material builder. See the attachments. One uses the principled shader applied as-is to my geo. The other is embedded inside a material builder. I get the same problem if I try to layer the shader in /mat and apply the layer vop as a material.
  4. One other question, your method of copying the interface as a whole works, but it does not actually promote the parameters inside the network. It links them, instead (channel references them). Any way to promote all? Or am I missing something?
  5. Thanks, Ben. I think my question might need some more clarification. So, in the old shops, everything was contained in a material shader builder, which then had attributes promoted. Like a standard vops sop, any changes inside the network forced an on-the-fly recompile, but any changes to exposed parameters did not. In the new materials, we have a material builder, which appears to be a vop network wrapper (we even have a button to force compile, like vops). Makes me think this should work just like the old material shader builder. So, in addition to that, we have these other nodes, like the principled shader that can live outside of the material builder vop. It seems like playing with the built-in settings there do not force a compile of that source, but when I plug some other vop in, like a procedural noise, and then start playing with the noise values, we are forcing a recompile somewhere in the chain. Embedding both in a material builder and promoting parameters does not seem to cause any recompiles. Try this with the ipr render view to verify. I'm trying to understand the logic of the materials from the material palette showing up in /mat as nodes that are not embedded in a material builder when the documentation recommends embedding in a material builder. There's a disconnect for me there that needs some clarification or further explanation.
  6. On the same (or similar) topic. If we do package up the material, is there a way to promote the entire principled shader interface with one click?
  7. I'm liking the new changes to the material system in H16! Looks like we have two paths to build materials. Either use the /mat context as an open playground, or use a material builder in there to package up a material. With this new system, I'm not sure about how/when shaders get compiled. Seems like if we just want to use the principled shader as-is, we're good. But if we want to start plugging in noises and other stuff, we need to wrap it in a material builder and promote those parameters, unless we get a recompile performance hit. Anyone know if this is right or able to shed some light here?
  8. Nice! Renders look really clean and crisp.
  9. Thanks, McNistor! I am in agreement about the 2 shots you're calling out. Hopefully I can go back into them at some point. They really bother me, too.
  10. Teaser trailer is out now! Lots still left to do, but things are coming together.
  11. We've just announced a four-part course I put together for Learn Squared, showing an intro to Houdini. This may be too basic for intermediate users, and probably not useful at all for power users, but for people just starting out and scratching their heads in confusion, it should be enlightening. We've put a lot of time into making sure the quality of these lessons is top-notch. Learn Squared is a new way of doing these kinds of online classes. Each course offers mentorship critiques through skype sessions, and each apprentice's journey is recorded and documented as part of the class. We strive to get a lot of cross-discipline relationships started. For instance, I became an apprentice to a matte painter, and my first apprentice was a real-time graphics artist. There are multiple levels of entry with different price points, etc., so not everyone has to be an apprentice and document their work. Check out the course here: https://www.learnsquared.com/courses/houdini-procedural-foundations There's a lot of other great content there, too, which is useful across the CG and design spectrum.
  12. Hey Clive, I'm sorry, that project has been archived for years. No access to it, unfortunately. First, make sure you understand how the cookie sop works. Second, create a tool to make the honeycomb pattern. It's just a bunch of platonic solids packed together. Some are 4-sided pyramids, some are 8-sided. Not too hard, but you need to check some of the math to make sure the angles and spacing are correct. Can all be done in a Copy sop. -Adam
  13. Great suggestions. I really like #2 as an idea.
  14. I think I'm qualified to answer that This was made by creating a uniform honeycomb grid first ( en.wikipedia.org/wiki/Convex_uniform_honeycomb ) and using a cookie operation to get the intersection of it and the geometry. First, remove the pieces that are outside of the intersection volume, then do the cookie operation.
  15. yes. did you try it?