[jitter] Re: nasty texture error

Likewise, I was unable to isolate and reproduce this error, despite many tries. However, the drawto workaround got me through several occurences of the error in a 1/2 hour performance without crashes or having to restart Max. 

best,
dan

-----Original Message-----
From: vade <doktorp at mac.com>

Date: Wed, 2 Apr 2008 17:40:13 
To:jitter at cycling74.com
Subject: Re: [jitter] Re: nasty texture error


I believe it is a corruption of some state saving code somewhere. I  
dont mean to be unhelpful or vague, but its intermittent, and  
dependent on fiddling with things for some time, and, eventually,  
state gets messed up somewhere in the stack and OpenGL is no longer  
happy.

Ive found that resetting openGL state by sending jit.gl.render a  
drawto message (saw, draw to a matrix, and then draw to my accelerated  
window, one RIGHT after the other), is enough to usually rebuild the  
state.

[drawto softwarematrix, drawto MYGLACCELERATEDWINDOW]

Dan Winckler and I came up with that little workaround, and, it seems  
to mostly work, but I havent fiddled with it in a long time,

Anyway...

On Apr 2, 2008, at 5:26 PM, jasmin wrote:

>
> hay
> I opened yours patch on my G5 with GeForce FX 5200 with no error  
> massages.
> --
> jaz
> _______________________________________________
> jitter mailing list
> jitter at cycling74.com
> http://www.cycling74.com/mailman/listinfo/jitter

_______________________________________________
jitter mailing list
jitter at cycling74.com
http://www.cycling74.com/mailman/listinfo/jitter