Comment 38 for bug 96991
Revision history for this message
| Oliver Mattos (omattos) wrote Re: 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI | #38 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On some systems this "bug" causes flickering as both compiz and the 3d app are writing to the same bit of framebuffer even when there are no 3d effects going on, making the 3d app unusable. This also occurs in fullscreen mode where there is really no need for compiz to be touching the framebuffer at all.
The most visible effect of this is that most of the included screensavers flicker, the included 3d games are unusable, and apps like google earth or opengl toolkits are pretty hard to use.
Since this bug looks like it'll take quite a few releases to fix, could a little app be written to detect that a 3d app is running and turn composite off. when the 3d app quits it can restart composite? (thats what Windows does for legacy apps that communicate directly with the graphics hardware)