Houdini 16 engine doesn't seem to be working when you have inputs in your asset

   9024   18   3
User Avatar
Member
28 posts
Joined: 11月 2013
Offline
Hi,

When I load my OTL asset in unity it doesn't show any option to connect geometry or a curve in unity.
In the old version of the engine I did get the inputs on the asset where I could choose the geometry or curve in the unity scene.
Does somebody has the same problem?
User Avatar
Member
402 posts
Joined: 3月 2013
Offline
Which version of Houdini/Unity are you using?
User Avatar
Member
28 posts
Joined: 11月 2013
Offline
I should have mentioned that I am now using the houdini 16 engine in unity now and I was comparing it to the houdini 15.5 engine.
User Avatar
Member
402 posts
Joined: 3月 2013
Offline
Ok, then this sounds like a bug in H16 Unity plugin. Can you submit a bug report with an example asset to support@sidefx.com and I'll try to fix asap.

That said, in the H16 Unity plugin, operator path parameters are now in the main list of asset parameters. They are no longer in a separate “inputs” section of the Houdini asset Inspector tab.
User Avatar
Member
11 posts
Joined: 4月 2010
Offline
i think i have similar problem. i draw a curve with houdini engine 16 in unity , i added this curve to curve decorator path. And i added a prefab to instance_object.

But houdini engine creating objects only to 0,0,0 point over and over. I added screenshot. I hope it helps to fix bug , thanks

Attachments:
curvedecorator.jpg (405.7 KB)

User Avatar
Member
4 posts
Joined: 9月 2015
Offline
I am having a similar problem. The curve decorator will not follow the path regardless of what I try. I have watched the videos and read the documentation but nothing works. Unity 5.5 and Houdini 16.

Attachments:
Capture_3.JPG (196.6 KB)

User Avatar
Member
402 posts
Joined: 3月 2013
Offline
This should actually be fixed in the latest daily builds of 16.0. I forgot to update this thread. My bad.
User Avatar
Member
21 posts
Joined: 4月 2016
Offline
damian
This should actually be fixed in the latest daily builds of 16.0. I forgot to update this thread. My bad.
Hi!

This problem seems to presist in build 568
User Avatar
Member
2 posts
Joined: 4月 2017
Offline
Yes!!!!! I met the same problem.
Input under OTLs(script) is missing.. Some code might be forgotten to include in the released version…
Edited by shixin - 2017年4月13日 06:27:12
User Avatar
Member
21 posts
Joined: 9月 2013
Offline
We are investigating this problem, and will update as soon as we have more information.
User Avatar
Member
20 posts
Joined: 5月 2016
Offline
Ken Xu
We are investigating this problem, and will update as soon as we have more information.
News??
This issue pretty much renders Houdini 16 digital assets useless in unity
Edited by marvalgames - 2017年4月27日 14:21:40
User Avatar
スタッフ
553 posts
Joined: 9月 2016
Offline
Hi,

This issue has been fixed and will be available on tomorrow's daily build (16.0.592).

To clear things up, there was actually two regressions:
- with object path parameter inputs, this was fixed by Damian a month ago (in 16.0.543)
- with “standard” sop/inputs, this one will be fixed in 16.0.592.
User Avatar
Member
20 posts
Joined: 5月 2016
Offline
Thanks.
It shows Inputs label but when expanded they are still empty.

No editable nodes show up.
Edited by marvalgames - 2017年4月28日 13:30:15
User Avatar
スタッフ
553 posts
Joined: 9月 2016
Offline
Hi,

Editable nodes (and painting) should be fixed in the latest Houdini daily (version 16.0.596).

For the inputs, if your plugin is updated to 16.0.592, they should be working.
How did you set them up? Are they SOP inputs or object path parameters?

Please send me your hda and I'll have a look at its issue.
User Avatar
Member
28 posts
Joined: 11月 2013
Offline
I switched to using operator path parameters instead of using the inputs of my assets. This works well, but before when I could use the inputs of the asset instead of the operator parameter and I used a curve in the input of the asset in unity, the asset would update realtime when I changed the curve. Is it possible to get this behavior with using the operator path parameter?
User Avatar
スタッフ
553 posts
Joined: 9月 2016
Offline
Hi,

Yes, it seems that curves connected to object path inputs were not triggering a recook.
This bug will be fixed in tomorrow's daily build (16.0.604)
User Avatar
Member
28 posts
Joined: 11月 2013
Offline
I just tried it with version 603, but doesn't work.
Should I be a little bit more patient and wait for the next build or is there something I need to check or change to make this work?
User Avatar
スタッフ
553 posts
Joined: 9月 2016
Offline
Yes, as I committed the fix yesterday, it's not in 16.0.603.

604 is available in the daily builds now, and will have the fix.
User Avatar
Member
28 posts
Joined: 11月 2013
Offline
Great thanks! it works now.
  • Quick Links