Відео

Kind of. Not exactly the copy stamp we had before. Theres a lot to Houdini. No one will be able to keep up with everything

If you're scattering points on a grid we covered that earlier on in this series. I believe that was in the Bringing SOPs into COPs video. If you are doing it on a uv'd mesh that's a little bit more complex and doesn't have a one size fits all solution if you are wanting to stay in COPs.

@@InsideTheMindSpace ah yeah. But thats when you use real geo as texture input. So 2D cop nodes as a source for seamless textures isnt as easy as substance designer?

No you can still do it. Just in this case because we are using points scattered onto the geometry as a source for our copying all inside cops it's not necessarily the easiest thing to approach. You can get seamless textures relatively easy with noises and other things which I will be covering. Just because of how this method works it will not necessarily be the easiest thing to accomplish

Its difficult to explain in text format. Maybe I'll explain in a separate video why it doesn't work and how to approach getting seamless copys

@@InsideTheMindSpace ah phew. Was almost worried making seamless textures in general was cumbersome. Looking forward to the next one. 😁

Check to make sure your viewport isn't locked maybe. Also if you are on Mac apparently cops doesn't work on Mac. Otherwise I'm not sure.

@@InsideTheMindSpace Yep. It's a Mac issue. No problem on my PC. Thank you!

No image really ever requires uniform sampling. Adaptive sampling just allows the engine to determine where samples are and are not needed. It can be valuable to use in every render

@@InsideTheMindSpace that makes total sense!

select recipe, Edit button

The display options should be all you need to change. It might be a bug. I haven't played with those settings although I also do not like the very bright white wireframe

The uv nodes actually aren't too bad in my opinion. Traditional modeling options definitely need a rework in my opinion.

I'm currently building a Modo-like destructive modeling node using Python Viewer States.

well there is @ModelerHoudini :)

Oh yeah. I totally forgot about this. Definitely something cool as well thats super useful. Thanks for pointing that out

you could do that even before, just store the positions to temporary attribute (like rest), set point positions based on your attribute you want to clip by (ie. in wrangle set @P=(@myattrib,0,0); ) then clip, and restore position from the temporary attribute you created before .. whats amazing in houdini is that when the clip creates new points, the stored position attribute is correctly interpolated on to the new points.. i mean this technique is bit redundant now for clipping based on attribute, but is always nice to know these tricks:)

Yeah it was possible but it was a little bit of a pain to do and not something that was readily apparent. This makes it a lot easier and less hacky

Very true. I hope they build on it more still and get something similar to zbrush with dynamic remesh and such. It would be awesome to be able to sculpt with more detail on meshes.

It’s one of the top 3 features I missed a lot when I switched from C4D. Love it!

​@InsideTheMindSpace would love to not have to open zbrush as wonderful as it is. The UI switch up from Houdini just drives me bananas. Love your channel.

Not sure. I haven't tried to replicate it but it also doesn't happen every time

I'm sure that's possible. I haven't really messed with PDG though so I would have to look into it.

@@InsideTheMindSpace that would be awesome .. thank you so much

Shouldn't be. Make sure your display flags are set correctly. It's still in beta so there are some issues

You can create dissipation with this method as well. Just multiply your volume by a value less than 1. I tried some other methods for creating a wetmap solver and there were some issues I ran into. Best of luck to you though

​@@InsideTheMindSpace Thanks for the reply. I got my setup working. I added the ability to control at what age dissipation will begin, because I wanted it to be "wet" for like 30 frames before starting to dissipate. And if the voxel becomes "wet" again that resets the 30 frame window. I did notice some odd results if there are lots of seams on the uvs. I tried using smooth fill and extrapolate boundaries, that seemed to help.

I dont remember for sure as I've switched hardware but I think I had a ryzen 3950x and a 3090. If the the 3090s weren't out at the time it would have been a 2080 super.

I'm not sure if it was intended to be that way or not. The documentation makes it seem like it was intended as it reads something to the effect of xpu to match cpu for that specific setting.

@@InsideTheMindSpace SideFX will let you know in response to a submitted bug report if it was an oversight or not (my bad if you were already aware of this). Still worth submitting in this instance.

@@InsideTheMindSpace Be sure to send a bug report to support

​@@InsideTheMindSpace Seems like they've just fixed it in today's build, 20.5.326 !

Good to know. Thank you for the update! I'll take a look

Happy to help!

Whatever you can think of. You can use them for transition effects like shown. They are used for making materials seem wet when water splashes around over dry objects by controlling roughness.

Thats unfortunate. It is still in beta so I would guess that it will get better with time.

@@InsideTheMindSpace I hope so, the Preview Material node doesn’t show any change when you connect smth to the height channel. I have to render it in karma to see the effect

@@junechevalier ahhhh god damn I've been searching all over as to why preview material isn't doing anything for me - this is why.

Thats a good explanation. Thank you. I refreshed my memory after recording this and you are correct. The ampersand specifies that the layer is write able. I like the extra information you provided as well.

@@InsideTheMindSpace No problem :) I'm an escaping programmer... I used to have to know this stuff for work :)

Thank you for your support