Solaris nodes make hip-filesize big ?!

   1057   2   0
User Avatar
Member
29 posts
Joined: Oct. 2015
Offline
Hi all, im going to give this another try.. I have a lighting-hipfile which contains several solaris / lop networks, but as my lopnetworks grows so do the hipfile and it grows quickly..much more quickly than any regular houdini nodes it seems..until the point its getting difficult to handle/save. To give you an example if I delete 5 karma pyroshader materials, that would free up around 20Mb of the filesize, which to me seems to be alot, thinking about all the hundreds of different LOP nodes that is required to light a bunch of shots. Im not sure that extrapolating the nodes to the filesize even makes sense but thats what I see anyway.. So all in all, I just wonder if anyone else have this problem and/or solution/workaround?

cheers

edit: This might actually be related to the karma pyroshader node itself, as I had a few of these laying around.. Cleaned away the ones I didnt use and filesize went from around 500Mb to 150Mb.
Edited by timjan - Aug. 16, 2024 08:42:55
User Avatar
Member
9384 posts
Joined: July 2007
Offline
is your pyroshader unlocked by any chance? potentially with some internal HDAs also unlocked
that would store all the internal network description in the hip file rather than pointing to external HDA which can increase your file size a lot if such nodes contain many nodes each
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
29 posts
Joined: Oct. 2015
Offline
Yeah, that would explain it, will take an extra look but as far as I remember there was no "unlocked padlock" on the node itself.
  • Quick Links