Jump to content

Search the Community

Showing results for tags 'Modeling'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 124 results

  1. patreon.com/posts/38913618 Subdivision surfaces are piecewise parametric surfaces defined over meshes of arbitrary topology. It's an algorithm that maps from a surface to another more refined surface, where the surface is described as a set of points and a set of polygons with vertices at those points. The resulting surface will always consist of a mesh of quadrilaterals. The most iconic example is to start with a cube and converge to a spherical surface, but not a sphere. The limit Catmull-Clark surface of a cube can never approach an actual sphere, as it's bicubic interpolation and a sphere would be quadric. Catmull-Clark subdivision rules are based on OpenSubdiv with some improvements. It supports closed surfaces, open surfaces, boundaries by open edges or via sub-geometry, open polygons, open polygonal curves, mixed topology and non-manifold geometry. It can handle edge cases where OpenSubdiv fails, or produces undesirable results, i.e. creating gaps between the sub-geometry and the rest of the geometry. One of the biggest improvement over OpenSubdiv is, it preserves all boundaries of sub-geometry, so it doesn't introduce new holes into the input geometry, whereas OpenSubdiv will just break up the geometry, like blasting the sub-geometry, subdividing it and merging both geometries as is. Houdini Catmull-Clark also produces undesirable results in some cases, i.e. mixed topology, where it will either have some points misplaced or just crash Houdini due to the use of sub-geometry (bug pending). Another major improvement is for open polygonal curves, where it will produce a smoother curve, because the default Subdivide SOP will fix the points of the previous iteration in subsequent iterations which produces different results if you subdivide an open polygonal curve 2 times in a single node vs 1 time in 2 nodes, one after the other. This is not the case for polygonal surfaces. VEX Subdivide SOP will apply the same operation at each iteration regardless of topology. All numerical point attributes are interpolated using Catmull-Clark interpolation. Vertex attributes are interpolated using bilinear interpolation like OpenSubdiv. Houdini Catmull-Clark implicitly fuses vertex attributes to be interpolated just like point attributes. Primitive attributes are copied. All groups are preserved except edge groups for performance reasons. Combined VEX code is ~500 lines of code.
  2. Hey magicians, I'm trying to model this cactus (crassula kimnachii) So far I have modeled a petal, bended, duplicated and transform in a foreach with metadata iteration for the scale and a sweep curveu to control the profile: My question is, I have the bend at the beginning of the node tree, and I need to access the bend scale on the foreach, to use with the iteration so is closed on the top and opened at the bottom. The bend got its own capture region so im having a hard time to play with this on the foreach, this is the way to go? or there's another alternative to make it closed on the top and opening on the bottom? Another test I did is using a curly curve (line with couple controls in vex), where I plugged the curly on the foreach and controls the opening with the metadata iteration: Any thoughts to approach this? Thanks!
  3. How do you guys deal with assembling a scene in Houdini? For example, say I make a ceiling tile, a floorboard, some wall panels etc. as separate geo nodes. Is there a way to arrange these procedurally on an object level? Or should I be working on one big 'room' SOP with subnets? Is there a general way one should think about piecing nodes together?
  4. I've been learning a lot of vex over the past couple of months and this is my first real practical use trying to make a procedural tool. Let me know what you think! Next iteration is to add more curved lines using trigonometry instead of smooth. https://youtu.be/UsDpGrcrLhE
  5. Modeler 2020

    Product link: https://gum.co/KYCgR What's new: 1. The Modeler core has been completely rewritten. Performance, stability and UX are improved. 2. A hotkey system has been created. Hotkeys are now configured in a separate editor (Hotkeys shelf tool). The editor allows you to quickly configure keyboard and mouse shortcuts. Unlike other modeling programs, you can now associate any tool with any combination of keys or mouse actions. In a similar way, the mouse and keyboard are configured in Nevercenter Silo, but unlike Silo, there are no restrictions here. That is, you can assign absolutely any tool to the mouse. On the other hand, mouse tools such as interactive selection can also be assigned to keyboard shortcuts. Also, unlike the standard Houdini behavior in Modeler, you can use the additional two mouse keys X1 and X2 (Ctrl+X1, Shift+Ctrl+X2 etc). The Hotkeys editor has two default mouse layouts: 1. Standard - that works just like DM and the previous Modeler version - LMB to select items and MMB to drag them 2. Pro - which allows us to select geometry components with RMB and drag with LMB. MMB used to select invisible items too. 3. The interactive state system (add-on for Python States) has been rewritten from scratch. Many tools have become more interactive and have the ability to customize the node in the viewport. In addition, you can quickly create custom interactive python tools for your own HDAs. The mouse wheel now works more universally. In many nodes, the wheel allows you to change the Uniform Scale parameter. List of nodes that now use state tools: Soft Boolean, Insert Mesh, QPrimitive, Array, Hose, Bevel, Extrude, Bridge, Set Flow, Smooth Points, Thickness, View Deform. 4. Retopology tools (Topo category) have been redesigned. TopoDraw tool (Alt+A) allows you to quickly draw poly patches on the reference geometry. It has an ability to snap to existing geometry. Topo mode (Alt+T) now packs the reference model. This speeds up the entire process of retopology with millions of faces. The Push tool now works in the Topo mode, which allows you to get the desired result even faster. In addition, the Push tool has improved performance and stability. 5. The Insert Mesh SOP was redone from scratch. It has interactive tuning, better performance, and more accurate results thanks to improved normals. 6. The Deform menu was merged with the Align menu and renamed to Transform Menu (Z). 7. The Relax tool renamed to Smooth. The tool is completely redesigned and takes advantage of Python States. Using the Smooth tool, you can smooth points or polygons in a standard way. On the other hand, the edges are smoothed as separate curves. Combined with interactive enhancements, the tool allows you to quickly fix messy areas. 8. Tools that create modeling nodes were removed from the Modeler shelf. Only general tools are now on the shelf. Direct modeling tools are now called from the Modeler mode. Added shelf tools: Delete Node, Merge Nodes, Stash History, Pack History, Clean History и Delete Attribs 9. Added a new tool Repeat Node Parms that allows you to apply settings from previously created nodes of the current tree 10. ToolsPanel (spacebar) renamed to Launcher. Launcher tools have been re-sorted and have a new Mouse section for interactive tools like selection or dragging 11. For Bevel, Bridge, Extrude and Smooth tools separate nodes were created 12. Bevel, Extrude, Inset, Smooth, Thickness hotkeys can work as sticky keys. That is, the call of a hotkey, for example, of the Extrude tool, leads to an instant change of the extrusion value before releasing the key. 13. Added Inset tool that uses Extrude SOP. In contrast to the Extrude tool, the first time you start Inset, you can change the inset with LMB. 14. The Lattice tool removed. It is now replaced by improved View 4 and View 9 (View Deform) from the Transform menu (Z) 15. Tools for a quick preview of the subdivided geometry were created: Preview Subdivide (Alt+1) и Preview Subdivide Wire (Alt+2). Standard viewport subdivision and instance subdivision (Symmetrize Tool) ar assigned to Alt+3 и Alt+4 respectivelly. 16. Select By Normals mode (6) allows you to select components based on normals 17. Local transformation tools have been added to the Transform menu: Local Move, Local Rotate и Local Scale 18. An Extend (Y) tool. This add-on to the Extrude tool allows you to quickly extrude edges and polygons using handles. 19. The Bridge Connected tool returned from the DM package 20. Slice, Clip and Mirror tools have the ability to set the initial origin based on points selection center 21. On the next call, the Delete tool changes the node so that it deletes unselected geometry. 22. The KitBash tool now offers to automatically create a KitBash panel if it is not created 23. Shift+Double Click can now replace the geometry of the current Insert Mesh SOP with the geometry from the KitBash panel 24. Combine and Boolean now offer to select nodes at the object level if the tool was launched inside the SOP container 25. Set Flow creates more accurate geometry in unusual situations. 26. Added a Point Weld tool (Alt+W) for interactive point stitching 27. The Soft Boolean SOP can be configured interactively. It also has a slightly improved performance. 28. Collapse History (Left) renamed to Pack History 29. Many tools are assigned to new hotkeys. The ToggleCompass tool is now called with the Backspace key. 30. The Edit Mesh shelf tool now renamed to Modeler 31. Modeler now moved to the package Houdini system instead of using houdini.env
  6. Cant close cracks in subdivide node

    Hey there! I am newer to houdini so this may be an obvious question, but I am currently working with a mesh that i would like to have part of it be a higher subdivided mesh so I can add parts of high detail to the mesh without having the entire thing be made of millions of polys. I was able to get that to work fine but after I subdivide the mesh using a subdivide node the option to close cracks is greyed out and it won't let me close the cracks that are created. Does anyone know why, and how can I use the close cracks function?
  7. How find "Cracked Edge" ?

    Hi. Now I trying make geometry optimizer for fracturing for rbd sim, making "Solid" geometry from background models which often have bad topology. So I must find "Cracked Edge", two Primitives appear to be connected by single line, but the number of Points on Edge belonging to one of the Primitives is insufficient.This looks like Shared Edge, but it is actually Unshared Edge so specifically break PolyExtrude SOP. This Edge can be fixed by Union Boolean SOP, but my asset may import bad surface geometry which has many problem about Boolean SOP so I don't want use it as possible. How can we detect this? GeometryOptimize.zip
  8. Hi there, new Houdini user here (couple months in). I'd like to group some collinear points along a polyline. And when I say polyline, I mean an edge I created using a curve with a primitive type of "polygon". Is there a simple way of doing this procedurally? I plan on running a polywire on this, then beveling edges at these points, but I would like to avoid beveling the edges on the collinear ones. Just a warning that I am an artist with limited scripting knowledge (I am beginning to learn a bit of vex and have done a small amount of python before). If the answer involves a ton of code, there is a good chance it will be lost on me Thank you
  9. Is there a way to use this technique and only keep the faces that the rays hit first, and to delete the faces that are occluded by shadow (or what would be in shadow)? Not sure if this makes sense, but I basically have a messy geo, with a bunch of inner faces. Normals facing in and out everywhere and I'd like to just be able to keep the outer most geometry. And I was thinking that using a set of lights might be a way to just select those outer faces. Any help is greatly appreciated.
  10. Photoreal Honeycomb help needed

    Hey ya'll, So I've been working on this photoreal honeycomb for a project and I'm not happy with the amount of detail I'm achieving. I'm relatively new to Houdini and I've been trying to use it as a Generalist package however as soon as I have to use any code I start to feel out of my depth. In saying that, my current solution is almost all procedural and all with nodes and no scripting. I have opted for using attribute noises and point VOPs to generate roughness, displacement/surface noise as well as using shader displacement/normal noise to get High frequency noise without having an insanely heavy mesh. I should mentioned I am using redshift to render currently. So my main question is how can I make this look more detailed and more photoreal? (I have provided a render of a test section as well as photo reference of the detail level I would like to achieve.) That test render is the starting point of a camera animation, so that is as close as I intend to get to the honeycomb. I was wondering if I should use a solver to get an organic growth effect or maybe a volume vop? I have tested a volume VOP set up with no luck. Also I find my shader in redshift gives me a plastic look with too much sheen and the normal/displacement looks fake but I can't get it looking better. Any suggestions would be greatly appreciated as I feel I've reached the edge of my knowledge on this. As mentioned I am currently using Redshift, however if someone has a Mantra solution that works well I would be happy to look at that too. I have provided a hip file with the dome light HDR and the mesh cache as well for simplicity. Annnnd this is a small section of the actual amount of honeycomb needed, the actual size is probably 10x that section. Thanks in advance for your help! Jon beach_parking_8k.hdr Honey_high_res.bgeo.sc JW_Honeycomb_Detail.hip
  11. map uniform pattern on a geometry

    Hi, I have been looking for a way to create a model that has a certain pattern (like tri, quad or hex - whatever being convex or hole). It is something like this in the picture but the pattern should be all universal in size and shape. (in the picture, the upper part goes smaller and the bottom part being squashed) I understand by doing this, it most likely changes the original shape of a model though. Cheers,
  12. Help with porcedural building

    Hello I'm working on a procedural building and actually i'm stuck with something. I've tried many thing but it doesn't work. I'm trying to add or remove the number of the window when I change the size of the building. I've wrote this and i've tried to add an offset to keep a space between 2 windows but I didn't find how. vector mypt = getbbox_size("../box1")/getbbox_size("../box2"); //box2(window), box1(building) float dist = distance(@P, mypt); if(dist > ch("distance")){ removepoint(0, @ptnum); } if(dist < ch("distance")){ addpoint(0, @ptnum); } Is someone can help me with that Thank you https://youtu.be/iwNiS0YTCms
  13. Hi all, There likely does not exist a perfect solution here, instead I'm looking to brainstorm and find the most automatic method by which to detect and remove one of two sides from a double-sided polygonal mesh. The end goal is preparing meshes for simulation with Vellum, of e.g. a t-shirt or pants, that has been modelled with two sides (to represent thickness during render). The simple solution would be to provide a separate one-sided mesh for simulation in addition to the renderable mesh, but when that is not possible the current workflow are as follows. Recieve double-sided render mesh (of potentially too-high polygonal count and needless edgeloops unsuitable for simulation) Manually select interior (via e.g. edgeloops and growing of primitive selections) to remove it Remesh to achieve a uniformly distributed triangular mesh Profit The manual step (2) is what's preventing my setup from being applied procedurally to the tens of characters with tens of double-sided geometries each. I'm attaching an example of one such mesh for clarity. Given that thickness is most commonly - but not always - achieved by extruding a single-sided mesh, there are some assumptions we can make about the extruded side; primarily that each exterior primitive will have exactly one associated interior primitive, and that their normals are facing away from each other. So what I've got in mind is somehow iterating over primitives, finding their closest neigbours and checking whether any of them are (1) unconnected, (2) within a certain distance and (3) faces the opposite way. That's about as far as I've gotten at this point, and wanted to enquire with the community about whether anyone has tackled a similar issue, or whether there are any ideas along the same lines? Thanks, Marcus
  14. Greetings, I want to model this attached picture in Houdini. I think the closest way to get this effect is to get into modeling a slime. I attach the link to a video on youtube which I think is close to what I want. Slime FX: Houdini Grains I do not know how to achieve this and what is the process. Any help would be appreciated. thanks,
  15. Modeler 1.0

    Modeler 1.0 for Houdini released! Free for all the DM 2.* users. $70 for the DM 1.* users. https://gum.co/xKBKM What's new: 1. DM now renamed to Modeler 1.0 2. new feature: the DM menu (Z hotkey) has been replaced with a new alignment menu where you can use tools for fast and accurate transformation. The menu includes the whole set of tools for working with a compass, geometry centring, quick flattening with gestures and many other transformation tools. Use the hotkeys for the tools of the old DM menu. 3. new feature: Deform Menu (N hotkey) with lots of interactive deformation tools including a new Lattice tool 4. new feature: MODELER_PICK_STYLE environment variable allows to override Modeler startup selection pick style. Add it to the houdini.env file. Use "Box", "Lasso", "Brush" or "Laser" values, then restart Houdini. 5. new feature: the hard and soft boolean tools are now combined in a new menu called Boolean (J hotkey) 6. new feature: a Fix Curves tool helps get rid of broken lines in open polygons. This helps when beveling corners of open polygons. 7. new feature: a Select Curves tool helps to select open polygons (curves) in the model 8. improvement: now some tools can create curves and process them. For example, the Extrude tool can produce lines from selected points. The Collapse tool can flatten open polygons (curves). The Connect tool can be used to cut a segment between two selected points or connect two open faces. The Push tool now properly moves points in open faces. 9. improvement: the RMB menu of the Push tool has a new item Toggle Connectivity, which allows you to move points, capturing the points of other closed pieces 10. improvement: the Push tool now works slightly faster 11. improvement: the Push tool can now slide point with Ctrl+MMB 12. improvement: the mouse and keyboard shortcuts of the Push tool have been completely redone 13. improvement: if nothing is selected, the Hose tool searches for all the curves in the current geometry 14. improvement: a Group parm added to the Hose Tool. Can be used in conjunction with a result of the Duplicate tool 15. improvement: Hose now creates straight edges tube if the Resample Curve set to zero value 16. improvement: Geometry Library renamed to KitBash and works only as the python panel 17. improvement: KitBash replace feature now doesn't update the item icon 18. improvement: Tools Panel now has a new category KitBash with tools for working with the library items. Now you can create, save, overwrite and update icons faster, without actually working in the KitBash panel 19. improvement: volatile edge sliding now does not require explicit movement of the mouse pointer to the edges 20. improvement: volatile edge sliding now can be used to slide points and faces 21. improvement: Fix Overlaps can now use face groups 22. improvement: Duplicate applied to edges now creates a curve in the current geometry object 23. improvement: the Resymmetry tool now works slightly better. The Tollerance parameter is no longer saved between nodes (). This allows you to not change the position of the seam points. 24. improvement: mouse wheel manipulation in various tools has been improved 25. improvement: new simple box type has been added to the QPrimitive HDA 26. improvement: Tools Panel now has a more logical structure for faster access to popular tools 27. improvement: the Modeler shelf was fully revisited 28. improvement: the Walk History Up and Walk History Down tools (Up and Down hotkeys) now work more interactively when traveling through nodes with more than one input or output. 29. improvement: the Select By Shells tools was replaced with a new Convert To Shells tool (Ctrl+1) 30. improvement: double-clicking with LMB in the viewport is completely revisited. Now you can jump to objects level by double-clicking LMB in an empty space. Clicking on a geometry allows you to quickly switch between objects. If you are in a certain state, double-clicking activates the selection mode. All these improvements speed up the modeling process. 31. improvement: the deformation tools (Size, Ramp, View) now have the fixed blend feature. The transition between the deformable points and the undeformable part looks more correct. 32. fix: Hose now orients rings copies correctly 33. fix: Slice, Mirror and Cut tools now set correct geometry center on tool activation 34. fix: JumpUp and JumpDown tools does not work when Compass is active 35. fix: QLight now works properly if you run it from the orthographic viewport 36. fix: sometimes camera movement with Alt did not work after a mouse click 37. Lots of tools have changed hotkeys. Look at Tools Panel for more details. 38. Python code has been revisited 39. Documentation has become more detailed 40. Overall speed improvement 41. Other improvements Works only in Houdini 18. Use build >= 18.0.346
  16. Hi all, I have been researching for this for days and so far haven't found a solution for this question. Maybe someone with more knowledge can point to the right direction. So, I have converted a 3D geo to a 2D version of it using the UV as reference through "@P = @UV". So far, so good. Now I need to perform some simple modeling procedures on the 2D geo like individual face extrusion, bevel etc and then bring the geo back to the original 3D version but with the modifications added. Would someone know how to bring the modified 2D mesh to its 3D format but keeping the mods performed while it was in 2D? Any suggestions would be appreciated. Thanks.
  17. Hello, I have an issue connecting two sets of points the way I want. As it can be seen in the screenshot, I have two groups of points, one along a square and an other along a smaller square. They each have exactly the same amount of points and I want each of the point from the bigger square to be connected to one point of the smaller square. Any help is appreciated. Thx.
  18. hi my dear friends In fact, I tried to imitation cinema 4d's Slide Tool >Clone edges https://help.maxon.net/us/index.html#XSLIDETOOL-MDATA_MAINGROUP Do you have a better idea? I use polyextrude node on a primitive, I want to merge point number 26 to primitive number 4, and primitive 4 , it has five point, it becomes N-gon Should I use facet or fuse node? Please check the attachmenthow to make a n gon.hipnchow to make a n gon.hipnchow to make a n gon.hipnc. Thank you!
  19. Hi ! my friends who can help me solve this problem Thank you very much $CEX GCX BBX ? how to move the pivot.hipnc
  20. modeling a cell (beginner)

    Greetings, I want to create a procedural shape like the one i am attaching to this thread. I cant seem to find the right process to achieve this. Would anybody please help and explain how to get this shape and form? any help would be appreciated.
  21. Random File to Point

    Hey guys, new user here. I have a folder of objects built and exported from Houdini, and a bunch if random points scattered on a surface. I'd like to copy a different file to each point based on an index attr. I've gotten it to work using packed disk prims but not as full geo. The issue with packed disk prims is I loose all the existing attrs and groups in the files. Perhaps I'm going about this all wrong because it seems like there should be a simple solution. Any help you guys can give would be thrilling!
  22. Sketch and etch style

    Like everyone else, I use a bunch of tools for my work. But I found myself using Houdini more and more for 2d work, including making a sketch or etch style of pictures like these. I did it using sops, and while I imagine there is at least a million ways to do that in Houdini, it was bloody fast, took just a few nodes, and with plentiful variations.
  23. Poly Carve SOP

    http://www.patreon.com/posts/31506335 Carves out polygons using a point attribute with the ability to define the carve values per primitive using primitive attributes. Pure VEX implementation, 10x faster than the default Carve SOP (compiled). It preserves all available attributes. It supports both open and closed polygons.
  24. Hi! I'm loading an .obj file that contains multiple pieces of geometry(with different names). I want to apply Boolean to every pair of them, to union them into one big object. I'm assuming I'll probably need to use the for loop somehow, but I can't seem to figure it out. Can you help me out?