On Mon, Jul 28, 2003 at 06:40:26PM +0200, Mica Telodico wrote:
> Ok here we are ;-)
> This is what I get when I start the game (in the
> console) . At a first watch it doesn't seem that the
> HW renedering is disabled :

Meanwhile I tried ET myself with an Nvidia card and it
appears to work fine, also the main menu is smooth as
it should be. I'm not at the machine right now, but
I'll have a look at the startup messages and see if
they are different from yours.

> r_smp is unsafe. Check com_crashed.
> r_mode is unsafe. Check com_crashed.
> r_depthbits is unsafe. Check com_crashed.
> r_stencilbits is unsafe. Check com_crashed.

Maybe it's harmless, but this looks suspicious to me.

> ...loading libGL.so.1: Initializing OpenGL display
> ...setting mode 4: 800 600
> Using XFree86-VidModeExtension Version 2.1
> XF86DGA Mouse (Version 2.0) initialized
> XFree86-VidModeExtension Activated at 800x600
> Using 8/8/8 Color bits, 24 depth, 0 stencil display.
> GL_RENDERER: Mesa DRI R200 20030328 AGP 4x
> x86/MMX+/3DNow!+/SSE TCL
> Initializing OpenGL extensions
> ...GL_S3_s3tc not found
> ...ignoring GL_EXT_texture_env_add
> ...using GL_ARB_multitexture
> ...using GL_EXT_compiled_vertex_array
> ...GL_NV_fog_distance not found
> XF86 Gamma extension initialized
> GL_VENDOR: Tungsten Graphics, Inc.
> GL_RENDERER: Mesa DRI R200 20030328 AGP 4x
> x86/MMX+/3DNow!+/SSE TCL
> GL_VERSION: 1.3 Mesa 5.0.2

Looks OK. AFAIR s3tc is nvidia only, so it's normal that
it is not found.

> Any way the speed in the menu seems really like if the
> SW rendering is enabled. Now I'll do a try with the
> software rendering and I'll compare the 2 things .
> Thank you again for your help , I hope that will be a
> solution for this :-)

It works for me apparently. I'll get a startup message
and compare it with yours.

freebsd-emulation@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org"