[tom]

But, it doesn't save these when you save the scene/mxm. Just FYI...

[Asmithey]

I use it. I would like to see it stay.

[oz42]

I use it all the time (almost everytime I build a material), incredibly useful for checking subtle differences between interations - please keep it!

[PA3K]

Didn`t know it exist, and that it is working this way - 1. store, 2. arows. Since it is stored, it can be used as "undo","redo" options, that I like on every software. So I voted for better keeping it. I will not use it massively.
May be little out of theme, but sometimes when I refresh material preview, it will not refresh, or sometimes it is just cyan ball as if it was emitter or sss there, and it is "stored" corrupted. Even after another refresh, where preview is ok, there is stored corrupted image preview.

Patrik

[zdeno]

this feature is usefull, but lack of it in name of UI simplicity is aceptable.

[polynurb]

Didn`t know it exist, and that it is working this way - 1. store, 2. arows. Since it is stored, it can be used as "undo","redo" options, that I like on every software. So I voted for better keeping it. I will not use it massively.
May be little out of theme, but sometimes when I refresh material preview, it will not refresh, or sometimes it is just cyan ball as if it was emitter or sss there, and it is "stored" corrupted. Even after another refresh, where preview is ok, there is stored corrupted image preview.

Patrik

Yes, that cyan ball. I know it too.
Happens only with std.preview scene here though.
Try stage 2 or so. It should render ok.
I always ignored it, as the material itself still renders ok in the scene.

[Tok_Tok]

Why would you remove this? It's great for comparing subtle changes! You can't remember the difference in each preview render between Roughness 40 or 42 but it can make the difference in a good material or a perfect material.