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.
Search the Community: Showing results for tags 'primitives'.
Found 4 results
I'm trying to add this geometry to the primitives of an object, in this instance a cube. I'm quite lost and have no idea how to continue, any suggestions? Also, is there a way to have a rectangle spawn from the corners of the grid towards the center, whilst following the height of the surface? VFX1.hipnc
Hey guys, I have a scene with one object copied into thousands of points (particles). Since I'm using packed primitives, the scene gets super fast on Houdini but it's impossible to export it out. Does anyone knows what would be the best way to send it to Maya? Is there a way to, maybe, export it as a placeholder (a box for example) and, inside of maya, replace the box with the original object, maintaining it's matrix (pos, rotation, scale..)? Thx, Alvaro
Jero3d posted a topic in Lighting & RenderingI have a question that has been bugging me for some time and I couldn't find much information about it. Which is the best and most efficient way to render many polygons? Using delayed load procedurals or using packed disk primitives? Or, am I confused and are they both doing the same thing and there's no difference between the 2 workflows? As far as I know, they both create instance geometry. The documentation doesn't help much either, half of the things I read talk bout optimizing a render using delayed load procedurals, and the other half about using packed primitives. I'm wondering if packed primitives is the new workflow and using delayed load procedurals was the old way of doing it as is now obsolete? Here are the 2 workflows I'm talking about: Packed Disk Primitives Here I pack all my geometry and write it out to disk. I then load it back and change the load setting to "Packed Disk Primitives". Then I generate my IFDs and they are now referencing the geometry from disk instead of having to write them out (And the IFDs are a few KB or MB big). I then render using those IFDs. Here is what the documentation says about it: "Packed Primitives express a procedure to generate geometry at render time." "Because Packed Disk Primitives by their nature are geometry streamed from a file, similar to Alembic primitives, we don’t have to use a special procedural to get smaller IFDs." Delayed Load Procedurals Here I write out my geometry (not packed) as bgeo and then make a Delayed Load Procedural shader and select the bgeo files I just wrote to disk. I then go to the Rendering -> Geometry tab of my object and load my Procedural Shader. I then create my IFDs and then render them out. In the documentation about the delayed load procedurals, it talks about optimizing geometry this way. So I know there are these 2 ways, but are they both equally the same, or is one of them better than the other? Which workflow do you use? Also, when using the packed disk primitives, if the geometry you want to render is unique and it can't be instanced (or there's just no point in doing it), do you still pack it (so its only 1 packed prim) and save it out? Or do you use the delayed load procedurals? Do you use any other workflow? Any advice on this would be greatly appreciated! Thanks
Hi, Is there a way to limit the scope of the Dirt Mask VOP to primitives? I am basically using a dirt mask to give a wear look to the fabric and set the scope to scope:self. But the problem is that when I create a dynamic simulation the dirt mask includes all primitives inside the object, as you can see in the image.