Material/texture nodes cause rendering bug #24027

New Issue

Johann M · 2010-09-27T14:38:04+02:00

Johann M commented

2010-09-27 14:38:04 +02:00

%%%OS: Win XP pro 32
g-force 7950gtx

bug confirmed on
r31865 win xp 32
r32060 win xp 32
r32037 OSX 10.6.2

A complex Material node setup seems to cause rendering bugs.
The first few parts of the render render the geometry without the applied textures. This applies to normal and color influences, sometimes both are missing, sometimes only one.

Steps to reproduce:
download this file:
http://www.mediafire.com/download.php?lme6y3kaeeksgu6
open
render straight away without any modifacation to the file.

The first render should show the bug, default colors on objects on the first parts rendered.
The second render however should render fine.
Whith increasing file complexity the second render will be flawed aswell.

My guess is that there is a problem mapping textures to the mesh, the rendering seems to start before the mapping is complete.

This is backed up by the following effect:
The console puts out many mapalloc errors when the following steps are taken:
open the file mentioned above
close the open node editor
save the file
reopen
then render

The console should be flooded with errors and blender crashes shortly after.

BA thread with renders here:
http://blenderartists.org/forum/showthread.php?t=198090 %%%

%%%OS: Win XP pro 32 g-force 7950gtx bug confirmed on r31865 win xp 32 r32060 win xp 32 r32037 OSX 10.6.2 A complex Material node setup seems to cause rendering bugs. The first few parts of the render render the geometry without the applied textures. This applies to normal and color influences, sometimes both are missing, sometimes only one. Steps to reproduce: download this file: http://www.mediafire.com/download.php?lme6y3kaeeksgu6 open render straight away without any modifacation to the file. The first render should show the bug, default colors on objects on the first parts rendered. The second render however should render fine. Whith increasing file complexity the second render will be flawed aswell. My guess is that there is a problem mapping textures to the mesh, the rendering seems to start before the mapping is complete. This is backed up by the following effect: The console puts out many mapalloc errors when the following steps are taken: open the file mentioned above close the open node editor save the file reopen then render The console should be flooded with errors and blender crashes shortly after. BA thread with renders here: http://blenderartists.org/forum/showthread.php?t=198090 %%%

Johann M commented

2010-09-27 14:38:04 +02:00

Changed status to: 'Open'

Nathan Letwory commented

2010-09-27 15:44:09 +02:00

%%%You have a rotation around Y of 4225°. Set it to 265° and you're fine.

Obviously Blender could do this automagically too.%%%

%%%You have a rotation around Y of 4225°. Set it to 265° and you're fine. Obviously Blender could do this automagically too.%%%

Johann M commented

2010-09-27 16:47:46 +02:00

%%%Oh, didn't see that you've posted here aswell.

reducing the values to 0 does get rid of the error on the cubes but they still occur on the plane.
Its important to save and reopen the file after changing the values, the second render usually doesnt produce the error.
Also it seems that letting blender calculate the shader preview for every node material cuases it to render fine.

In my actual project file im using a much simpler node setup and only one node material.
It used to be similar to what the setup in the example file is like but now its really siplified but still produces the error occasionally. %%%

%%%Oh, didn't see that you've posted here aswell. reducing the values to 0 does get rid of the error on the cubes but they still occur on the plane. Its important to save and reopen the file after changing the values, the second render usually doesnt produce the error. Also it seems that letting blender calculate the shader preview for every node material cuases it to render fine. In my actual project file im using a much simpler node setup and only one node material. It used to be similar to what the setup in the example file is like but now its really siplified but still produces the error occasionally. %%%

Nathan Letwory commented

2010-09-27 21:21:54 +02:00

%%%The crash you see is most likely because you're exhausting your system memory, and going over the limits one process can have. On windows 32bit it's somewhere around 1.3GB, and your scene takes 1717MB to render ( bpy.wm.memory_statistics() gives you a somewhat low-level overview of memory allocation. )%%%

Nathan Letwory commented

2010-09-27 21:24:05 +02:00

%%%sorry, typo: bpy.ops.wm.memory_statistics()%%%

Nathan Letwory commented

2010-09-27 21:46:21 +02:00

%%%And yet more adjustments: memory is that in use after rendering and saving blend first time over.%%%

Nathan Letwory commented

2010-10-17 23:10:44 +02:00

%%%I think the problem here is that the node trees in use here hog awful large amounts of memory, which is problematic on at least 32bit systems. Anyway, the current best workaround is to just click in one field of mapping in material node and press enter (so no change, just trigger tree execution).

I further move this report to our todo, since it's not a trivial bug fix :/

http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Node_Materials

%%%

%%%I think the problem here is that the node trees in use here hog awful large amounts of memory, which is problematic on at least 32bit systems. Anyway, the current best workaround is to just click in one field of mapping in material node and press enter (so no change, just trigger tree execution). I further move this report to our todo, since it's not a trivial bug fix :/ http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Node_Materials %%%

Nathan Letwory commented

2010-10-17 23:10:44 +02:00

Changed status from 'Open' to: 'Archived'

Nathan Letwory closed this issue

2010-10-17 23:10:44 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Material/texture nodes cause rendering bug #24027