uv's and st's are very similar. It's not a rename. uv's are texture coordinates, and st's are (parametric) surface coordinates. essentially the same when it comes to simple primitives.
GAWD DAMN, haven't watched the full video but I know is gonna be amazing. I was just starting to want to learn more about USD too and lo and behold this gets uploaded haha. Can't wait to watch it!
This is great and well worth it! This master class really clicked with me, I think I will be returning to it alot as my go to karma tutorial as its full of tips and helpful tricks. I think I can accept Karma (and USD) into my life now that I feel way less confused. Anyway, this is really awesome, a great piece of education, comprehensive and pretty much perfect. Great job , it's greatly appreciated and thank you.
Thank you so much. This is the first time someone explained the essence of USD in a really clear way without too much technical jargon. I now understand it much better and the purpose of USD.
Thankyou So Much for Giving Master Class You Explained Very Well I just Want You Keep Creating Tutorials For Us❤ I started My Houdini Journey With your Lectures And Tutorials I am So Glad That You are Creating More Tutorials. By the Way Love From India❤
So good, incredibly well explained and useful. Thank you so much! Also love the fader mode of the Light Linker, especially for ArchViz and controlling grouped lights.
How to create and use mtx Volume material in the new Houdini 20? They changed everything a little and now it’s impossible to create outside the container And In hip files of your examples, rendering smoke does not work in XPU mode
AHA! Thank you, I was having such trouble getting information that made sense on how to get packed primitives that I created in a Sop Create, to instance correctly on my points! You are a life-saver! Though I realise by skimming this video for the information I needed that I actually know nothing about Solaris or USDs, I'll have to come back :D
Awesome, I'm glad that you found it helpful! The funny thing is, I often come back to my own tutorials for reference, and this one is one of those, lol.
First of all, thank you for the excellent presentation. I have one question, sir: Is there any difference between Karma Volume VOP and MtlX Volume VOP?
Thanks a lot for this! Best tutorial on USD I've found so far. Do you think it's possible to render out single variants using their variant name as output file name (such as gumdrop.png, smarties.png etc.)?
Awesome stuff! I haven't been able to test this so far, but does this USD workflow in combination with materialX mean that if we set up our scenes correctly, we can have a seamless way to unreal for rendering? I heard Unreal did support materialx in some way. I started learning houdini like a year and a half ago. The most confusing part for me was "deciding" if i would go straight for LOPS instead of OBJ when starting something, as i wanted to use karma anyway. it felt like it didn't make sense, why these 2 completely overlapping workflows? But it slowly became a little more clear what the big power is of solaris. especially this video helps with that! But that still keeps me wondering if the OBJ level is getting more and more redundant and maybe even phased out/merged over time. anyway, the thing i really don't like about your video's is when they end, and i have to wait for the next one :) keep it up!
This tutorial looks very good, I only have one question, is it a good idea to do this tutorial instead of Karma "a beautiful game", what do you think? :)
Hi! Great teacher, great tutorial! I have a question thou. In the Component Builder chapter, when building our component builder for the gummy, the geo appears as a Scope primitive. Why it is not a Xform primitive? If I understood you correctly, geo is normaly Xform. Thank you
Hey! Good question. In this case, the geo is held in an xform because we won't move it directly. However, if you look at the component itself (the /ASSET primitive), it is an xform. As far as I can tell, this is because when moving the primitive, you would move the complete asset, and not what's inside of it. I may be wrong, but that's how I understand it. I hope that helps👌
No problem! I'd suggest not focusing on it too much. It's good to have a broad idea of what these things mean, but it isn't necessary to understand them perfectly.
question for USD export component builder section: Assuming we have a very complex asset variant that has multiple materials. The lookdev artist has set it all up in the assign material node. Then now it is ready to export the asset with the component builder. I assume the artist can copy and paste the material library over but what about the material assigns. Does he need to redo all of the material assigns to the component material node? or there has a portable way?
Cool, My question is what if I get file with LOP import camera, but need to render this in redshift inside houdini, I cant create DOF, if its a way to convert LOP import camera with animation to classic camera node to control redshift DOF ?
Hey! I don't think we'll be making a massive fluid sim tutorial any time soon, but there are a lot of great tutorials out there already. We will be covering FLIP soon and explaining how it works, we'll touch on ocean simulations as well.
bro you are best i can unreal eassly and i rewatch our videos again again to speed up my traininig process . I did't seen any tutorials on massive scale .they are but paid and not understandble . question 2;- did we have to create sperate sperate elements and to create massive vfx or all at a time ? thanks you brother for your reply @@NineBetween ❤
@@prraneth-skyop1374 Thanks for the great comment! When we create massive simulations, they are usually broken up into smaller simulations. For example, if you are creating a shot of a spaceship landing in the ocean, you only simulate the area around the impact. The rest of it is just a grid with an ocean spectrum for displacement. Then you add all of the secondary simulations such as white water, splashes and mist. Also, many large simulations are either wedged (many smaller simulations put together) or distributed (a big simulation which is cut into separate parts for simulating). I hope that helps! I'll try to create an Ocean series in the future.
Either is perfectly fine. It depends on how your scene is set up. If you'd like multiple stages, then the lopnet node will allow individual setups to be made. Hope that helps!
what if it was the other way around like someone sent me a USD scene containing multiple objects then I want to extract it to normal sops to work on it? how can I do this?
Hey! There's a USD import node at the SOP level, which imports a USD file and brings in a selected primitive. Alternatively, you can bring a USD file into LOPs and then use the LOP import node at the SOP level to bring that in.
@@NineBetween thank you this will help. but this way I think FBX is better option for bigger scenes with maybe 100 different objects that needs sim maybe. when I import the FBX it will split and arrange the objects into its own geo/sop without having to extract every object in the file manually by hand, right?
It turns out to be very stupid and pointless to create one asset with several variations of materials and geometries. Since in the layout node you cannot conveniently switch between variations. But you have to search in graph like a fool, right-click, and select the geometry and material. Couldn't it have been made more convenient?
That would be true if the Layout Node was the only node that uses variants. If you're manually importing your assets, you can choose from a variety of pre-made variations of that asset. That alone is powerful, but combine that with things like the instancer, and you can get a lot out of variants
Love this. clear and concise explanations throughout. Why do I get a console error every time that I try to paint instances? brushpanel.py:1047 AssetWorkingSetPanel.onEventCallback layout1 {'event_type': nodeEventType.SelectionChanged, 'layout_node': }
