Announcement

Collapse
No announcement yet.

Wine's Shader Compiler Now Handles... Reflections

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

  • Wine's Shader Compiler Now Handles... Reflections

    Phoronix: Wine's Shader Compiler Now Handles... Reflections

    There's a new unstable version of Wine available on this Friday. There's only a few prominent changes, but among them is finally having reflection support in its Direct3D shader compiler...

    http://www.phoronix.com/vr.php?view=OTE3NQ

  • #2
    ...

    Phoronix, please, you're missing the most important feature of this wine.
    It can now use natively sRGB textures (if the driver supports it) which means, that games using sRGB textures are not going to be disproportionally slow but would run just as good as in Windows.

    Comment


    • #3
      Am I the only one who things that the wine developers have their priorities screwed up? How about making it actually run real useful and necessary software before messing with implementation of pointless graphical features that nobody really needs?

      Comment


      • #4
        Originally posted by droidhacker View Post
        Am I the only one who things that the wine developers have their priorities screwed up? How about making it actually run real useful and necessary software before messing with implementation of pointless graphical features that nobody really needs?
        I guess it's because their userbase mostly votes for games:

        http://appdb.winehq.org/votestats.php

        Comment


        • #5
          Yes Linux is good for games, especially thanks to WINE. Don't you know? This is where people flee when bashed by "professionals" assigning linux to server, or when they are tired of windows, tired of viruses, tired of companies not releasing linux native version.

          In fact, and sadly, AMD graphics card linux users make some portion in windows gaming segment.

          And they do not need .net, it seems .net actually started to walk here on his own in form of Miguel.

          Whats left,.. visual basic?

          Comment


          • #6
            What kind of reflection are we talking about here?

            Mirrors or Reflection in computer programming.

            Comment


            • #7
              Looks like this is referring to "code" reflection not the graphical effect (the article could have been clearer on that...)

              The Wine developers implemented methods needed for the ID3D11ShaderReflection interface, which returns information about a shader.

              Comment


              • #8
                The article could only have been clearer about that if Michael had understood it correctly.

                Comment


                • #9
                  what ever happened to that legitimate dx10 and dx11 implementation into wine? if thats still happening, the wine developers should seriously ditch the open gl conversion into dx and focus more on the functionality of wine itself. seriously, all wine needs is a REAL dx and everything should be relatively easy from there on, making small tweaks here and there for any program or game that doesn't work for reasons irrelevant to graphics.

                  Comment


                  • #10
                    Originally posted by schmidtbag View Post
                    what ever happened to that legitimate dx10 and dx11 implementation into wine? if thats still happening, the wine developers should seriously ditch the open gl conversion into dx and focus more on the functionality of wine itself. seriously, all wine needs is a REAL dx and everything should be relatively easy from there on, making small tweaks here and there for any program or game that doesn't work for reasons irrelevant to graphics.
                    Did you mean using the the Gallium 3D State tracker for DX10/11?

                    I think that that would be the best way to go about it.

                    +1 To that idea

                    Comment


                    • #11
                      The problem is that WINE is not an Linux only program

                      Comment


                      • #12
                        Originally posted by droidhacker View Post
                        Am I the only one who things that the wine developers have their priorities screwed up? How about making it actually run real useful and necessary software before messing with implementation of pointless graphical features that nobody really needs?
                        You clearly have a firm grasp of how open source development works.

                        Ask a bunch of random people what they want from an open source project and you'll get a diverse set of opinions about what should be prioritized. But you know what? The persons submitting patches or other contributions get their itches scratched.

                        Comment


                        • #13
                          I thought the removal of Win9X tests was interesting - almost sounds like Wine 1.2 is the last version to attempt to support bug-for-bug compatibility with Win9X.

                          I'm sure there's a lot of people who will want to run old/archaic/bug-dependent Windows 9X software in the future (even just for retro purposes), so I thought these people will be left with maintaining the 1.2 branch until ReactOS has equivalent support. Did some googling and found this though:
                          http://www.mail-archive.com/wine-dev.../msg67102.html
                          Right now all the test results that differ for win9x versions are marked
                          as broken(), i.e. Wine intentionally makes an effort to NOT replicate it.
                          So removing checks for (broken) results will change nothing.

                          Comment


                          • #14
                            Originally posted by grantek View Post
                            I thought the removal of Win9X tests was interesting - almost sounds like Wine 1.2 is the last version to attempt to support bug-for-bug compatibility with Win9X.

                            I'm sure there's a lot of people who will want to run old/archaic/bug-dependent Windows 9X software in the future (even just for retro purposes), so I thought these people will be left with maintaining the 1.2 branch until ReactOS has equivalent support. Did some googling and found this though:
                            http://www.mail-archive.com/wine-dev.../msg67102.html
                            I wanted to ask some questions when this came up on the mailing list, but kept quiet because there was some controversy. Now that that's over, can someone explain what this really means?

                            What is the test suite used for? Why were tests marked broken for Win9x? What does that mean for Win9x compatibility?

                            Comment


                            • #15
                              Originally posted by zeealpal View Post
                              Did you mean using the the Gallium 3D State tracker for DX10/11?

                              I think that that would be the best way to go about it.

                              +1 To that idea
                              yes, but is a know fact that most wine devs use nvidia (and the binary blob) (and this is the best to work with wine). sadly, nvidia does not support Gallium 3D, so it is a long shot to adopt that, at least for now.

                              Comment

                              Working...
                              X