Jump to content

rich_lord

Members
  • Content count

    231
  • Joined

  • Last visited

  • Days Won

    12

rich_lord last won the day on May 25

rich_lord had the most liked content!

Community Reputation

161 Excellent

About rich_lord

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://richardlord.tumblr.com/

Personal Information

  • Name
    Richard
  • Location
    Seattle
  1. Hello. I'm using a model which is rigged up with a spring constraint network. I'm then copying this around multiple times and using the pscale attribute to get different sized setups. Everything works great, but the spring strength does not scale in the copy node (obviously), so each rigs springs act wildly different. So my question is: What do I need to multiply the spring strength by to make it scale at the same rate as everything else? I would of thought just multiplying strength by pscale would do it, but no, the springs act differently across the setups. So does anyone know the formula for adjusting the strength of a spring in relation to the amount the objects it is constraining scale?
  2. rotating in increments

    Thanks @ikoon. It works great, and now I know how to apply scripts too! This tiny script will save me hours. That's true @f1480187. That's the response I got from sideFX when I RFE'd this. The ladder does technically work, but its not a very good method for what I need though. I want to see if Houdini would make a good tile set editor for games, and I see the incremental snap feature as a pretty big deal for making that easy to work with. Its not easy to use the ladder to get exact numbers, particularly if they are not whole numbers. For instance, consistently, and quickly, getting values of 22.5, 1.25, 72 is not easy to do once. Imagine doing that thousands of times as I'm laying out a bunch of tiles where the numerical value is paramount. Maya and Unity integrate step snapping into their apps in a much simpler way than Houdini's ladder, which is great for some things, but crappy for this. Anyway, I've got a few hacks and workarounds now, including making big grids of points, and snapping to them. It's not ideal, but should let me test out some of the other features I need.
  3. rotating in increments

    Ok, will do. Anyone know how to script this behavior in the meantime? Is that even possible? I guess it would be ok(ish) right now to press a hotkey and have the object rotate by 22.5 each time I press it. I only need to rotate things around Y for now. For the translate snap, I can use grid snapping for now.
  4. I'm hoping I'm missing something basic, but is there a way to turn on incremental snapping for the rotate tool in Houdini? I'd like to set it so it rotates in increments of 22.5 I'd also like to do the same with the move tool. Have it only move in increments of 1. Thanks.
  5. ASUS Zenbook 4K Cinematic

    Nice one. There's a lot going on for such a short video!
  6. simple vector problem

    Thanks Juraj!
  7. Hello. I have two points. Each point has the same direction normal. I'd like to find out which of the two points is in front of the other, based on that direction normal. Is there a simple way to calculate this? This is a 2D problem. Y is always 0 for both points, and the direction normal is always flat along the XZ plane.
  8. Spring constraint networks

    Also, If you are trying to learn this stuff in general, I've got a thread about it over here.
  9. Spring constraint networks

    Spring constraint networks are amazing and ace. Here's an example of how they work. There's a hip file in videos description.
  10. Impact Data from Particular Object Id

    In a sop solver, you get an impacts node. Each point in there depicts one impact in your sim. There's also data on that point which will tell you who collided with what. I don't remember the name of the point attribute that corresponds to who impacted with who, but it's there. I think it is called objid and otherobjid. I'd take a look but I'm not near my computer. that should get you started. I can make an example hip for you later if it's still opaque. This stuff is a bit tricky and hidden.
  11. Thats a neat trick Houdini7. Its pretty quick for axis alligned snapping. If I have something that is off axis that i'd like to strighten out, its a bit more of a pain. You can repeat your trick by using orientation picking to rotate the handle. It works, its just a lot of clicking and fiddling about. In general, I use orientation picking alot when im modelling, and Houdini's is a bit hidden away, and not very streamlined. But that has helped me a bunch for the time being. Thanks for that Houdini7!
  12. Thanks Marty, I sent in an RFE.
  13. Hello. I'm modelling more and more in Houdini, but there's still a couple of things that I need to make it fast. Say I have a certain number of points selected, when I use the snap tool, the relative difference between the points is retained. That's great for many things. Often though, I want to snap to a point, and have every point snap individually. So, if I snapped a bunch of points in the Y direction to another point, all the points would end up with an equal Y value, regardless of their initial spacing. I know there are ways to do this, but they are all multiple steps, for example, grouping, or setting the y value with a wrangle. These methods are too slow for an operation I need to do many times a minute. Here's a picture to hopefully illustrate what I mean. I want to quickly set the selected points to the same y value. In other packages, i'd do this by snapping them all to a point with ignore component spacing turned on.
  14. Basic pyro settings confusion

    Oh the shame, I realized I was importing a velocity field, which didn't exist, and then scaling my sim down to 0. Sorry! I fell foul of posting, and then solving the problem immediately..... Looks like this now. A much better starting point.
×