I’m using the new 2.5 Blender Beta, but this file crashes the render.
I’m new to Blender so I’m not sure what it is doing it.
After some experimentation, I found that if you render all the layers except #2 it renders fine. Layer #2 is the one with the Photon Torpedo on it.
It does work in 2.49, but I’ve downloaded the latest 2.53 Beta and if you open the file and render, Blender crashes. You have to turn off layer 2 for it to render.
Are you saying it rendered for you in the new 2.53 Beta without out turning off layer 2?
Maybe I’m calling the layer by the wrong number, it’s the top row,second box.
It sure crashes every time if that layer is rendered with 2.53 Beta on my computer.
Well, the fact that it worked on your 2.53 Beta got me wondering…Hmmm…What could be different? Maybe you’re using the 32 bit version? So I downloaded it, and sure enough the file opens and renders fine even with the Photon Torpedo layer; However the 64 bit 2.53 Beta crashes every time.
Update: Well four months later and hundreds of bug fixes, this file still renders fine on the 32 bit build of Blender 2.55, but crashes the 64 bit build everytime. The problems lies on layer 2. If you turn off that layer, even the 64 bit build renders it, but turn in on and CRASH!
I tried to report this bug months ago, but I’m not sure if the bug report went through.
I removed the build modifier from the torpedoes and everything rendered fine in 2.54 64bit. With the modifier active, this would cause the crash every time. This seems to be the thing that is wrong. I would have tried running the build modifier on something else, but ran out of time. If someone else has used the modifier on something in recent builds and it has run fine, perhaps there is something that is wrong with the .blend and how the modifer is used or what it is used with.
I reported this to the bug list, and you are right ajm, it was the build modifier.
Apparently the way the build modifier was being used was causing particles to be emitted before there was any geometry to emit them from. There was a negative index value for an array that was causing a memory violation.