Відео

@@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

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.

@@chr1st0pher It spits out Alembic and does so superfast. So getting a cache into Houdini is a two click operation.

i think its a "logitech g413 silver".

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.

@@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)

@@theshadow6273 this one is an a5000 which I believe should be a little shower than a 3090

Yep, flip is still unbeatable for high quality fluid stuff, but for quick grains and fluid this is a game changer!

i dont really, but i usually use the flip dop source. it's pretty forgiving. if you have higher particle sep on your source than your sim, flip will just handle it. if you have reseeding on it will remove points. if you have it off it will still keep all those points. i definitely would recommend using the flip dop source most of the time, play with reseeding on / off if you are adding extra particles with a scatter or somethign to see if it helps. you could always increase the particles per voxel or bandwidth on the reseeding tab.

@@zayjin3894 it should work with a daz character as long as you’re importing and setting things up properly. There are some gotchas, I tried bringing in a mixamo fbx and because the joints were named mixamo:hips for example apex didn’t like the : character so I had to get rid of it and change the names on the joints and skinning. Besides that though apex just needs you to be bringing in the character geo with bonecapture attribs that match the joints, skeleton, and the guide skeleton as I showed here. I might test and see if your rig is working in kinefx with a bone deform. If it works there and doesn’t have the namespace issue with the : symbol it should work in apex

@@chr1st0pher So im trying to solve this issue for like 5 hours now but i just cant seem to figure out whats the problem. I followed your tutorial step by step several times now ( except the blendshape part ). The joints dont have any : in their name and i think i import the character correctly ( with the fbx character import node) Bonedeform also works everything fine. When i connect the packfolder into the APEX autorig component node and choose fktransform for example the circles to move the skeleton dont even show up, only the skeleton outline. When i try it with any of the test houdini characters everything works fine...

@@zayjin3894 just tried this with a daz fbx i had lying around. the issue i ran into was that the transform scale was all screwed up for the bones. i fixed this with a attribtransformextract node and a attribtransformcompute node. i set the extract to "crack transform" decomposition and to run over the transform attribute. then i checked off the boxes for it to output the rotation and scale. next in the compute node i set it to run over the transform attribute and i checked on rotation. can share the file on discord if you join the houdininerd.com discord.

just posted the file on the houdini-character channel of the houdininerd.com discord for you :)

@@chr1st0pher Thank you sooo much! I would've never figured out this issue myself. Apex is still so confusing for me tho. I still have issues setting up ik's but i try to solve this tomorrow. Again thank you for helping me.

that's a great question and I'm not sure honestly what the best / intended workflow is, but I would imagine the way you could do it right now is to instead of attaching the hair, attach the guides, and then invoke those after all your animation and vellum sim + use them to deform the hair. you could probably also include the hair as a separate .shp in the apex rig so it's included with the rig itself if you want it to be more portable, and then maybe set up an hda to handle all the vellum + deform stuff in sops. you could also always deform it at rendertime using the hair procedural for extra efficiency.

i just made a tutorial for how to do face mocap stuff on my patreon using the fbx files you can get from faceapp, but in terms of getting live mocap over im not sure what the best solution is. there's a mocapstream node that has some options that might suit your needs?

@@chr1st0pher I just bought your patreon after your reply, I am going to try your method thanks!

where am i rn

bread man!!!!!!!!!!!

It’s weird but it’s on the geometry object at object level, there’s a setting on the render tab called “shade open curves in viewport” that you need to turn on

@@chr1st0pher Thanks