It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
dtgreene: Here are my two requests (which I've mentioned in other threads):

Shante and the Pirate's Curse
Guacamelee: Super Championship Turbo Edition
RE: Guacamelee

I am able to get the game running just fine but I can't for the life of me get controller support working via Wine. Getting controllers working under Wine has always been an issue for me as I can either get controller support going quickly (Super Time Force Ultra) or not at all.

If this were any other game I would let it go but with Guacamelee I really recommend playing it with a controller as the game requires multiple inputs simultaneously at times...
avatar
JudasIscariot: RE: Guacamelee

I am able to get the game running just fine but I can't for the life of me get controller support working via Wine. Getting controllers working under Wine has always been an issue for me as I can either get controller support going quickly (Super Time Force Ultra) or not at all.

If this were any other game I would let it go but with Guacamelee I really recommend playing it with a controller as the game requires multiple inputs simultaneously at times...
avatar
niniendowarrior: Have you tried using x360ce? I finished Assassin's Creed and Batman Arkham games on Wine using this for controller support.
Yes I have and no matter how much dotnet winetricks I stuffed into the prefixes it would not work :)
avatar
JudasIscariot: Yes I have and no matter how much dotnet winetricks I stuffed into the prefixes it would not work :)
avatar
niniendowarrior: This steam thread might help then.http://steamcommunity.com/app/214770/discussions/0/846960628457513544

As a side note, I'm not sure why you would need to do dotnet winetricks thing for controller support. If the game works with dotnet, then sure, but dotnet just for controller support sounds odd to me.

x360ce in particular is just running an app and configuring the controller and copying its xinput dlls into the game's install folder path.
I used dotnet because that's what the system requirements call for: http://www.x360ce.com/
Winetricks got a version bump last night: https://github.com/Winetricks/winetricks
avatar
JudasIscariot: Winetricks got a version bump last night: https://github.com/Winetricks/winetricks
avatar
niniendowarrior: I can never find the release notes for those. :-(

Anything significant?
vcrun2015 DLL issue got fixed, I believe some winetricks got 64-bit support.

Best way to get a grasp of what's changed with winetricks is to look at the most recent closed issues on its github and look for ones that were solved :)

You can also look through the commits section as Austin tends to write in human readable English so you can see what the most recent changes were :)
avatar
niniendowarrior: Speaking of Xbox 360 controller support... Judas, did you see my post on x360ce? Just hoping that it helped you get it working. :-)
I did see your post, thank you :) I'll try it and report back :)

It's just weird that you need to go through such a routine for Guacamelee when for Way of the Samurai 4, all I needed was an xinput dll and an xpadder profile in the same directory as the game's executable and everything worked fine...
avatar
niniendowarrior: dotnet just for controller support sounds odd to me.
avatar
Rixasha: It's just to run the program that creates the configuration file. I don't think I ever got it running though, no matter what I tried. In the end I wrote my own x360ce.ini by hand. I'm not sure what I based it on, because there probably isn't any documentation. But I've used it with a bunch of games since with no big issues, or at least no issues I couldn't figure out and work around. And no need for dotnet.

LEGO Harry Potter actually took a bit of a rewrite though since I wanted to play it with my daughter using xbone and x360 controllers.
Would you care to share this ini?
Game: DEADBOLT
Installer MD5:
314C13491A3ABFD6F55BE2B8C102EFF8 setup_deadbolt_2.0.0.3.exe
WineHQ AppDB link: N/A

Wine version(s) tested: Wine 1.9.5 (i686) from the multilib Arch repo.

Install notes: Requires d3dx9 and vcrun2010
How well does it run: Quite well.
Details:

Run

$winetricks d3dx9 vcrun2010

then run

$wine deadbolt_game.exe

Enjoy the game :)
Initial tests with regular Wine 1.9.6 for Grim Dawn have proven to be ineffective. Also, here's the AppDB entry for Grim Dawn: https://appdb.winehq.org/objectManager.php?sClass=version&iId=29162

With that in mind I am currently waiting for wine-gallium-nine to finish compiling before I make a proper report since I would like to see if I have to do all that nasty registry editing :/
avatar
JudasIscariot: With that in mind I am currently waiting for wine-gallium-nine to finish compiling before I make a proper report since I would like to see if I have to do all that nasty registry editing :/
avatar
Gydion: I don't think It should be needed as long as you have the 20160311 winetricks or master (which is currently the same).
I have that installed, tried the registry hack listed in that AppDB entry and I still couldn't get the game to work under regular Wine 1.9.6.

Wine-gaming-nine which is basically Wine 1.9.5-staging with the Gallium patches and some other patches added in.

In any case, the game works fine under Wine-1.9.5-staging with CSMT enabled. I need to try some tweaks and run the game under my i3 window manager as GNOME3 eats up a lot of memory and this is quite a demanding game :)
avatar
shmerl: They disabled CSMT because mainline Wine is getting it, and patching for it started conflicting with the main code.
Did WineHQ say this anywhere? Can't seem to find any source on this...
avatar
JudasIscariot: Did WineHQ say this anywhere? Can't seem to find any source on this...
avatar
shmerl: https://www.wine-staging.com/news/2016-03-21-release-1.9.6.html

Before talking about the smaller additions, there is another important announcement regarding this release. We are aware that a big group of people uses Wine Staging because of the CSMT (commandstream multithreading) patchset, and we are glad to see that there is again (slow, but steady) progress to include this feature in the development version of Wine. The whole process also has a downside though. Various design goals have been changed during the upstreaming process and we are currently not aware of any fully functional patchset, which provides all CSMT features. So far the multithreading part, which contains the actual performance improvement, is not upstream yet and the remaining patches are geting more and more incompatible. Working around all those problem (which we did in the last releases) is not possible in the long term, and we therefore decided to disable CSMT support in this release. If you depend on this feature, you should not update to Wine Staging 1.9.6. The feature might be available in future versions again, so don't forget to check the release notes.
avatar
shmerl:
>slow but steady

Great, we'll see DX11 and 64-bit support before that happens :P
avatar
JudasIscariot: >slow but steady

Great, we'll see DX11 and 64-bit support before that happens :P
avatar
shmerl: Who knows ;) We might get DX 11 support before Witcher 3 will come out for Linux as well.

64-bit support exists in Wine for quite a long time already.
Sure, and every time I see a bug report with a 64-bit prefix used, the OP gets told to use a 32-bit prefix in Bugzilla so either

a) Wine can support it but no one else wants to do so for bug reports

or

b) 64-bit support isn't as stable as 32-bit

Which is it?
avatar
shmerl: No idea. You can't use 32 bit Wine for 64 bit games anyway.
Of course not but I run a WoW64 version of Wine and I'd like to be able to file bug reports without having to resort to a 32-bit prefix.
avatar
Gydion: So, is there a coherent entry for Grim Dawn? I ask as I did not follow what everyone did or did not do to get it running.

avatar
JudasIscariot:
avatar
Gydion: Also, <i>rzip</i> is your friend. Works quite well on larger log files.
You'll get a native version of Grim Dawn before a coherent AppDB entry is made for that game :P