I was given Crysis 2 by a friend a while back and now I am trying to get it to work in wine. I have tried it with wine versions 1.6-rc4-d3d_doublebuffer, 1.4-rc5-d3d_doublebuffer and 1.3.19 but they all have different issues. I have used the guide from http://gamersonlinux.com/forum/threads/ ... guide.297/, doing similar things but for a non steam version of the game. Does anyone have Crysis 2 working properly in wine?
The problem with 1.6-rc4-d3d_doublebuffer is that it is completely unable to play cutscenes, there is just a white screen. 1.4-rc5-d3d_doublebuffer seems to be the best, it runs cutscenes properly (apart from audio stuttering, but that is a game bug and not a wine bug) and the first bit of the game on the boat works, but when I start the first real mission I get awful graphics artifacts (looks like http://wine.1045685.n5.nabble.com/Bug-2 ... 59i20.html) and the game quickly freezes. I am running patch 1.9 with 1.4-rc5-d3d_doublebuffer. When I use wine 1.3.19 neither the cutscenes or gameplay works. I have Crysis 1 working fine, no crashing, very few graphics issues. I used the GamersOnLinux guide for that too (http://www.gamersonlinux.com/forum/thre ... guide.252/).
My system:
Intel i3 2100 3.1GHz
Intel HD 2000
Seagate Barracuda 7200RPM 1TB HDD
4GB Corsair Vengance CL9 1600MHz RAM, running at 1333MHz
Xubuntu 13.10 32 bit
Thanks for any answers.
Crysis 2
Re: Crysis 2
i_will_now_break_it we don't support Play on Linux patched versions. They are worthless to us because we don't know the exact patch and bug the patch is from. It is very import to us to know what patch is applied and if it current or not. We don't wish to be chasing our tail fixing faults that are fixed in newer version of patch.
We lack reports on the state of our stable versions.
http://appdb.winehq.org/objectManager.p ... &iId=12827 There is no entry is our tested applications for steam version of crysis at all.
http://appdb.winehq.org/objectManager.p ... &iId=29144 Again no reports with our current releases at all. Again no bug report linkage on the patch used.
Play on Linux at first said their methods would be recorded in the appdb. In fact they have not done this.
Sorry due to lack of information provided to us by PlayonLinux we cannot help you. i_will_now_break_it
Basically for us to provide you with support we need far better information. Yes we have a classic case of downstream not working with upstream leaving poor users stuffed.
We lack reports on the state of our stable versions.
http://appdb.winehq.org/objectManager.p ... &iId=12827 There is no entry is our tested applications for steam version of crysis at all.
http://appdb.winehq.org/objectManager.p ... &iId=29144 Again no reports with our current releases at all. Again no bug report linkage on the patch used.
Play on Linux at first said their methods would be recorded in the appdb. In fact they have not done this.
Sorry due to lack of information provided to us by PlayonLinux we cannot help you. i_will_now_break_it
Basically for us to provide you with support we need far better information. Yes we have a classic case of downstream not working with upstream leaving poor users stuffed.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
I understand. Should I try it with the latest wine beta (1.7.X) and the latest stable? Would it be fine if I used official unpatched wine versions in PoL?
Re: Crysis 2
i_will_now_break_it using the Ubuntu Wine PPA would be preferable we know that group better.
1.7.x would be the one to try since it shows them applying patches to 1.6. There are a lot of patches between 1.6 and 1.7.5.
1.7.x would be the one to try since it shows them applying patches to 1.6. There are a lot of patches between 1.6 and 1.7.5.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
I did what was said in http://bugs.winehq.org/show_bug.cgi?id=32348 and installed vcrun2008 and d3dx9 with winetricks in a new prefix before installing the game. I then installed Crysis 2 as normal and that went fine. When I try installing the 1.9 patch the installer crashes with "the program has encountered a serious error and needs to close". This is with wine 1.7.4.
Next I tried PoL. I followed the GamersOnLinux guide but using 1.7.4 and not the patched versions of wine. The game installed fine and when I patched it that worked too. There are a few issues, one of them is that the nanosuit has no texture, it is just black. The most important one is that the game very quickly freezes, within 15 seconds. The huge graphics glitches seem to be much less of a problem. Something I noticed is that my wine FPS is a lot lower than people get on windows, could it be that my hardware (graphics card ) is just inadequate for a heavy game like this?
Running the game from the PoL wineprefix but through wine directly produces the "Failed to initialize the GameStartup Interface!" error.
Next I tried PoL. I followed the GamersOnLinux guide but using 1.7.4 and not the patched versions of wine. The game installed fine and when I patched it that worked too. There are a few issues, one of them is that the nanosuit has no texture, it is just black. The most important one is that the game very quickly freezes, within 15 seconds. The huge graphics glitches seem to be much less of a problem. Something I noticed is that my wine FPS is a lot lower than people get on windows, could it be that my hardware (graphics card ) is just inadequate for a heavy game like this?
Running the game from the PoL wineprefix but through wine directly produces the "Failed to initialize the GameStartup Interface!" error.
Re: Crysis 2
i_will_now_break_it POL runs it own versions of wine. Even when POL claims unpatched it can still be patched. This is why we find it worthless. We need to know the patches applied to work with it.
Wine 1.7.4 Ubuntu Wine PPA right? https://launchpad.net/~ubuntu-wine/+archive/ppa
I need the wine log from when that failure happens to attempt to help you. http://wiki.winehq.org/FAQ#get_log applicaiton messages are not much use they are too vague. Wine default logging output still might be too vague but we have other options we can enable to get more details.
Intel HD 2000 and most intel graffics drivers are not know to be fast under Linux. Also wine is not as yet exploiting multi threading of opengl that is supported in the newer drivers.
The freezing with intel HD 2000 sorry to say is kinda Windows, Linux and OS X. There is a lot of work from intel developers trying to to bottom of this. It might not be wine at all. Could you please try running http://www.xonotic.org/ as native Linux application and see if it shows same issue of locking up. If so you have one of the effected boards.
This is basically normal. Don't cross wine versions on prefix bad things can happen. Did you WINEPREFIX=--polprefix location-- before wine if you did not the drive c would have been in the wrong place and the wrong registery loaded. Yes of course game would fail.Running the game from the PoL wineprefix but through wine directly produces the "Failed to initialize the GameStartup Interface!" error.
When I try installing the 1.9 patch the installer crashes with "the program has encountered a serious error and needs to close". This is with wine 1.7.4.
Wine 1.7.4 Ubuntu Wine PPA right? https://launchpad.net/~ubuntu-wine/+archive/ppa
I need the wine log from when that failure happens to attempt to help you. http://wiki.winehq.org/FAQ#get_log applicaiton messages are not much use they are too vague. Wine default logging output still might be too vague but we have other options we can enable to get more details.
Intel HD 2000 and most intel graffics drivers are not know to be fast under Linux. Also wine is not as yet exploiting multi threading of opengl that is supported in the newer drivers.
The freezing with intel HD 2000 sorry to say is kinda Windows, Linux and OS X. There is a lot of work from intel developers trying to to bottom of this. It might not be wine at all. Could you please try running http://www.xonotic.org/ as native Linux application and see if it shows same issue of locking up. If so you have one of the effected boards.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
Note: this post was written over a few hours as I tested. If I contradict myself it is because something changed for reasons I dont understand.
##########
Test 1 - Crysis2 prefix
##########
I dont know why, but this time the patcher worked. The only thing that I know to have changed is that I installed wine1.7-dbg (at the suggestion of the FAQ). My terminal output from when it works:
My terminal output from running the game:
##########
Test 2 - Cry2 prefix
##########
I installed and ran the game again. As far as I am aware I did exactly the same thigns as in test 1. This is the annotated terminal output from the entire process:
About Test 1, I was able to play it but then when I installed to the Cry2 prefix and did all of that stuff in Cry2 it stopped working in Crysis2!
Sorry if this is incoherent, it is starting to confuse me now.
##########
Test 1 - Crysis2 prefix
##########
I dont know why, but this time the patcher worked. The only thing that I know to have changed is that I installed wine1.7-dbg (at the suggestion of the FAQ). My terminal output from when it works:
I am using wine 1.7.4 from the wine PPA. When it was giving me "the program has encountered a serious error and needs to close" I was doing nothing different to this time.matthew@Matthew:~/Downloads$ WINEPREFIX=/home/matthew/.Crysis2 wine Crysis2Patch19.exe
fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevationType, ...) semi-stub
fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevationType, ...) semi-stub
fixme:sfc:SfcIsFileProtected ((nil), L"Z:\\home\\matthew\\Iso\\Mounted\\Crysis2\\bin32\\activation.exe") stub
matthew@Matthew:~/Downloads$
My terminal output from running the game:
When I played Xonotic it went fine. I played 2 matches and it usually played at 60fps on low settings at 1080p. There were no apparent graphics problems and it did not crash at all. I ran it with the xonotic-linux32-glx executable if it makes a difference.matthew@Matthew:~/.Crysis2/drive_c/Program Files/Electronic Arts/Crytek/Crysis 2/bin32$ WINEPREFIX=/home/matthew/.Crysis2 wine Crysis2.exe
fixmeSHGetKnownFolderPath flags 0x0000a000 not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x32e788,0x00000000), stub!
fixme:d3d11:D3D11CreateDevice stub: adapter 0x48e1ec8, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 0x32ec38, levels 0x1, sdk_version 7, device 0x32ec34, feature_level (nil), context (nil)
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x960e9bc): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e038,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32dee8,0x00000000), stub!
fixme:wbemprox:client_security_SetBlanket 0xb62f92d8, 0x4926e18, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xb62f92d8
fixme:win:EnumDisplayDevicesW ((null),0,0x32db78,0x00000000), stub!
fixme:wbemprox:enum_class_object_Next timeout not supported
matthew@Matthew:~/.Crysis2/drive_c/Program Files/Electronic Arts/Crytek/Crysis 2/bin32$
SHGetKnownFolderPath flags 0x0000a000 not supported##########
Test 2 - Cry2 prefix
##########
I installed and ran the game again. As far as I am aware I did exactly the same thigns as in test 1. This is the annotated terminal output from the entire process:
I think the patching of the game is the strangest thing there. I installed the game as normal (which should install version 1.0 as far as I ma aware) and then ran the patcher. It scanned my hard drive searching for something but when it finished it said I already had patch 1.9 installed. Very strange. Any ideas?ANNOTATION: This is the enetire process of installing and playing Crysis 2 in wine 1.7.4 from the wine PPA with annotations.
ANNOTATION: First I install d3dx9 and vcrun2008 with winetricks.
matthew@Matthew:~/Iso/Mounted/Crysis2$ env WINEPREFIX=/home/matthew/.Cry2 winetricks d3dx9 vcrun2008
Executing w_do_call d3dx9
Executing load_d3dx9
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9 -L -F *d3dx9*x86* /home/matthew/.cache/winetricks/directx9/directx_Jun2010_redist.exe
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2005_d3dx9_25_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2005_d3dx9_25_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2006_d3dx9_30_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2006_d3dx9_30_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2007_d3dx9_33_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/apr2007_d3dx9_33_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2005_d3dx9_27_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2005_d3dx9_27_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2007_d3dx9_35_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2007_d3dx9_35_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2008_d3dx9_39_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2008_d3dx9_39_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2009_d3dx9_42_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/aug2009_d3dx9_42_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/dec2005_d3dx9_28_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/dec2005_d3dx9_28_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/dec2006_d3dx9_32_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/dec2006_d3dx9_32_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/feb2005_d3dx9_24_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/feb2005_d3dx9_24_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/feb2006_d3dx9_29_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/feb2006_d3dx9_29_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2005_d3dx9_26_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2005_d3dx9_26_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2007_d3dx9_34_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2007_d3dx9_34_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2008_d3dx9_38_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2008_d3dx9_38_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2010_d3dx9_43_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/jun2010_d3dx9_43_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/mar2008_d3dx9_37_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/mar2008_d3dx9_37_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/mar2009_d3dx9_41_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/mar2009_d3dx9_41_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/nov2007_d3dx9_36_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/nov2007_d3dx9_36_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/nov2008_d3dx9_40_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/nov2008_d3dx9_40_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Executing cabextract -q -d /home/matthew/.Cry2/dosdevices/c:/windows/system32 -L -F d3dx9*.dll /home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/oct2006_d3dx9_31_x86.cab
/home/matthew/.Cry2/dosdevices/c:/windows/temp/_d3dx9/oct2006_d3dx9_31_x86.cab: WARNING; possible 5960 extra bytes at end of file.
Using native override for following DLLs: d3dx9_24 d3dx9_25 d3dx9_26 d3dx9_27 d3dx9_28 d3dx9_29 d3dx9_30
Executing winetricks_early_wine regedit C:\windows\Temp\_d3dx9\override-dll.reg
Using native override for following DLLs: d3dx9_31 d3dx9_32 d3dx9_33 d3dx9_34 d3dx9_35 d3dx9_36 d3dx9_37
Executing winetricks_early_wine regedit C:\windows\Temp\_d3dx9\override-dll.reg
Using native override for following DLLs: d3dx9_38 d3dx9_39 d3dx9_40 d3dx9_41 d3dx9_42 d3dx9_43
Executing winetricks_early_wine regedit C:\windows\Temp\_d3dx9\override-dll.reg
Executing w_do_call vcrun2008
Executing load_vcrun2008
Using native,builtin override for following DLLs: msvcm90 msvcp90 msvcr90 vcomp90
Executing winetricks_early_wine regedit C:\windows\Temp\_vcrun2008\override-dll.reg
Executing wine vcredist_x86.exe
fixme:clusapi:GetNodeClusterState ((null),0x32ebf4) stub!
fixme:advapi:DecryptFileA ("c:\\5481b07db1cb0c432ef1595803\\", 00000000): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:LsaOpenPolicy ((null),0x33f2d8,0x00000001,0x33f2c4) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:storage:create_storagefile Storage share mode not implemented.
matthew@Matthew:~/Iso/Mounted/Crysis2$
ANNOTATION: d3dx9 and vcrun2008 should now be installed.
ANNOTATION: I now install Crysis 2.
matthew@Matthew:~/Iso/Mounted/Crysis2$ WINEPREFIX=/home/matthew/.Cry2 wine AutoRun.exe
matthew@Matthew:~/Iso/Mounted/Crysis2$ fixme:clusapi:GetNodeClusterState ((null),0x33ebf4) stub!
fixme:advapi:DecryptFileA ("c:\\6eaa0c6170854aebbdc1e2f9ed0a82\\", 00000000): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:LsaOpenPolicy ((null),0x33f2d8,0x00000001,0x33f2c4) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:storage:create_storagefile Storage share mode not implemented.
err:richedit:ReadColorTbl malformed entry
err:richedit:ReadColorTbl malformed entry
err:richedit:ReadColorTbl malformed entry
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:CharAttr unknown font 0
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
fixme:gameux:GameExplorerImpl_VerifyAccess (0x5e4448, L"C:\\Program Files\\Electronic Arts\\Crytek\\Crysis 2\\GDFBinary.en-us.dll", 0xd5d4fc)
^C
matthew@Matthew:~/Iso/Mounted/Crysis2$
ANNOTATION: Crysis 2 should now be installed.
ANNOTATION: Now I install patch 1.9.
matthew@Matthew:~/Downloads$ WINEPREFIX=/home/matthew/.Cry2 wine Crysis2Patch19.exe
matthew@Matthew:~/Downloads$
ANNOTATION: This behaved very strangely. It seemed to scan my hard drive (looking for the installation?) before saying that 1.9 is already installed, even though I know it is not. It also gave no terminal output.
ANNOTATION: Now I try to run Crysis 2.
matthew@Matthew:~/.Cry2/drive_c/Program Files/Electronic Arts/Crytek/Crysis 2/bin32$ WINEPREFIX=/home/matthew/.Cry2 wine Crysis2.exe
fixme
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x95fe978): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e038,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32dee8,0x00000000), stub!
fixme:wbemprox:client_security_SetBlanket 0xb22d82d8, 0x16fad8, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xb22d82d8
fixme:win:EnumDisplayDevicesW ((null),0,0x32db78,0x00000000), stub!
fixme:wbemprox:enum_class_object_Next timeout not supported
matthew@Matthew:~/.Cry2/drive_c/Program Files/Electronic Arts/Crytek/Crysis 2/bin32$
ANNOTATION: It crashed with the "Failed to initialize the GameStartup Interface!" error.
About Test 1, I was able to play it but then when I installed to the Cry2 prefix and did all of that stuff in Cry2 it stopped working in Crysis2!
Sorry if this is incoherent, it is starting to confuse me now.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
I just found http://unixblogger.wordpress.com/2011/04/01/74/. I will try it to see if it works and post a more detailed tutorial if it is somewhat usable, or at least might provide a base for other people to test on.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
Well, it "worked". I compiled wine 1.3.16 with that patch and it all went fine until I tried to install the 1.9 patch. It appears that the problem is in the patching, not the game itself. I then tried with what I think is 1.0 and that "worked" (by which I mean it crashed at the first cutscene). It appears that the best non-PoL setup is wine 1.7.4 with Crysis 2 1.0. No good for playing online, but you get to enjoy the excellently written crysis stories. I will update this thread as I get more information. Thanks for helping oiaohm.
-
i_will_now_break_it
- Level 2
- Posts: 33
- Joined: Wed Apr 24, 2013 1:35 pm
Re: Crysis 2
Pretend my last three posts never happened. Now I have done it properly and it seems to work.
First create a new wine prefix and install vcrun2008 and d3dx9. Run something like "env WINEPREFIX=/home/USERNAME/.Crysis2 winetricks vcrun2008 d3dx9" to do this. Next install the game. Just run the setup file on your disc/iso/steam in your new win prefix. I would not recomend a custom installation as all of this is rather precarious and that could break it. Once that is installed you need to patch the game. as of the witing of this post, 1.9 is the latest patch. I downloaded it from here. If the patch does not install and returns something along the lines of "You already have the most recent version (1.9) of Crysis 2 installed on your system" or "Crysis 2 could not be located on your system. Re-install and then run this patch again" then you are one of the people Crytek's attempts at anti piracy have affected. From my research the patch installer gets the checksum of crysis2.exe and compares it with what it "should" be. This is allegedly meant to stop people from using cracked executables but it is known to affect people who have bought a copy too. The only practical way I have found around this bug is to download the "original" executable. I would link to the one I downloaded but I think that would violate the forum rules. Search "crysis 2 original exe" and that should give some relevant results. BE VERY CAREFUL what you download here as people will exploit this bug in Crytek's patches to give people viruses. Once you have downloaded one of the "original" executables, place it in [crysis 2 install path]/bin32 and overwrite the crysis2.exe that is already there. Then run the patch installer again and it should work. If you want to prove that the patch installer's messages bear no relation to the actual problem, run the patch installer in an empty wine prefix. Now the game should work. I can not test properly as my PC is completely unable to run this game properly. Please test this if you have a real graphics card.
Good luck to anyone else trying to get this working!
This worked on:
Intel i3 2100 3.1GHz
Intel HD 2000
Seagate Barracuda 7200RPM 1TB HDD
4GB Corsair Vengance CL9 1600MHz RAM, running at 1333MHz
Xubuntu 12.10 32 bit
EDIT: To an admin, please remove that huge quote from my post above.
First create a new wine prefix and install vcrun2008 and d3dx9. Run something like "env WINEPREFIX=/home/USERNAME/.Crysis2 winetricks vcrun2008 d3dx9" to do this. Next install the game. Just run the setup file on your disc/iso/steam in your new win prefix. I would not recomend a custom installation as all of this is rather precarious and that could break it. Once that is installed you need to patch the game. as of the witing of this post, 1.9 is the latest patch. I downloaded it from here. If the patch does not install and returns something along the lines of "You already have the most recent version (1.9) of Crysis 2 installed on your system" or "Crysis 2 could not be located on your system. Re-install and then run this patch again" then you are one of the people Crytek's attempts at anti piracy have affected. From my research the patch installer gets the checksum of crysis2.exe and compares it with what it "should" be. This is allegedly meant to stop people from using cracked executables but it is known to affect people who have bought a copy too. The only practical way I have found around this bug is to download the "original" executable. I would link to the one I downloaded but I think that would violate the forum rules. Search "crysis 2 original exe" and that should give some relevant results. BE VERY CAREFUL what you download here as people will exploit this bug in Crytek's patches to give people viruses. Once you have downloaded one of the "original" executables, place it in [crysis 2 install path]/bin32 and overwrite the crysis2.exe that is already there. Then run the patch installer again and it should work. If you want to prove that the patch installer's messages bear no relation to the actual problem, run the patch installer in an empty wine prefix. Now the game should work. I can not test properly as my PC is completely unable to run this game properly. Please test this if you have a real graphics card.
Good luck to anyone else trying to get this working!
This worked on:
Intel i3 2100 3.1GHz
Intel HD 2000
Seagate Barracuda 7200RPM 1TB HDD
4GB Corsair Vengance CL9 1600MHz RAM, running at 1333MHz
Xubuntu 12.10 32 bit
EDIT: To an admin, please remove that huge quote from my post above.
