Slune crashes almost instantly with Soya unknown GL error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
soya (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Slune in an up-to-date edgy crashes almost straight away. The initial window comes up with a black background and then disappears. The same thing happened to me in dapper though I never reported a bug previously because an existing bug showed a similar problem and I seem to remember a post about it being fixed in edgy. I don't know if this is really a Slune bug or Soya bug.....
Running the game from a terminal gives this output:
* Slune * Slune lives in /usr/share/games
libGL warning: 3D driver claims to not support visual 0x4b
* Soya * Using 8 bits stencil buffer
* Soya * version 0.12
* Using OpenGL 1.3 Mesa 6.5.1
* - renderer : Mesa DRI Radeon 20060327 AGP 4x NO-TCL
* - vendor : Tungsten Graphics, Inc.
* - maximum number of lights : 8
* - maximum number of clip planes : 6
* - maximum number of texture units : 3
* - maximum texture size : 512 pixels
* Using OpenAL 1.1
* - renderer : Software
* - vendor : OpenAL Community
/usr/share/
import slune.globdef as globdef, slune.character, slune.sound as sound
/usr/share/
import py2play.action as action, py2play.character as py2play_character
Unknown GL_ERROR
Traceback (most recent call last):
File "/usr/games/slune", line 159, in ?
slune.
File "/usr/share/
action = gui_idler.idle()
File "main_loop.pyx", line 109, in _soya.MainLoop.idle
File "main_loop.pyx", line 158, in _soya.MainLoop.
File "/usr/share/
soya.render()
File "renderer.pyx", line 424, in _soya.render
File "renderer.pyx", line 404, in _soya.check_
_soya.GLError: Unknown GL_Error
* Soya3D * Quit...
I have a Compaq Evo laptop with on-board ATI graphics. lspci gives my graphics chip as:
ATI Technologies Inc Radeon Mobility M6 LY
I will attach the output to glxinfo and glewinfo shortly....
I had the same problem with soya (writing own stuff).
I found out, that this is caused by textures larger than the "maximum texture size".
From your log I see this value is 512 on your machine, which seems quite low (on my its for 2048 for example).
I think one could fix this by providing textures in different resolutions and look what the gpu can manage (or let the user decide).
Maybe you could fix this even yourself by scaling the textures down, just take care that the size stays a power of two. (64, 128, 256, 512 in your case)