Damien Pernuit

Hey,

Have you tried refining the proxy mesh output ? (right click > refine)
By default, the plugin uses Houdini Proxy meshes (that's why there's a Houdini logo on top of Flippy).
They are much faster to create than StaticMeshes, but wont come with LODs or colliders.

The idea is that they will give you faster visual feedback when tweaking the parameters - and can easily be refined when you're satisfied with the results.
Proxies can be disabled either in the plugin settings, or in your HDA's detail panel.

Hi,

Please see https://www.sidefx.com/docs/houdini/unreal/attributes.html#generic

Generic attributes can be applied to the HDA itself, if the attribute is set as a detail attribute.

To get the list of attributes that can apply to a given class, type the following CMD in Unreal:

Houdini.DumpGenericAttribute XXX

XXX being the name of the class, in your case, you'll type

Houdini.DumpGenericAttribute UHoudiniAssetComponent

Which will list all properties that can be modified on a HoudiniAssetComponent, you'll be interested in:
unreal_uproperty_bOutputless : bOutputless (Outputless) - UE TYPE: BoolProperty - H TYPE: int.

so to automatically change the "Do Not Generate Outputs" toggle, you want to create the detail attribute "unreal_uproperty_bOutputless" and set its value to 1.

Well, HiddenInGame will be a special case - as it's one of the properties that the plugin controls by default,
if the mesh is visible/invisible/tempalted etc.. in Houdini will control that property - it's also one that we change when switching between proxy / refined meshes etc..

You're basically applying an extra layer by manually overriding this property on top of it - and this could either apply to the whole actor - or individual components...

Your example is also not the best - if you have multiple clearly distinct outputs - why pack and merge everything into a single output instead of using multiple outputs? The plugin does its best to sort that out - but Houdini Engine still see all of this as a single output.

As mentioned above - some attribute working before/after pack is expected
as some properties exist on the static mesh - other on the component/actor - if you want to modify mesh properties place the attribute before the pack - if you want to modify comp/actor properties, place it after.

The spline being separate when baking as one actor is likely to be a bug.