Crash at end of voxelization

Crash at end of voxelization#364527

By hatts - Fri Jan 25, 2013 4:32 pm

- Fri Jan 25, 2013 4:32 pm #364527

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

Matthew Spencer | http://www.mspncr.com

Re: Crash at end of voxelization#364528

By JDHill - Fri Jan 25, 2013 4:41 pm

- Fri Jan 25, 2013 4:41 pm #364528

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?

Next Limit Team

Re: Crash at end of voxelization#364534

By hatts - Fri Jan 25, 2013 6:49 pm

- Fri Jan 25, 2013 6:49 pm #364534

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...

Matthew Spencer | http://www.mspncr.com

Re: Crash at end of voxelization#364535

By JDHill - Fri Jan 25, 2013 7:03 pm

- Fri Jan 25, 2013 7:03 pm #364535

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.