Using official 2.57 version for Windows, Both x32 and x64. Video card Nvidia GF GTX 260. OS Win XP x64.
Using the standart start file with a camera, lamp and a cube...
1. Enable GLSL for the 3d viewport and textured shading.
2. Right click and add a driver to the Cube's material Emit value and hook the driver to a custom property.
3. Change the custom property values - the 3d viewport does not update the changes at all.
4. Render the frame at values of the custom propery 0.0 and 1.0 - nothing changes
5. Change the Emit value by hand (not via custom property) - the viewport updates and the rendered frames too.
Concerning point 5 the driver exists in the Graph editor -> Drivers, but does not control the value at all
When adding driver to a value (in this case Emit) does not change the slider UI color to purple.
The value still can be keyed and changed manually.
I've hook the custom property to x translation also, just to be sure that I've hook things right - the Cube moves and the UI x axis slider resets when I try changing it's value.
One more test - now with a value in texture for Cube's material.
1. Add generated green image as a texture over a bright red material diffuse color.
2. Hook up the Color Influence of the texture to a custom property via driver.
3. Same as above the custom property does not affect the look of the cube - seems adding driver does not work in material and texture panels and property values.
I can hook a property and drive a value in render panel (i've tried to control the resolution of the frame and it worked), but the more usable driven properties both for materials and textures are not working.
Hope this will be solved asap.
Keep up the good work
Description
Event Timeline
Hi Tsvetelin,
I know it's frustrating, but we really need an example .blend from reports that illustrate the issue perfectly. Long instructions in reports only lead to misunderstandings.
Checking our current todo list is also worth a bit of time, like:
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools
Which states that glsl display is currently optimized, and doesn't show animated material changes. It should work for rendering though (F12) and for UI redraws.
It would also be more clear to not combine a set of issues in 1 report, but provide us bugs one by one.
All of these look like todo issues.
AFAIK custom property updates do not tag depsgraph.
On second thought, perhaps I should include depsgraph hacking on soc todolist ;)
Hi Ton and Joshua,
No problem for the example.
For recreating the issue I got, you have to:
1.Open the file I've uploaded.
2. You can see a Cube with bright red material added and a green texture mapped over the diffuse color.
3. In the drivers there is a Driver created for Influence>Color slider for the green texture.
4. Move the slider. After I created the driver I expect the value of color influence slider not to be editable, but it still is.
5. There is Custom Property in the Texture called col_infl. I connect this property via driver to control the value of the color influence of the texture over the material color.
However changing the value of col_infl does not affects the driven value(or the "Color" slider value).
6. Render an animation(Top right button in the UI). I animated col_infl for 10 frames from 0.0 to 1.0 and render those frames. There is no change at color of the cube in rendered frames.
So my conclusion is that drivers don't work for properties in Material and Texture tabs, since I made some tests with other properties.
You are really pushing limits here :)
Also custom properties are currently outside the dependency graph (which signals data in Blender to update). Another todo... the idea to have 'everything animatable' in Blender has severe impacts on how blender internally should be coded. We do our best, hopefully for next release.
It is noted here, search for "Dependency graph"
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/UserInterface