Page 1 of 1

some graphics artefacts

Posted: Sun Apr 01, 2012 1:46 pm
by GHost
Hi all, i have Radeon Mobility FireGL 9000 (RV250 gpu chip) and use open source driver, after switching to KMS i have some artefacts on planets like this - http://gallery.icf.org.ru/icfteam/GHhos ... 7.png.html and http://gallery.icf.org.ru/icfteam/GHhos ... 0.png.html, and white square instead oolite logo while game startup, all other works fine, oolite version 1.76, is here any way to fix this? snips from logs:

17:07:10.418 [rendering.opengl.version]: OpenGL renderer version: 1.3.0 ("1.3 Mesa 7.11.2"). Vendor: "Tungsten G
raphics, Inc.". Renderer: "Mesa DRI R200 (RV250 4C66) x86/MMX/SSE2 TCL DRI2".
17:07:10.419 [rendering.opengl.extensions]: OpenGL extensions (88):
GL_ARB_texture_env_crossbar, GL_S3_s3tc, GL_EXT_abgr, GL_EXT_texture, GL_IBM_texture_mirrored_repeat, GL_EXT_tex
ture_edge_clamp, GL_EXT_separate_specular_color, GL_EXT_blend_minmax, GL_ARB_texture_env_add, GL_EXT_texture_obj
ect, GL_INGR_blend_func_separate, GL_EXT_texture_cube_map, GL_EXT_blend_logic_op, GL_EXT_texture_env_dot3, GL_IB
M_rasterpos_clip, GL_ARB_texture_env_dot3, GL_EXT_framebuffer_object, GL_NV_light_max_exponent, GL_EXT_blend_sub
tract, GL_EXT_copy_texture, GL_ATI_texture_mirror_once, GL_MESA_window_pos, GL_ARB_multitexture, GL_EXT_stencil_
wrap, GL_ARB_texture_border_clamp, GL_ARB_texture_env_combine, GL_EXT_texture_env_add, GL_SGIS_texture_edge_clam
p, GL_EXT_packed_pixels, GL_SGIS_texture_lod, GL_ARB_occlusion_query, GL_ARB_transpose_matrix, GL_NV_packed_dept
h_stencil, GL_NV_texgen_reflection, GL_ARB_robustness, GL_OES_EGL_image, GL_EXT_gpu_program_parameters, GL_EXT_r
escale_normal, GL_ATI_fragment_shader, GL_EXT_secondary_color, GL_ARB_copy_buffer, GL_OES_read_format, GL_ARB_te
xture_mirrored_repeat, GL_SUN_multi_draw_arrays, GL_EXT_blend_equation_separate, GL_ARB_half_float_pixel, GL_EXT
_draw_range_elements, GL_EXT_polygon_offset, GL_EXT_texture_lod_bias, GL_EXT_texture_filter_anisotropic, GL_EXT_
texture_compression_dxt1, GL_SGIS_texture_border_clamp, GL_SGIS_generate_mipmap, GL_ARB_texture_rectangle, GL_NV
_texture_rectangle, GL_ARB_point_sprite, GL_EXT_packed_depth_stencil, GL_EXT_texture_compression_s3tc, GL_ARB_ve
rtex_buffer_object, GL_EXT_texture_mirror_clamp, GL_IBM_multimode_draw_arrays, GL_EXT_texture_rectangle, GL_EXT_
fog_coord, GL_EXT_texture3D, GL_EXT_subtexture, GL_ARB_window_pos, GL_EXT_point_parameters, GL_EXT_texture_env_c
ombine, GL_ARB_vertex_program, GL_ARB_texture_cube_map, GL_ARB_point_parameters, GL_EXT_compiled_vertex_array, G
L_EXT_bgra, GL_EXT_vertex_array, GL_ARB_multisample, GL_ARB_vertex_array_object, GL_ARB_draw_buffers, GL_ATI_dra
w_buffers, GL_ARB_texture_compression, GL_EXT_multi_draw_arrays, GL_APPLE_vertex_array_object, GL_ATI_texture_en
v_combine3, GL_APPLE_packed_pixels, GL_EXT_blend_func_separate, GL_MESA_pack_invert, GL_ATI_blend_equation_separ
ate, GL_EXT_blend_color, GL_NV_blend_square
17:07:10.461 [rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_langua
ge_100 is not available).
17:07:10.461 [speech.synthesis]: Spoken messages are off.
17:07:10.946 [shipData.load.begin]: Loading ship data.
17:07:15.112 [script.javascript.init]: JavaScript reset successful.
17:07:15.602 [script.load.world.listAll]: Loaded 92 world scripts:
Anarchies 2.7
assassins
AsteroidStorm 4.02

