Hi, I've also been trying to get this to work as a way to have a minimum of effort in Unreal and here are some of the gotchas I bumped into.

First I couldn't make an USD with Unreal materials and MaterialX work at the same time, so it seems you need to decide which one you want to use. Changing the USD Stage Editor > Options > Render Context changes which material kind you'll see (click the bulletpoint instead of the text if you want the menu to continue open).


--Unreal Materials
I got the unrealMaterial attribute working, just make sure it's not named as primvars:unrealMaterial, and it's not an Array like it will be if you set it as polygons attribute. You can simply set it in an Attribute Wrangle LOP, or if using SOP Create LOP you can put it in the USD Custom Attributes parameter so it avoids the primvar: prefix. It can be set to subsets.

The path to the Unreal material can either have the Type bits before /Game/ like this "/Script/Engine.Material'/Game/StarterContent/Materials/M_Basic_Floor.M_Basic_Floor'" or shorter like '/Game/StarterContent/Materials/M_Basic_Floor.M_Basic_Floor', it doesn't seem to matter.


--MaterialX
So first thing is that the materials shouldn't come inside of the USD but the .mtlx files referenced in it. So in your USD ROP make sure in your Save Style you are "Preserving References". Flattening the Stage will prevent the materialX's from working in Unreal.

I haven't figured out if there's a way of using relative paths, so I just didn't use any Houdini variables like $HIP and made sure all my paths were absolute.

If you authored your mtlx in Houdini exporting it from a Mtlx Surface Material node works for me, when exporting from Mtlx Standard Surface or Collect nodes it doesn't.


--
So because of having to decide which Render Context to work with, it seems to me that if it's not important for you to have your materials set in Houdini, you should simply set the unrealMaterial primvar and have all your materials in Unreal, even your MaterialXs, as you can import them separately from your USD. This way you can mix them with Bridge's surfaces easily, for intance.

USD Preview Materials also work out of the box but for some reason sometimes the BaseColorScaleTranslation color come with weird values in the alpha that I need to reset for the textures not to be all stretched out.

As a side note, lights and cameras were imported nicely on first try, with even correct area lights colour/sizes and focus length. Also, transform animations and point deformations come for free, so the whole process is looking promising.

I attached a zip with my HIP, USD, MTLX and texture files for you to play with. Just check the paths as they'll be absolute, and here's a preview of Houdini next to Unreal:

Cheers

So, one dirty easy way you can do this is simply use the File SOP set to write *_$F.fbx and play your frame range.

It's missing all the FBX options but it did do the job for me, as I need to import it as "geometry cache" in an old software.

I just wish the ROP FBX Output frame range would work, and I also couldn't make TOPs export this quickly. This dirty method above is much much quicker for my case.

I get your point, yeah it's not so straightforward.

One way I managed to get it working here is to delete the root and the mid joints before the rig pose, so only use the tip for the FullBodyIK. If you rotate the joint you get your twist effect. It's not as predictable but maybe it works for you.

Cheers

Any reasons on why not to use the FullBodyIK? It worked here on a test similar to this reference video.

I generally go to the Houdini installation and delete 3DSceneColors.dark from there, since I prefer my own gradient scheme.

It would be great to know how to add more colour options to the Background dropdown.

There's an ACES discord channel with good explanations on what it is and how to set it up on several apps: https://discord.gg/bFMU3CX [discord.gg]

I never understood this as well.

https://vimeo.com/225159293 [vimeo.com]

Hi Andi

I'm just a beginner myself, but I'll try to share my insight.

in SOPs, a Point/Primitive/Vertex VOP is just an Attribute VOP with the Run Over parameter already adjusted for the type you want to change. it's just a shortcut.

other than that VOPs are going to behave a little different depending on the context, like if you put down a Volume VOP you gonna get density attribute to work with out of the box.

in DOPs I'm not too sure what the differences are, but from their name - Geometry VOP, Gas Field VOP, POP VOP, VOP Force - you can have an idea, and all of these work on the Dynamics Context, so considering the previous frame, simulation time, relationships, etc

I agree it's a bit confusing.

Hi all

so, on my long journey to learn Houdini I quite too often stumble into things like “why wouldn't this node connect to this one?”, and “why is it showing orange?”, “which different types of these are there?” and so.

for this I started to dig what different colors and parameters are there, I came up with these guide images. posting here because I haven't seen any mentions on the docs and I think it might help someone.

if you know of any of these to be wrong of incomplete, I'd be glad to correct these.

cheers

I also got confused on this but eventually found the new panel.

Shouldn't it have a Quadruped preset there as well? the docs puts it as a new feature..