Aven 1.1.15 display redraws slowly on every mouse movement.

[Duncan Collis]

The display of the cave, scalebar, depth indicator, etc, is redrawn slowly (total time is only a fraction of a second, but it's slow enough to see the labels on the depth bar being written in order from bottom to top, for example) whenever the mouse is moved or when the survey is rotated or moved using the keyboard. This makes Aven extremely difficult to use and makes smooth rotation of the cave impossible.

Linux 2.6.35-23-generic i686
wxWidgets 2.8.11 (GTK+ >= 2.6)
Display Depth: 24 bpp (colour)
OpenGL 2.1 Mesa 7.9-devel
Mesa Project
Software Rasterizer
R8G8B8
Max Texture size: 4096x4096
Max Viewport size: 4096x4096
Smooth Point Size 1.000-60.000 (granularity 0.100)
Aliased point size 1.000-60.000
GL_ARB_copy_buffer GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_swizzle GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_logic_op GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_convolution GL_EXT_copy_texture GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_fog_coord GL_EXT_gpu_program_parameters GL_EXT_histogram GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_paletted_texture GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_shared_texture_palette GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_swizzle GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_3DFX_texture_compression_FXT1 GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_APPLE_object_purgeable GL_ATI_blend_equation_separate GL_ATI_envmap_bumpmap GL_ATI_texture_env_combine3 GL_ATI_texture_mirror_once GL_ATI_fragment_shader GL_ATI_separate_stencil GL_IBM_multimode_draw_arrays GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_INGR_blend_func_separate GL_MESA_pack_invert GL_MESA_resize_buffers GL_MESA_texture_array GL_MESA_ycbcr_texture GL_MESA_window_pos GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_light_max_exponent GL_NV_packed_depth_stencil GL_NV_point_sprite GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_NV_texture_rectangle GL_NV_vertex_program GL_NV_vertex_program1_1 GL_OES_read_format GL_SGI_color_matrix GL_SGI_color_table GL_SGI_texture_color_table GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays

[Duncan Collis]

I reverted to 1.1.13 - still the same problem. I think that upgrading from Ubuntu 10.4 to 10.10 may have broken something, although Aven is the only application I've noticed not working properly. Additionally, if Aven is run from the command line, the following error is produced:

The program 'aven' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch? (invalid parameter attributes)'.

(Details: serial 3731 error_code 8 request_code 73 minor_code 0)

[Olly Betts]

The reason this is slow is that your 3D rendering is happening in software ("Software Rasterizer" on line 6 of the info you pasted).

Nothing has changed in Aven in regard to this, so it's probably the video card drivers. You probably wouldn't notice unless applications are using 3D.

You can check what graphics hardware you have with:

sudo lshw|more

Aven should really avoid pointlessly redrawing on a non-dragging mouse move though (unless the mouse moves over a station and the measuring line needs to be drawn/undrawn, and even then we should be able to avoid redrawing the whole scene, and just draw the line on top of the existing image, after saving a copy of what is underneath.

[Duncan Collis]

I think this is the relevant bit:

*-display UNCLAIMED

description: VGA compatible controller product: 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter vendor: Silicon Integrated Systems [SiS] physical id: 0 bus info: pci@0000:01:00.0 version: 00 width: 32 bits clock: 66MHz capabilities: pm agp agp-3.0 vga_controller cap_list configuration: latency=0 resources: memory:c0000000-c7ffffff memory:cfee0000-cfefffff ioport:bc00(size=128)

Redrawing takes place on all mouse movements over the viewport, including non-dragging moves without a measuring line.

I'll go and read some Ubuntu forums to see if I can find out whether there were any changes to the video card drivers in 10.10...

[Olly Betts]

OK, there are two issues here.

The "software rasteriser" issue is one - perhaps we should throw up a warning box the first time we're run and see that (and clear the flag when we're run and don't see it, so upgrading from software -> hardware -> software reissues the warning.

The other is the needless redraws on every mouse movement, which we should avoid - even when running with hardware acceleration it would improve responsiveness to redraw less often.

[Olly Betts]

The needless redraws are fixed by r3637.

[Olly Betts]

My newer laptop also shows "Software Rasterizer", but it's fast so presumably actually using hardware acceleration (or perhaps it's just sufficiently quick not to matter). But that means that checking for that string isn't a reliable way to decide whether to warn the user.

I can't seem to find a reliable way to check if hardware acceleration is available, and in fact it's really more of a sliding scale - some operations may be hardware accelerated while others are still implemented in software - so perhaps that idea isn't really a good one.

I've opened a new ticket (#22) for the remaining related issue of slicker updating of the measuring line (by saving the background rather than redrawing it, or similar) and so I'll close this ticket now.