Gerrit Jan Baarda <gjbaa...@xs4all.nl> (16/02/2010): > > 2 things you could try: > > - Disable direct rendering: LIBGL_ALWAYS_INDIRECT=1 blender… and see > > whether that changes anything. > > No, that doesn't help....
OK, so might be mesa-unrelated. > > - Or even switch to the vesa driver. > > Please let me know how that goes. > > Yes, that helps. I guess that you want to report a bug against your driver then (IIRC X11-related packages have some bug scripts to collect interesting data, that's why I'm not reassigning this bugreport right away). > However the vesa driver doesn't set my monitors native resolution > automatically (2x 1920x1200). I probably need to enter some more > stuff in xorg.conf. I only use vesa very occasionally (mainly for debugging purposes), so I never looked much into it, but it might just be limited. > > In case it's rather a bug in blender, there's 2.50 alpha 0 in > > experimental > > I am running unstable, and I tried the 2.5 alpha from unstable > too. The selection bug is in blender 2.5 too. Thanks for checking. > And on top of that blender 2.5 has *very* poor display performance > with the radeon driver. > > I had tried the 2.5 alpha when it was still possible to use the > fglrx driver and I don't remember display problems that time. > > My guess is that a reasonable proportion of the blender users have > modern graphics cards such as mine, so I would not recommend pushing > blender 2.5 to unstable until or the radeon driver has improved > enough or the fglrx driver support Xorg 7.5 and is installable > again. I'm not sure about the proper course of action here. Lagging behind is probably not a good idea anyway. And waiting for X stuff to improve is basically what we've been doing for years; given I don't have much hardware to test or run benchmarks, it's also difficult to draw the line and decide when something's usable enough. :( Mraw, KiBi.
signature.asc
Description: Digital signature
