https://bugs.winehq.org/show_bug.cgi?id=40863
Bug ID: 40863 Summary: Multiple 64-bit Unreal Engine 4 games crash at start (need d3d11_device_CreateUnorderedAccessView) Product: Wine Version: 1.9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: fjfrackiewicz@gmail.com Distribution: ---
Now that this bug has been fixed https://bugs.winehq.org/show_bug.cgi?id=40792 Unreal 4 Engine games still continue to crash when attempting to start them but this time they require a different feature to be implemented.
https://bugs.winehq.org/show_bug.cgi?id=40863
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple 64-bit Unreal |Multiple 64-bit Unreal |Engine 4 games crash at |Engine 4 games crash at |start (need |start |d3d11_device_CreateUnordere | |dAccessView) |
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #1 from fjfrackiewicz@gmail.com --- Created attachment 54874 --> https://bugs.winehq.org/attachment.cgi?id=54874 Wine 1.9.13 Terminal output for The Solus Project Windows 7 64-bit
https://bugs.winehq.org/show_bug.cgi?id=40863
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple 64-bit Unreal |Multiple 64-bit Unreal |Engine 4 games crash at |Engine 4 games crash at |start |start (need | |d3d11_device_CreateUnordere | |dAccessView)
https://bugs.winehq.org/show_bug.cgi?id=40863
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |40792
https://bugs.winehq.org/show_bug.cgi?id=40863
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t@web.de
--- Comment #2 from Ker noa blue-t@web.de --- https://www.winehq.org/pipermail/wine-patches/2016-June/151625.html features wined3d: Introduce wined3d_unordered_access_view.
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #3 from Ker noa blue-t@web.de --- and https://www.winehq.org/pipermail/wine-patches/2016-June/151626.html makes it for D3D11
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #4 from fjfrackiewicz@gmail.com --- (In reply to Ker noa from comment #2)
https://www.winehq.org/pipermail/wine-patches/2016-June/151625.html features wined3d: Introduce wined3d_unordered_access_view.
According to this commit: http://source.winehq.org/git/wine.git/commit/2f47a73c37e1549100e3dd69a6e567d...
that patch is already in Wine 1.9.13 so I should only need the second patch you proposed, right?
https://bugs.winehq.org/show_bug.cgi?id=40863
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
https://bugs.winehq.org/show_bug.cgi?id=40863
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #5 from super_man@post.com --- (In reply to fjfrackiewicz from comment #4)
Yes. Can you test it?
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #6 from fjfrackiewicz@gmail.com --- (In reply to super_man from comment #5)
Certainly. The only thing that worries me is that the patch was rejected. Give me some time, please, as I will need to compile Wine and all that :)
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #7 from fjfrackiewicz@gmail.com --- (In reply to super_man from comment #5)
I applied the patch, recompiled, and I am still getting the following error:
fixme:d3d:wined3d_shader_resource_view_init Buffer shader resource views not supported. fixme:d3d11:d3d11_device_CreateUnorderedAccessView iface 0xf09640, resource 0xf0c6c0, desc 0x60efe8, view 0x60efe0 stub!
Perhaps there is a reason it was rejected in the first place?
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #8 from fjfrackiewicz@gmail.com --- Fallout 4 also needs this feature implemented:
https://bugs.winehq.org/show_bug.cgi?id=40588
https://bugs.winehq.org/show_bug.cgi?id=40863
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia@gmail.com Component|-unknown |directx-d3d Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED
--- Comment #9 from Józef Kucia joseph.kucia@gmail.com --- Duplicate
*** This bug has been marked as a duplicate of bug 40588 ***
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #10 from Józef Kucia joseph.kucia@gmail.com --- (In reply to fjfrackiewicz from comment #7)
fixme:d3d11:d3d11_device_CreateUnorderedAccessView iface 0xf09640, resource 0xf0c6c0, desc 0x60efe8, view 0x60efe0 stub!
FWIW, the d3d11_device_CreateUnorderedAccessView() function is still a stub in your Wine so you haven't tested with the patch applied.
https://bugs.winehq.org/show_bug.cgi?id=40863
Rogutės rogutes@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rogutes@gmail.com
--- Comment #11 from Rogutės rogutes@gmail.com --- Created attachment 54993 --> https://bugs.winehq.org/attachment.cgi?id=54993 +d3d11,+dxgi,+fixme logs for Fallout4 with wine-1.9.13 + ID3D11UnorderedAccessView
I've tested Fallout 4 with wine-1.9.13 + the "Implement ID3D11UnorderedAccessView interface" patch from https://www.winehq.org/pipermail/wine-patches/2016-June/151626.html. Compare this log with https://bugs.winehq.org/attachment.cgi?id=54455 (wine-1.9.9 without ID3D11UnorderedAccessView).
With the patch, Fallout 4 doesn't complain about d3d11_device_CreateUnorderedAccessView anymore but it still doesn't run, so no idea if the patch is correct or not.
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #12 from Ker noa blue-t@web.de --- it mentions swapchains a couple of times, which might be the next problem to solve
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #13 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Rogutės from comment #11)
It seems that some texture format is not supported in wined3d. A log with "warn+d3d" should tell more.
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #14 from Rogutės rogutes@gmail.com --- Created attachment 55041 --> https://bugs.winehq.org/attachment.cgi?id=55041 Fallout 4 with WINEDEBUG=+d3d,+d3d11,+dxgi,+fixme
warn+d3d only adds this: warn:d3d:resource_init Format WINED3DFMT_R16_TYPELESS cannot be used for depth/stencil buffers. warn:d3d:resource_init Format WINED3DFMT_R16_TYPELESS cannot be used for depth/stencil buffers. warn:d3d:resource_init Format WINED3DFMT_R16_TYPELESS cannot be used for depth/stencil buffers. warn:d3d:resource_init Did not find a suitable GL resource type for resource type WINED3D_RTYPE_TEXTURE_2D. warn:d3d:wined3d_texture_init Failed to initialize resource, returning 0x8876086c warn:d3d:texture_init Failed to initialize texture, returning 0x8876086c. warn:d3d:wined3d_texture_create Failed to initialize texture, returning 0x8876086c.
Attached a log with +d3d,+d3d11,+dxgi,+fixme.
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #15 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Rogutės from comment #14)
This should be fixed in the current version from Git.
http://source.winehq.org/git/wine.git/commitdiff/c7fdde8e83640c43746fd363c1f...
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #16 from Rogutės rogutes@gmail.com --- Thanks Józef. Indeed with wine-1.9.14 Fallout4 goes one step further and shows a blank screen :)
I am willing to keep testing until it works. Is it ok if I keep reporting bugs for every new error we get? Where is the best place to get help deciphering the logs, so I know how to best describe a new bug? A separate bug for all bugs related to running Fallout4 wouldn't make sense, would it?
For now attaching the logs with wine-1.9.14 and a blank screen below.
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #17 from Rogutės rogutes@gmail.com --- Created attachment 55082 --> https://bugs.winehq.org/attachment.cgi?id=55082 WINEDEBUG=warn+d3d,+d3d11,+dxgi,+fixme fallout4.log
Attaching log from: WINEDEBUG=+fixme wine Fallout4 (wine-1.9.14, now shows a blank screen, was crashing in previous versions)
Here is a bigger attachment with warn+d3d,+d3d11,+dxgi,+fixme: http://chunk.io/f/dabcb4ba31354c568ee310d41da34022
https://bugs.winehq.org/show_bug.cgi?id=40863
--- Comment #18 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Rogutės from comment #17)
It seems that your GPU is not recognized as SM4-capable and the game runs in D3D_FEATURE_LEVEL_9_3 mode. Do you use Mesa drivers? Setting MaxGLVersion can be helpful. See also bug 38648.
Generally, I don't think that reporting bugs for every issue is very helpful. There is still a lot of work required to make this game run in Wine.
https://bugs.winehq.org/show_bug.cgi?id=40863
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #19 from Bruno Jesus 00cpxxx@gmail.com --- Closing duplicate bugs.