Page MenuHome

Node Group defaults not working
Closed, ResolvedPublic

Description

System Information
osx 10.9.1, macbook pro 13.1

Blender Version
Broken: buildbot 1ea5c2a own 2.69.8 0445454
Worked: official 2.69

Short description of error
Default Values and Limits in Node Groups made with buildbot or own down't work at all, everything is 0.
Node Groups made with earlier versions work, and edit with buildbot and own do work too. So there must be something about how newer builds make Node Groups.

Exact steps for others to reproduce the error
use buildbot build: Make Node Group, give some default values and Limits, remember name of this Node Group. Delete Node Group. Add same Node Group with shift+a and look at Default Values and Limits

Event Timeline

To me this seems to work correctly. The settings for node group values are slightly complicated, but this is because of how they work:

The settings marked in the lower half are the common default and limit values for the "Fac" input. The input values displayed on the group node in the upper half are the values for that particular instance of the group, they are not shared between instances. Any new instance will initialize these values from the default, but changing the default will not immediately update all instance values (this would overwrite any specific inputs).

If this is not what you mean, could you make a test file so we can compare the official 2.69 to current trunk? I can't find anything wrong following your description.

"Any new instance will initialize these values from the default" - That whats not working - every new instance has 0 as default Value and does not respect limits at all.

However - it does respect Default + Limits if the File is saved before adding the instance.

"However - it does respect Default + Limits if the File is saved before adding the instance."

Thus i don't think it makes sense to upload a sample .blend -...

Lukas Toenne (lukastoenne) triaged this task as Confirmed, Medium priority.Jan 10 2014, 4:47 PM

Ah sorry, i can confirm this is a bug.