Page MenuHome

Blender Internal Material Node
Closed, ArchivedPublic

Description

System Information
OS - Ubuntu 14.04.1 LTS 64-bit
CPU - AMD A8-5550M APU with Radeon(tm) HD Graphics × 4
GPU - AMD Radeon HD 8550G
RAM - 8GB

Blender Version
Broken: 2.72 b 9e963ae

Short description of error
According to the following wiki, blender should enable and auto-add a two node setup for materials if the USE NODE button is enabled, yet it does not when in the blender internal renderer.
http://wiki.blender.org/index.php/Doc:2.6/Manual/Materials/Nodes

Exact steps for others to reproduce the error
Video: https://dl.dropboxusercontent.com/u/11171255/BI_material_node_bug.ogv
Text:

  • Make sure that the startup file is set on the blender internal renderer else switch to it, press CTRL+U, ENTER and restart.
  • Split view and open the NODE EDITOR.
  • Add a new material to any object and tick the USE NODE button in the material panel (in between the material name and the materials data links).

How to enable it; Once the above steps have been completed, switch the engine to CYCLES then back to BI. Doing so makes blender realize it should actually use the nodes.

Related Objects

Event Timeline

Oren Titane (Genome36) raised the priority of this task from to 90.
Oren Titane (Genome36) updated the task description. (Show Details)
Oren Titane (Genome36) edited a custom field.

Reproduced with 2.72.3 Git master.

OS - Arch Linux
CPU - AMD E-300 APU with Radeon(tm) HD Graphics
GPU - AMD Radeon HD 6310 Graphics
RAM - 4GB

Please note that this bug is only reproducible on linux.

Hey @Oren Titane (Genome36),
I can't reproduce with latest master here. Could you try it with the latest build from buildbot?

Nevertheless, thanks for the report :)

Julian Eisel (Severin) lowered the priority of this task from 90 to 30.Dec 14 2014, 2:08 PM

Versions 2.72 up to 2.72.3 (2.72 - 2.72b - 2.72.3) have shown a reproducibility of 100% with a startup file created with the first release of 2.72.
I have loaded the factory defaults on 2.72 - 2.72b and still shown a rate of 100%.
I then tried saving a startup file from 2.72.3 and has proven to fix the issue on all the versions I tested (2.72 - 2.72b - 2.72.3).

Tried with 2.72b and could not reproduce

OS- Ubuntu -14.04 LTS 64 Bit
Graphics- Intel Graphics HD 4600

Julian Eisel (Severin) changed the task status from Unknown Status to Unknown Status.Dec 14 2014, 9:29 PM
Julian Eisel (Severin) claimed this task.

I talked a bit about this with @Oren Titane (Genome36) on IRC and we agreed to close the bug, since loading factory settings solved it.
I will keep my eyes open for similar reports and point them to this place.