https://bb.oolite.space/viewtopic.ph ... 15#p162268 looks similar, can anyone point me there depth buffer and colors in code?

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 9:56 am
by Disembodied
Hi GHost, welcome to the boards! Unfortunately our local Brains Trust (of which I am not, I have to say, a member) seem to be drawing a blank on this one, but maybe a small *bump* might get something going ...

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 10:13 am
by Gimi
Like Disembodied, I'm no expert.
But since you mentioned that the start-up logo is blank, please try to start Oolite with the -nosplash option.

That would be oolite.exe -nosplash

It's a long shot, but worth a try while we wait for the experts to come along.

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 10:34 am
by Kaks
Minor correction: Gimi, the command line should probably be

Code: Select all

oolite -nosplash
There's no oolite.exe in linux! :)

GHost, it seems that your kms mesa driver is still leaving something to be desired.
I'd try and see if there are alternative (i.e. proprietary) drivers available for your chipset, and/or hopefully try and prod the mesa driver developers in the right direction. Failing that, I'm afraid that your only other option as far as Oolite is concerned is to revert from kms to a more mature - if somewhat slower - X driver.

Unfortunately Oolite can only work with what the OS tells it it can do.

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 10:41 am
by Gimi
Kaks wrote:
Minor correction: Gimi, the command line should probably be

Code: Select all

oolite -nosplash
There's no oolite.exe in linux! :)
:oops:
I know that! I know that! (he tells himself) and I promise myself right now I will remember that next time.
:oops:

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 1:00 pm
by Commander McLane
Disembodied wrote:
Unfortunately our local Brains Trust (of which I am not, I have to say, a member) ...
Somehow this sounds sad for somebody who is nothing but brain ... :roll:

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 1:22 pm
by Disembodied
Commander McLane wrote:
Disembodied wrote:
Unfortunately our local Brains Trust (of which I am not, I have to say, a member) ...
Somehow this sounds sad for somebody who is nothing but brain ... :roll:
Unfortunately it's more about function than about form ... :)

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 3:45 pm
by GHost
Kaks wrote:
Minor correction: Gimi, the command line should probably be

Code: Select all

oolite -nosplash
There's no oolite.exe in linux! :)

GHost, it seems that your kms mesa driver is still leaving something to be desired.
I'd try and see if there are alternative (i.e. proprietary) drivers available for your chipset, and/or hopefully try and prod the mesa driver developers in the right direction. Failing that, I'm afraid that your only other option as far as Oolite is concerned is to revert from kms to a more mature - if somewhat slower - X driver.

Unfortunately Oolite can only work with what the OS tells it it can do.
Hi.

Seems you are right, i try switch to UMS and artefacts goes away, --nosplash not change anything, i also find there buffer and colors depth setup in code and try to raise limits but no luck, seems it broken comletely on any color depth, i add bugreport to mesa developers about this - https://bugs.freedesktop.org/show_bug.cgi?id=48203 , but according to numbers of bugs open seems its very long time to wait a fix:) there is no proprietary drivers for my hardware, and also i hate such blobs:)

Also i test latest svn trunk with NEW_PALENTS enabled and it's work fine without artefacts, but it's not very stable and i have no shaders.

Re: some graphics artefacts

Posted: Tue Apr 03, 2012 7:41 pm
by Lone_Wolf
GHost,

it seems your videocard uses the classic R200 driver, and that driver will not get many updates.
One thing you could try is switching to the latest stable mesa version, 8.0.2 . It has many improvements.
What distro are you using ?

Re: some graphics artefacts

Posted: Wed Apr 04, 2012 7:02 am
by GHost
Lone_Wolf wrote:
GHost,

it seems your videocard uses the classic R200 driver, and that driver will not get many updates.
One thing you could try is switching to the latest stable mesa version, 8.0.2 . It has many improvements.
What distro are you using ?
right, it's r200, it's can work with classic and KSM depends from settings, with classic all fine, problem appears only with KMS mode. i use debian, there is no mesa8 in it for now, only in experimental and 8.0, not 8.0.2. in 8.0 i don't se anything related to r200 in release notes, i will try build in by hand a bit later, will see is it change anything.