[ Material > Viewport Display > Color ] no longer saved with the scene #69266

New Issue

Vlad Kostin · 2019-08-28T21:41:28+02:00

Vlad Kostin commented

2019-08-28 21:41:28 +02:00

System Information
Operating system: Windows
Graphics card: 1050Ti

Blender Version
Broken: v2.8.75

Short description of error
On some materials the changes to Viewport Display Color stop being saved. Saving and reloading the scene causes those color to be reset to the color it had when it worked last time. Other materials get saved as expected.

This is a crucial feature because viewport color is the export color!

Exact steps for others to reproduce the error

Change Viewport Display color on material named "BUGGED_MATERIAL" to some distinctly different color
Save the file
Reload the file
The color should be as it was before any changes were made
If you do the same with other materials, most of them work as expected (C1_7 doesnt save as well)

ColorSaveBug.blend

**System Information** Operating system: Windows Graphics card: 1050Ti **Blender Version** Broken: v2.8.75 **Short description of error** On some materials the changes to Viewport Display Color stop being saved. Saving and reloading the scene causes those color to be reset to the color it had when it worked last time. Other materials get saved as expected. This is a crucial feature because viewport color is the export color! **Exact steps for others to reproduce the error** 1) Change Viewport Display color on material named "BUGGED_MATERIAL" to some distinctly different color 2) Save the file 3) Reload the file 4) The color should be as it was before any changes were made 5) If you do the same with other materials, most of them work as expected (C1_7 doesnt save as well) [ColorSaveBug.blend](https://archive.blender.org/developer/F7708414/ColorSaveBug.blend)

Vlad Kostin commented

2019-08-28 21:41:28 +02:00

Added subscriber: @illinar

dark999 commented

2019-08-28 23:33:34 +02:00

Added subscriber: @dark999

dark999 commented

2019-08-28 23:33:34 +02:00

you forgot to fill relevant data as request in bug template

The operating system, main memory size, GPU brand and model, GPU driver version and Blender hash or its build date may be needed by developers to investigate on this problem
i not find any issue here, IMO all work fine on linux Blender 2.80 f6cb5f5449 (Stable) AMD FX8350, 16GB DDR3, GTX690 2+2 GB VRam- Nvidia drivers 435.17 and Blender 2.81 f88022b96f

changing Viewport Color in all materials without updating the keyframe color does not produce color change on a new saved file, changing Viewport Color and updating all Keyframe color you get all material Viewport Color changed to the new setting in the saved file. All this work as expected foe each material

you forgot to fill relevant data as request in bug template ```The operating system, main memory size, GPU brand and model, GPU driver version and Blender hash or its build date may be needed by developers to investigate on this problem``` i not find any issue here, IMO all work fine on linux Blender 2.80 f6cb5f54494e (Stable) AMD FX8350, 16GB DDR3, GTX690 2+2 GB VRam- Nvidia drivers 435.17 and Blender 2.81 f88022b96f3a changing `Viewport Color` in all materials without updating the` keyframe` color does not produce color change on a new saved file, changing `Viewport Color` and updating all `Keyframe` color you get all material `Viewport Color` changed to the new setting in the saved file. All this work as expected foe each material

Vlad Kostin commented

2019-08-28 23:58:48 +02:00

Thanks for the reply. Not sure if that was a bug or if it had something to do with animation. First of all, right clicking broken materials and clicking Unset fixed them. (No idea what it does) I'm not sure what you've been saying about Keyframes, but I went to animation window and saw that I'm not in the frame 0 and that I have some keyframes. Just in case I deleted them and went to frame one. I think that fixed the last material, but not sure.

If what that behavior was supposed to be there it is still very confusing. I was in modeling window changing colors on some materials and it was working, and on some materials it would stop working for no visible reason. In fact it took me a long time to realize that my exported colors are all wrong because the viewport color changes were not saved on some materials. Absolutely does feel like a bug.

Thanks for the reply. Not sure if that was a bug or if it had something to do with animation. First of all, right clicking broken materials and clicking Unset fixed them. (No idea what it does) I'm not sure what you've been saying about Keyframes, but I went to animation window and saw that I'm not in the frame 0 and that I have some keyframes. Just in case I deleted them and went to frame one. I think that fixed the last material, but not sure. If what that behavior was supposed to be there it is still very confusing. I was in modeling window changing colors on some materials and it was working, and on some materials it would stop working for no visible reason. In fact it took me a long time to realize that my exported colors are all wrong because the viewport color changes were not saved on some materials. Absolutely does feel like a bug.

Bastien Montagne commented

2019-08-29 11:18:59 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-08-29 11:18:59 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-08-29 11:18:59 +02:00

Bastien Montagne self-assigned this 2019-08-29 11:18:59 +02:00

Bastien Montagne commented

2019-08-29 11:18:59 +02:00

We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com and our devtalk should be used for that matter.

If a property is animated (yellow or green outline/background), then its value is fully defined by its animation curve(s), changing the value without defining a new keyframe won't do anything.

We do not handle user support on this tracker, only bug reports. User forums like [blenderartists.org](http:*blenderartists.org/) or [blender.stackexchange.com](http:*blender.stackexchange.com/) and our [devtalk](https://devtalk.blender.org) should be used for that matter. If a property is animated (yellow or green outline/background), then its value is fully defined by its animation curve(s), changing the value without defining a new keyframe won't do anything.

Vlad Kostin commented

2019-08-29 12:54:31 +02:00

If a property is animated (yellow or green outline/background), then its value is fully defined by its animation curve(s), changing the value without defining a new keyframe won't do anything.

That's a good explanation thank you. Now I see how it's not a bug. And knowing how to spot if it's animated is also very useful.

> If a property is animated (yellow or green outline/background), then its value is fully defined by its animation curve(s), changing the value without defining a new keyframe won't do anything. That's a good explanation thank you. Now I see how it's not a bug. And knowing how to spot if it's animated is also very useful.

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 > Viewport Display > Color ] no longer saved with the scene #69266