[jitter] Bug report: jit.gl.slab not able to change context
Trond Lossius
lossius at bek.no
Mon Sep 3 12:42:19 MDT 2007
- Previous message: [jitter] Re: loading more than 2GB of matrixes?
- Next message: [jitter] Re: Re: Control camera?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Coming in late on this one again, as I have kept working on slab-based patches and seen some more patterns that might be worth reporting. I am not able to find any consistent steps that will produce the errors. However, when the error appears, it starts immediately as soon as I start rendering to a new context (e.g. first time after opening the patch and starting to bang jit.gl.render et al.). And I have found a simple workaround that seems to consistently solve the problem without having to close the patch or restart Max: If I use a rect message to jit.window to resize/move it somewhere else, and then move it back where I want it to be, the errors are gone and rendering and slabs work as supposed to. I don't know if this might provide some additional clues to tracking down what causes it. Best, Trond Wesley Smith wrote: > I don't think this problem has anything to do with shader files but > instead with the offscreen context generated by jit.gl.texture > internal to jit.gl.slab for processing input textures. Clearly > something is not being initialized or destructed appropriately and is > throwing errors to the Max window. I've noticed this behavior as > well. If anyone has any simple patches that generate these errors > consistently, please post 'em. > > thanks, > wes > _______________________________________________ > jitter mailing list > jitter at cycling74.com > http://www.cycling74.com/mailman/listinfo/jitter >
- Previous message: [jitter] Re: loading more than 2GB of matrixes?
- Next message: [jitter] Re: Re: Control camera?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
