Staszek Ciesielski

seelan
Does the long prefab update also happen if you make a change directly to the prefab and apply it (i.e. not going through Houdini Engine)?

@seelan Did you tried / manage to recreate the issue?

So far I hacked a walkaround by replacing the prefab placing nodes in HDA definition with simple dummy mesh that's packed and copied to points. After baking the HDA in Unity I run custom script that replaces each dummy with chosen prefab. Although I'd still appreciate some update on this.

STC

Hi, thanks for quick response.

If I make a direct change to “small” prefab that is embedded inside another major prefabs they will also update once I apply the changes - this is standard behavior.
To clarify my HDAs are not making any changes to the small prefab. They just place it in locations of the points generated by the Houdini Engine.

STC

Piggy backing on the main question.
I hava a HDA that does exactly that: it takes path to Unity prefab stored in unity_instance attribute and among other things places this prefab along curve path.

Our workflow is that at the end all content created with the HDA is baked into objects (not prefabs). These objects are grouped together under parent Unity Game Object and all this is saved as a major prefab.
We do this to allow multiple team members to work on the same Unity scene at the same time.

I noticed some strange behavior:
Every time I recook or rebake HDA that uses some Unity prefab (let's call it prefab A) - it will cause Unity to update every major prefab where said prefab A is also used. The more scenes in the project the longer it takes to go through all the major prefabs. I am writing this post while waiting for Unity to finish recooking 20 HDAs due to some changes in the HDA definition. Every HDA causes series of “Hold on…” pop ups:


I'd appreciate some information on why it might be happening and how to get rid of it.
Cheers,
STC