I would like to use specified TerrainData file in my terrain. And I have added “unity_hf_terraindata_file attribute” in my the generation network. (see settings below)
The issue is that although the specified TerrainData file has been created in output folder, the HDA instance still use default TerrainData. The specified TerrainData is never used when rebuild or recook.
Hmm this could be a bug due to Unity 2017.1 which uses the old terrain path. Could you try with Unity 2019.1? If its still a bug, please submit a bug report with an HDA. Thanks.
Working fine for me with Houdini 17.5.328 and Unity 2017.1.1f1.
Have you tried a fresh instance of your HDA (drag & drop another one into scene)?
Note that the plugin will still make a copy of the referenced TerrainData file into your working directory. It does not actually directly refer to the TerrainData file, but rather copy it at generation time. The reason is to keep the non-destructive workflow since the TerrainData will be modified during the terrain generation process.
seelan Working fine for me with Houdini 17.5.328 and Unity 2017.1.1f1.
Have you tried a fresh instance of your HDA (drag & drop another one into scene)?
Note that the plugin will still make a copy of the referenced TerrainData file into your working directory. It does not actually directly refer to the TerrainData file, but rather copy it at generation time. The reason is to keep the non-destructive workflow since the TerrainData will be modified during the terrain generation process.
Yes, I have tried a fresh instance. But it does not work for me. It seems that HDA create a new default TerrainData.asset first when it is instantiated. Then, when the terrain data asset paths is passed, the HDA instance only refresh the initial TerrainData.asset and copy the specified terrain data, but it does not update the reference to the copied terrain data asset when recook.
