Initial release of the game
What does not
CD-Installation without tricks
What was not tested
When installing `wineserver` kept an open file handle on the file \Disk1\install.wav (background music during install). This means that you cannot properly eject the CD1 and insert the CD2 (which is required during installation). There are two workarounds for this problem: * By copying file back and forth (RECOMENDED!) 1. Insert CD2 first 2. Copy the directory "\Disk2" on the CD to your home directory 3. Eject CD2 4. Insert CD1 5. Install as usual until you see the "Insert CD2"-popup 6. Select the directory "Z:\home\\Disk2" and click "OK" * Using lazy umount and physical tampering: 1. Insert CD1 and do the install up to the point where it asks you for CD2. 2. Do a lazy `umount` using `sudo umount -l /dev/sr0` 3. Eject the drive using `eject /dev/sr0` 4. Take out the CD1 5. Physically disconnect your drive by unplugging the SCSI connector 6. Plug your drive back in 7. Insert CD2 like you normally would 8. Mount it manually using `sudo mount /dev/sr0 /mnt` 9. Select the directory /mnt/Disk2 in the installer and complete the installation
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Ubuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)||Feb 02 2014||1.7.11||Yes||Yes||Gold||Alexander Schlarb|
|Show||Ubuntu 10.10 "Maverick" i386 (+ variants like Kubuntu)||Dec 26 2011||1.3.34||Yes||Yes||Silver||Alexander Schlarb|
|Show||Ubuntu 9.04 "Jaunty" i386 (+ variants like Kubuntu)||Sep 05 2009||1.1.29||Yes||Yes||Bronze||an anonymous user|
|Show||Gentoo Linux x86_64||Jul 30 2009||1.1.26||Yes||Yes||Bronze||an anonymous user|
|Show||Ubuntu 9.04 "Jaunty" amd64 (+ variants like Kubuntu)||Apr 10 2009||1.1.18||Yes||Yes||Bronze||John Jackson|
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