- User Since
- Apr 13 2019, 1:48 PM (74 w, 6 d)
Aug 16 2020
Jul 13 2020
It's hard to follow because the behavior changed from version 2.83 to 2.90, and I found out the reason after opening the ticket.
Jul 9 2020
Jul 7 2020
Currently this is the default config:
It looks like the issue was that now (after 2.90) a mandatory "Default" view space alias was needed for each display group. That solves the issue I think, but I don't feel comfortable reading "Default" without knowing what explicitly the view transform is. If you want a default, pick the first one whatever it's named.
Jul 4 2020
I was using an old config (not available anymore) from Daniel Brylka at this page: https://www.toodee.de/?page_id=858
Jul 2 2020
Sorted it by adding viewing transforms under the sRGB display group. Guess it's solved (?)
May 4 2020
Overlay statistics is a very useful feature. People think whether you need poly count or such, no, overlay statistics is for everything you want to show as an overlay. We already have a few stats; framecounter, camera view, collection... this only expands the stats on an optional way.
I don't understand this patch to be honest, there are dozens of -free- addons that do a better job at it.
As a matter of fact I picked YuriyAndropov AStats and modded it to add filename, engine, version and committed memory. If you wonder those are a lot of stats, you can disable everything and is fully customizable, position, color, size... It also differentiates between global and local.
Jan 27 2020
Not sure what's the relation between interface colors and render viewing transform, from an user stand point it doesn't make much sense. (ie. using a "False Colors" viewing transform messes up the GUI)
Jan 14 2020
It looked wrong with Load UI, with the option unchecked it looked fine.
Anyway, this commit from yesterday fixed it. Thanks for looking into it:
Jan 13 2020
Bad or very bad I think it's the source of the same bug. I wanted to rule out my preferences or addons getting in the way.
Jan 12 2020
Dec 12 2019
I think currently this behavior only applies to byte type formats (ie EXR half-float unaffected)
Dec 9 2019
Nov 30 2019
Nov 26 2019
Just a reminder for T71705 to also be CM aware.
Nov 1 2019
Sep 6 2019
I subscribe most things noted here but I write some observations below.
It should expose the quality slider in the same way it is exposed for JPGs.
If the Open EXR specification allows it it should also allow for compression of other layers/channels.
Aug 3 2019
And Ctrl+Shift for adding range selection. Would be great to expand it to all browser dialogs too.
Apr 22 2019
I see T54659 is considered high priority. In my opinion this ticket should be handled alongside for proper OCIO colorspace workflow from start to finish.
When you have time please review the video.
Apr 14 2019
From a fresh and updated to 14th of April Blender install, default config.ocio.
Apr 13 2019
Sorry for the confusion I was using aces 1.0.3 variant terminology from last year compared to spi-vfx which is like 7 years old.
Aren't there plans to update to a more modern aces variant OCIO framework?
Color Space setting that is broken. (See also T63571). So a solution is to fix it or remove it (hopefully the former). Currently the only practical implementation for OCIO is as a tonemapper which is a sad end for such a robust color framework.
Sorry I think I have been misunderstood, I haven't name Cycles here (for that I created this other ticket T63572), I'm talking about Blender 3D View and internal behavior.