Debugging Hip file size
3826 4 1- MathieuLeclaire
- Member
- 79 posts
- Joined: Feb. 2008
- Offline
- mrCatfish
- Member
- 731 posts
- Joined: Dec. 2006
- Offline
You can try hexpand [www.sidefx.com] to expand the hipfile into a regular file structure on disc and then use normal shell tools to sort by size.
Sean Lewkiw
CG Supervisor
Machine FX - Cinesite MTL
CG Supervisor
Machine FX - Cinesite MTL
- martin-egger
- Member
- 30 posts
- Joined: May 2017
- Offline
I've found hexpand in the HFS, yet I have no idea how to actually use that. I'm on windows, and the various standalone .exes I can use, but hexpand is one of those without a file extension. Are those tools limited to linux only?
Thanks in advance,
Martin
Thanks in advance,
Martin
- Martin Egger
Student at Filmakademie BW
& Freelance FX TD
Student at Filmakademie BW
& Freelance FX TD
- mrCatfish
- Member
- 731 posts
- Joined: Dec. 2006
- Offline
Before you go to hexpand, yes, look for stash nodes. A quick way of doing this is open a textport (Alt Shift t) and type
This will show you where all the stash nodes are.
You can also lock nodes, which are not as easy to find. To track these down, again in the textport:
… then in the directory where you launched Houdini, there will be a text file that describes your scene. Now do a simple find for “-l on” which is “hard lock”. These nodes can be massive too.
If you haven't found anything, you can again, through the textport, rebuild the scene from scratch as if you laid down every node individually. Just open the textport in a blank houdini, and source the debug.txt file you created earlier. This is a quick and easy way to rebuild corrupt files.
Still no joy? You could try hexpand through (you guessed it), the texport (cuz I have no idea about Windoze):
… although it does not seem to work on .hipnc files which is what I have to test on.
Sean
opfind -t stash
This will show you where all the stash nodes are.
You can also lock nodes, which are not as easy to find. To track these down, again in the textport:
opcf / ; opscript -b -r -s * > ./debug.txt
… then in the directory where you launched Houdini, there will be a text file that describes your scene. Now do a simple find for “-l on” which is “hard lock”. These nodes can be massive too.
If you haven't found anything, you can again, through the textport, rebuild the scene from scratch as if you laid down every node individually. Just open the textport in a blank houdini, and source the debug.txt file you created earlier. This is a quick and easy way to rebuild corrupt files.
./debug.txt
Still no joy? You could try hexpand through (you guessed it), the texport (cuz I have no idea about Windoze):
system("hexpand /path/to/hipfile.hip")
… although it does not seem to work on .hipnc files which is what I have to test on.
Sean
Edited by mrCatfish - Oct. 22, 2020 16:28:39
Sean Lewkiw
CG Supervisor
Machine FX - Cinesite MTL
CG Supervisor
Machine FX - Cinesite MTL
- megger
- Member
- 5 posts
- Joined: March 2020
- Offline
-
- Quick Links