Atom Posted March 11, 2017 Share Posted March 11, 2017 Hi All, This is the first time I have seen Houdini do this, but my scene size keeps going up every time I save. My scene originally weighed in around 2Mb-4Mb as a tracking scene. Now it is up to 198Mb. I close and reopen the scene and save it again and it has jumped up to 768Mb. Has anyone else experienced this kind of large growth in scene file size? Quote Link to comment Share on other sites More sharing options...
Netvudu Posted March 11, 2017 Share Posted March 11, 2017 umm....I remember this bug hitting Houdini with older versions. Maybe it has resurfaced? Quote Link to comment Share on other sites More sharing options...
goldleaf Posted March 11, 2017 Share Posted March 11, 2017 Definitely sounds like a bug, though I haven't hit it; I'd submit it pronto. Quote Link to comment Share on other sites More sharing options...
acey195 Posted March 11, 2017 Share Posted March 11, 2017 In old versions (earlier versions of H13, I think) it happened with mantra nodes, removing those and then recreating them got the file size back to normal, for a time at least :P. Quote Link to comment Share on other sites More sharing options...
Atom Posted March 12, 2017 Author Share Posted March 12, 2017 (edited) I have submitted this one. The odd thing is that when I ZIP down the HIP file for submission, it becomes very small in file size. So I don't think the bloat is real data. It is definitely related to the Trackers generated by the SynthEyes hScript.cmd. When I delete all my trackers and save, the file starts to behave normally again. But without trackers I have no scene... The odd thing is that I worked with the Trackers for several iterations before this bloat began. Actually I think it worked fine using the production build H16.504 but when I moved up to the daily build H16.540 (because viewport sluggishness has been fixed) I think that is when problems occurred. I typically prefer production builds but the viewport lag on the H16 release is so slow that I had to upgrade. Edited March 12, 2017 by Atom Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted March 13, 2017 Share Posted March 13, 2017 As an alternative problem with same bloat issue. If the tracker program is placing nulls for it's tracks, an increasingly large amount of nodes can make the file size jump extremely large. The same happens when large fbx or alembic trees are imported into the scene, especially if it keeps running tracker say on load, or you keep adding fbx/alembics to a scene. If you dump the tracks to a native bgeo cache, and remove the nodes the scene file would shrink. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.