[Wine] Re: Problems with pbuffers

[agruman]

Hi,

Thanks for the fast answer :)
You are very correct that the extension is missing in the overall extension list (if im correct that you are talking about the "GLX extensions:" field).

Here is the output i get: 

Code:
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group
client glx extensions:
    GLX_ARB_create_context, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_MESA_allocate_memory, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_NV_swap_group, GLX_OML_swap_method, 
    GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_pbuffer, GLX_SGIX_swap_barrier, GLX_SGIX_swap_group, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX extensions:
    GLX_ARB_create_context, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_MESA_swap_control, GLX_NV_swap_group, GLX_OML_swap_method, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_swap_barrier, GLX_SGIX_swap_group, GLX_SGIX_visual_select_group




And from what i can tell, all that are present in "GLX extensions" are also present in "client glx extensions" but not all of the ones in "client glx extensions" are present in "GLX extensions".
Perhaps this is normal behaviour (if some need both client and server to work) i wouldnt know.

Can i do some "hack" to make pbuffer appear as present in "GLX extensions" (linux side) or is this embedded inside the binary driver somehow?
Or perhaps its possible to modify the check for this specific extension in Wine so its a bit more "liberal" (as a temporary solution for me).

I understand that the error lies within ATI's driver, but that doesnt help me much ...