Members

5

409

Members

2

780

Members

1

1,940

Members

1

156

Popular Content

Showing most liked content on 03/09/2019 in all areas

1. 5 points

17.5 Launch Event Presentation

Article on SideFX.com: https://www.sidefx.com/community/houdini-175-launch-event/
2. 2 points

Multiply vectors to a plane (Trigonometry questions)

I exposed some parameters, in case someone is looking for a screw nut / cog wheel generator ; ) hex_nut.hiplc
3. 1 point

Thistle One

Hey all, this is a collaborative project directed by Bobby Beck from Pixar (ex employee) and a bunch of artists from all over the world. My role was FX lead/sup so I did both shot works and lead roles on the FX side. All done in Houdini and rendered in Arnold. Thanks for watching and feel free to share it all over. https://www.youtube.com/watch?v=sl0J4XoARjk
4. 1 point

17.5 Launch Event Presentation

Is confirmed that is included also in Indie, so don't worry
5. 1 point

Multiply vectors to a plane (Trigonometry questions)

By "multiplying" you mean projecting them onto a plane? If so, cross() seems to be enough: // P is a vector in world space and POS, NORM are point // and (unit) normal vector defining infinite plane vector p0 = P - POS; vector projected = cross(p0, NORM); projected = cross(NORM, projected) + POS;
6. 1 point

Assign volume shader at SOP level

Your shader is getting assigned alright (which you can test by using different shader) but i guess it has something to do with "uniform volume" render property which I guess should not be assigned per primitive but as a whole object in order to determine surface of a volume. I guess when you pack an object beforehand - you are assigning material to the WHOLE, pack object, not just individual primitives - therefore it may work. Alternatively, you could add your "uniform volume / volume quality / volume density" render properties separately on the geometry level. material builder_test2.hip
7. 1 point

CentOS for Linux newcomer?

The performance will not change. The viewport performance might get worse. Linux is much more manageable, controllable, and it can be easily automated which is the key. Especially if you have many machines on a render farm. I'm not saying you shouldn't move to Linux, just saying that if you're expecting performance gains then you'll be disappointed. The only reason I'd use CentOS or RHEL is if an application requires it. Otherwise it's a pretty terrible option. Especially for someone new to Linux. Install the video drivers through a repository like EL Repo. The drivers from there have DKMS support already configured so when the kernel changes (like from an update) it won't break the system. http://elrepo.org/tiki/tiki-index.php https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support People new to Linux think they can download stuff from a website and just install it (like you can on Windows). On Linux this is usually a shit plan. If it exists in a repository then install it from there instead. Sounds like you were doing it wrong. Sounds like you should use driver packages with DKMS. When done properly Linux is extraordinarily reliable. Unfortunately, yes, I'm using Houdini on CentOS but only because I need Autodesk products and Autodesk foolishly supports only CentOS and RHEL. If I didn't need Autodesk products I'd be using Ubuntu, specifically an LTS release like Ubuntu 18.04 LTS.
8. 1 point

Difference between Fit Range / Unclamped

Clamped is useful to fit and make sure no values exceed your new limits. Unclamped fits and extrapolates. Here you have a small clip showing a basic visual explanation. You can see that both clamped and unclamped have the same slope but clamped gets blocked between newMin and newMax. The uses for this are many, I hope it's a bit clearer now. Cheers! JT_clampedUnclamped.mp4
×