Re: Raptor 0.1.1 released

Actually, the 'render_to_crut_window' causes the X error.  I'm not sure 
how the 'render_to_app_window' option behaves in a sort-last 
configuration.

By commenting out both, I get the renderspu window and a null rendered 
crut server winodw that grabs events.  So I can still interact, it's just 
in the render window.

-Dave


On Mon, 19 Jul 2004, Mike Houston wrote:

> Hmmm, that will prevent interaction from working.  But, it sounds like 
> we will need to find a workaround for the Nvidia drivers and 
> glXMakeCurrent.  What happens if you just comment out render_to_app_window?
> 
> -Mike
> 
> David Jones wrote:
> > So there is a 'partial' fix to this.  Commenting out both
> > 
> > renderspu.Conf('render_to_app_window', 1 )
> > renderspu.Conf('render_to_crut_window', 1 )
> > 
> > in the config file fixes things.
> > 
> > As best I can tell, the glXMakeCurrent calls made at around line 1120 in 
> > renderspu_glx.c are freaking out.  Unfortunately, I don't really know 
> > enough about this code to know what's going on.
> > 
> > -Dave
> > 
> > 
> > On Mon, 19 Jul 2004, Mike Houston wrote:
> > 
> > 
> >>Includes David's glXGetProcAddress bug fix.  I should have been using 
> >>the ARB version...
> >>
> >>There is still a bug with Nvidia hardware in sort-last cluster rendering 
> >>mode to still track down.  It's throwing a invalid drawable error. 
> >>Since the local rendering version works, this looks like an odd 
> >>interaction between Chromium and Nvidia's Linux drivers doing sort-last 
> >>rendering.
> >>
> >>-Mike
> >>
> >>
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click