Posted March 09, 2016
niniendowarrior
Savory Chicken
Registered: Dec 2010
From Philippines
P-E-S
I like games
Registered: Nov 2008
From United States
Posted March 09, 2016
As expected Shardlight runs perfectly in Wine-skin (Mac mini). No winetricks needed of any kind. :)
Mac OS X Yosemite 10.10.4 (64-bit)
Intel Iris 5100
OpenGL 4.0
Wine1.7.52
Winetricks: None
Mac OS X Yosemite 10.10.4 (64-bit)
Intel Iris 5100
OpenGL 4.0
Wine1.7.52
Winetricks: None
Post edited March 10, 2016 by mistermumbles
Gydion
Aexander
Registered: Oct 2011
From United States
Posted March 09, 2016
Agreed! Thanks again.
mistermumbles: As expected Shardlight runs perfectly in Wine-skin (Mac). No winetricks needed of any kind. :) AGS game, yes? What engine did you use, and could I get you to add your system info like in this post?
Post edited March 09, 2016 by Gydion
JudasIscariot
Thievin' Bastard
GOG.com Team
Registered: Oct 2008
From Poland
JudasIscariot
Thievin' Bastard
GOG.com Team
Registered: Oct 2008
From Poland
Posted March 10, 2016
Game: Legend of Grimrock 2
Installer MD5:
76fa6758d19e6a7ec326a02a56b8d299 setup_legend_of_grimrock_2_2.1.0.5.exe (the installer is already updated to in-game version 2.2.4)
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=31115 (warning: old results with almost no instructions!)
Wine version(s) tested: Wine 1.9.5 (i686) from the multilib Arch repo.
Install notes: Requires d3dx9, d3dcompiler_43 (thanks adamhm for letting me know about d3dcompiler as winetricks does not list it in the GUI version :) ), and xact_jun2010 winetricks
How well does it run: Quite well with all the settings on "High".
Details:
First, please make sure you have openal and the 32-bit development libraries installed if you are on a distro that uses the official Arch repositories then you will need the packages "openal" and "lib32-openal". If you are compiling Wine 1.9.5, make sure you enable 32-bit openal. THe reason I mention this is because the various xaudio DLLs will not get registered properly by regsvr32 when you run "winetricks xact_jun2010". I did manage to kind of work around this in a "dirty" prefix by setting the overrides for xaudio2_7 to "native, built-in" but I am not 100% sure that this actually worked so just make sure to properly install openal and the 32-bit development libraries.
Supposedly there is a crash bug when you attempt to go into the Options menu (https://bugs.winehq.org/show_bug.cgi?id=40261 ) but I did not experience this for myself.
I played the game for approximately 2 hours or so and I have not encountered any major issues.
Installer MD5:
76fa6758d19e6a7ec326a02a56b8d299 setup_legend_of_grimrock_2_2.1.0.5.exe (the installer is already updated to in-game version 2.2.4)
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=31115 (warning: old results with almost no instructions!)
Wine version(s) tested: Wine 1.9.5 (i686) from the multilib Arch repo.
Install notes: Requires d3dx9, d3dcompiler_43 (thanks adamhm for letting me know about d3dcompiler as winetricks does not list it in the GUI version :) ), and xact_jun2010 winetricks
How well does it run: Quite well with all the settings on "High".
Details:
First, please make sure you have openal and the 32-bit development libraries installed if you are on a distro that uses the official Arch repositories then you will need the packages "openal" and "lib32-openal". If you are compiling Wine 1.9.5, make sure you enable 32-bit openal. THe reason I mention this is because the various xaudio DLLs will not get registered properly by regsvr32 when you run "winetricks xact_jun2010". I did manage to kind of work around this in a "dirty" prefix by setting the overrides for xaudio2_7 to "native, built-in" but I am not 100% sure that this actually worked so just make sure to properly install openal and the 32-bit development libraries.
Supposedly there is a crash bug when you attempt to go into the Options menu (https://bugs.winehq.org/show_bug.cgi?id=40261 ) but I did not experience this for myself.
I played the game for approximately 2 hours or so and I have not encountered any major issues.
Post edited March 10, 2016 by JudasIscariot
P-E-S
I like games
Registered: Nov 2008
From United States
Posted March 10, 2016
Gydion
Aexander
Registered: Oct 2011
From United States
Matruchus
Don't ignore Tux
Registered: Jun 2011
From Slovenia
Posted March 10, 2016
Anybody managed to get Pharaoh running on 1920x1080 in Wine? After playing Lethis I wanted to play a bit of Pharaoh too. Can't get it to run bigger then 1020x768 (ingame settings) and if defaults to 640x480 on start of the game. Virtual desktop emulation does nothing.
Post edited March 10, 2016 by Matruchus
te_lanus
A Hybrid
Registered: Jun 2012
From South Africa
Posted March 10, 2016
vv221
./play.it developer
Registered: Dec 2012
From France
Posted March 10, 2016
Fallout
setup_fallout_2.1.0.18.exe (MD5: 47b7b3c059d92c0fd6db5881635277ea)
setup_fallout_french_2.1.0.18.exe (MD5: 12ba5bb0489b5bafb777c8d07717b020)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=25713
known bug: If using the HD patch, going with the DirectDraw 7 or DirectX 9 renderer can mess up the display of the game (it may depend on your graphics driver). It is of course reversible by switching back to the default rendrerer.
Setting a widescreen resolution while keeping the default renderer will not trigger any bug that I’m aware of.
-----
Fallout 2
setup_fallout2_2.1.0.17.exe (MD5: b40a8f2e1ff9216e25b8f09577c27f33)
setup_fallout2_french_2.1.0.17.exe (MD5: 7df6f834b480873bea2f8593254b1960)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=27466
known bug: If using the HD patch, going with the DirectDraw 7 or DirectX 9 renderer can mess up the display of the game (it may depend on your graphics driver). It is of course reversible by switching back to the default rendrerer.
Setting a widescreen resolution while keeping the default renderer will not trigger any bug that I’m aware of.
-----
Fallout Tactics
setup_fallout_tactics_2.1.0.12.exe (MD5: 9cc1d9987d8a2fa6c1cc6cf9837758ad)
setup_fallout_tactics_french_2.1.0.12.exe (MD5: 520c29934290910cdeecbc7fcca68f2b)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=810
Debian Sid amd64
Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
installers: Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
setup_fallout_2.1.0.18.exe (MD5: 47b7b3c059d92c0fd6db5881635277ea)
setup_fallout_french_2.1.0.18.exe (MD5: 12ba5bb0489b5bafb777c8d07717b020)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=25713
known bug: If using the HD patch, going with the DirectDraw 7 or DirectX 9 renderer can mess up the display of the game (it may depend on your graphics driver). It is of course reversible by switching back to the default rendrerer.
Setting a widescreen resolution while keeping the default renderer will not trigger any bug that I’m aware of.
-----
Fallout 2
Debian Sid amd64
Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
installers: Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
setup_fallout2_2.1.0.17.exe (MD5: b40a8f2e1ff9216e25b8f09577c27f33)
setup_fallout2_french_2.1.0.17.exe (MD5: 7df6f834b480873bea2f8593254b1960)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=27466
known bug: If using the HD patch, going with the DirectDraw 7 or DirectX 9 renderer can mess up the display of the game (it may depend on your graphics driver). It is of course reversible by switching back to the default rendrerer.
Setting a widescreen resolution while keeping the default renderer will not trigger any bug that I’m aware of.
-----
Fallout Tactics
Debian Sid amd64
Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
installers: Kernel: 4.5.0-rc1amdgpu-pp+ x86_64
Card: AMD Radeon R9 380X
OpenGL Renderer: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL Version: 4.1 (Core Profile) Mesa 11.1.1
setup_fallout_tactics_2.1.0.12.exe (MD5: 9cc1d9987d8a2fa6c1cc6cf9837758ad)
setup_fallout_tactics_french_2.1.0.12.exe (MD5: 520c29934290910cdeecbc7fcca68f2b)
WINE version: 1.8.1
WINEHQ AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=810
Post edited March 10, 2016 by vv221
shmerl
🐧
Registered: Sep 2011
From United States
Posted March 10, 2016
Just found this thread (and subscribed). I'm playing KoTOR II in Wine now, since native Aspyr version is still not here.
vv221
./play.it developer
Registered: Dec 2012
From France
Posted March 10, 2016
Let’s hope it will change soon, now that Aspyr is on board ;)
shmerl
🐧
Registered: Sep 2011
From United States
Posted March 10, 2016
Aspyr are all eager to release the game on GOG. The problem with KoTOR II is the fact that it involves a lot of parties besides Aspyr themselves to make it appear here. I.e. all those distributors (who compete with GOG) and partners have to be somehow satisfied. I got a response from them that they are working on releasing it here. But it appears to be a very slow process.
Post edited March 10, 2016 by shmerl
Gydion
Aexander
Registered: Oct 2011
From United States
rampancy
Think Different.
Registered: Sep 2008
From Canada
Posted March 11, 2016
It's got a good rating on the AppDB, but it's frustratingly vague when it says stuff like, "it works on nVidia, doesn't work on Intel graphics". It makes me think of the earlier complaints about the AppDB on this thread -- if they're going to be stupidly inconsistent about accepting reports then it may as well be useless to people like me.
And also, why is the AppDB not accepting PlayOnLinux reports?
And also, why is the AppDB not accepting PlayOnLinux reports?