Davide Mella
wlvl_r
About Me
Connect
LOCATION
Not Specified
ウェブサイト
Houdini Engine
Availability
Not Specified
Recent Forum Posts
SIDEFXLABS - VHDA Workflows 2024年12月4日6:27
Hello!
I have a vhda.config file in my preference folder, with the defaults I need ( suffix, user, version, hda location etc )
Works perfectly for right click > Create Digital Asset
Does not work for right click > Digital Asset > Save Copy As
when trying to create a new digital asset from an existing one
This is probably meant to be, since one assumes the copy to be consistent with the original.
In my case I prefer to always stick to our convention ( written in the vhda.config ) for any new hda.
Is there a way to change the behavoiur for the Save Copy As? Where should I dive and modify?
Thanks
EDIT: I found where it lies.
C:\Program Files\Houdini20.5\houdini\OPmenu.xml
right click node menu
C:\Program Files\Houdini20.5\houdini\python3.11libs\assettools.py
line 3245 is where the Save As function is
Maybe the easiest solution is to just make a custom Create Digital Asset option always visible when right clicking..
I have a vhda.config file in my preference folder, with the defaults I need ( suffix, user, version, hda location etc )
Works perfectly for right click > Create Digital Asset
Does not work for right click > Digital Asset > Save Copy As
when trying to create a new digital asset from an existing one
This is probably meant to be, since one assumes the copy to be consistent with the original.
In my case I prefer to always stick to our convention ( written in the vhda.config ) for any new hda.
Is there a way to change the behavoiur for the Save Copy As? Where should I dive and modify?
Thanks
EDIT: I found where it lies.
C:\Program Files\Houdini20.5\houdini\OPmenu.xml
right click node menu
C:\Program Files\Houdini20.5\houdini\python3.11libs\assettools.py
line 3245 is where the Save As function is
Maybe the easiest solution is to just make a custom Create Digital Asset option always visible when right clicking..
Can't Stop the DOP (cook) 2024年10月10日12:54
Is there a flag that will freeze this, or do I have to resort to creating an initial .sim file?I don't think such a flag exist, you could use the first frame of .sim file as the start, but this workflow could become cumbersome quickly and I'm not sure you would get speed benefit ( needs to be tested on your specific setup )
node cooking on selection depends on a few things:
-if you have the geometry spreadsheet open it will cook any node selected to give you the data
-if you have a scene view open , you have to make sure "Show Display Operator" is on, and not "Show Current Operator" , which is default ( screenshot attached )
Bear in mind that when Show Current Operator is needed for viewport interactive tool such as paint etc
Houdini ignoring node state and cooking everything 2024年4月11日11:20
I had a similar issue.
When running a dopnet live the sim is running fine.
When caching that sim, some of the upstream nodes where unnecessarily cooking every frame ( even if time independent )
The problem with this bug is that is hard to reproduce because the same network sometimes bugs sometimes not. ( ie. after relaunching Houdini)
I had no plugin installed locally just pref files that gets created automatically.
Deleting the folder content solved the issue.
I wonder if anyone from the staff could give us a pointer on what kind of file could cause this instability?
H 20.0.653 Windows
When running a dopnet live the sim is running fine.
When caching that sim, some of the upstream nodes where unnecessarily cooking every frame ( even if time independent )
The problem with this bug is that is hard to reproduce because the same network sometimes bugs sometimes not. ( ie. after relaunching Houdini)
I had no plugin installed locally just pref files that gets created automatically.
Deleting the folder content solved the issue.
I wonder if anyone from the staff could give us a pointer on what kind of file could cause this instability?
H 20.0.653 Windows