Re: [Dri-devel] Slowdown with recent DRI... Update...

[Adam K K. <ad...@vo...>]

On Sun, 18 Jun 2000, Brian Paul wrote:

> Adam K Kirchhoff wrote:
> > 
> > OK,
> > 
> >         So I woke up and noticed a GL mode from xscreensaver running...
> > And running at it's normal accelerated screen.  They seem to be fine when
> > running fullscreen (which would also explain Quake3) but slow down
> > tremendously when running windowed.
> >         Also, I double checked all my environmental variables, and they're
> > still set properly (ie, FX_GLIDE_SWAPINTERVAL is set to 0).
> >         So what am I doing wrong? :-)
> 
> Sorry, I have no ideas off the top of my head.  I haven't heard of
> this problem from anyone else (yet).
> 
> -Brian
> 

I figured it out :-)  So, can anyone come up with a reason why certain
enlightenment themes (in this case, ganymede) would show such a slowdown
in windowed GL apps?  I started X with a different windowmanager (fvwm2)
and everything worked fine...  WindowMaker worked fine, too.
Enlightenment didn't.  On a hunch I switched to a different theme.  Worked
fine...  Went back to Ganymede, and it slowed down...  Then I went to a
completely different theme...  Worked fine. :-)

Any ideas now? :-)

Adam

> 
> 
> > 
> > Adam
> > 
> > ---------- Forwarded message ----------
> > Date: Sat, 17 Jun 2000 22:13:36 -0400 (EDT)
> > From: Adam K Kirchhoff <ad...@vo...>
> > To: DRI Devel <dri...@li...>
> > Subject: Slowdown with recent DRI...
> > 
> > So, I just installed upgraded to RedHat 6.2.  I decided to do it from
> > scrath, only backing up what isn't on the RedHat CD or what couldn't
> > easily be downloaded.
> > 
> > So, after the installation, I pulled the DRI this evening, and compiled.
> > I reinstalled Quake3 and UnrealTournament.  Quake3 was my first test.
> > Played beautifully.  Getting approximately the same framerates as I was
> > getting before the upgrade.  UnrealTournament, however, didn't work quite
> > as well.  It started up, but completely in black and white stripes...  I
> > was able to quit out, and discovered the following message on the
> > command-line:
> > 
> > fx Driver: No space for texture
> > 
> > Then I tried the gears Mesa demo:
> > 
> > [adamk@sorrow demos]$ ./gears -info
> > GL_RENDERER   = Mesa DRI Voodoo3 20000616
> > GL_VERSION    = 1.2 Mesa 3.3 beta
> > GL_VENDOR     = Precision Insight, Inc.
> > GL_EXTENSIONS = GL_ARB_multitexture GL_ARB_tranpose_matrix GL_EXT_abgr
> > GL_EXT_blend_func_separate GL_EXT_clip_volume_hint
> > GL_EXT_compiled_vertex_array GL_EXT_histogram GL_EXT_packed_pixels
> > GL_EXT_paletted_texture GL_EXT_point_parameters GL_EXT_polygon_offset
> > GL_EXT_rescale_normal GL_EXT_shared_texture_palette GL_EXT_stencil_wrap
> > GL_EXT_texture3D GL_EXT_texture_env_add GL_EXT_texture_object
> > GL_EXT_texture_lod_bias GL_EXT_vertex_array GL_INGR_blend_func_separate
> > GL_MESA_window_pos GL_MESA_resize_buffers GL_NV_texgen_reflection
> > GL_PGI_misc_hints GL_SGI_color_matrix GL_SGI_color_table
> > GL_SGIS_pixel_texture GL_SGIS_texture_edge_clamp GL_SGIX_pixel_texture
> > 3DFX_set_global_palette
> > 107 frames in 5.027 seconds = 21.2851 FPS
> > 119 frames in 5.017 seconds = 23.7194 FPS
> > 119 frames in 5.002 seconds = 23.7905 FPS
> > 120 frames in 5.01 seconds = 23.9521 FPS
> > 119 frames in 5.021 seconds = 23.7005 FPS
> > 
> > Needless to say, I'm used to something 15 times faster.  I have no ideas
> > if these problems are related.  Nor do I understand why Quake3 works fine.
> > 
> > Any ideas?
> > 
> > Adam
> > 
> > _______________________________________________
> > Dri-devel mailing list
> > Dri...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dri-devel
>