The spec that you linked to says that if blending is enabled, the the framebuffer value is decoded, blended with the linear shader output, then re-encoded. It also says that if blending is disabled, the shader output will be encoded before being written. (all this also depending on the FBO state)


@Ponkx, maybe see the bits in the spec about FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING and the interactions with EXT_texture_sRGB.

The spec that you linked to says that if blending is enabled, the the framebuffer value is decoded, blended with the linear shader output, then re-encoded. It also say that if blending is disabled, the shader output will be encoded before being written.


@Ponkx, maybe see the bits in the spec about FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING and the interactions with EXT_texture_sRGB.

The spec that you linked to says that if blending is enabled, the the framebuffer value is decoded, blended with the linear shader output, then re-encoded. It also say that if blending is disabled, the shader output will be encoded before being written.


@Ponkx, maybe see the bits in the spec about FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING and the interactions with EXT_TEXTURE_SRGB.

The spec that you linked to says that if blending is enabled, the the framebuffer value is decoded, blended with the linear shader output, then re-encoded. It also say that if blending is disabled, the shader output will be encoded before being written.


@Ponkx, maybe see the bits in the spec about FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING.

The spec that you linked to says that if blending is enabled, the the framebuffer value is decoded, blended with the linear shader output, then re-encoded. It also say that if blending is disabled, the shader output will be encoded before being written.