Page MenuHome

render crash
Closed, InvalidPublic

Description

System Information
Operating system and graphics card

Blender Version
Broken: (All)
Worked: (None)

Exact steps for others to reproduce the error
open this file, try to render - we will have crush(render will stop)

Details

Type
Bug

Event Timeline

Alexey (Inwader77) updated the task description. (Show Details)
Alexey (Inwader77) raised the priority of this task from to Needs Triage.
Alexey (Inwader77) set Type to Bug.
Campbell Barton (campbellbarton) triaged this task as Incomplete priority.EditedFeb 4 2016, 5:07 AM

At what percentage does the render crash? And what kind of crash to you get?

Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes).

Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far.

Also, please include information (os, blender version etc...)

Alexey (Inwader77) added a comment.EditedFeb 4 2016, 10:52 AM

At what percentage does the render crash? And what kind of crash to you get?

Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes).

Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far.

Also, please include information (os, blender version etc...)

this bug is active for all versions, include last version 50a19cc.
i don't know how to repeat it, if i was change anything in 3D view - render maybe properly.
if we switch off ray tracing - working properly, all other - not important. this scene is very simple.




System Information
windows7 64
ASUS ATI Radeon HD6870

Blender Version
Broken: (All)
Worked: (None)

Brecht Van Lommel (brecht) claimed this task.

To be clear, does Blender actually crash? Or does it hang and become unresponsive? Or is the render just really slow, but you can still cancel it?

From your last comment it seems it's just rendering really slow. The reason for that is that the "Substract" material has Depth set to 100 under Mirror, which Blender Internal just can't render efficiently. Just lower it to get render time under control again.

Blender Internal would need rendering algorithms like probabilistic splitting and Russian roulette to fix that, precisely the kind of things the Cycles shading system was designed for.

Depht is 2 only, not equal 100. this is hang and become unresponsive. i was set depth zero - i have this bug again.

The "Substract" material on the floor has depth 100. The way the renderer works this means it will render up to a 100 bounces after that, potentially through the rest of the scene, regardless if other materials have a lower depth set.

If you can't cancel the render when it's stuck rendering very slowly, I can't reproduce that problem. Blender stays responsive for me, the render is just really slow.