Quoting: GuestAnd what about Paladins? It worked fine on Wine 6 months ago, is still working?

Patch 0.40 appears to have introduced an anti-cheat system which does not work at all in Wine as of right now: https://bugs.winehq.org/show_bug.cgi?id=42172 [External Link]

View this comment - View article - View full comments

Not to be too pedantic about it but Wine Staging is where all the experimental, not-ready-even-for-development patches go, like the one patch that removes the 32GB RAM limit for The Witcher 3.

Wine Development is where patches go before they finally end up in the stable version of Wine.

Basically it's like this:

Wine Staging -> Wine development -> Wine stable

Speaking from observation, of course :)

View this comment - View article - View full comments

Quoting: Avehicle7887Staging 2.3 has just been released in PPA Repos. Unfortunately performance in Guild Wars 2 is still 15-20fps less than 2.0 Staging. Meanwhile in Crysis Warhead there's 2-3 FPS more in Wine 2.3.

It's also available in the official Arch repos as well :D

View this comment - View article - View full comments

Quoting: Shmerl

Quoting: JudasIscariotWitcher 3 on Windows has support for the Xbox 360 controller. Have you been successful in getting that to work at all?

I don't have a controller to test at present unfortunately. Feel free to run some tests. Let me know if you need help with building Wine with all needed patches to run it.

FYI: To run TW3 you don't need the complicated WoW64 build, which requires using something like lxc container, and running 32-bit build twice. You can simply build 64-bit Wine with patches from staging and buffer pool hack.

Well, I use Arch's PKGBUILD which builds WoW64 Wine for me anyways so I don't have to worry about all that :) I only asked about controller support because the usual workaround (i.e. install x360ce in a prefix, dump some files next to the game's executable) does not work with purely 64-bit games for a number of reasons, the main one having to do with certain dotnet versions just not working in 64-bit prefixes.

I was hoping that the game may see the controller somewhat but perhaps just needs a winetrick or two...

View this comment - View article - View full comments

Quoting: Nouser64 GB is more memory than anyone will ever need.

For the next 5 years :P

View this comment - View article - View full comments

Quoting: Shmerl

Quoting: qptain NemoFantastic. Are there any non-graphical issues or does everything function as it should?

So far I didn't notice any non graphical issues.

Witcher 3 on Windows has support for the Xbox 360 controller. Have you been successful in getting that to work at all?

View this comment - View article - View full comments

Quoting: imdan12Please test Overwatch on Wine to see if it is playable.

It's not playable just yet as not all of the patches by Andrew Wesie have made it into Wine as of right now.

View this comment - View article - View full comments

I went with 32 GB when building my new system as the system before that only had 4 GB of RAM...in 2017 :P

I run games in Wine quite often and with DX11 support getting better with each Wine release, I want to ensure I don't have to worry about memory issues. Also, I run GNOME3 and that isn't the lightest of DEs.

The only bottleneck I may have at the moment is my 970 GTX card but it seems OK for now.

View this comment - View article - View full comments

Quoting: sr_ls_boyAnyone having problems during compilation? This is with the patches.

make[1]: Entering directory '/home/sr_ls_boy/src/wine/build64/dlls/concrt140'
../../tools/winegcc/winegcc -o concrt140.dll.so -B../../tools/winebuild -m64 -fasynchronous-unwind-tables -shared ../../.././dlls/concrt140/concrt140.spec \
../../libs/port/libwine_port.a -Wl,-rpath,/usr/lib64 -L/usr/lib64 -Wl,-rpath,/lib64 -L/lib4
../../.././dlls/concrt140/concrt140.spec:349: function '_CurrentScheduler_Id' not defined
winegcc: ../../tools/winebuild/winebuild failed
make[1]: *** [Makefile:165: concrt140.dll.so] Error 2
make[1]: Leaving directory '/home/sr_ls_boy/src/wine/build64/dlls/concrt140'
make: *** [Makefile:5982: dlls/concrt140] Error 2

Are you attempting to compile Wine Staging? Reason I ask is because it looks like this patch https://github.com/wine-compholio/wine-staging/commit/fae17cd83a1523444e93bdd9ef86a88756c5cacf [External Link] may be at fault judging by the "concrt140.spec:349: function '_CurrentScheduler_Id' not defined" error.

If so, you may want to submit a bug report to Wine HQ under the Wine Staging product...

View this comment - View article - View full comments

Quoting: GuestThanks for the information. I’d get LOOM as I remember reading great things about it back in the day, but it’s most likely a DOSbox wrap and I don’t want to spend hours fixing the config like I did for Pinball Dreams, and still end up with something I can’t play in fullscreen because it blocks alt-tab…

If we could have a universal DOSBox configuration, we would but that's impossible. You can, however, send us a message via our Support page and we can see what needs to be tweaked in order to reduce the time needed to tweak and configure a game. We won't be able to remove that step in its entirety but we can at least try to reduce the hassle :)

View this comment - View article - View full comments