Announcement

Collapse
No announcement yet.

kwin discontinued ?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    s3tc *should* work with r300g if you install libtxc-dxtn, but only in 32 bits, and it's a shady legal situation.

    It does not work at all on r600c/g.

    The short answer is that open drivers are not allowed to support this stuff although they could trivially implement it.

    Comment


    • #32
      Originally posted by pingufunkybeat View Post
      s3tc *should* work with r300g if you install libtxc-dxtn, but only in 32 bits, and it's a shady legal situation.

      It does not work at all on r600c/g.

      The short answer is that open drivers are not allowed to support this stuff although they could trivially implement it.
      Does anyone have a link to the source for libtxc-dxtn? I think I might be able to help here, but every link so far seems to be dead.

      Additionally, wasn't there a discussion on a S3TC "passthrough" implementation, where compressed textures are uploaded directly (and legally) to the hardware and online compression is allowed to fail? IIRC, this should be conforming to the OpenGL spec.

      Comment


      • #33
        KDE is totally unusable on ati for me, with oss and fglrx. Its just so laggy and unresponsive, while gnome is fine. (ati hd2600)

        Comment


        • #34
          Originally posted by agd5f View Post
          We are working to improve the performance of the open source driver, but at the moment we can't match fglrx.
          One thing that stands out with fglrx driver is that the performance hit going from 720p to 1080p is very small (10%):

          http://www.phoronix.com/scan.php?pag...00g_q410&num=1

          On the other hand, r600g performance hit is as large as 40% going from 720p to 1080p (it's understandable because 1080p screen has twice as much pixel as 720p). I'm curious to know if fglrx uses different optimization at 1080p resolution.

          Comment


          • #35
            The proprietary driver shares code across OSes, so it's highly optimized compared to the open source driver. For example, tiled surfaces help a lot if the code is doing a lot of texture lookups, especially on cards with more limited memory bandwidth. Some of the low hanging optimizations for the open source drivers for 6xx+ hardware:
            - pageflipping (will show up in 2.6.38)
            - tiling (initial render buffers implemented already, advanced tiling modes and texture tiling needs some minor changes to the ddx and r600g and requires kernel 2.6.37)
            - fast clears
            - hyperz
            - optimizing constant buffer updates

            Comment


            • #36
              That sounds like there are many optimisations coming our way!

              Do you mean that texture tiling is coming with 2.6.37?

              w00t w00t!

              Comment


              • #37
                Originally posted by BlackStar View Post
                Does anyone have a link to the source for libtxc-dxtn? I think I might be able to help here, but every link so far seems to be dead.
                Try this:

                http://cgit.freedesktop.org/~cbrill/libtxc_dxtn/tree/

                And some comments here:

                https://bugs.freedesktop.org/show_bug.cgi?id=31257

                It'd be great if you can help with it.

                Comment


                • #38
                  Originally posted by agd5f View Post
                  - pageflipping (will show up in 2.6.38)
                  - tiling (initial render buffers implemented already, advanced tiling modes and texture tiling needs some minor changes to the ddx and r600g and requires kernel 2.6.37)
                  - fast clears
                  - hyperz
                  - optimizing constant buffer updates
                  I'm on 2.6.37-rc5 right now, with latest mesa git. How can I try this texture tiling you mentioned? I'd be happy to test and file bugs.

                  BTW, I tried the pageflipping patches. It actually slows down XBMC main menu from 30fps (pageflipping off) to 15fps (pageflipping on), so I disabled it and reverted back all the patches (kernel and x86-video-ati).

                  Thanks.

                  Comment


                  • #39
                    well that was my question exactly; i thought i had read somewhere that libtxc-dxtn was no longer necessary for r300c, or something. i thought that maybe that was why the link was dead.

                    i have 32 bit btw, so it's no issue. if i could only get my hands on that lib, so i could try it ........

                    Comment


                    • #40
                      Originally posted by ntt2010 View Post
                      Try this:

                      http://cgit.freedesktop.org/~cbrill/libtxc_dxtn/tree/

                      And some comments here:

                      https://bugs.freedesktop.org/show_bug.cgi?id=31257

                      It'd be great if you can help with it.
                      Oh, someone mirrored it on fd.o. Great, thanks!

                      Comment


                      • #41
                        well alright i found some shady website that had the source for the lib, compiled it, move it to /usr/lib and now the game runs.

                        linux is crafty

                        Comment


                        • #42
                          Originally posted by pingufunkybeat View Post
                          Older versions of KWin (<4.5) used to force indirect rendering. I forgot the main reason, but it might have to do with driver issues.
                          Indirect rendering does not resolve any driver issues. It actually adds new issues, removes features*, and makes everything slower. If this is KDE developers' policy, then everything is starting to make sense now.

                          * You can "remove" features simply by not using them.

                          Originally posted by pingufunkybeat View Post
                          s3tc *should* work with r300g if you install libtxc-dxtn, but only in 32 bits, and it's a shady legal situation.
                          It works on a 64-bit CPU with 64-bit apps too. For it to work with 32-bit apps as well (i.e. the most closed-source games), you have to compile libdrm + Mesa libs and drivers + libtxc-dxtn with the appropriate compile flags to get the 32-bit versions of everything.

                          Comment


                          • #43
                            Open drivers have a history of crashing when direct rendering is used, though. Open Arena had the same problem, as did many other games, back in the early days of r600c. We used to run the games using indirect rendering as a workaround.

                            I agree that documenting the issue and fixing the bugs is the right way to approach this, btw.

                            Comment


                            • #44
                              KWin performance pitfalls

                              I have found that many times when KWin performs badly, it's either because of the chosen window decorator, or a misbehaving plasmoid.

                              Both are active inside KWin's compositor render loop and some are just not well written.

                              Try to create a new user on your system, and start with default window decorations and no plasmoids, then tell us if it helped

                              Comment


                              • #45
                                As far as I know, KWin runs by default some checks at the start of KDE and disable OpenGL rendering, thus use software rendering, if these checks fails. However, they added an option to the disable these checks, as sometimes, the checks failed but overall, the driver could very well do OpenGL compositing.
                                What you could try :

                                - Go into the System Settings, and go into where Desktop Effects are set up (in 4.5.X, it's in Desktop Effects). In the last tab, check the Disable Self-Test option or whatever it's called in english (I use french so don't know the exact translation).
                                - Enable the effects.
                                - In the Effects tab, unselect the Blur effect (it doesn't work anyway with ATI right now, neither with r300g nor with r600g, at least on my systems).

                                I sometimes have to fumble a bit with these settings (Enabling the effects fail with Blur but you cannot uncheck Blur before you tried at least once to enable the effects).
                                But with this, I don't have any special lag with Kwin and it works nicely, though I don't play games, so I cannot see exactly how much they're slowed down.

                                Comment

                                Working...
                                X