https://bugs.winehq.org/show_bug.cgi?id=40376
Bug ID: 40376 Summary: Black screen in Epic Games Launcher caused by d3d11 Product: Wine Version: 1.9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: felix-bachl@web.de Distribution: ---
A black screen can be seen. The following output is repeated endlessly.
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:d3d11:d3d11_immediate_context_RSSetState Ignoring FrontCounterClockwise 0x1. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented.
https://bugs.winehq.org/show_bug.cgi?id=40376
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #1 from super_man@post.com --- Is this the launcher?
https://launcher-public-service-prod06.ol.epicgames.com/launcher/api/install...
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #3 from super_man@post.com --- How do you install this? To me it seems that it needs more than wine-mono. Tried winetricks -q dotnet20 and it has some errors like this one
LogWindows:Error: === Critical error: === Assertion failed: SUCCEEDED(Hr) [File:D:\BuildFarm\buildmachine_++Portal+Release-Live\Engine\Source\Developer\StandaloneRenderer\Private\Windows\D3D\SlateD3DShaders.cpp] [Line: 80] D3D11 Error Result 80070057
Also how do you run this?
After this (invalid installation?) I only have
Epic Games/Launcher/Engine/Binaries/Win32
CrashReportClient.exe file in that directory. Most likely I need to redo the installation.
https://bugs.winehq.org/show_bug.cgi?id=40376
felix-bachl@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #2 from felix-bachl@web.de --- (In reply to super_man from comment #1)
Is this the launcher?
https://launcher-public-service-prod06.ol.epicgames.com/launcher/api/ installer/download/ParagonEpicGamesLauncherInstaller.msi
Yes it is.
https://bugs.winehq.org/show_bug.cgi?id=40376
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |michael@fds-team.de Ever confirmed|0 |1
--- Comment #4 from Michael Müller michael@fds-team.de --- I don't have any native dotnet installed in my prefix, but you need the following patch to prevent the application from running into an assert (included in Wine Staging 1.9.6).
https://github.com/wine-compholio/wine-staging/blob/master/patches/dwmapi-Dw...
I don't get the mentioned d3d11 error/assertion, only the fixmes mentioned in the original bug description (and the the black screen).
https://bugs.winehq.org/show_bug.cgi?id=40376
felix-bachl@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |felix-bachl@web.de
--- Comment #5 from felix-bachl@web.de --- (In reply to super_man from comment #3)
How do you install this? To me it seems that it needs more than wine-mono. Tried winetricks -q dotnet20 and it has some errors like this one
LogWindows:Error: === Critical error: === Assertion failed: SUCCEEDED(Hr) [File:D:\BuildFarm\buildmachine_++Portal+Release- Live\Engine\Source\Developer\StandaloneRenderer\Private\Windows\D3D\SlateD3DS haders.cpp] [Line: 80] D3D11 Error Result 80070057
Also how do you run this?
After this (invalid installation?) I only have
Epic Games/Launcher/Engine/Binaries/Win32
CrashReportClient.exe file in that directory. Most likely I need to redo the installation.
The latest wine-staging version is needed.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #6 from felix-bachl@web.de --- Actually it is a black window. The black screen can be seen if the application is running fullscreen.
https://bugs.winehq.org/show_bug.cgi?id=40376
felix-bachl@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Black screen in Epic Games |Black window in Epic Games |Launcher caused by d3d11 |Launcher caused by d3d11
https://bugs.winehq.org/show_bug.cgi?id=40376
Zentarim zentarim@rambler.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zentarim@rambler.ru
--- Comment #7 from Zentarim zentarim@rambler.ru --- Same problem in Warhammer 40000: Kill Team. Appears only black window. In wine log endless cycle of messages:
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:dxgi:dxgi_swapchain_Present Unimplemented sync interval 1 fixme:dxgi:dxgi_swapchain_GetFullscreenState iface 0xa0d4940, fullscreen 0x33fa28, target (nil) stub! fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #8 from Zentarim zentarim@rambler.ru --- (In reply to Zentarim from comment #7)
Same problem in Warhammer 40000: Kill Team. Appears only black window. In wine log endless cycle of messages:
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:dxgi:dxgi_swapchain_Present Unimplemented sync interval 1 fixme:dxgi:dxgi_swapchain_GetFullscreenState iface 0xa0d4940, fullscreen 0x33fa28, target (nil) stub! fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented.
Wine 1.8 or 1.8-staging. Nvidia GeForce9600. Core i5-760. Ubuntu 14.04.2 LTS, Trusty Tahr
https://bugs.winehq.org/show_bug.cgi?id=40376
plata@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |plata@mailbox.org
--- Comment #9 from plata@mailbox.org --- Not a fix, but you can avoid the issue by using OpenGl. Just use the "-OpenGL" parameter when you run Epic Games Launcher.
https://bugs.winehq.org/show_bug.cgi?id=40376
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #10 from winetest@luukku.com --- Could you put the download into url field and add a keyword: download? It would improve wine bug database searches.
I redownloaded the installer. This time I only used wine-staging. It installs and wants to download something. Assuming an update. Everything is going smoothly so far.
Then suddenly it gives an error something going terribly wrong. The original issue was black window. I can't replicate it.
wine-staging 2.0rc5. But the installer isn't usable at current form.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #11 from plata@mailbox.org --- Not sure about the download. Usually you must login to download the Launcher. Therefore I wasn't sure if it's ok to publish the URL.
I guess you are experiencing #41258 now.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #12 from winetest@luukku.com --- (In reply to plata from comment #11)
Not sure about the download. Usually you must login to download the Launcher. Therefore I wasn't sure if it's ok to publish the URL.
I guess you are experiencing #41258 now.
Could be. But are you still experiencing the black window? Could you take a screenshot?
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #13 from plata@mailbox.org --- I do not get the black window anymore. Just the error in #41258. (In fact it worked quite nicely before the Launcher update).
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #14 from winetest@luukku.com --- (In reply to Michael Müller from comment #4)
I don't have any native dotnet installed in my prefix, but you need the following patch to prevent the application from running into an assert (included in Wine Staging 1.9.6).
https://github.com/wine-compholio/wine-staging/blob/master/patches/dwmapi- DwmSetWindowAttribute/0001-dwmapi-Return-S_OK-from-DwmSetWindowAttribute- functi.patch
I don't get the mentioned d3d11 error/assertion, only the fixmes mentioned in the original bug description (and the the black screen).
The patch has been relocated already?
Fresh wineprefix. I only tested wine-staging 2.6 which should include the patch mentioned. I don't see black screen issue. To me it looks like that bug can't be reproduced anymore.
(In reply to plata from comment #13)
I do not get the black window anymore. Just the error in #41258. (In fact it worked quite nicely before the Launcher update).
I can confirm bug 41258. But not this one.
Unless someone is able to somehow reproduce this bug I think this should be closed.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #15 from plata@mailbox.org --- I get #41258 immediately when I start so I cannot tell if this bug is fixed or not.
https://bugs.winehq.org/show_bug.cgi?id=40376
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000@yahoo.co.uk
--- Comment #16 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- I can reproduce this blackscreen after using the installer sha1sum EpicGamesLauncherInstaller-2.14.0-3399308.msi 53f167f8a80ef38a75c796be2cbf3847cb32d5ff
(+ hack from bug https://bugs.winehq.org/show_bug.cgi?id=41258#c10)
With another installer a have lying around here I get the d3d11 crash described in bug 41258.
sha1sum EpicGamesLauncherInstaller-2.12.25-3343384.msi
As the installer keeps getting updated I think it`s very important to add info about what version of installer is used in the bugreport. For now I think we should keep this one open until bug 41258 is fixed.
https://bugs.winehq.org/show_bug.cgi?id=40376
--- Comment #17 from winetest@luukku.com --- (In reply to Louis Lenders from comment #16)
I can reproduce this blackscreen after using the installer sha1sum EpicGamesLauncherInstaller-2.14.0-3399308.msi 53f167f8a80ef38a75c796be2cbf3847cb32d5ff
(+ hack from bug https://bugs.winehq.org/show_bug.cgi?id=41258#c10)
With another installer a have lying around here I get the d3d11 crash described in bug 41258.
sha1sum EpicGamesLauncherInstaller-2.12.25-3343384.msi
As the installer keeps getting updated I think it`s very important to add info about what version of installer is used in the bugreport. For now I think we should keep this one open until bug 41258 is fixed.
The bug you mentioned is now STAGED. Been so sometime already also someone claimed that the issue has been fixed also client side. Can you reproduce these issues anymore?
https://bugs.winehq.org/show_bug.cgi?id=40376
Anton Romanov theli.ua@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |theli.ua@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=40376
js0803795@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |js0803795@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=40376
winetaste@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetaste@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=40376
temp82@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82@luukku.com
--- Comment #18 from temp82@luukku.com --- I think it's not anymore possible to reproduce this bug and this bug should be marked abandoned.
https://bugs.winehq.org/show_bug.cgi?id=40376
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
--- Comment #19 from mirh mirh@protonmail.ch --- I feel like it might be marked as a duplicate of bug 48068 (which has a far more compelling explanation, and far less detoured chatter)
https://bugs.winehq.org/show_bug.cgi?id=40376
Patrick McMunn doctorwhoguy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |doctorwhoguy@gmail.com
--- Comment #20 from Patrick McMunn doctorwhoguy@gmail.com --- (In reply to mirh from comment #19)
I feel like it might be marked as a duplicate of bug 48068 (which has a far more compelling explanation, and far less detoured chatter)
This bug was filed first, but yes, they are duplicates.
https://bugs.winehq.org/show_bug.cgi?id=40376
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |michelle@iheartmichelle.com
--- Comment #21 from Ken Sharp imwellcushtymelike@gmail.com --- *** Bug 48068 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=40376
F H francisco278herrera@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |francisco278herrera@gmail.c | |om
--- Comment #22 from F H francisco278herrera@gmail.com --- i can still reproduce this bug with the latest version of the epic games launcher in wine 10.0 rc2 and ubuntu 24.04. installing dxvk using winetricks works around this bug