Announcement

Collapse
No announcement yet.

Wine 1.7.20 Finally Released, Brings X11 Drag & Drop Fixes

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

  • Wine 1.7.20 Finally Released, Brings X11 Drag & Drop Fixes

    Phoronix: Wine 1.7.20 Finally Released, Brings X11 Drag & Drop Fixes

    Wine 1.7.20 was delayed an extra two weeks due to outside scheduling conflicts, but that new release is now available. While the release schedule was twice as long, the release isn't too particularly exciting...

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

  • #2
    on my case steam still working with this wine version



    Comment


    • #3
      Originally posted by pinguinpc View Post
      on my case steam still working with this wine version



      I think the Wine devs would be in hot water if they even had a beta release in which Steam *didn't* work. Of all titles I'm sure Steam will be the last program to break.


      That said, there's been quite a few months of "not really exciting" lately.

      Comment


      • #4
        Originally posted by dffx View Post
        That said, there's been quite a few months of "not really exciting" lately.
        Depending who you talk to... In this release; ntdll: Fix LdrLockLoaderLock()/LdrUnlockLoaderLock() on 64bit is great for those who were affected by the bug this patch fixes; 64bit VSTs crashing under certain conditions [easy to trigger with some out-of-tree wine patches]. and it wouldn't just not just _some_ plugins, it would crash ANY x64 plugin... So it's kind of a big deal, that this problem is now solved upstream. [i've been using that patch for weeks, but previously had to hack around the problem].

        I guess by "not really exciting" you probably mean no CSMT yet, eh?

        Comment


        • #5
          Originally posted by ninez View Post
          Depending who you talk to... In this release; ntdll: Fix LdrLockLoaderLock()/LdrUnlockLoaderLock() on 64bit is great for those who were affected by the bug this patch fixes; 64bit VSTs crashing under certain conditions [easy to trigger with some out-of-tree wine patches]. and it wouldn't just not just _some_ plugins, it would crash ANY x64 plugin... So it's kind of a big deal, that this problem is now solved upstream. [i've been using that patch for weeks, but previously had to hack around the problem].

          I guess by "not really exciting" you probably mean no CSMT yet, eh?
          I'm personally not super concerned about CSMT -- as I recall there are a couple of games that I play that don't run well with the CSMT patch. I haven't played with it for quite a few versions. Do you know if it works with the latest version? Last I heard you had to use an older version to use it.

          But no, I'm just talking about overall compatibility improvements, or any progress towards that most elusive and distant of goals, namely increased DX10/11 support.

          Of course I greatly appreciate all of the bug fixes, though I don't believe any of them effected me directly.

          Comment


          • #6
            I'm really sad about the latest Wine versions because they can't play my Neverwinter Nights install from GOG (it actually couldn't install it either, but I worked around that by using Windows to install to a USB drive). It starts the launcher just fine, but it crashes right after clicking "play"

            This makes me sad because two years ago, Wine played the Disk Install version BETTER (faster, etc) than my Windows install did.

            Comment


            • #7
              Originally posted by Daktyl198 View Post
              I'm really sad about the latest Wine versions because they can't play my Neverwinter Nights install from GOG (it actually couldn't install it either, but I worked around that by using Windows to install to a USB drive). It starts the launcher just fine, but it crashes right after clicking "play"

              This makes me sad because two years ago, Wine played the Disk Install version BETTER (faster, etc) than my Windows install did.
              Why not perform a bisect?

              Comment


              • #8
                Originally posted by Daktyl198 View Post
                I'm really sad about the latest Wine versions becBeen beause they can't play my Neverwinter Nights install from GOG (it actually couldn't install it either, but I worked around that by using Windows to install to a USB drive). It starts the launcher just fine, but it crashes right after clicking "play"

                This makes me sad because two years ago, Wine played the Disk Install version BETTER (faster, etc) than my Windows install did.
                Ummm.. NWN? Just use the native binary: http://icculus.org/~ravage/nwn/

                Been out for a loooooong time....

                Comment


                • #9
                  Originally posted by bakgwailo View Post
                  Ummm.. NWN? Just use the native binary: http://icculus.org/~ravage/nwn/

                  Been out for a loooooong time....
                  First things first: I don't have the CDs. My dad gave them away a while ago (hence why I bought it on GOG.com)

                  I've done the method of:
                  - Install on Windows
                  - Copy installed files over to Linux partition
                  - overwrite files with Linux client

                  And it works, but there's no sound (neither in game or in menus) and the movies don't work
                  I actually tried this method first, before resorting to Wine (I wasn't aware this method existed the last time I played NWN on Linux) but since I really, REALLY wanted sound...

                  Originally posted by Rexilion View Post
                  Why not perform a bisect?
                  I have no idea what a bisect is, but I assume it's a form of debugging. Honestly, it's less work for me to boot into Windows and play. I just remember getting more performance on Linux+Wine at higher resolutions than on Windows (which I thought was funny).

                  Comment


                  • #10
                    Originally posted by Daktyl198 View Post
                    And it works, but there's no sound (neither in game or in menus) and the movies don't work
                    The movies not working is by design, it's mentioned in the documentation. Probably bink playback wasn't supported back then under linux. (By the way, it doesn't work under Vista/7/8 either, only under XP and earlier). Having no sound, however, is a real problem and must be connected to miles. I remember having problems with NWN because of miles, crashing or something like that. There was a workaround to exclude the binary that comes with the client and after that everything was OK. If you're interested making it to work, try googling about this problem, the solution may as well work for your no sound issue as well.
                    Last edited by tarceri; 06-14-2014, 10:13 AM. Reason: Fix quote tag

                    Comment


                    • #11
                      Originally posted by Daktyl198 View Post
                      I have no idea what a bisect is, but I assume it's a form of debugging. Honestly, it's less work for me to boot into Windows and play.
                      He's basically saying that you should look for the commit that broke that game for you.
                      Basically you know the last date when it worked, and you know that now it doesn't.
                      So you try with a wine build at half in between those dates.
                      Depending on the result, you do the same of the right half or the left half and so on, till you find the bad commit.

                      Comment


                      • #12
                        Originally posted by Daktyl198 View Post
                        I'm really sad about the latest Wine versions because they can't play my Neverwinter Nights install from GOG (it actually couldn't install it either, but I worked around that by using Windows to install to a USB drive). It starts the launcher just fine, but it crashes right after clicking "play"

                        This makes me sad because two years ago, Wine played the Disk Install version BETTER (faster, etc) than my Windows install did.
                        Its strange on my case i have GOG version and works without problem



                        But I use nvidia card with lastest propietary drivers with this command

                        __GL_ExtensionStringVersion=17700 WINEDEBUG=-all wine steam
                        Sometimes also need rename movies folder for work

                        Last edited by pinguinpc; 06-14-2014, 08:09 AM.

                        Comment


                        • #13
                          Originally posted by geearf View Post
                          He's basically saying that you should look for the commit that broke that game for you.
                          Basically you know the last date when it worked, and you know that now it doesn't.
                          So you try with a wine build at half in between those dates.
                          Depending on the result, you do the same of the right half or the left half and so on, till you find the bad commit.
                          It's technically not debugging I think. Say, that for example, wine 1.7.12 worked and wine 1.7.13 failed. Then you create a clone of the wine tree and do:

                          git bisect start v1.7.13 v1.7.12
                          Now, rebuild (configure, make, make install) and run the app each time. If the app succeeds

                          git bisect good
                          if the app fails

                          git bisect bad
                          Eventually git will say something like:

                          First broken commit <long value here>

                          Where <long value here> is change between v1.7.13 and v1.7.12. You could report this to the wine developers and view the difference. On some occassions (if you bisect early) you could go to the latest version and revert this commit and see if this fixes the issue:

                          git revert <long value here>
                          Developers like working on the latest version of their software. So a fix in the latest version (a revert in this case) to showcase the problem will definitly get their attention.

                          Comment


                          • #14
                            Originally posted by dffx View Post
                            I'm personally not super concerned about CSMT -- as I recall there are a couple of games that I play that don't run well with the CSMT patch. I haven't played with it for quite a few versions. Do you know if it works with the latest version? Last I heard you had to use an older version to use it.

                            But no, I'm just talking about overall compatibility improvements, or any progress towards that most elusive and distant of goals, namely increased DX10/11 support.

                            Of course I greatly appreciate all of the bug fixes, though I don't believe any of them effected me directly.
                            I'd be happy if they supported the DX9 state tracker. I have tried CSMT on my laptop and it makes little difference. It's probably better with a really powerful CPU, which my laptops i3 is not. The move to support DX10/11 would probably bring even further degradation of performance. Something more dramatic needs to be done to go that route.

                            Comment


                            • #15
                              I was excited when he mentioned the drag&drop functionality was finally fixed, so I updated Wine... it's still broken
                              I use Wine to run Notepad++ for development, but recently drag&drop stopped working, so I had to add entry to dolphin's "Open With" context menu, unfortunately that's dependent on the extension (which I could also add the option for), so for non-php files I press Shift+F4 to bring up a terminal and type "npp file" (I have an alias for it in ~/bin/).

                              Comment

                              Working...
                              X