Page 1 of 1
Crash at end of voxelization
Posted: Fri Jan 25, 2013 4:32 pm
by hatts
Maxwell seems to be crashing C4D at the end of voxelization under FIRE, only for one certain project.
Can anything be gleaned from the attached bug report?
https://dl.dropbox.com/u/2569505/net/_BugReport.txt
Re: Crash at end of voxelization
Posted: Fri Jan 25, 2013 4:41 pm
by JDHill
Not a lot from where I sit, it shows an unexpected problem occurring inside the SDK or engine code, but since you say it's related to a particular scene, would it be possible for you to let me have a copy of that (going by the bug report, it may be important to get the referenced textures too), to try and find a cause?
Re: Crash at end of voxelization
Posted: Fri Jan 25, 2013 6:49 pm
by hatts
After you said the magical word "textures" i just decided to delete MXMs I wasn't using from the scene, and that fixed it.
Unused materials interfering with FIRE...very curious...
Re: Crash at end of voxelization
Posted: Fri Jan 25, 2013 7:03 pm
by JDHill
Before saying it is curious, we would first need to define
unused.
Perhaps unused in Fire, but the plugin assumes a person wants the things in their scene to make it into MXS files, and for sake of consistency, it minimizes the differences between exporting for use in Fire or otherwise. It's been wished before for there to be an option to skip unused materials, and I see the reasoning behind that, but accomplishing it is actually not as simple as it might sound.
Re: Crash at end of voxelization
Posted: Fri Jan 25, 2013 7:19 pm
by hatts
Actually that is new information to me: I thought MXS exports skipped all unused materials and fully-hidden objects.
Thanks for the enlightenment
Re: Crash at end of voxelization
Posted: Fri Jan 25, 2013 7:26 pm
by JDHill
Since hiding an object may often be done for the purpose of reducing file size, the data in Cinema is indeed skipped in that case.