On 17/01/07, Mirek <[EMAIL PROTECTED]> wrote:
Ok, but complete d3d_shader trace has about 2 GB :(

If you want to narrow it down, just include the GLSL part for the
shader that generates the error, and the d3d part. Ie, the TRACE for
SetFunction for that shader. We should probably give shader constants
their own debug channel.


Reply via email to