Your solution seems to work but a problem with your explanation is that I used ACEScg in the scene_linear role when i used ACES 1.3 and it did not have the problem where textures needed to match the working colorspace.
Testing here with the OCIO v1 ACES 1.2 config, and the the OCIO v2 ACES 1.3 config ( cg-config-v2.2.0_aces-v1.3_ocio-v2.4.ocio ), “View as Render” does function in the Image Editor. I’m not sure if you are seeing the same behavior?
It’s quite possible the behavior is different on platforms other than Linux. It is also quite possible that my hunch which I outlined above is flawed in some way. Like I said, I am not an expert in blender’s color management system.
I did notice that this error was printed in my shell when opening blender with the ACES 2.0 OCIO v2 config:
ERROR (gpu.shader): OCIO_Display FragShader:
|
689 | float lo = texture(to_display_reach_m_table_0Sampler, (i_lo + 0.5) / 360.0).r;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
|
690 | float hi = texture(to_display_reach_m_table_0Sampler, (i_hi + 0.5) / 360.0).r;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
|
723 | vec3 lo = texture(to_display_gamut_cusp_table_0Sampler, (i_hi - 1 + 0.5) / 362).rgb;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
|
724 | vec3 hi = texture(to_display_gamut_cusp_table_0Sampler, (i_hi + 0.5) / 362).rgb;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
|
739 | float lo = texture(to_display_upper_hull_gamma_table_0Sampler, (i_lo + 0.5) / 362).r;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
|
740 | float hi = texture(to_display_upper_hull_gamma_table_0Sampler, (i_hi + 0.5) / 362).r;
|
| Error: C1115: unable to find compatible overloaded function "texture(sampler2D, float)"
Maybe it’s related to the behavior?
I actually got view as render working with aces 2.0 on windows 11 blender 4.4 stable. it’s possible that these issues are related to those errors, Do you think using Wayland or X11 would change it? I think something to mention with the texture viewer in blender is that I have basically never had to use view as render for it, when using every other config. So it should ideally be left as default for actual use.
all of this is making me want to revert to ACES 1.3 which is a shame as, I’d like to enjoy ACES 2.0’s benefits. Perhaps we’re on the cusp of discovering something seriously wrong with Blender’s Color Management or something missed with ACES 2.0. I’m learning a lot of this as i go along so please correct me if i get anything wrong.
it seems like Blender themselves say that they still account for the view transform internally.
They say that Blender 4.5 is supposed to fix this but it simply does not.
I’d like to able to test it different software but it seems like Gaffer doesn’t support OCIO v2.4, is there any other FOSS software i can try it with?
Resolve 20.0 comes with libOpenColorIO 2.4 … I tested with this config and it seems to function without erroring, although performance is hilariously bad… I’m getting less than 1 frame per second playback using just an OCIO Display set to ACES 2.0, playing back a 2k prores log clip 
I tested with Maya 2026, it’s definitely broken on Blender’s end. I don’t have much experience with Maya but it’s working properly, so now that I know that it is on Blender’s end, how should i word my Issue report?
Currently most Wayland compositors would have color management protocol supported, however Blender itself doesn’t have it supported yet, and compositor would treat blender window as sRGB and convert that to monitor color space.
I think there are some existing templates? Also can you post the issue address here after creating it?
Sure I’m just wondering how I should phrase the issue, perhaps it should be “OCIO 2.x config does not apply View Transform to image textures” maybe something like that. I just want to get the wording right from professionals, so that the Blender team knows exactly what I’m talking about and can resolve it in a timely manner.
since you seem to know what the intended behavior is, do you mind giving advice on how i should word my issue report to blender? I mean if i get something wrong it won’t be the end of the world but it will prolong the process.