[Bug 44675] New: Stories Untold: DX11 Shader is so strong that text becomes illegible
https://bugs.winehq.org/show_bug.cgi?id=44675 Bug ID: 44675 Summary: Stories Untold: DX11 Shader is so strong that text becomes illegible Product: Wine Version: 3.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: rca(a)psy-q.ch Distribution: --- Created attachment 60683 --> https://bugs.winehq.org/attachment.cgi?id=60683 Log while playing Stories Untold In the Windows version, the text on screen in the first chatper of this game should be yellow and easily legible. In WINE 3.3, it's orange-red and almost unreadable. The attached message repeats endlessly in the log. Perhaps this issue is also related to blur shaders in some DX11 games (e.g. Dirt 3) being too strong. There seems to be a trend of "too much". The following is on WINE 3.3: https://i.imgur.com/9S6bXvv.png?1 This is how it looks on Windows: https://i.redd.it/c3rramoeahaz.png -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3dx11 |directx-d3d CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Don't think it's an d3dx issue, shaders are usually a problem with the core d3d library. Do you know how to use apitrace? If so, you could record a d3d apitrace under wine, then we could just replay the trace to reprodcue the problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #2 from Ramon Cahenzli <rca(a)psy-q.ch> --- (In reply to Fabian Maurer from comment #1)
Do you know how to use apitrace?
Not yet :) I just quickly browsed the docs but will have to read a little more about it and then I'll try to generate a trace. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #3 from Ramon Cahenzli <rca(a)psy-q.ch> --- I have apitrace set up now, but Stories Untold does not use d3d9.dll. The log says: warning: Z:\*PATH_REDACTED*\win\apitrace\apitrace-msvc\x86\bin\..\lib\wrappers\d3d9.dll was never used: application probably does not use this API And I'm attaching a much longer log that shows some of the d3d11 messages. I tried to snip those that are endlessly repeating. Maybe one of the known missing features is making the shaders behave in this way? The apitrace web page lists DX11 in its support matrix, but the binaries released at https://people.freedesktop.org/~jrfonseca/apitrace/ don't include a DLL for it. I'm unable to cross-compile the DLLs from Linux (if they would even compile without Visual Studio). If I can get to DX11 versions of those DLLs I'm happy to do a trace. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #4 from Ramon Cahenzli <rca(a)psy-q.ch> --- Created attachment 60688 --> https://bugs.winehq.org/attachment.cgi?id=60688 Longer log showing more d3d11 messages -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #5 from Ramon Cahenzli <rca(a)psy-q.ch> --- I just found out about DXGI tracing for DX10/11. Ignore my previous comment. Will start on that now. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #6 from Ramon Cahenzli <rca(a)psy-q.ch> --- I have a DXGI trace now. Unfortunately, running apitrace makes the game loop so slow that I can't start a game (the mouse clicks are ignored) so the dark scene from the screenshot is never reached. But there is stuff that is too dark with very weird shaders in the background of the main menu as well. Maybe these things are related and the traces are useful anyway: https://drive.google.com/drive/folders/1KPyWliGSGQK9u8ikNUDIijaSQzM3bD4t?usp... The .trace file is when launching Stories Untold.exe via apitrace, but then it launches Steam from within itself and restarts Stories Untold.exe. That produces Stories Untold.1.trace. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Stories Untold: DX11 Shader |Stories Untold: text is |is so strong that text |illegible |becomes illegible | --- Comment #7 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Is the problem also reproducible with the GOG or Steam demo? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #8 from Ramon Cahenzli <rca(a)psy-q.ch> --- The demo shows additional problems not present in the full version. The scene is even darker, you can barely make out the lighted are of the desk lamp: https://i.imgur.com/tB55ITp.png The logs are attached but don't differ too much from the full version. DXGI apitrace of the demo is available, but the game crashes after the menu and before getting in-game when being traced: https://drive.google.com/open?id=1KPyWliGSGQK9u8ikNUDIijaSQzM3bD4t The error produced is "dxgitrace.dll caused an Access Violation (0xc0000005) in module dxgitrace.dll at 0023:019a4590.", so I guess that's it for apitraces at the moment. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #9 from Ramon Cahenzli <rca(a)psy-q.ch> --- Created attachment 60696 --> https://bugs.winehq.org/attachment.cgi?id=60696 Stories Untold demo log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #10 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-4.9? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #11 from Ramon Cahenzli <rca(a)psy-q.ch> --- Created attachment 64621 --> https://bugs.winehq.org/attachment.cgi?id=64621 Stdout when running on AMD with Mesa 19.0.2 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #12 from Ramon Cahenzli <rca(a)psy-q.ch> --- (In reply to joaopa from comment #10)
Does the bug still occur with wine-4.9?
It's worse for me now, I have switched to an AMD graphics card and the game shows only a black screen when going in-game. Menus (accessed via ESC) work, but nothing is rendered, the attached log displays in stdout. I am sorry that I can't test this bug anymore in my original configuration. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=44675 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #13 from Stian Low <wineryyyyy@gmail.com> --- Created attachment 80910 --> http://bugs.winehq.org/attachment.cgi?id=80910 Screenshot WINED3D, DAMAVAND, & Windows all displaying consistent text graphics Unable to reproduce original gl err/fixme logs reported: 003f:err:d3d:wined3d_debug_callback 0x99a82a8: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.". Attached is a screenshot of WINED3D, DAMAVAND/Vulkan, and Windows versions all displaying consistent graphics that appear yellow that reporter describes as correct. Unfortunately original images were not uploaded to wine and URLs are broken so unable to compare with those. (In reply to Ramon Cahenzli from comment #12)
It's worse for me now, I have switched to an AMD graphics card and the game shows only a black screen when going in-game. Menus (accessed via ESC) work, but nothing is rendered, the attached log displays in stdout. I am sorry that I can't test this bug anymore in my original configuration.
Regarding black screen, it was probably caused by default Windows version switching from win8 to win10 around that time which changes many Unity game behaviors including vulkan/DAMAVAND rendering graphics darker than gl/WINED3D as described by https://bugs.winehq.org/show_bug.cgi?id=45364. Black screen is reproducible for `winecfg /v win10` so attached screenshots were only possible for `winecfg /v win8` These fixmes are spam/logged for black screen which seems similar to problems for Signifier videos playing black (https://bugs.winehq.org/show_bug.cgi?id=56614): 02d8:fixme:dxgi:dxgi_resource_GetSharedHandle iface 0000000040BA12B8, shared_handle 0000000006E5EC60 stub! 02d8:fixme:dxgi:dxgi_resource_GetSharedHandle iface 0000000040BA12B8, shared_handle 0000000006E5EC60 stub! 02d8:fixme:dxgi:dxgi_resource_GetSharedHandle iface 0000000040BA12B8, shared_handle 0000000006E5EC60 stub! Unlike Signifier however, Stories Untold remains black even for gameplay vs Signifier which only has black screens for videos but not gameplay. This issue should probably remain open until the black screen issues are fixed despite the original text illegibility seemingly fixed for win8. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #14 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #13)
Created attachment 80910 [details] Screenshot WINED3D, DAMAVAND, & Windows all displaying consistent text graphics
Screenshot was taken for Windows 11 so Unity would be using win10 methods of rendering which causes black screen for wine that win8 works around by handling video and rendering without calls to dxgi_resource_GetSharedHandle that wine needs to support so that game runs consistent with win11. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #15 from Stian Low <wineryyyyy@gmail.com> --- Black screen for win10 seems caused by different way Unity loads/plays videos via mfplat vs win7. Black screen for win10 is fixed by renaming StreamingAssets to bogus name such as StreamingAssets_bogus: /wine_pfx/drive_c/GOG Games/Stories Untold/Stories Untold_Data/StreamingAssets /wine_pfx/drive_c/GOG Games/Stories Untold/Stories Untold_Data/StreamingAssets_bogus StreamingAssets contains StoriesUntold_Credits_1.mp4 which is the first video that plays for win7 but causes black screen for win10. mfplat involving dxgi_resource_GetSharedHandle seems to cause some malfunction that is not recovered from after video finishes playing. Renaming to StreamingAssets_bogus prevents the video from ever loading/playing which skips straight to gameplay without black screen that otherwise occurs if video is not forced to skip via bogus rename solution. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=44675 --- Comment #16 from Stian Low <wineryyyyy@gmail.com> --- wine-11.8-68dd9ef2cb5 for all my reports -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla