Installing the game, and playing it for a couple of seconds.
This was tested on the following system:
Amd Athlon X2 3800
1.5 GB Kingston DDR
Areca 1210 + several hd's
Nvidia 6600 GT 128 MB (compiz / beryl not enabled, using Nvidia driver 169.12 )
I first downloaded and compiled wine 0.9.60 which didn't work. Then i grabbed the latest cvs and recompiled, didn't work either.
Installed the game by mounting both iso's and -=> "wine autorun.exe" on the first cd. When the installer asks for the next cd, change the driveletter to your second wine mount (F:\ in my case, I HAD to use the keyboard).
The in game menu's were functioning ok (mostly).
Both gameplay and FPS were perfect. Too bad the game is only playable for a few seconds (quits when one enters combat).
For bash output plz check bugzilla Bug nr 12684:
What does not
Playing the game for more than a few seconds.
I copied the installed game-directory to a Windows XP box and it played just fine.
What was not tested
The game installs fine, but the game itself only runs a few seconds after which it crashes. Gameplay and fps are perfect until one enters combat. Bugzilla : 12684
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Arch Linux||Dec 25 2011||1.3.35||Yes||Yes||Gold||fetter_oml|
|Show||Debian GNU/Linux 6.x "Squeeze"||Jul 31 2010||1.3.0||Yes||Yes||Bronze||an anonymous user|
|Show||Debian GNU/Linux Unstable "Sid"||Jun 29 2008||1.0.0||Yes||Yes||Bronze||deben|
|Current||Ubuntu 7.10 "Gutsy" i386 (+ variants like Kubuntu)||Apr 20 2008||0.9.60||Yes||Yes||Garbage||an anonymous user|
|Show||Ubuntu 7.10 "Gutsy" amd64 (+ variants like Kubuntu)||Dec 13 2007||0.9.50.||Yes||No||Garbage||Jeroen Benckhuijsen|
When starting Stronghold 2 on most machines it will silently fail because it cannot open enough files at once.
You can raise this limit, adding (as root)
* soft nofile 65535
* hard nofile 65535
to /etc/security/limits.conf (replace the * with your username if you believe these limits are anything but stupid and would be unsafe to raise for all users) and logging out and back in.
The limits currently in effect can be checked using ulimit -Sn and ulimit -Hn.
This should work for any app, if you have Intel + AMD or AMD + AMD with open source drivers.
If you have laptop with hybrid graphics cards. You can launch game with command:
env DRI_PRIME=1 vblank_mode=0 wine ~/path/to/your/exe/file
In case of using command, you get swich to powerful graphics card and disable vsync for more FPS.
If you have Mesa drivers 17.x.x or more, you can use this command:
env DRI_PRIME=1 mesa_glthread=true vblank_mode=0 wine ~/path/to/your/exe/file
Last command is most best in performance that you can get in this moment, you can use it for any wine application that you need. But argument mesa_glthread=true may not always work, so if your app crash, remove it.
For Steam users, you can set environment variable of any applications in properties.
DRI_PRIME=1 mesa_glthread=true vblank_mode=0 %command%
(It will work only with native Steam for Linux) For Wine, you have to start Steam or game with those arguments