You'll need to make the curve node editable for it to show up (i.e. add to Editable nodes in Type Properties).

And you can make the curve editing snap to terrain by either use the terrain collider or the setting the layer of the terrain in the curve's collision section. Specifically, change the Draw Collision Type to Layer, then set the layer of the terrain as the value.
https://www.sidefx.com/docs/unity/_curves.html#Curves_ParametersUI [www.sidefx.com]

As of 16.5.483, attached scripts to output gameobjects will now be copied over when using duplicate asset. Note that keeping material overrides on cooking was also added in this latest build, so there was a bit of an output generation overhaul.

Check the changelogs for more info: https://www.sidefx.com/changelog/ [www.sidefx.com]

Just tested it and it's not working as intended. Most likely a bug with the plug-in, so I'll add to my list to look at.

So by Unity 2017, I believe you meant that you are using version 1 of the plugin, and by Unity 2018, you are using version 2. The new version 2 does not support splitting geometry by groups, except for LOD groups. If you want to split the output geometry, then create a subnet with multiple geometry nodes, then merge just the geometry you want for each geometry node (might have to do a delete on other groups).

Another way to do it for what you are trying to achieve is in the same geometry network, separate the geometry by group, make the nodes editable, then merge it back. When editing in Unity using the Edit Attribute Tools, you should be able to select the individual edit nodes. Note that the final output will be the merged geometry, not groups as separate meshes.

Version 1 did support group splitting but we decided to not support that in version 2 due to problems caused by it.

Yes, you're right that it doesn't carry over. I'll add to my list to implement it.

Available in today's build (16.5.475) is the option to use points instead of vertices.

Also added LOD Groups as well: https://www.sidefx.com/docs/unity/_meshes.html#Meshes_Output_LOD [www.sidefx.com]

Those errors lead me to believe that the plug-in might NOT have been installed properly (looks like everything is inside the Editor folder which is incorrect). Did you import the plug-in package via Assets->Import Package? Or perhaps accidentally moved the other folders into the Editor folder?

I just tested on Unity 2018.1f with H16.5.466 and its working correctly.

I understand your concern. I'll add an RFE to investigate the possibility of perhaps strictly using points, instead of vertices, or another similar method to reduce the overhead. This probably won't happen for a while though.

That Split Points by Vertex Attributes is only available in version 1 of the plugin. Version 2 will always split vertices. The decision for this was to reduce issues when marshaling attribute data back and forth between Houdini and Unity.

This was a bug on macOS with HOUDINI_INSTALL_PATH not being defined for Unity run-time, or in this case, when trying to build the project. Should be fixed in tomorrow's build.

We do ship version 1 of the plugin on Linux. Version 2 hasn't been added yet.

As for the distro, it will work on whatever Unity supports, though that looks to be just Ubuntu so far.
See Unity info here:
https://blogs.unity3d.com/2015/08/26/unity-comes-to-linux-experimental-build-now-available/ [blogs.unity3d.com]
https://forum.unity.com/threads/unity-on-linux-release-notes-and-known-issues.350256/page-2#post-3450822 [forum.unity.com]

I'll look to add version 2 to our Linux installer soon.

Sure. We can add an optimization section to the documentation.
https://www.sidefx.com/docs/unity/index.html [www.sidefx.com]

Use Unity 2017.3 or newer. Otherwise you'll need to split into different objects under a subnet with object merges.

I tried using the new texture but looks like the parameters aren't correct, or need the other generated files as well. Could you attach your entire project?

Attach your textures please.

Thanks for attaching the example. Looks like Unity is converting the texture from RGBA Half (16-bit per pixel) to RGBA 32-bit automatically when going from Standard PC build to UWP. The conversion is most likely losing the required data. Try re-exporting from the Vertex Animation Texture tool as TGA instead, with Export for Mobile turned on. Also make sure to set import settings such that power of 2 is none or disabled, wrap mode to repeat, filter mode to point, and compression to None.

Currently, the plugin will remove any objects without geometry as way to provide a clean output. So there is no way to just get empty GameObjects at the moment. What I recommend as a short term solution is to output a simple geometry for those null objects with a unity_tag detail attribute. Then in an Event callback in Unity, look for GameObjects with that tag and remove all their components.

I'll add a note to optionally allow empty GameObjects in the near future.

Could you attach a simplified version of your project with the problem and relevant files?

Try turning Export for Mobile option on in the vertex animation texture exporter tool.

The issues you are coming across leads me to believe that you are mixing version 1 and 2 of the plugin. I recommend you pick one and use that in your project, ideally version 2.

Assets/Plugins/HoudiniEngineUnity/Scenes/ParamModifierExample.unity only exists in version 2. Note that currently it is missing the Evergreen HDA which will be fixed in tomorrow's build.

Assets/scripts/HoudiniApiAssetAccessorExample.cs is only available in version 1, and does not work with version 2.

The warning you are getting about Substance support is harmless if you are not using Substance Designer materials. Unity is warning that support for importing Substance materials automatically is being deprecated in future versions of Unity. This will fixed be in the near future once Substance releases their own Unity plugin.

As for the last post about the shader warning, which project platform are you using in Unity? You can find this by going into to File -> Build Settings. Also, what graphics card are you using? It seems either the platform setting or your current graphics card does not support the shader. It could be as simple as changing the platform to the correct one, or changing the shader.