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.

Sabes

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sabes

  • Rank
    Peon

Personal Information

  • Name Sebastian Pienta
  1. That works fine for me! Now I know how to achieve the grouping of the seams to use it for the bevel. Thanks for that knowledge! This is such a great forum with a lot of talented people!
  2. Here we go. As I said. I just want to make the bevel on the edges... even if I change the rows on the sphere. (increase the tubes)... The bevel should also work with an adjustable tube-intersection-count. Lamp_03.hipnc
  3. Hm, ok...I see. But isn't it possible to take those edges and say via grouping and a boudingbox that those "seems" should be beveled? Tried something like this here:
  4. Hey friends, for me as a beginner in Houdini it's complicated to understand what Houdini tries to tell me. Maybe someone could help with one sentence. I'm simply modeling for training purposes and try to make some parametric holes into a curved surface. Cylinder+Sphere -> extruded with back -> tubes intersecting! The Tubes intersect with the geometry as I want them to. It's also possible to add and decimate the number of cutted holes by simply adding rows to the connected geometry. So far so good. But in the next step I try to give the cutted holes a bevel at the edge. Houdini shows up an error! What does this error mean? How can I achieve beveling an edge when working with parametric models? I tried to convert it into a vdb but the resulted mesh looked terrible! Cheers, Sebastian
  5. Hey marty, I found out that the bullet dynamics makes a bounding box around the complete mesh. Had to change the dynamic to RBD and merge the tires with the cars body and it seems to work now. Is there an easy way to group different parts of a mesh for dynamics on object-level? Because a problem was that when I was importing my mesh into the scene, the complete car broke into pieces (I still don't know why and how I fixed it. I think it was inside the cars SOP in the assemble-node). Any suggestions here? I'll link a screenshot of the car node-setup. Maybe this helps.
  6. Hey marty, thanks for the quick reply. But is there any way to show the pivot that I'm moving after disabling this both options? I did that already and my car started to spin.... Maybe this indicates other problems I should solve first?
  7. Hey people, I heard this forum has a lot of really talented and technical oriented people who can help me out of my problem. At work I have to do some research and create a little scene where a car SLOWLY falls down a cliff. Imagine someone would push a car down a hill without a driver and it falls down to hell. So as a Houdini-Newbie I imported an OBJ of a car and declared it as an RBD-Object. My simple-geometry-plane is a static object. Through the gravity tag my car "rolls" down that hill and jumps over the cliff. But there is one problem. The center of mass should be more in the front of the car. Is there any easy way to move the CoM-point to the position where the engine sits? I tried different things like pushing the pivot aso. but nothing worked. It seems like Houdini tries to calculate the center of mass in the Object-Level with a bounding box and ignoring my custom moved pivot. Is there an easy way to define an exact point, where my center of mass is? Or is there any way to show it at least? My goal is, like you will see in the screenshot, that my car falls down a little bit faster in the front. Like it would behave in real world. Now it is pushing itself over the cliff until it gets over the center point of the OBJ. Thanks, Bastian