[Bug 58632] New: Against the Storm: Encyclopedia doesn't display animated sequences
http://bugs.winehq.org/show_bug.cgi?id=58632 Bug ID: 58632 Summary: Against the Storm: Encyclopedia doesn't display animated sequences Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kajitsu22(a)gmail.com Distribution: --- Created attachment 79188 --> http://bugs.winehq.org/attachment.cgi?id=79188 A complete terminal output of the running game. While I was playing Against the Storm, I opened the in-game encyclopedia. It works almost perfectly, but there's a bug: clickable animations on encyclopedia entries are not displayed at all, and are not playable. There are many entries with static images instead of clips, which are displayed normally, but not animations. It looks like this: https://filebin.net/9yz60cx4nhq0dlg9/bug_video.mp4 OS: Gentoo Linux x86_64 Kernel: 6.12.31-gentoo Videocard: NVIDIA GeForce RTX 2050 Mobile Against the Storm Steam page: https://store.steampowered.com/app/1336490/Against_the_Storm/ -- 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=58632 --- Comment #1 from Rafał Mużyło <galtgendo(a)o2.pl> --- First guess would be something being wrong with your gstreamer plugin set, but it might also be a result of a problem with your video drivers and/or mesa/vulkan. -- 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=58632 --- Comment #2 from kajitsu22(a)gmail.com --- (In reply to Rafał Mużyło from comment #1)
First guess would be something being wrong with your gstreamer plugin set, but it might also be a result of a problem with your video drivers and/or mesa/vulkan.
My mesa and video drivers are up to date, and I've just reinstalled gstreamer. I've also checked this on stable Wine Staging installation, and on newly-compiled master Wine Staging. The issue remains, unfortunately. -- 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=58632 --- Comment #3 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...:sigh:... First of all, does it work with vanilla wine ? Second, does it work with staging, but without dxvk ? Third, does it work if you remove vaapi gstreamer plugins ? - OK, this one might be a red herring, but as I don't use dxvk, I can't tell whether or not are those 'glx: failed to create dri3 screen' expected or not and if they have any impact on the gstreamer failures (which - surprisingly enough - don't seem to come (as it's usually the case) from *missing* plugins). Oh, if those animations are accessible outside of the game, run something like ffprobe/gst-discoverer-1.0 on them and post the info. -- 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=58632 --- Comment #4 from kajitsu22(a)gmail.com --- (In reply to Rafał Mużyło from comment #3)
...:sigh:...
First of all, does it work with vanilla wine ? No, it doesn't. The same. Second, does it work with staging, but without dxvk ? Nope, it also doesn't. Third, does it work if you remove vaapi gstreamer plugins ? - OK, this one might be a red herring, but as I don't use dxvk, I can't tell whether or not are those 'glx: failed to create dri3 screen' expected or not and if they have any impact on the gstreamer failures (which - surprisingly enough - don't seem to come (as it's usually the case) from *missing* plugins). If I knew how to remove them (or if I even have them), I'd do it just check. Oh, if those animations are accessible outside of the game, run something like ffprobe/gst-discoverer-1.0 on them and post the info. It's a Unity game with its classic file layout, so no. It's not possible.
-- 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=58632 --- Comment #5 from Rafał Mużyło <galtgendo(a)o2.pl> --- (In reply to kajitsu22 from comment #4)
(In reply to Rafał Mużyło from comment #3)
Oh, if those animations are accessible outside of the game, run something like ffprobe/gst-discoverer-1.0 on them and post the info. It's a Unity game with its classic file layout, so no. It's not possible.
You mean it's too much of a hassle, especially when it's not clear which file will it be. Well, that's unfortunate, but might not matter... So, we'll need to sift through a rather verbose log. Get it by running wine with WINEDEBUG='mfplat,quartz'. -- 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=58632 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #6 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Rafał Mużyło from comment #3)
...:sigh:...
...:sigh:... indeed Confirming for 10.13 commit d74d97cbf87 using shared wow64. Encyclopedia videos do not play. The game is also very laggy when moving the camera around. Or as a simple workaround, run the game via steam proton which typically works around video bugs: https://bugs.winehq.org/show_bug.cgi?id=56614#c23 https://bugs.winehq.org/show_bug.cgi?id=58492#c9 https://bugs.winehq.org/show_bug.cgi?id=50277#c32 To enable all video features run steam from command line via this command: steam steam://unlockh264/ Then, once steam is launched via the command above. To workaround this issue for now: 1. Click LIBRARY at the top left of Steam client 2. Click "+ Add a Game" button at the bottom left 3. Choose "Add a Non-Steam Game" 4. Click Browse and add your games .exe file 5. Click "Add Selected Program" 6. Right click the game .exe file just added to the game list 7. Click Properties in the right-click menu 8. Click Compatibility tab 9. Check mark "Force the use of a specific Steam Play compatibility tool" 10. Choose "Proton Experimental" from the list Why these workaround solutions are not more commonly recommended by WineHQ is an enigma to me. Proton uses a different rendering backend that not only fixes the video bugs but also the laggy gameplay when moving the camera around. I test proton outside of steam but for non-technical users using proton via steam is the easiest point click workaround solution for these types of video/rendering bugs. This issue should remain open despite the workaround until WineHQ resolves whatever discrepancy that prevents game videos from working for vanilla wine. -- 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=58632 --- Comment #7 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Rafał Mużyło from comment #5)
You mean it's too much of a hassle, especially when it's not clear which file will it be.
Well, that's unfortunate, but might not matter...
So, we'll need to sift through a rather verbose log. Get it by running wine with WINEDEBUG='mfplat,quartz'.
Many bug reporters may not be as technical as WineHQ insiders and are looking for simple fixes. Thank for the report and provide the quickest solution possible and sweat the technicalities after. -- 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=58632 --- Comment #8 from Rafał Mużyło <galtgendo(a)o2.pl> ---
Why these workaround *'solutions'* are not more commonly recommended by WineHQ is an enigma to me.
The emphasis is the shortest explanation. Basically, your approach is nearly opposite of bugs fixing. It's adding layers of duct tape and plaster without ever trying to determine what the actual problem is. And without knowing that, the actual bug will only ever get fix by chance due to a dev's unrelated tampering with the affected component. -- 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=58632 --- Comment #9 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Rafał Mużyło from comment #8)
And without knowing that, the actual bug will only ever get fix by chance due to a dev's unrelated tampering with the affected component.
These video bugs do not get fixed even when devs deliberately try: https://bugs.winehq.org/show_bug.cgi?id=50277 https://bugs.winehq.org/show_bug.cgi?id=56614
Basically, your approach is nearly opposite of bugs fixing.
Hard disagree. Bugs to users: videos broken My approach: fix users broken videos I agree much more technical work is required close this bug. But when bugs have workarounds and are already well documented it's not necessary to burden reporters with redundant work. Even if the work were not redundant, workarounds should be still suggested.
It's adding layers of duct tape and plaster without ever trying to determine what the actual problem is.
The actual problem is caused by whatever is lacking in wine that is solved by proton. Those layers of duct tape and plaster probably contain the solution that needs to be propagated to wine so that videos play without workarounds anymore. My approach: Diff proton vs wine to find the discrepancy. Hardly not ever trying to determine the actual problem. Rather I found a solution and now trying to apply it to wine. Why proton devs do not contribute fixes back to wine is also an enigma to me. Special sauce stays special for now. But 99% of the sauce just pure wine. So those layers of duct tape and plaster are quite thin. -- 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=58632 --- Comment #10 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Stian Low from comment #9)
Why proton devs do not contribute fixes back to wine is also an enigma to me.
Source is all available so technically contributed back. Perhaps it's less explicit to avoid wasting time on winehq. -- 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 (1)
-
WineHQ Bugzilla