Timeline for Why doesn't a value node set to 1 evaluate to pure white in the shader editor? [duplicate]
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2021 at 6:24 | history | closed |
susu Timaroberts |
Duplicate of World displays as grey even though set to white | |
| Feb 18, 2021 at 3:37 | review | Close votes | |||
| Feb 18, 2021 at 6:24 | |||||
| Feb 18, 2021 at 3:35 | vote | accept | fmotion1 | ||
| Feb 18, 2021 at 3:14 | answer | added | susu | timeline score: 2 | |
| Feb 18, 2021 at 2:06 | comment | added | Allen Simpson | Welcome to color space, you can stay as long as you like. | |
| Feb 18, 2021 at 1:12 | comment | added | fmotion1 | I think Scurest hit it on the head. It's the view transform that's making the color appear to be non-white. | |
| Feb 18, 2021 at 1:09 | comment | added | scurest | Go to Color Management (scroll to the bottom of the properties editor you have open) and switch Filmic to Standard. | |
| Feb 18, 2021 at 1:08 | comment | added | Nascent Space | Your'e absolutely right Christopher, I also noticed something else interesting. It doesn't actually reach true pure white until you set the value to 15. You can check this by using an eye dropper colour picker. | |
| Feb 18, 2021 at 1:04 | comment | added | Christopher Bennett | I think once the value goes beyond 1 it goes into HDR range. Go to EEVEE, turn on bloom, and set the value to anything higher than 1 (the higher the better the example - try 50) to see what I mean. | |
| Feb 18, 2021 at 1:00 | history | asked | fmotion1 | CC BY-SA 4.0 |