[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 264259] Window content not updated after changes
From:       Thomas Lübking  <thomas.luebking () gmail ! com>
Date:       2011-01-31 23:47:59
Message-ID: 20110131234759.C55037CC79 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=264259





--- Comment #24 from Thomas Lübking <thomas luebking gmail com>  2011-02-01 00:47:57 ---
Not perfect :-(

With indirect rendering the client (in this case probably kwin, do you run any
other opengl based clients? cairo-dock or so?) doesn't access the GL hardware
directly but through the X11 server.
This has a major advantage if you're operating on a distant machine, since X
can schedule paintings etc. to lower bandwidth but also has some overhead (ie,
direct rendering is faster)

We've however had a *lot* of trouble with mesa/opensource GL drivers and direct
rendering in the past (from crashes to freezes, so your experience is actually
an "advance") - so you've likely been using indirect rendering in the past for
some blacklist or failed test and no used direct rendering - so nothing would
be lost.

In the long run you however should use direct rendering. Also v'syncing is NOT
possible with indirect rendering at all (not matter what you check in the
config dialog - it's simply not supported) as well as probably some effects or
the lanczos filter (i think glsl does not work w/o dri, but am not really sure
about this)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]