ParticleSkull Posted January 20, 2017 Share Posted January 20, 2017 Does anyone know's how to solve it? It must be simple but I just can't find a solution anywhere :/ Grains in Dop: Mesh in Sop: Thx again, Alvaro granular sheet - ripping it.rar Quote Link to comment Share on other sites More sharing options...
Hans Peter Posted January 23, 2017 Share Posted January 23, 2017 (edited) What about the option "constraint break"? Maybe you can also play with some attributes exposed in the grain update node. For example the constraint weight? The object could transfer some attributes onto the granular sheed while it tried to cut thourh it. So setting the value on that area to 0 (constraint weight) or to 1 (constraint break) could give more precise control over the area which is meant to tear. Didn't try this but maybe you can get it to work. Edited January 23, 2017 by Heraklit Quote Link to comment Share on other sites More sharing options...
Hans Peter Posted January 23, 2017 Share Posted January 23, 2017 Oh, sry man, its late. didn't took a close enough look. You actually had it breaking in dops Quote Link to comment Share on other sites More sharing options...
Farmfield Posted January 23, 2017 Share Posted January 23, 2017 How about deleting prims or edges bigger than a specific number? Because the Farmfield lives for those ugly @$$ workarounds... 4 Quote Link to comment Share on other sites More sharing options...
Zybrand Posted January 23, 2017 Share Posted January 23, 2017 A different approach you can try is to compare the sim point neighbours with the initial point neighbours and use the attribute to delete primitives on the mesh. Have a look at my hip file it's just a quick proof of concept but with some work I think you can get good results with it. granular sheet - ripping it ZJ.hiplc 3 Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 23, 2017 Author Share Posted January 23, 2017 Awesome, thank you very much guys, I'm trying all of it right now. Be right back to let you know how it's working Quote Link to comment Share on other sites More sharing options...
Farmfield Posted January 23, 2017 Share Posted January 23, 2017 Great setup, Zybrand. Much appreciated - I love when I don't have to figure out stuff for myself. *** Alvaro - Add a shitload of drag and you got yourself a decent metal rip system. Remember the Monster rip tut w. Pflow? Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 23, 2017 Author Share Posted January 23, 2017 (edited) Hey Johnny, my setup is totally based on that tut I just think it's weird when Max can rip the mesh based on broken constraints but Houdini can't! EDIT: btw, it looks like I can't put a shitload of drag on it. At some point it kinda looks the same Edited January 23, 2017 by ParticleSkull Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 23, 2017 Author Share Posted January 23, 2017 Hi @Zybrand, thx man, you're a genius! It works just perfectly! I still have some doubts about what's going on there though and I'd really apreciate some help to understand it properly. My doubts are all on the vex codes: 1st - start_n and sim_n are getting the amount of connected neighbours of each point, right? 2nd - difference is checking if sim_n is loosing connections. If it does, @blast = 1. 3rd - why do I need the sim_n line on the difference node? Shouldn't I be able to compare sim_neighbours with start_neighbours directly? Something like: if(i@sim_neighbours < i@start_neighbours) Thank's Alvaro Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 23, 2017 Author Share Posted January 23, 2017 (edited) In fact I think I got it. the line int sim_n = point(1,"sim_neighbours",@ptnum); is just a way to copy the sim_neighbours attribute into the difference node. Thank you Edited January 23, 2017 by ParticleSkull Quote Link to comment Share on other sites More sharing options...
Zybrand Posted January 23, 2017 Share Posted January 23, 2017 Thanks Johnny, next time I'll grab one of your setups Hi Alvaro, cool I'll glad it works. Yes I think you understand get it, I am setting the initial amount of neighbours before the sim and getting the amount of neighbours after the sim. You have to set the start neighbours before the 2D triangulate because the amount of neighbours changes and I am calculating the the neighbours after the sim to get the new amount. And then the difference node just compares the the values on the geometry you want to tear. You can probably get better results if you work on the attribute promote -> delete prims part of my setup. That was just a quick test to see if it would work but maybe an edge group can get you better tear lines. 1 Quote Link to comment Share on other sites More sharing options...
Skybar Posted January 23, 2017 Share Posted January 23, 2017 Had a quick go at this with another idea, marking the points as broken during the sim: granular sheet - ripping it DV.hiplc 2 Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 24, 2017 Author Share Posted January 24, 2017 Hey David @Skybar, that's fancy! It would be even better than Zybrand's excellent solution but, unfortunatelly, it generates these suspended poligons around. Do you think it can have any solution on this? /Alvaro Quote Link to comment Share on other sites More sharing options...
Guest tar Posted January 24, 2017 Share Posted January 24, 2017 5 hours ago, ParticleSkull said: Do you think it can have any solution on this? CleanSOP -> Manifold-Only Topology. Quote Link to comment Share on other sites More sharing options...
Zybrand Posted January 24, 2017 Share Posted January 24, 2017 @Skybar Nice one! getting the attribute as part of the sim handy. And good idea to just use the attribute copy to transform the mesh. Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 24, 2017 Author Share Posted January 24, 2017 Yeah, that's it, thank you @marty! It's perfect now Thank you guys, you're all awesome. I always learn way more than expect on these topics Cheers, Alvaro Quote Link to comment Share on other sites More sharing options...
Farmfield Posted January 24, 2017 Share Posted January 24, 2017 (edited) Still very difficult to replicate the behaviour in Pflow, though - but I remember it didn't translate well using Thinking Particles either. But I might try setting this up with bullet and constraints and see what you can get. The great part with packed primitives is, they are points, so instead of unpacking them after the sim, you can simply delete all the packed primitive related attributes and use them as points together with the point deform SOP. And funny, even with all the control in Houdini, I still miss the TP workflow, it's just so easy to "organize" the particles using rules. Sure, you can do that in POPs using streams, but it just isn't as straightforward as the TP workflow. And note it was 2+ years since I did anything in TP, so this is a pretty persistent feeling. Edit: Here's William Wallace's tutorial and the "look" is just over 20 minutes in. [link] I might try constraining particles to their original height, or have a higher drag in Y than X/Z, that should make them bulge more outwards. Alvaro, aside from disabling gravity and upping drag, lower the constraint stiffness to keep the particles from "springing back", thus keeping the rip shape - if you hadn't figured that out already. Edited January 24, 2017 by Farmfield 1 Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 24, 2017 Author Share Posted January 24, 2017 Hey Johan, Cool! Would love to see the packed primitives setup. Thx for the tip on the stiffness! I haven't realised it works this way. The solution I got to have the metal look is to decrease a lot the Scale Time (0.01) on the Dop Network node. We could also play with the Max Speed and Max Acceleration on POP Grains' Solver tab but for now the Scale Time looks perfect. 1 Quote Link to comment Share on other sites More sharing options...
Farmfield Posted January 24, 2017 Share Posted January 24, 2017 Oh, that was a smart workaround, mess with the timescale - great tip. Lowering the speed/acceleration was the first things I did, then lower the stiffness, increase drag and disable gravity. But the timescale basically does the same thing in one setting. Very clever Alvaro. 1 Quote Link to comment Share on other sites More sharing options...
ParticleSkull Posted January 24, 2017 Author Share Posted January 24, 2017 (edited) Yeah, i'm a genius! haha Have you tried the Drift Threshold (solver tab also) ? It kinda freezes particles below certain speed. Looks cool Edited January 24, 2017 by ParticleSkull Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.