Interesting. I remember that just using LoadAssetAtPath was not working in certain cases, hence the ImportAsset call before it. This was from my testing a couple of years ago, so perhaps they have improved it.

I suppose I can do a LoadAssetAtPath first, then fallback to ImportAsset then LoadAssetAtPath if it fails as well.

Yes, AssetDatabase.ImportAsset is needed for loading assets since that is Unity's catch all API for it.

I did make a change to make this faster though. In tomorrow's daily build (Houdini 18.0.531), it will now support instances with assets from the Resources directory, which makes for a faster loading time, and eliminate the need for updating the AssetDatabase.

To use this new feature, move your assets into the Resources directory, and specify the path as you would normally to them.

The Education downgrade has been fixed in Houdini 18.0.522 and newer.

As for SessionSync clearing the scene, it was intentionally done for the previous Houdini Engine Debugger. But we'll be looking at improving it in the near future.

There are a bunch of different ways to access an attribute through python / hython:

https://www.sidefx.com/docs/houdini/hom/hou/Attrib.html [www.sidefx.com]

Off the top of my head, get the geometry using something like the following: hou.Node(“/obj/geo/grid1”).geometry().findGlobalAttrib(“unity_input_mesh_name”)
Then check out the documentation on it: https://www.sidefx.com/docs/houdini/hom/hou/Geometry.html [www.sidefx.com]

Each attribute has a owner of type which is one of Vertex, Point, Primitive, or Detail. Check out the Attribute Create SOP node.

Add a TimeShift geometry node to end if your graph, and set the frame there.

The plugin does not support runtime, so you'd have to use it in Editor only.

No updates.

Nope, script callbacks are only done at end of cook.

If you use points, make sure all your attributes are using points as owner.

If you use vertices, make sure all your attributes are using vertex as owner. Otherwise, point attributes will get split into vertices.

If you are still having issues, please submit a bug with a sample HDA to support@sidefx.com

Currently there are no plans to support the new terrain holes yet for the Unity plugin.

Do you have Houdini installed? Does it running properly? Which license is it using? Please submit license diagnostic info to support@sidefx.com if you are still having issues. https://www.sidefx.com/faq/license-management/#faq357 [www.sidefx.com]

I've responded to your bug about this, but posting it here for others as well:

By design, HOUDINI_PACKAGE_DIR is only supported when set in the process environment before launching Houdini or HARS (i.e. HAPI server). It is not supported when specified via houdini.env. The reason is that the packages are processed before houdini.env, and are in fact, meant to replace houdini.env.

For now, the recommendation would be set HOUDINI_PACKAGE_DIR as an environment variable for your process. Then load packages dynamically, using the conditional expression mechanism specified here: https://www.sidefx.com/docs/houdini18.0/ref/plugins.html#package_path [www.sidefx.com]

Another option is to start the HARS server manually (instead of using HAPI_StartThriftNamedPipeServer or HAPI_StartThriftSocketServer) in a new process with the HOUDINI_PACKAGE_DIR environment variable set beforehand. Then connect to it with HAPI_CreateThriftNamedPipeSession or HAPI_CreateThriftSocketSession. So basically you have your own version of HAPI_StartThriftNamedPipeServer / HAPI_StartThriftSocketServer, where you can set up your own environment for it.

Hi, sorry for the delay. I will look into this very soon and get back to you. I have received your bug report as well.

You'll have to cook the asset if you want to see the update on the UI. That's how its designed as otherwise we can get into pretty bad state between the asset in Houdini and its representation in Unity.

When you call RequestCook with bUploadParameters set to true, it uploads the parm values, which triggers the button script. I wonder if it will trigger directly just by uploading the parm value, instead of calling RequestCook. You can test this by following code:


You might still have to cook later to use the HDA, but if you are just doing this through code, it might be okay.

Sorry guys, I should have responded before. We have updated the tutorial video and files for Houdini 18, and will be uploading them soon. That should fix most of the issues you are coming across. Will update this thread when its in.

In the mean time, I've attached the updated section 6 files that work with Houdini 18.0.460 (and newer) to this post. Let me know otherwise.

A special treat for you all with the recent Houdini 18 Production build which has lots of goodies, but specifically the new SessionSync feature for Unity plugin (which replaces Houdini Engine Debugger): https://www.sidefx.com/community/houdini-18-backport/#viewport [www.sidefx.com]

https://www.sidefx.com/docs/unity/_session_sync.html [www.sidefx.com]

Give it a spin and let me know how it goes.

Sure, submit a bug with necessary files to support@sidefx.com. Thank you.

You have to make the mesh data readable via whatever generated it, so in this case, it would be ProBuilder.

Maybe look for something like this in the mesh import settings:
https://answers.unity.com/storage/attachments/149976-capture.png [answers.unity.com]