Mike Mestnik wrote: > On Mon, Jun 19, 2006 at 08:01:09AM -0600, Brian Paul wrote: > >>Mike Mestnik wrote: >> >>>I keep trying to send this :( >>> >>>http://www.transgaming.com/showthread.php?forum=1262&thread=61671&msg=61671 >>> >>>LIBGL_ALWAYS_INDIRECT works. >>> >>>Grand Theft Auto III, in game black screen. - Request for support (open) >>>more >>>help needed >>>by cheako on Tuesday June 13, 2006 @ 10:20PM. >>> >>> >>>Cedega Version: 5.1.4 >>>Distribution: Debian >>>Video Card: ATI X600. Driver: DRI r300 >>>Sound Card: Black Sheep - onboard. Driver: ALSA >>>Game Title: Grand Theft Auto III 3 three >>> >>> >>>Using LIBGL_ALWAYS_INDIRECT fixes this problem. If any one else reports it >>>this >>>could be a bug in the r300 driver. >>> >>> >>>I was playing GTA3 and then I don't know what I did, but now after the >>>intro >>>movies(hit space twice!!) all I get is a black screen. I'm able to start >>>the >>>game and even drive around blindly with the cops after me. The speed is >>>fast >>>and I'm sure I get hardware rendering... >>>libGL: XF86DRIGetClientDriverName: 4.0.3 r300 (screen 0) >>>libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r300_dri.so >>>drmOpenByBusid: Searching for BusID pci:0000:02:00.0 >>>drmOpenDevice: node name is /dev/dri/card0 >>>drmOpenDevice: open result is 14, (OK) >>>drmOpenByBusid: drmOpenMinor returns 14 >>>drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0 >>>EOF >>> >>> >>>Re: Grand Theft Auto III, in game black screen. >>>by cheako on Tuesday June 13, 2006 @ 10:48PM. >>> >>> >>>Ohh, wait... >>> >>>This is with MESA_DEBUG. >>>Mesa: User error: GL_INVALID_ENUM in glStencilFunc >>> >>>I don't get this with LIBGL_ALWAYS_INDIRECT, a goggle says that this is >>>for not >>>drawing things. How do I know if this is emitted by the app, cedega, or >>>mesa? >> >>It's emitted by Mesa when the application makes an invalid API call. >> >>-Brian > > > How do I prove that? I'm thinking they might try and say that a > software mesa path is calling this, I'd assume that internally you > would call something like _glStencilFunc.
The internal function is called _mesa_StencilFunc. It's called directly by glStencilFunc, or via executing a display list. In either case, the only way that error will be reported is if the application provides an invalid value. > My other problem is that if the error is caught, why is the screen all > black? I can't say. Maybe correct stencil operation is required for anything to appear. Or, it may be a totally unrelated issue. > What would be the next step in tracking this down be? One of the r300 driver developers will probably have to look into it. -Brian -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel