Announcement

Collapse
No announcement yet.

Wine 1.2 Reaches Release Candidate State

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

  • Wine 1.2 Reaches Release Candidate State

    Phoronix: Wine 1.2 Reaches Release Candidate State

    Last week we shared that Wine 1.2 was being prepared for release in June and as part of that the release candidates would start being pushed out next week. Well, it's now that time and the first release candidate of Wine 1.2 is now available...

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

  • #2
    In the full changelog for Wine 1.2 RC i found the following:


    d3dx9: Add ps_3_0 instructions parsing to the shader assembler.
    d3dx9: Shader assembler ps_3_0 support.
    d3dx9: Add missing texkill instruction parsing.
    d3dx9: Use separate opcodes for TEXLDP and TEXLDB.
    d3dx9: Check for oCx register number.
    d3dx9: Shader assembler vs_2_x support.
    d3dx9: Add some more tests on register number checking.
    d3dx9: Shader assembler ps_2_x support.


    Does this mean that Pixel Shader 3, Pixer Shader 2 and Vertex Shader 2 are supported now. I really hope so.

    Comment


    • #3
      Well nice

      1.1.44 to 1.2rc1 oblivion works again and yes graphic works very nice.

      wine 1.2 will become a impressive leader in Quality :-)

      Comment


      • #4
        Originally posted by Qaridarium View Post
        Well nice

        1.1.44 to 1.2rc1 oblivion works again and yes graphic works very nice.

        wine 1.2 will become a impressive leader in Quality :-)
        starcraft2 works nice :-) no more menue corruption and runs very fast..

        Comment


        • #5
          Wine 1.2 is indeed shaping up very nicely.

          Now, if we could get Visual Studio to run...

          Comment


          • #6
            Font antialiasing configuration through fontconfig.
            About damn time. It was easy enough to fix manually but I always thought it was silly that Wine didn't do this by default.

            Comment


            • #7
              In release announcement there is
              "This is the first release candidate for Wine 1.2. It marks the beginning of the code freeze period. Please give this release a good testing to help us make 1.2 as good as possible."

              I ask: What should be tested now if the code is frozen? Should I only look for regressions between 1.1.44 and 1.2?

              Comment


              • #8
                Originally posted by cyrex View Post
                In the full changelog for Wine 1.2 RC i found the following:


                d3dx9: Add ps_3_0 instructions parsing to the shader assembler.
                d3dx9: Shader assembler ps_3_0 support.
                d3dx9: Add missing texkill instruction parsing.
                d3dx9: Use separate opcodes for TEXLDP and TEXLDB.
                d3dx9: Check for oCx register number.
                d3dx9: Shader assembler vs_2_x support.
                d3dx9: Add some more tests on register number checking.
                d3dx9: Shader assembler ps_2_x support.


                Does this mean that Pixel Shader 3, Pixer Shader 2 and Vertex Shader 2 are supported now. I really hope so.
                The d3dx9_* dlls are utility dlls which can optionally be used by games. Among functionality this contains a shader compiler/assembler, functions create e.g. a texture from a jpg file and so on.

                At this stage our own d3dx9 is not good enough for running games and you need the microsoft versions of the dlls to run them. Note the dlls just call d3d9.dll of which we always use the Wine version. Our d3d9 has supported Pixel Shader 2 / 3 for years but this just adds some of the functionality to d3dx9.

                Comment


                • #9
                  Originally posted by cyrex View Post
                  In the full changelog for Wine 1.2 RC i found the following:


                  d3dx9: Add ps_3_0 instructions parsing to the shader assembler.
                  d3dx9: Shader assembler ps_3_0 support.
                  d3dx9: Add missing texkill instruction parsing.
                  d3dx9: Use separate opcodes for TEXLDP and TEXLDB.
                  d3dx9: Check for oCx register number.
                  d3dx9: Shader assembler vs_2_x support.
                  d3dx9: Add some more tests on register number checking.
                  d3dx9: Shader assembler ps_2_x support.


                  Does this mean that Pixel Shader 3, Pixer Shader 2 and Vertex Shader 2 are supported now. I really hope so.
                  I'm pretty sure they've all been supported for years. I think this just adds support to the built in d3dx9 dlls. Not really a big deal since the native dlls get installed by games anyway.

                  Comment


                  • #10
                    Originally posted by Chewi View Post
                    About damn time. It was easy enough to fix manually but I always thought it was silly that Wine didn't do this by default.
                    where and how do i actually avtivate font antialiasing?

                    Comment


                    • #11
                      Wow this WINE release is seriously stuffed up, I'm getting access violation errors in all my apps.

                      Comment


                      • #12
                        Sc1!

                        Does this mean the end of a 6 year old bug? http://bugs.winehq.org/show_bug.cgi?id=2467 Some say the bug is there because alpha blending was not implented.

                        Comment


                        • #13
                          Originally posted by bugmenot2 View Post
                          Wow this WINE release is seriously stuffed up, I'm getting access violation errors in all my apps.
                          It's not even done yet as it is just an RC.

                          Report the bugs you find and maybe the cause of those access violations can be identified and fixed (if truly a Wine bug and not caused by the app)

                          And are you the original bugmenot?

                          Comment


                          • #14
                            Originally posted by DeepDayze View Post
                            And are you the original bugmenot?
                            There is no original bugmenot. bugmenot is just an account that's used by people who don't want to register just to post a single message. See http://www.bugmenot.com/.

                            Comment


                            • #15
                              Originally posted by DeepDayze View Post
                              It's not even done yet as it is just an RC.

                              Report the bugs you find and maybe the cause of those access violations can be identified and fixed (if truly a Wine bug and not caused by the app)
                              The previous release of Wine 1.2 (just before the RC) worked fine on the apps I use daily and as soon as I upgraded to the RC I got those access violation errors. I downgraded and everything worked fine again.


                              And are you the original bugmenot?
                              A fellow phoronix forum member (gilboa) decided to change the password of the original bugmenot because he/she didn't like an opinion of someone else while using the bugmenot account.

                              Comment

                              Working...
                              X