Unplayable in OpenGL mode ;-/

[Cthulhu]

Hello @all,

hopefully nobody else started a thread with my problem before. Otherwise I am sorry and doomed to hell *bliss*

I can play legay doom very well in software mode - speed and gameplay is exelent!

But when i switch to opengl mode. I am nearly unable to move one inch in a minute. Absolutely unplayable ;-/

I own a Acer TravelMate 661
- Intel Centrino 1.4 GHz
- 512 RAM
- Intel 855GM Integrated Graphics Controler

Kernel 2.6
- AGP and DRI support enabled

I habe absolutely no idea where the "performance" is gone. And even more strange: I can play Quake2 OpenGL absolutely smooth and fast!!!

But who wants to play Quake ;-//

Hope somebody can help getting the OpenGL power in my doom.

Thank you in advice.

Regards

Ingo

[Hurdler]

humm, strange. maybe it's just the screen depth which is not good. I suggest you to try 32 bits, then 16 bits and if both failed, 24 bits mode, at the same resolution you plya Quake2.

You might also lsdldoom instead of llxdoom (or llxdoom instead of lsdlsoom) and see if things changes.

You can also copy/paste here the result of glxinfo if nothing helps.

[Cthulhu]

Thank you for your quick reply!

Here are the things I tried:

- changing the screen depth shows no result (maybe 24 Bit is a little better) but how to measure if all is damn slow ;-/

- changed to all posible screen resolutions

1280x1024 - no way to play
1024x768 - no way to play
800x600 - hey i can move somehow
640x480 - lightning speed (but even here some little stucks)

In high resolutions > 1024x768 even the starting menu is so damn slow you nearly can't change any option. sound stucks also.

As I said Quake2 in 1280x1024 is nicely playable.


The results of glxinfo:

name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM 20021115
OpenGL version string: 1.2 Mesa 4.0.4
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_transpose_matrix, GL_EXT_abgr,
GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_convolution, GL_EXT_compiled_vertex_array, GL_EXT_fog_coord,
GL_EXT_histogram, GL_EXT_packed_pixels, GL_EXT_polygon_offset,
GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_texture3D,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_object,
GL_EXT_texture_lod_bias, GL_EXT_vertex_array, GL_IBM_rasterpos_clip,
GL_MESA_window_pos, GL_NV_texgen_reflection, GL_SGI_color_matrix,
GL_SGI_color_table
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x22 24 tc 1 24 0 r y . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x23 24 tc 1 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x24 24 tc 1 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x25 24 tc 1 24 0 r . . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x26 24 tc 1 24 0 r y . 8 8 8 0 0 0 0 16 16 16 0 0 0 Slow
0x27 24 tc 1 24 0 r . . 8 8 8 0 0 0 0 16 16 16 0 0 0 Slow
0x28 24 tc 1 24 0 r y . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow
0x29 24 tc 1 24 0 r . . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow

Any help is welcome!

Thank you,

regards Ingo

[Pate]

This may be somewhat similar to the Windows case where the software OpenGL emulator is activated instead of the HW accelerated one. Mesa has this kind of a SW OpenGL implementation and I have triggered it a few times.

I have no experience with your video card so I can't help you with that. However did you try the SDL version as Hurdler suggested?

[The Undertaker]

Try downloading the latest drivers (http://downloadfinder.intel.com/scripts-df/filter_results.asp?strOSs=39&strTypes=DRV%2CARC&ProductID=922&OSFullName=Linux*&submit=Go%21).

[Hurdler]

Yes, Pate might be right about software OpenGL implementation in Mesa drivers. I remember when I used them with my Voodoo2 (a few years ago, dri didn't exist at that time), there was an env var for allowing hardware mode. Maybe Quake2 set that env var before loading the OpenGL driver and that's why it works in hardware accelerated mode and not Legacy. If that's the problem, it's just a matter of finding that env var and add it to your .profile

EDIT: humm, but then, glxinfo wouldn't say "DRI + the name of your chip". It would probably say something like "software rendering".

BTW, did you try Tux Racer to see if it works great or if it has the same problem as Doom Legacy ?

[Cthulhu]

Thank you for all the replys!

I finaly was able to solve the problem with all your hints. This damn bastard was switchingto software mode when playing legacy doom.

Now legacy doom runs like hell^^

Regards,

Ingo

[Hurdler]

what did you do exactly (just so we know if someone else see the same problem)

[Inglor]

This precisely is my problem ... please, Cthulhu, describe your solution!

[Cthulhu]

So i am back again. Sorry for the long time since reply :(

That damn Intel Integrated Graphic Device 855GM is only capable of 3D acceleration in 16 Bit mode. I found a note at http://www.xfree86.org/4.1.0/DRI10.html. Here is what they say:

"3D acceleration for the i810 is only available in the 16 bit/pixel screen mode at this time. 32bpp acceleration is not supported by this hardware. Use xdpyinfo to verify that all your visuals are depth 16. Edit your XF86Config file if needed."

So make sure you have nailed your X to 16 Bit mode in XF86config. In the "Screen" section make sure you have a line "DefaultDepth 16" and the appropriate Subsection "Display" for yout 16 Bit mode.

Hope that solves your problem.

Regards,

Ingo

[MR_ROCKET]

lol thats reminds me of my old voodoo3 card , it was 16 bit only also..