Strider

2.12 Staging
Peppermint OS 7 x64
HIS R9 270 GPU
oibaf Mesa ppa
Q6600 2.40GHz CPU
8GB DDR2 1000 Gskill Ram
GA-X38-DS4 Motherboard


Game load screen is complete along with proper music but "resume game" option is listed and greyed out & cannot be accessed (unsure why it would show in the first place since I would've not been able to access game at all prior to this 2.12 staging update). Game has incomplete shaders (I guess) b/c it's about 65% dark in color gammette. Game also plays about 50% of normal speed with speed bursts randomly occurring. Couldn't test with 360 gamepad since I don't own one, but doesn't work with my Steam Controller at this time besides Strider's movements & pausing (no jumping or slashing). Sound seems 100% spot on so far. Played game with keyboard upto the point it crashed at introduction of first boss (dragon). Still thankful to see any improvements at all.

I've add pretty much the same experience as you did with Wine Staging.

Things I've noticed are:

* setting WINEDEBUG=-all makes a huge difference in performance since there are a lot of fixmes in the console
* controller is fully supported with x360ce (autoconfigured with Lutris)
* game is very unstable, it can crash at any time

This is some very good progress considering there was only a black screen at best with previous Wine versions. Hoping that further development in DirectX11 support will fix those graphical glitches and instabilities.

I don't have much knowledge of Lutris but have been looking at it since I read your reply. I couldn't understand which tab or section to place the " WINEDEBUG=-all " setting you mentioned and copied it into "System Options" tab>in the "Command Prefix" field but will have to look for better Lutris tutorials since the ones I briefly viewed seemed lacking. Thanks for the advice.

For WINEDEBUG=-all, you don't have to do anything at all, it's the default setting for Wine games (since setting it tends to increase performance). Command prefix won't work because the field is for actual commands but on the same tab, there a widget to set environment variables which would have worked as well. If you do want to enable debugging ouput, there's an (advanced) option in the runner tab "Output debugging info".

For the joypad, on the same tab, you have an option called "Path to the game's executable, for x360ce support", if you set this to where Strider.exe is located, you'll get full controller support automatically.

Hello Mathieu, I realized you are the creator of Lutris. I myself am just a moderate Linux user and enthusiast. It's an honor to s/w someone involved with such a project as Lutris since I myself have been attempting to discover more seemless & efficient methods to launch games & applications w/in Linux for quite some time.

Ok, I think I've followed your advice correctly but the game fails to launch in Lutris. Steam launches & for a brief second & tries to open the game, but it crashes before launch. I'm wondering if it has anything to do w/game not being in default home directory (I install all Steam & other games into another hard drive). I'm able to still normally play the game (without Lutris) by clicking a desktop shortcut I saved after installing steam thru wine (I'm not using playonlinux--which hasn't loaded games for me properly since ~2.10-staging-- guessing POL doesn't like anything beyond 2.9). I'm guessing it's not a distro-specific problem, but more likely wine bug(s) or could it perhaps be a minor bug in Lutris since I'm not using the default game repo w/in /Home partition? I took screenshots of game's config if you think it helps. If the problems are wine-related, I guess I'll have to remain hopeful subsequent wine-staging revisions restore accessibility for other games I can't play as well. In any event, thank you for your time.