https://bugs.winehq.org/show_bug.cgi?id=38436
Bug ID: 38436 Summary: Grand Theft Auto V failed to launch Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: franklin@goodhorse.idv.tw Distribution: ---
Created attachment 51297 --> https://bugs.winehq.org/attachment.cgi?id=51297 Backtraces of page fault when launching GTA5 on Linux.
When launching GTA5, it crashed with page fault. My GTA5 was installed via steam running on Linux. My steam was installed with winetricks.
However, I found that when installing steam with winetricks, it installed 32-bit(x86) version instead of 64-bit version. I wonder if this is why it failed to launch.
https://bugs.winehq.org/show_bug.cgi?id=38436
Francesco Munda syylk@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |syylk@hotmail.com
--- Comment #1 from Francesco Munda syylk@hotmail.com --- I'm trying my luck with GTAV/Steam too.
And it fails to launch, too.
What I discovered is this:
1) Steam and GTAV need to be launched as a 64bit app. I do that with a custom WINEPREFIX and using wine64. YMMV (wildly).
2) One crash is during Social Club logging in, and the culprit seems to be "subprocess.exe", that's installed and launched from "Program Files (x86)", so a 32bit app. I tried to link the (x86) and regular 64bit Program Files folder, and at least it started, only to crash a bit later.
3) R* claims that the game requires DX10 (and at least Vista). I don't know if our directx implementation covers that, or if we're doomed to fail until WINE has proper DX10 lib entry points and translation code.
I'm ready to test this extensively, because I'd love to play GTAV under linux.
My specs:
i7 4970K @ 4 / GTX770-2 / 32GB / 120G+1T SSD's / DK2 (one can dream)
Kubuntu 14.04.02 LTS / nv 346.xx / WINE 1.7.38 (from PPA)
https://bugs.winehq.org/show_bug.cgi?id=38436
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Francesco Munda from comment #1)
- R* claims that the game requires DX10 (and at least Vista). I don't know
if our directx implementation covers that, or if we're doomed to fail until WINE has proper DX10 lib entry points and translation code.
If it's dx10+ game then you have to wait for more complete implementation. We have some code for dx10 already, but it's not enough. But from your backtrace it looks like it crashed earlier than that, as dx10 libs are not loaded. And it was probably launcher that crashed.
(In reply to Franklin Weng from comment #0)
Created attachment 51297 [details] Backtraces of page fault when launching GTA5 on Linux.
When launching GTA5, it crashed with page fault. My GTA5 was installed via steam running on Linux. My steam was installed with winetricks.
However, I found that when installing steam with winetricks, it installed 32-bit(x86) version instead of 64-bit version. I wonder if this is why it failed to launch.
Yes, I think it's normal, as Steam is installed for 32 bit program files dir on windows as well.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #3 from Francesco Munda syylk@hotmail.com --- (In reply to Nikolay Sivov from comment #2)
(In reply to Francesco Munda from comment #1)
If it's dx10+ game then you have to wait for more complete implementation. [...]
Yup, what I imagined.
Btw, the backtrace is from Franklin, the OP. I'm Francesco, just chiming in, with some further details I tumbled onto. Credit where credit is due! :)
Yes, I think it's normal, as Steam is installed for 32 bit program files dir on windows as well.
I was able to at least launch the Launcher when I put everything in a 64bit WINEPREFIX. The Launcher starts correctly, then "subprocess.exe" crashes and leaves a loading pattern in the Launcher window.
From the path where it starts from, I guess it's the helper app to login the
Social Club platform of Rockstar:
'${HOME}/.wine64/drive_c/Program Files/Rockstar Games/Social Club/subprocess.exe'
I will try and register my copy from a Windows machine, and see if it starts after the bump of the Social Club helper.
https://bugs.winehq.org/show_bug.cgi?id=38436
kaito.linux@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kaito.linux@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=38436
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- The bug reporter's original issue was that steam was installed with winetricks, which makes 32bit wineprefixes. Both GTAV and Social Club are 64bit programs and need a 64bit wineprefix.
I have the DVD version. There is an issue with the installer that I worked around by installing the game in a 32bit wineprefix and copying the install dir and registry keys over to a 64bit wineprefix. Full story there: https://forum.winehq.org/viewtopic.php?f=8&t=24515
I confirm what is described in comment #1. The launcher starts but shows an endless loading rotating animation. When alt-tabbing, an exception error is produced by subprocess.exe, which is the Rockstar Social Club executable.
I'll attach the backtrace of the subprocess.exe exception error.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #5 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Created attachment 51319 --> https://bugs.winehq.org/attachment.cgi?id=51319 Backtrace of Social Club crash at launcher startup
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Olivier F. R. Dierick from comment #4)
The bug reporter's original issue was that steam was installed with winetricks, which makes 32bit wineprefixes. Both GTAV and Social Club are 64bit programs and need a 64bit wineprefix.
winetricks does not make 32-bit prefixes. It warns if using a 64-bit prefix for some verbs that require 32-bit prefixes, but it doesn't force 32-bit anywhere.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #7 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Austin English from comment #6)
(In reply to Olivier F. R. Dierick from comment #4)
The bug reporter's original issue was that steam was installed with winetricks, which makes 32bit wineprefixes. Both GTAV and Social Club are 64bit programs and need a 64bit wineprefix.
winetricks does not make 32-bit prefixes. It warns if using a 64-bit prefix for some verbs that require 32-bit prefixes, but it doesn't force 32-bit anywhere.
I didn't say that it forced 32bit either, but winetricks does make 32bit prefixes when WINEARCH=win64 is not defined and it has to create the prefix, either because the prefix doesn't exist or --isolate is used. I believe --isolate is the default for the winetricks steam recipe. So even if the user has a 64-bit prefix, winetricks will make a new 32-bit prefix, unless --no-isolate is given.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #8 from Austin English austinenglish@gmail.com --- (In reply to Olivier F. R. Dierick from comment #7)
(In reply to Austin English from comment #6)
(In reply to Olivier F. R. Dierick from comment #4)
The bug reporter's original issue was that steam was installed with winetricks, which makes 32bit wineprefixes. Both GTAV and Social Club are 64bit programs and need a 64bit wineprefix.
winetricks does not make 32-bit prefixes. It warns if using a 64-bit prefix for some verbs that require 32-bit prefixes, but it doesn't force 32-bit anywhere.
I didn't say that it forced 32bit either, but winetricks does make 32bit prefixes when WINEARCH=win64 is not defined and it has to create the prefix, either because the prefix doesn't exist or --isolate is used. I believe --isolate is the default for the winetricks steam recipe. So even if the user has a 64-bit prefix, winetricks will make a new 32-bit prefix, unless --no-isolate is given.
No, it doesn't: austin@debian-laptop:~/src/winetricks$ grep WINEARCH src/winetricks austin@debian-laptop:~/src/winetricks$
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #9 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Austin English from comment #8)
(In reply to Olivier F. R. Dierick from comment #7)
(In reply to Austin English from comment #6)
(In reply to Olivier F. R. Dierick from comment #4)
The bug reporter's original issue was that steam was installed with winetricks, which makes 32bit wineprefixes. Both GTAV and Social Club are 64bit programs and need a 64bit wineprefix.
winetricks does not make 32-bit prefixes. It warns if using a 64-bit prefix for some verbs that require 32-bit prefixes, but it doesn't force 32-bit anywhere.
I didn't say that it forced 32bit either, but winetricks does make 32bit prefixes when WINEARCH=win64 is not defined and it has to create the prefix, either because the prefix doesn't exist or --isolate is used. I believe --isolate is the default for the winetricks steam recipe. So even if the user has a 64-bit prefix, winetricks will make a new 32-bit prefix, unless --no-isolate is given.
No, it doesn't: austin@debian-laptop:~/src/winetricks$ grep WINEARCH src/winetricks austin@debian-laptop:~/src/winetricks$
You're right. I just checked and the default is 64-bit on a shared WoW64 setup. I don't know why I thought it was 32-bit.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #10 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- There seems to be two issues: The one of the OP is with GTALauncher.exe and mine and Francesco Munda's is with subprocess.exe. I filed another bug report for the unhandled exception in subprocess.exe: it is bug 38493.
https://bugs.winehq.org/show_bug.cgi?id=38436
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #11 from super_man@post.com --- (In reply to Olivier F. R. Dierick from comment #10)
There seems to be two issues: The one of the OP is with GTALauncher.exe and mine and Francesco Munda's is with subprocess.exe. I filed another bug report for the unhandled exception in subprocess.exe: it is bug 38493.
Care to retry this? Last time I tried this I was blocked some compiler bug. This time I had to download 1.3Gb update to the game and after it social club complains about some error. I checked game cache. Downloaded a launcher it suggested which couldnt find the game installed.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #12 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to super_man from comment #11)
Care to retry this? Last time I tried this I was blocked some compiler bug. This time I had to download 1.3Gb update to the game and after it social club complains about some error. I checked game cache. Downloaded a launcher it suggested which couldnt find the game installed.
Tested with wine 1.9.1. There is the splash screen, then the launcher. It display "loading" with an animation, then I get "page faults in 64 bit code" errors at various addresses, all in subprocess.exe (Chromium libcef executable). It keeps opening crash dialogs until I click on "cancel" in the launcher and close the last error dialog, then wine closes.
https://bugs.winehq.org/show_bug.cgi?id=38436
Jonathan Schuett bioshacker001@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bioshacker001@gmail.com
--- Comment #13 from Jonathan Schuett bioshacker001@gmail.com --- I feel like the issues that have been stated here are related to the games DRM rather than Wines implementation. Anyone test using a cracked version? I would be willing to, but I'm unsure if the results would be acceptable.
https://bugs.winehq.org/show_bug.cgi?id=38436
Blauer_Hunger blauerhunger@outlook.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |blauerhunger@outlook.de
--- Comment #14 from Blauer_Hunger blauerhunger@outlook.de --- Created attachment 53746 --> https://bugs.winehq.org/attachment.cgi?id=53746 Backtrace of game/launcher "subprocess.exe"
The wine error window with this backtrace appeared after the Social Club Launcher window was opened.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #15 from super_man@post.com --- I am no longer stuck at the social club launcher I just tried wine-staging 1.9.4
The crash location is now at
=>0 0x00007fedfdc10bf4 wined3d_get_adapter_identifier+0xa4() in
https://bugs.winehq.org/show_bug.cgi?id=38436
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #51319|0 |1 is obsolete| |
--- Comment #16 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Created attachment 53873 --> https://bugs.winehq.org/attachment.cgi?id=53873 first unhandled exception (wine 1.9.5)
I get these two unhandled exceptions with wine 1.9.5 compiled from git (shared wow64; win7 mode).
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #17 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Created attachment 53874 --> https://bugs.winehq.org/attachment.cgi?id=53874 second unhandled exception (wine 1.9.5)
https://bugs.winehq.org/show_bug.cgi?id=38436
Blauer_Hunger blauerhunger@outlook.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #54021|Backtrace of game/launcher |Backtrace of game/launcher description|"subprocess.exe" |"subprocess.exe" (Wine | |1.9.6)
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #18 from super_man@post.com --- (In reply to super_man from comment #15)
I am no longer stuck at the social club launcher I just tried wine-staging 1.9.4
The crash location is now at
=>0 0x00007fedfdc10bf4 wined3d_get_adapter_identifier+0xa4() in
Most likely not helpful at all, but the crash is still there.
wine-staging 1.9.6.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #19 from Blauer_Hunger blauerhunger@outlook.de --- Created attachment 54021 --> https://bugs.winehq.org/attachment.cgi?id=54021 Backtrace of game/launcher "subprocess.exe"
https://bugs.winehq.org/show_bug.cgi?id=38436
Blauer_Hunger blauerhunger@outlook.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #53746|0 |1 is obsolete| |
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #20 from super_man@post.com --- fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xadb30, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x23f760, desc (nil) partial stub! fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xadb30, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x23f760, desc 0x962870 partial stub! fixme:dxgi:DXGID3D10CreateDevice Ignoring flags. fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:d3d11:device_parent_create_swapchain_texture device_parent 0xe1860, container_parent 0xa9c90, wined3d_desc 0x23ecf0, wined3d_texture 0xc35e0 partial stub! fixme:d3d11:device_parent_create_swapchain_texture Implement DXGI<->wined3d usage conversion. wine: Unhandled stack overflow at address 0x7fd5d0307ca4 (thread 00dc), starting debugger...
wine-staging 1.9.7
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #21 from super_man@post.com --- Created attachment 54370 --> https://bugs.winehq.org/attachment.cgi?id=54370 error message
It has gone forward again. This time wine-staging 1.9.8
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #22 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- No change for me with plain wine 1.9.9: Same exceptions as comment #16 and #17.
With wine-staging 1.9.8, I get int $3 exception as in comment #19.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #23 from super_man@post.com --- Still doesnt run.
I am blocked by bug 38648. Which I had to hack around.
fixme:d3d11:shdr_handler Unhandled chunk "STAT" fixme:d3d11:skip_dword_unknown Skipping 4 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0x57fa7fb8 fixme:d3d11:skip_dword_unknown 0xb118f398 fixme:d3d11:skip_dword_unknown 0x6b36ae8a fixme:d3d11:skip_dword_unknown 0x5b01ad24 fixme:d3d11:skip_dword_unknown Skipping 1 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0x00000001 fixme:d3d11:shdr_handler Unhandled chunk "RDEF" err:d3d_shader:shader_get_registers_used Invalid resource index 24. fixme:d3d11:d3d11_immediate_context_GetData iface 0x480b4da0, asynchronous 0x482cbb40, data 0x54ede310, data_size 4, data_flags 0 stub! fixme:d3d:wined3d_buffer_create Ignoring access flags (pool). fixme:d3d11:d3d_buffer_init Ignoring structure byte stride 40.
I quess some of these lines needs fixing.
staging 1.9.13
https://bugs.winehq.org/show_bug.cgi?id=38436
Zeke Sonxx zeke@zekesonxx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zeke@zekesonxx.com
--- Comment #24 from Zeke Sonxx zeke@zekesonxx.com --- So, it's been several months since someone attacked this, so I decided to give it a go.
The current version of the R* Social Club launcher has an updated version of CEF, which has resumed causing subprocess.exe to crash (I suspect it's the same problem that Steam's steamwebhelper has). I have a version of R*SC from my Windows installation, almost a year old at this point, which says it's corrupted if you try to use it.
/However/, if I load that version, and then run the SC installer included in the game ("Social-Club-Setup.exe"; not "Social Club v1.1.5.6 Setup.exe"), the launcher will actually launch the game. The launcher will also break itself, but setting "Program Files/Rockstar Games" and it's 32-bit equivalent to read-only will prevent that.
winetricks installed: vcrun2012 (as included with the game), steam, dxd10
I'd be happy to privately provide a copy of that R*SC installation to anyone who would like it, just email me.
So, I can now reliably launch the actual game. I've been testing with Wine 1.9.23-staging and Wine 1.9.24 non-staging. The game behaves identically in both versions unless otherwise mentioned
For Windows versions I have default on WinXP, GTA5.exe on Win7 and GTAVLauncher.exe on WinXP (also Steam.exe and steamwebhelper.exe on WinXP just so they stop complaining at me).
Running with GTA5.exe in WinXP mode results in it starting to launch (full-screen black window) followed by a popup ERR_MEM_EMBEDDEDALLOC_ALLOC "Out of game memory. Please reboot and restart the game."
Running with GTA5.exe in Win7 mode results in it trying to start, followed by a Wine "this application has buggered up" box. On 1.9.23-staging it gets a black screen and crashes quickly, on 1.9.24 it never opens anything and eventually Wine pops up with the crash box.
Running with GTA5.exe in WinVista mode results in pretty much the same result as Win7 mode, however under 1.9.24 it gives me a different backtrace.
I intend to do more experimentation, including trying some recent git versions of Wine, and will report back with what I find.
After I post this comment I'll also post backtraces for the current launcher version, 1.9.24 crash in Win7 mode, and 1.9.24 crash in WinVista mode.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #25 from Zeke Sonxx zeke@zekesonxx.com --- Created attachment 56349 --> https://bugs.winehq.org/attachment.cgi?id=56349 Up-to-date launcher subprocess.exe crash as of posting date (Win7, Wine 1.9.24)
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #26 from Zeke Sonxx zeke@zekesonxx.com --- Created attachment 56350 --> https://bugs.winehq.org/attachment.cgi?id=56350 GTA5.exe Wine 1.9.24 crash in Win7 mode
Upon further examination the crash in WinVista mode appears to be identical to this one, so I will not be posting the WinVista backtrace unless requested.
https://bugs.winehq.org/show_bug.cgi?id=38436
Kimmo Myllyvirta kimmo.myllyvirta@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kimmo.myllyvirta@gmail.com
--- Comment #27 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- (In reply to Zeke Sonxx from comment #24)
I intend to do more experimentation, including trying some recent git versions of Wine, and will report back with what I find.
After I post this comment I'll also post backtraces for the current launcher version, 1.9.24 crash in Win7 mode, and 1.9.24 crash in WinVista mode.
Could you tell your system specs (gpu mainly)?
Here's my results with GTX980 (367.57), Ubuntu 16.04, wine-1.9.24. Clean prefix, steam version, nothing changed from winecfg (so it is winxp), no winetricks used.
The launcher shows up, disappears, nothing visible happens, and after a few seconds the game crashes. +d3d,+d3d11 does not give any hints, it doesn't go that far. +loaddll shows that the the game tries to load nvapi64.dll repeatedly for a few seconds. It eventually gives up and crashes.
There's stub implementation for nvidia nvapi in staging, but I didn't try that, instead I opened regedit and added these to HKCU/Software/Wine/Direct3D; VideoPciDeviceID 0x67df VideoPciVendorID 0x1002
That's AMD RX480. Now the game starts up. I can hear the sounds and music, but the screen is black. It doesn't crash. It eventually hangs, but I didn't investigate that far. The terminal is filled with the usual d3d11 fixmes.
So, the first issue for us nvidia card owners is the missing nvapi, it seems.
Setting the windows version to win7 results to the same libcef.dll crash as you mentioned.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #28 from Zeke Sonxx zeke@zekesonxx.com --- Created attachment 56363 --> https://bugs.winehq.org/attachment.cgi?id=56363 GTA5.exe crash, page fault from d3d11 (Wine 1.9.24)
(In reply to Kimmo Myllyvirta from comment #27)
Could you tell your system specs (gpu mainly)?
Intel Core i5-2320; shitty prebuilt Acer motherboard; NVIDIA GeForce GTX 970; 16GB RAM. Arch Linux x64, kernel 4.8.11-ARCH, proprietary nvidia drivers 375.20, wine versions as mentioned.
Now the game starts up. I can hear the sounds and music, but the screen is black. It doesn't crash. It eventually hangs, but I didn't investigate that far. The terminal is filled with the usual d3d11 fixmes.
So I can't seem to get that far. Using the RX480 regedit I can get /farther/, but then crash due to a page fault with d3d11 at the top of the stack. Log attached.
https://bugs.winehq.org/show_bug.cgi?id=38436
cetedus@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cetedus@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #29 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- Created attachment 56371 --> https://bugs.winehq.org/attachment.cgi?id=56371 debug log tid,dxgi,d3d,d3d11 with -dx10
(In reply to Zeke Sonxx from comment #28)
So I can't seem to get that far. Using the RX480 regedit I can get /farther/, but then crash due to a page fault with d3d11 at the top of the stack. Log attached.
I already moved to wine-2.0-rc1. The game is extremely unstable with 1.9.24, it needs WINED3DFMT_R32G8X24_TYPELESS and various other fixes, which are in wine-2.0-rc1.
Now the debug log is almost free of errors, there's only one obvious issue there; fixme:d3d11:d3d_texture2d_init Multisampled textures not implemented.
Which can be worked around by starting the game with "-dx10" command line argument (which forces it to use feature level 10), see; https://support.rockstargames.com/hc/en-us/articles/202518358-Available-Comm...
But still just a black screen. No errors, mostly harmless fixmes and warns, afaics.
Debug log attached, there's lots of background noise from the launcher (which uses d3d9) and Steam. grep '00bd:|00d1:' should help.
If someone wants to update the dependencies, then; multisampled textures: bug 39754 and/or bug 41207 nvidia nvapi: bug 35062
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #30 from Zeke Sonxx zeke@zekesonxx.com --- (In reply to Kimmo Myllyvirta from comment #29)
But still just a black screen. No errors, mostly harmless fixmes and warns, afaics.
I'm able to replicate your results in 2.0-rc1 and 2.0-rc2, with the RX480 regedit. Even with the -staging versions of rc1 and rc2 it won't run without the RX480 regedit.
Well cool. Now Wine just needs multistream texture support, and GTAV might just get working.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #31 from Zeke Sonxx zeke@zekesonxx.com --- Wine 2.0-rc5-staging update: same results across the board as with 2.0-rc2. As expected due to the code freeze.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #32 from Zeke Sonxx zeke@zekesonxx.com --- So it's been a while. Wine 2.0-staging, 2.1-staging, 2.2-staging, and 2.3-staging all have had nothing really change.
I've been testing with CSMT enabled and disabled, -dx10 and -dx11, and the RX480 registry hack enabled and disabled.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #33 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- (In reply to Zeke Sonxx from comment #32)
I've been testing with CSMT enabled and disabled, -dx10 and -dx11, and the RX480 registry hack enabled and disabled.
Yep, there's not much progress with the nvapi, so the registry hack is needed. I'll continue in bug #42330 with that black screen issue. You could try the alt+enter trick (it may need some retries).
https://bugs.winehq.org/show_bug.cgi?id=38436
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #34 from winetest@luukku.com --- (In reply to Kimmo Myllyvirta from comment #27)
There's stub implementation for nvidia nvapi in staging, but I didn't try that, instead I opened regedit and added these to HKCU/Software/Wine/Direct3D; VideoPciDeviceID 0x67df VideoPciVendorID 0x1002
That's AMD RX480. Now the game starts up. I can hear the sounds and music, but the screen is black. It doesn't crash. It eventually hangs, but I didn't investigate that far. The terminal is filled with the usual d3d11 fixmes.
So, the first issue for us nvidia card owners is the missing nvapi, it seems.
Does your gpu match any of these lines?
https://source.winehq.org/git/wine.git/?a=search&h=HEAD&st=grep&...
At least mesa part seems to be missing for that card...or it's a dupe with some other card.
cards_nvidia_mesa[] =
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #35 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- GTX980 with proprietary 375.39 (so that should not affect). Crashes also with GTX680, GTX970, and also with GTX1060 in bug #42528. Let's clarify the current situation. If you are running this game with (any?) nvidia card, the game expects to find nvapi64.dll, which exists only in staging, so; Without the nvapi64.dll, the game crashes. With nvapi64.dll; - start it in fullscreen mode, then the game complains about missing directx 10/11 compatible adapter, and crashes. - start it in windowed mode, then the game complains about "Out of game memory.", and crashes.
But then; When you fool the game to think you have some intel or AMD card with that regedit hack, the game doesn't even try to use nvapi64.dll, and starts ok. So yes, I'm pointing my finger at the stub nvapi.
https://bugs.winehq.org/show_bug.cgi?id=38436
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=38436
BieHDC byi5000@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |byi5000@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #36 from winetest@luukku.com --- It starts for me now. The main screen is only blank and I had to go to full screen I quess I did alt+enter.
I had to workaround bug 38648.
I was able to start story mode game then. But it's all so slow and console is spammed heavily.
wine-staging 2.4.
https://bugs.winehq.org/show_bug.cgi?id=38436
Lectrode electrodexsnet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |electrodexsnet@gmail.com
--- Comment #37 from Lectrode electrodexsnet@gmail.com --- Created attachment 58349 --> https://bugs.winehq.org/attachment.cgi?id=58349 Out of memory error log
I can't seem to get passed the "Out of memory" error. Upon executing the game, Social club loads correctly. I get to a black screen and immediately get an out of memory error Tried starting windowed and full screen. I don't get a chance to press Alt+Enter before the error message appears.
GTX970 -proprietary driver: 375.66
16GB RAM Filesystem: Btrfs
Wine build: wine-2.8 (Staging) Platform: x86_64 Version: Windows 7 Host system: Linux
Kernels tested: -4.9.30-1-MANJARO -4.11.3-1-MANJARO
Create prefix: WINEPREFIX=$HOME/.wine_gta5 winetricks -q allfonts steam
Tried with and without: WINEPREFIX=$HOME/.wine_gta5 wine reg add "HKCU\Software\Wine\Direct3D\" /v VideoPciDeviceID /d 0x67df /f WINEPREFIX=$HOME/.wine_gta5 wine reg add "HKCU\Software\Wine\Direct3D\" /v VideoPciVendorID /d 0x1002 /f
Tried with and without: WINEPREFIX=$HOME/.wine_gta5 wine reg add "HKCU\Software\Wine\Direct3D\" /v MaxVersionGL /d 0x30002 /f
Tried with and without: WINEPREFIX=$HOME/.wine_gta5 winetricks videomemorysize=2048
Game run with and without -DX10
Please see attached log. It is 4.11 + VideoPciDeviceID + VideoPciVendorID + MaxVersionGL + -DX10
What am I missing?
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #38 from Lectrode electrodexsnet@gmail.com --- for my previous comment: *past, not passed
Just a tad more info: Upon clicking "Ok" on the Out of Memory error, GTA 5 crashes and returns to the social club launcher, which can be closed normally.
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #39 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- (In reply to Lectrode from comment #37)
Please see attached log. It is 4.11 + VideoPciDeviceID + VideoPciVendorID + MaxVersionGL + -DX10
What am I missing?
It is still using nvapi, in the log you'll see lots of; fixme:nvapi:unimplemented_stub function ... You are adding deviceid and vendorid as strings, they need to be dwords, this should work; wine reg add "HKCU\Software\Wine\Direct3D\" /v VideoPciDeviceID /t REG_DWORD /d 0x67df /f wine reg add "HKCU\Software\Wine\Direct3D\" /v VideoPciVendorID /t REG_DWORD /d 0x1002 /f
There's an alternative for the registry hack, start the game with "-GPUCount 1" command line argument (yes, even if you have only one gpu). But it may cause other problems problems. E.g. Settings -> Graphics -> Video Memory always shows something like xxxx / 512 MB due to unimplmeneted NvAPI_GPU_GetPhysicalFrameBufferSize. Probably best to use the registry hack for now.
https://bugs.winehq.org/show_bug.cgi?id=38436
Michale Willis frankypapper@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frankypapper@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #40 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Tested with plain wine 2.11.
The game no longer fail to launch. It starts and runs as bad/good as with wine-staging.
The fix is in the 9 patches submitted by Michael Müller, previously found in the wine-staging patch-set server-LABEL_SECURITY_INFORMATION.
The bug should be closed and other issues reported separately, IMO.
https://bugs.winehq.org/show_bug.cgi?id=38436
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #41 from Kimmo Myllyvirta kimmo.myllyvirta@gmail.com --- (In reply to Olivier F. R. Dierick from comment #40)
Tested with plain wine 2.11.
The game no longer fail to launch. It starts and runs as bad/good as with wine-staging.
The fix is in the 9 patches submitted by Michael Müller, previously found in the wine-staging patch-set server-LABEL_SECURITY_INFORMATION.
The bug should be closed and other issues reported separately, IMO.
I can't confirm that with the Steam version of the game and wine-2.11-dev, clean prefix, GTX980 (375.66), still crashes. Did you use the same prefix with staging and dev (or didn't have nvidia card)? You may have nvapi64 dll left from staging if you ran only make install. With wine-2.11-staging the game starts up without regedit or command line hacks, and video memory size is correct in settings->graphics, behaves as before after reverting patches; 0017-nvapi-Improve-NvAPI_D3D_GetCurrentSLIState.patch 0018-nvapi-Implement-NvAPI_GPU_Get-Physical-Virtual-Frame.patch 0019-nvapi-Add-stub-for-NvAPI_GPU_GetGpuCoreCount.patch
https://bugs.winehq.org/show_bug.cgi?id=38436
--- Comment #42 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- The original bug is about the crash in GTA5Launcher.exe/subprocess.exe that did prevent the launcher from starting at all.
The nvapi issue appears in a later stage of the startup of the program.
It was exposed with wine-staging because wine-staging did have the fix for original bug.
The original bug is now fixed because the fix that was in wine-staging has been merged with plain wine 2.11.
The nvapi issue is still present and requires registry tweaks or patching.
I do not agree to make this bug a meta-bug about any crash/issue of the game. It has already been abused enough and should be closed.
Please, file other bugs reports for the other issues that have been exposed while fixing the original bug.
https://bugs.winehq.org/show_bug.cgi?id=38436
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |joseph.kucia@gmail.com Resolution|--- |FIXED
--- Comment #43 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Olivier F. R. Dierick from comment #40)
Tested with plain wine 2.11.
The game no longer fail to launch. It starts and runs as bad/good as with wine-staging.
The fix is in the 9 patches submitted by Michael Müller, previously found in the wine-staging patch-set server-LABEL_SECURITY_INFORMATION.
Fixed.
https://bugs.winehq.org/show_bug.cgi?id=38436
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #44 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.1.
-
wine-bugs＠winehq.org