Aidan Ryan

I am running the Windows version and am having segmentation faults. I was getting errors on Objects/cam before that, so I'm sure it's a reference that was misnamed somewhere in the source.

Hello all, I have been trying to render a project for some time now, and have made the project three separate times and attempted to render it on both the production build of H15 and .305 to try to get it to work. I get error 139 (doesn't mean anything significant). After tinkering for the last day, I got an error to read that it was a segmentation fault. The error only shows up on a physically based render, as the other render engines freeze on the first frame. I am attaching my .hipnc file for you all to see. I had no issues like this on H14, and suppose I can roll back to 14 to get it to render.

Hey all, I am doing some rather complex renderings of an explosion in Houdini using Mantra, and have (since upgrading to version 395 and any later versions, specifically .440 and .442) had renders quit on me at 26, 70, and 86 frames in, depending on the complexity and settings of the render. Is it possible that my cache settings (I can't remember if I had any in version .335) didn't carry over, or is there a bug regarding Mantra, RAM allocation, or anything else? I have done renders exactly like the one I have been attempting over the last couple of days on my computer, and never had them just stop with no error messages until now. Please help!