TextureViews on rendertargets will render under the parent format instead of the textureView's format in AMD OpenGL Windows driver

Discussion created by blinkhawk on Apr 27, 2019
Latest reply on Apr 29, 2019 by dorisyan

I'm not sure if the developers are aware of this bug but I've had it a long time and have had to resort to glCopyImageSubData to avoid it. The issue occurs when you have a Texture of Format A and a Texture View of that Texture using format B. If I setup the TextureView as a renderTarget, the data rendered will be wrong and use the format of the parent texture. I have tested this in other drivers, including NVIDIA's and Intel's where it works correctly, so I'm assuming it's an AMD's driver bug.