https://bugs.winehq.org/show_bug.cgi?id=44315 Chris <Chris.Samberg(a)Gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Chris.Samberg(a)Gmail.com --- Comment #1 from Chris <Chris.Samberg(a)Gmail.com> --- The problem is affecting me as well. Normally I get around 40-60 FPS on Windows but now I get less than 25 FPS in Wine. CPU: AMD FX-8370 Memory: 32 GB 1600MHz DDR3 GPU: nVidia GTX 1080 Ti / v384.98 Drivers Somewhat unrelated but may be worth noting: Guild Wars 2 has had problems with older AMD CPUs given that they don't have simultaneous multithreading (SMT). AMD's newer Ryzen CPUs and most of Intel's CPUs have SMT. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #3 from Chris <Chris.Samberg(a)Gmail.com> --- I'm looking into the issue right now. I'm sure Mr. Bugs will need more information on the issue, but I'll ask for some in the meantime. Run these both in the terminal while you play Guild Wars 2: - Wine Terminal output: "wine /path/to/Guild-Wars-2.exe > wine-output.txt" - nVidia GPU usage: "nvidia-smi -l 2 > gpu-usage.txt - CPU usage: Install sysprof and monitor wineserver and Gw2.exe. Take a picture with Shutter and upload that as an image. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #5 from Henri Verbeet <hverbeet(a)gmail.com> --- (In reply to Matteo Bruni from comment #4) It's a bit awkward to have this as a bug against the Wine product though, since it basically amounts to "D3D performance could be better". Wine never had those hacks—and for good reason—so GW2 performance in Wine shouldn't be any worse than it ever was. (If it is, please do a regression test.) At the same time, it doesn't seem al that likely that Staging would be willing to take this as their bug and work on bringing those hacks back in an acceptable form. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #7 from Ganni87 <jonfarr87(a)gmail.com> --- (In reply to Henri Verbeet from comment #5) Unfortunately the performance loss is very much noticeable especially when you play the same game regularly for over 5 years. As I've mentioned in my report, the rest of the games I play weren't affected. If there's a way to apply this hack manually to modern Wine versions I wouldn't mind building the binaries myself. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Anders Dahlberg <dahlberg(a)lysator.liu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dahlberg(a)lysator.liu.se -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 mrdeathjr28(a)yahoo.es changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28(a)yahoo.es -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #10 from Ganni87 <jonfarr87(a)gmail.com> --- Tested the game using Wine Staging 2.21 + PBA / https://github.com/acomminos/wine-pba The usual place I test the game at came back to an 80+ fps (as it was with 2.0 Staging), in other areas however it has improved by at least 5-10 fps and more importantly the fps drops are much less. No graphical errors occurred. This was done using the 32bit version of the game. Once I figure out how to build a WoW64 version of Wine I will be able to test it a lot more. Overall I'm satisfied with such results already. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 duozerk <ben(a)tokidev.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ben(a)tokidev.fr --- Comment #12 from duozerk <ben(a)tokidev.fr> --- It seems this issue also occurs with The Witcher 3 and Kingdom Come: Deliverance (see bug #44682), that is: great perfs on 2.21-staging, much worse perfs in 3.3 and 3.3-staging, and the issue seems to be fixed (mostly) when applying wine-pba on top of 3.3-staging. Both apps are launched using wine64. I've taken the liberty of linking both games, and Guild Wars 2, to this ticket. As per your question, for me at least, GPU usage (as seen through nvidia-settings) in Kingdom Come: Deliverance appears to be around 65% (it hovers between 60 and 70). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Buffer maps cause CPU-GPU |Buffer maps cause CPU-GPU |synchronization (Guild Wars |synchronization (Guild Wars |2) |2, The Witcher 3) CC| |joseph.kucia(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #15 from mrdeathjr28(a)yahoo.es --- (In reply to duozerk from comment #14) If you want more can follow this theme here https://github.com/acomminos/wine-pba/pull/26 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Daniel Oom <oom.daniel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oom.daniel(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 caleb(a)phobeus.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caleb(a)phobeus.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #16 from Shmerl <shtetldik(a)gmail.com> --- I tested Wine pba with regular Wine - it doesn't really improve performance much for the Witcher 3 for example. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #18 from Shmerl <shtetldik(a)gmail.com> --- (In reply to Kai Krakow from comment #17) You can fix rendering with PBA by increasing heap sizes. See: * https://github.com/acomminos/wine-pba/issues/46#issuecomment-375942122 * https://github.com/acomminos/wine-pba/issues/47 Performance is still bad though. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Freso <bugs.winehq.org(a)freso.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.winehq.org(a)freso.dk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #20 from Shmerl <shtetldik(a)gmail.com> --- Is there any progress with this? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #22 from Shmerl <shtetldik(a)gmail.com> --- Regular Wine performs quite badly for me with wined3d, GPU is underutilized so it doens't look like a staging related issue, but may be staging performs even worse. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sr-tream(a)yandex.ru --- Comment #24 from Matteo Bruni <matteo.mystral(a)gmail.com> --- *** Bug 44638 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #26 from Shmerl <shtetldik(a)gmail.com> --- I tested esync - it didn't improve framerate for TW3 for me: https://i.imgur.com/4foGfC0.jpg -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #28 from Shmerl <shtetldik(a)gmail.com> --- (In reply to Zebediah Figura from comment #27) Got it, thanks! Is there some list of games known to benefit from it? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Andrew Wesie <awesie(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie(a)gmail.com --- Comment #30 from Andrew Wesie <awesie(a)gmail.com> --- I was unable to reproduce the performance regression between wine-staging-2.21 (CSMT enabled) and wine-staging-3.14, with: Guild Wars 2 Intel i5-4690 AMD Radeon R9 290 (with Mesa 18.0.5) Is this only an issue with NVIDIA cards / driver? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #32 from mirh <mirh(a)protonmail.ch> --- OP had mentioned 2.21-staging *plus pba* to be the 'golden' release in comment #10, to be fair. If you can't test it otherwise, 2.0-staging was the last good one. Also for the records of any nvidia user: 390.87 and 396.54 fixed a long standing important performance regression (just to further mess bisecting, yay!) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #33 from mirh <mirh(a)protonmail.ch> --- https://www.reddit.com/r/linux_gaming/comments/9fko3n/guild_wars_2_with_win… Friendly reminder pba can give you a 50% performance boost, in GW2 with nvidia cards. And Kai (the only one reporting it was faulty on nvidia) never got back to test it with the right params. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #35 from mirh <mirh(a)protonmail.ch> --- Pba was originally created by comminos for World of Warcraft actually. (and if I really had to say it: I think it's almost basically the only obstacle for wined3d for sacred "dxvk level" performance) My theory was that people were reporting "different results" because GL_ARB_buffer_storage is bugged to hell on radeon/mesa. But comment 17 of yours (contrarily to others, and my narrative, duh) claimed even for nvidia pba sucked. After this last testimony it makes for *a lot* of improvement though, I am really really wondering whether you couldn't have done something wrong yourself instead. If you could re-check.... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #37 from mirh <mirh(a)protonmail.ch> --- Idk, maybe we could CC Zebediah or Alistair? Anyway, latest pba everybody seems to refer to is one of these https://gitlab.com/users/Firer4t/projects For other references, maybe this could be of help? https://github.com/Tk-Glitch/PKGBUILDS/tree/master/wine-tkg-git -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #39 from Zebediah Figura <z.figura12(a)gmail.com> --- Andrew Comminos' "wine-pba" patchset is hugely invasive, completely unmaintained, difficult to understand and in an area that neither Alistair nor I have more than passing knowledge of. Put simply, the maintenance burden is too much for us to accept it into Staging. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #41 from Kai Krakow <kai(a)kaishome.de> --- It looks like pba requires inclusion of many (if not all) d3d staging patches - which includes the deferred context patches. Apparently, these also depend on the nvapi patches which is a no-go if you want to allow using dxvk: While it works, it slows dxvk down because it has to deal with command streams in games then (resulting from nvapi) and it cannot do so and complains loudly. There is no support for this in Vulkan so it's unlikely to be supported in dxvk any time soon. But: If someone would work on removing the nvapi dependency from the deferred context patches, I would work on importing the pba patches into my wine-proton branch and into my wine-gaming branch. I think even without pba, the deferred context patches could be a benefit. What I don't like about the pba patches is that it requires to manually adjust the heap space. Thanks to Fireat, at least this can be done with environment variables. The next step would be to make it more automatic. I would opt-in to work on such a patch if the above issues with nvapi and other dependencies are fixed. But I'm far far away from understanding how pba integrates with the rest of the wine d3d. It is also difficult to follow the individual changes that are done with the various wine branches that integrate pba because most of the time these are an undefined collection of various staging and pba patches squashed together into one single, huge patch committed to the repository. This shouldn't be done if you want others to also work on your branches. It also prevents from reworking the individual commits to integrate better with wine staging and refactor them to be less intrusive. This really needs some love and work. Currently, I rebased proton to wine-3.16 which was a lot of headache work due to the vulkan fullscreen hacks not applying cleanly. But the result is very rewarding: Shadow of Tomb Raider went from 19 fps or 31 fps in my system, and a lot of other bugs related to focus-out events (icon-sized game when focusing back in, game freezes) and gaming windows doing full-screen are fixed with that. BTW: Thanks a lot to all the guys working on the official proton wine branch and their individual own wine branches: You have done really great work, I want to mention Zeb, Andrew and Aric especially here for their work on threading improvements, input improvements (with improved force-feedback) and audio improvements. The branch is here if someone is interested (but it's not to be used as a stand-alone wine prefix, it's for integration with proton because it includes the steam client hacks): https://github.com/kakra/wine/releases/tag/wine-proton_3.7-3.16-unofficial-1 BTW: I don't think there's a chance to get pba upstreamed into wine any times soon without the inter-dependencies with wine-staging being resolved and making the changes to the code more easy to follow. But this only means we should work on it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #43 from Kai Krakow <kai(a)kaishome.de> --- (In reply to Zebediah Figura from comment #42) This is good news and makes me want to experiment with this. And yes, I see this a lot with Git... Parts of function bodies may end up in the wrong function after merge due to very similar structure of nearby functions, especially with rerere enabled. A solution here is to refactor out the similarities into helper functions or move the invasive patch into its own file and just reference that with a function call. I found that meld is a very nice tool to help with that. I used kdiff3 before which is very convenient because it does a lot of stuff automatically but it is often also very wrong with its decisions. The meld tool was which finally enabled me to rebase the fullscreen hacks properly and discover that actually one git revert was missing to add back in what was refactored out before. I'll look into it and try to understand what it does but I'm not sure if I'll be successful with it because I lack the time to deeply work into the wine code and DX in general. I think I only got a very small glimpse of that while I rebased proton 3.7 to wine 3.16. Maybe we can start with adjusting the code to no longer show these rebase conflicts - but this is probably where my help would end currently. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #45 from Kai Krakow <kai(a)kaishome.de> --- Okay, I've updated my proton branch with PBA and it's impressive how far it has come: The Witcher 3 looks a bit different (nothing wrong but subtly different) than with DXVK but it plays exceptionally well with it (except some intermittent freezes after scene changes). I've then added the deferred contexts patches but needed to resolve some conflicts - but in the end it worked. I've successfully run Path of Exile with this but there are very visible occasional freezes and very inconsistent FPS. But at least it works. Dynamic resolution kicks in very often, this almost never happens with DXVK. I've also tried Shadow of Tomb Raider which looks very strange with WineD3D. It reminds me of the early days playing Witcher 3 with WineD3D with polygons sticking out of models, parts of models completely missing, and polygons flickering across the whole scene (but without the performance hit that could be seen in Witcher 3). The benchmark shows it's 48% CPU bound (vs. 12% with DXVK), with about half the avg FPS. Loading times without DXVK are a lot longer - I mean really a lot (cold shader cache). Here's my branch (to be used as Proton drop-in): https://github.com/kakra/wine/releases/new?tag=wine-proton_3.7-3.16-unoffic… Thanks to Zeb and Firer4t for the tips on patches dependencies, and mirh for helpful links. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 --- Comment #47 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to mirh from comment #46) Perhaps you should take up your profiler and find out. Remember that everyone here is working in their spare time—or, if they are being paid to work, they are working on specific things. Complaining that they are not working on the parts of D3D that you want to be worked on, does more harm than good. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #50 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-6.5? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

https://bugs.winehq.org/show_bug.cgi?id=44315 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |2.1 Keywords| |Abandoned? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.