https://bugs.winehq.org/show_bug.cgi?id=33776
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #18 from Adam Bolte abolte@systemsaviour.com --- I've got Far Cry 4 which requires Uplay and a 64-bit Windows 7 minimum, and have configured a prefix as such. I also have Far Cry 3 (which also requires Uplay) installed into the same prefix for comparison, the difference being Far Cry 3 is a 32-bit executable, and Far Cry 4 is 64-bit.
Neither of these work by default. Using Qian Hong's OpenProcess hack from comment #8, Far Cry 3 launches. Far Cry 4 however continues to fail. I do get the output:
fixme:process:OpenProcess hack: access is 00001400 fixme:process:OpenProcess hack: access is 00001400
Also, the game_starter_log.txt log shows: [ 115] 2014-12-29 01:39:38 [ 116] ERROR inject_impl.cpp (166) Getting thread context failed. System error code is 5 [ 150] 2014-12-29 01:39:38 [ 111] ERROR GameStarter.cpp (291) Failed to inject suspended process. Process terminated '28' [ 150] 2014-12-29 01:39:38 [ 111] ERROR UplayConnection.cpp (303) Failed to inject overlay and create process exepath 'C:\Far Cry 4\bin\FarCry4.exe', working directory 'C:\Far Cry 4\bin', inject overlay 'false', Steam runtime present 'false'
This suggests to me the hack does not work for 64-bit games. Does that sound correct?
Also, the link to Erich E. Hoover's patches is broken. I assume these are the ones I should try? https://github.com/wine-compholio/wine-staging/tree/master/patches/server-Mi...
Thanks.