@@KefuP I’ve played with it and self collisions do work, as do cloth sims. I think they just have them turned off by default because it’s faster and they aren’t needed for fluid/grains
@@Elysium.4D it seems like grains and fluid have their own kind of way of dealing with self collisions. When I can though self collisions are the first thing that I turn off to optimize sims, a lot of times they aren’t actually necessary for vellum stuff and it can be a huge speed boost (even with the regular vellum solver)
i havent, it seems really impresive, but it also sounds like a huge hassle transferring data back and forth between there and elsewhere, so it doesnt honestly interest me too much. it would be really cool for realtime visuals though, running it on a computer and feeding stuff into touchdesigner or something. probably not super practical for cg production though except maybe for niche situations.
Man this tutorial its amazing i have been trying the vellum fluid part and the quality and speed are really good 💛, but i have a little problem i tried to retime the simulation of the fluid after cache the sim on disk to get a slow-motion effect and from the retime node i get like glitchs and jumps in the frames, i tried to set up ID point attribute in the attribute wranger but nothing and i havent found any info how to solve those glitches from the retime node 😭
I've been thinking of moving to houdini for a while, mainly due to the fact that 3ds max plus vray plus phoenix fd is just impossible to pay for as a passionate hobby. I mainly like creating extremely detailed fluid simulations and visuals for my music using tyflow particle physics, smoke and liquid. So couple of questions if you have the time.... What is the cheapest version of houdini that I should aim for? Are the indie licenses fully functional especially when it comes to particle physics and fluid sims? Does this Include render engine on par with vray or would I need to buy another engine? Also is the workflow quite easy to adopt coming from max? I tried blender once but I really didn't like the workflow at all so left at the first hurdle? Many thanks and subbed
I think houdini sounds perfect for you. 1. you can start with houdini apprentice. when you become confident you will actually use it, houdini indie is fully functional (no different from the more expensive versions feature wise) and you can upgrade your files to work there. 2. yeah karma is amazing. I havent used vray much. ive used redshift, arnold, octane, and I think karma is definitely what you want. it specializes in doing stuff like volumes/particles/hair but is a really strong all around renderer. you can always get vray if you really miss it. 3. i can't say about coming from max because i havent really used it but i have heard from a lot of people who have switched to houdini from max that they love it. i think houdini is pretty different to your other DCCs. Maya, Max, Blender, C4D are all a bit similar in a way. Different features are nested in different menus, there are sort of different contexts for doing different tasks that feel kind of like separate programs. The nice thing with houdini is that its all procedural/node based in a really fun and friendly way and that logic is fairly consistent throughout the entire program. Once you learn the fundementals you will just be building off those and I think it helps to understand 3d in general a lot better. Hope you give it a shot. Check out the resources at houdininerd.com including the discord when you dive in, we are there to help!
@@chr1st0pher amazing response thank you... I'll hop into the discord now and take the houdini trial this coming week... Excited to start a new journey, thanks man!!
interesting, but makes sense as gpu things tend to be less stable and more dependent on specific hardware and drivers and such. I might recommend trying to update to your latest drivers and see if it makes a difference.
