[Bug 59142] New: Wine does not use blizzard.ax for WC3 cinematics when registered and displays black screen during cinematics
http://bugs.winehq.org/show_bug.cgi?id=59142 Bug ID: 59142 Summary: Wine does not use blizzard.ax for WC3 cinematics when registered and displays black screen during cinematics Product: Wine-staging Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: garrettm4@protonmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: --- For Warcraft III v1.29.2 (the last version before Blizzard changed from MPQ to CASC) both wine and wine-staging will not use the blizzard.ax media codec when registered ("wine regsvr32.exe /path/to/wc3_game/blizzard.ax") for playing in-game cinematics. The blizzard.ax codec is loaded and unloaded when the game is launched rather than when a cinematic is played. In wine and wine-staging 10.20, the in-game cinematics for v1.29.2 could be played when using LAVfilters with wine "regsvr32.exe /path/to/LAVFilters/LAVSplitter.ax /path/to/LAVFilters/LAVVideo.ax". However, this no longer works in wine-staging 11.0-rc1 and only a black screen is shown with audio playing. Curiously, Warcraft III v1.27b (the last stand-alone update to classic WC3) the videos will play with LAVFilters codecs on wine and wine-staging 11.0-rc1 when using a virtual desktop. Ultimately, LAVFilters shouldn't even be needed, the blizzard.ax codec included with the game should be used but isn't currently working with Wine. Both versions of WC3 classic can be obtained from hiveworkshop.com: https://www.hiveworkshop.com/threads/wc3-download-archive-1-00-1-31-1-beta-d... NOTES: 1. Valid CD keys are needed to play the base game and its expansion. An existing installation with patch 1.27b or older contains the keys in the MPQ files. The keys can be extracted and used with newer versions of the game by using a utility from hiveworkshop.com. 2. LAVFilters can be obtained from: https://github.com/Nevcairiel/LAVFilters/releases 3. All tests with v1.29.2 and v1.27b were done with wine and wine-staging using the Wayland driver by editing the registry and adding string "Graphics" with value "wayland,x11" to key HKCU\Software\Wine\Drivers 4. If display scaling is greater than 100% in GNOME/KDE, WC3 v1.27b may need forced high dip aware behavior with value "~ HIGHDIPAWARE" added to the default string in key HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. The winecfg DPI setting must match the display scaling: e.g., 200% display scale in GNOME/KDE => 192DPI setting in winecfg (100% display scale => 96DPI). 5. When testing WC3 v1.29.2 and v1.27b, know that the registry settings conflict with each other and you will want to delete the old registry values before switching or test with different prefixes. -- 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=59142 --- Comment #1 from garrett m <garrettm4@protonmail.com> --- Created attachment 79962 --> http://bugs.winehq.org/attachment.cgi?id=79962 screenshot before playing cinematic -- 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=59142 --- Comment #2 from garrett m <garrettm4@protonmail.com> --- Created attachment 79963 --> http://bugs.winehq.org/attachment.cgi?id=79963 screenshot of cinematic (black screen with audio) -- 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=59142 --- Comment #6 from garrett m <garrettm4@protonmail.com> --- Created attachment 79967 --> http://bugs.winehq.org/attachment.cgi?id=79967 log: v1.29.2, WINEDEBUG=-all,+loaddll with lavfilters registered --- Comment #7 from garrett m <garrettm4@protonmail.com> --- One may wonder why use v1.29.2 or v1.27b when Blizzard allows "Classic" playback in Reforged? First, any version newer than v1.29.2 uses CASC instead of MPQ and has very high CPU load compared to v1.29.2 or older when playing in Wine. For laptop users, this is a big deal. Furthermore, Reforged is also massive in size (30GB vs. 1.4GB) without any benefit for Classic mode gameplay. Version 1.29.2 is preferred over v1.27b since it fixes the stretched UI (keeping the cursor, menus, etc. all in 4:3 aspect ratio) and has better text scaling. It also works better with Wayland since this version defaults to a borderless fullscreen window instead of mode setting / exclusive fullscreen. It is also the last version that supports working OpenGL gameplay with "-graphicsapi OpenGL2" launch argument (use "-opengl" with 1.27b). -- 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=59142 Patrick Hibbs <hibbsncc1701@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hibbsncc1701@gmail.com --- Comment #9 from Patrick Hibbs <hibbsncc1701@gmail.com> --- FYI: It does play for me with the K-Lite Codec Pack if winegstreamer.dll is unregistered from the prefix, and the relevant filters are re-registered. (I.e. regsvr32.exe /u /s C:\windows\system32\winegstreamer.dll regsvr32.exe /s Path\to\K-Lite Codec Pack\DirectVobSub\vsfilter.dll regsvr32.exe /s Path\to\K-Lite Codec Pack\Filters\LAV\LAVAudio.ax regsvr32.exe /s Path\to\K-Lite Codec Pack\Filters\LAV\LAVVideo.ax regsvr32.exe /s Path\to\K-Lite Codec Pack\Filters\LAV\LAVSplitter.ax) Haven't tried with just blizzard.ax, but maybe something is causing winegstreamer to be chosen regardless of another custom filter being present? -- 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=59142 --- Comment #10 from garrett m <garrettm4@protonmail.com> --- I created a fresh 10.20 prefix, switched to the Wine Wayland driver and did not register blizzard.ax or lavfilters. WC3 was launched at 3840x2160,32bit resolution with the OpenGL 2 game engine and subtitles were enabled. For 1.27b, high DPI aware behavior was forced in the prefix. Turns out that Wine will auto load blizzard.ax, so there is no need to manually register it. It just loads/unloads when reaching the main menu, rather than loading while playing the cinematics. For both WC3 1.27b and 1.29.2, Using export WINEDEBUG=+quartz,+gstreamer,+mfplat caused the terminal log to spew infinite spam so fast that I'm not sure my logs are even useful. In 1.27b, the cursor could be hid when moving to the center of the screen, subtitles were shown but in the wrong position, the audio plays, but the screen otherwise remained black. In 1.29.2, the cursor is frozen, no subtitles are shown, the audio plays and the screen is black. When registering lavfilters: In 1.27b, the video is shown but small, subtitles are shown and in the correct position (at the bottom of the video). In 1.29.2, the video plays and is full-screen but no subtitles are shown. I tried unregistering winegstreamer.dll but it did not seem to do anything? The terminal output showed the command worked, but getting the cinematics to work still required lavfilters. The blizzard.ax codec was never used. -- 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=59142 --- Comment #11 from garrett m <garrettm4@protonmail.com> --- Created attachment 79982 --> http://bugs.winehq.org/attachment.cgi?id=79982 screenshot: wine 10.20, WC3 1.27b cinematic, default wine config audio plays, subtitles are shown but in wrong location, cinematic isn't shown -- 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=59142 --- Comment #12 from garrett m <garrettm4@protonmail.com> --- Created attachment 79983 --> http://bugs.winehq.org/attachment.cgi?id=79983 screenshot: wine 10.20, WC3 1.27b cinematic working with lavfilters -- 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=59142 --- Comment #13 from garrett m <garrettm4@protonmail.com> --- Created attachment 79984 --> http://bugs.winehq.org/attachment.cgi?id=79984 screenshot: wine 10.20, WC3 1.29.2 cinematic working with lavfilters -- 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=59142 --- Comment #14 from garrett m <garrettm4@protonmail.com> --- Created attachment 79985 --> http://bugs.winehq.org/attachment.cgi?id=79985 log: wine 10.20, WC3 1.27b cinematic, WINEDEBUG=-all,+quartz,+gstreamer,+mfplat -- 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=59142 --- Comment #15 from garrett m <garrettm4@protonmail.com> --- Created attachment 79986 --> http://bugs.winehq.org/attachment.cgi?id=79986 log: wine 10.20, WC3 1.29.2 cinematic, WINEDEBUG=-all,+quartz,+gstreamer,+mfplat -- 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=59142 --- Comment #16 from garrett m <garrettm4@protonmail.com> --- I forgot to mention, that to see the video play in Wine 10.20 with WC3 1.29.2, you have to press "super key" (windows key) to show the desktop in GNOME and then click on another window and then back on the WC3 window. I have no idea why that makes the cinematic visible. This trick does not seem to work with Wine 11.0-rc1. For 1.27b, you have to use launch the game with a virtual desktop for the cinematics to work (e.g., "wine explorer /desktop=wine,3840x2160 war3.exe -opengl"). WC3 1.27b uses mode setting / exclusive fullscreen and opens a new window to play the cinematic while 1.29.2 uses a borderless fullscreen window and does not create a new window when playing the cinematic. -- 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=59142 --- Comment #17 from Zeb Figura <z.figura12@gmail.com> --- I need the entire log, sorry, not just the last bit. You can compress it to make it fit in the attachment size; text files compress well. Also, I just need one configuration that should work and pick up blizzard.ax; please give me the case without lavfilters installed. -- 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=59142 --- Comment #18 from garrett m <garrettm4@protonmail.com> --- Created attachment 79995 --> http://bugs.winehq.org/attachment.cgi?id=79995 full log for wine 10.20, WC3 1.29.2 cinematic, WINEDEBUG=-all,+quartz,+gstreamer,+mfplat I disabled the terminal's scroll back limit and made two logs: One for the opening cinematic (only played when launching the game for the first time) and another when manually playing the first campaign's cinematic. Since the WINEDEBUG=-all,+quartz,+gstreamer,+mfplat debug log generates so much data, I tried to close the cinematics as fast as I could, but the logs are still 40k and 60k lines. I believe the logs should be complete this time. Let me know if you need anything else. -- 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=59142 --- Comment #19 from Rafał Mużyło <galtgendo@o2.pl> ---
I disabled the terminal's scroll back limit
...and what that does have anything to do with getting a full log ? Neither my favorite 'wine <the executable> 2>&1 | tee <random log name>' nor the slightly more hamfisted 'wine <the executable> &> <random log name>' recommended by wine's wiki page relies on the terminal scrollback. Also, just like 'all' is usually excessive for many reasons, including, but not limited to turning on 'relay' and the allocation channel (don't recall the name atm.), '-all' may filter out some messages, that *may* but don't have to be redundant. -- 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=59142 --- Comment #20 from Zeb Figura <z.figura12@gmail.com> --- (In reply to Rafał Mużyło from comment #19)
I disabled the terminal's scroll back limit
...and what that does have anything to do with getting a full log ?
Rafał, can you please stop finding the most rude and aggressive way to respond to people? Not everyone is used to redirecting output in the terminal. Your practice of discouraging people from continuing to engage with or file bug reports is doing an awful lot of harm to the project. -- 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=59142 --- Comment #21 from Rafał Mużyło <galtgendo@o2.pl> --- (In reply to Zeb Figura from comment #20)
(In reply to Rafał Mużyło from comment #19)
I disabled the terminal's scroll back limit
...and what that does have anything to do with getting a full log ?
Rafał, can you please stop finding the most rude and aggressive way to respond to people? Not everyone is used to redirecting output in the terminal. Your practice of discouraging people from continuing to engage with or file bug reports is doing an awful lot of harm to the project.
On one hand, you might be right that they might not know, but how would *you* get them to learn those basics ? Cause: a) sometimes the basics suffice to carry you for quite a bit; in this context, I personally actively know very little past the basics of shell redirection/autoconf syntax, yet on many occasions it had been still enough for my private use when I've tinkered in the past with some semi-abandoned projects, that needed minor fixes/updates there, yet some of the constructs in the resulting configure script tend to baffle me... b) given than one of those bits comes from wine's bug filing guide (well, maybe one reference away), do you actually discourage reading those ? yeah, bit of a strawman here, yet... On the other hand, Zeb, why are you so hype about it ? "the most rude and aggressive" ...not even close on the first (and that's only if you feel the need to read that as rude) and not at all on the second "Your practice of discouraging people..." Not my intent, quite the opposite actually...but, well, snowflakes... Yeah, yeah, I know, on occasions I'm bit of a one too, still... Everyone has their snowflake/idiot moments every now and then, it's how you get back on the track that matters. (I wonder, am I having a snowflake moment right now ? I don't think so, but, you know, difficult to tell while you're having one...) (personally, I'm starting to think you might be holding a bit of a grudge about the last cycle...) (...OK, the line above might count as passive aggressive (if you squint a bit), but you do see the difference, don't you ?) (this is getting at least a bit counterproductive (we're pretty much having a spat), but I still have have to say one thing: my first question was at very least semi-genuine) (I'm actually somewhat interested in this bug progressing, cause while I don't particularly care about the game, the described problem looks interesting, looking like a combination of codec priority problems (as long as that codec is actually getting effectively registered while the executable is running (obviously, a game won't be *globally* registering its private codec...at least one developed by an experienced studio shouldn't)) and creating/picking the right window to output the video to (will that be pixel format or something wayland specific ?)) (damn, I get so ranty on occasions, also so little actually relevant to the bug, now I feel the need to put some effort into something actually productive to balance this...:sigh:) -- 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=59142 --- Comment #22 from Zeb Figura <z.figura12@gmail.com> --- (In reply to Rafał Mużyło from comment #21)
On one hand, you might be right that they might not know, but how would *you* get them to learn those basics ?
"You can get the whole file more easily by redirecting to a file, e.g. `wine foo.exe &>log.txt`. See also <https://gitlab.winehq.org/wine/wine/-/wikis/FAQ#how-can-i-get-a-debugging-lo...>"
Cause: a) sometimes the basics suffice to carry you for quite a bit; in this context, I personally actively know very little past the basics of shell redirection/autoconf syntax, yet on many occasions it had been still enough for my private use when I've tinkered in the past with some semi-abandoned projects, that needed minor fixes/updates there, yet some of the constructs in the resulting configure script tend to baffle me...
And many Linux users have never interacted with the terminal at all, ever. That's a good thing! That also means that teaching someone to file a bug report is going to take a decent amount of effort given how far away from what it is they're used to.
b) given than one of those bits comes from wine's bug filing guide (well, maybe one reference away), do you actually discourage reading those ? yeah, bit of a strawman here, yet...
No, of course not, but I would rather have this bug report, with its flaws, and type a simple sentence like above explaining how to do something, than not have it because I'm too elitist to not drive the user away from the project.
"the most rude and aggressive" ...not even close on the first (and that's only if you feel the need to read that as rude) and not at all on the second
Hyperbole notwithstanding, yes, your responses are very rude and aggressive.
"Your practice of discouraging people..." Not my intent, quite the opposite actually...but, well, snowflakes... Yeah, yeah, I know, on occasions I'm bit of a one too, still... Everyone has their snowflake/idiot moments every now and then, it's how you get back on the track that matters.
Then please get back on track by adopting a much more neutral and helpful tone from now on. If you don't have the patience for that, please stop responding to bug 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.
http://bugs.winehq.org/show_bug.cgi?id=59142 --- Comment #23 from Zeb Figura <z.figura12@gmail.com> --- Created attachment 80004 --> http://bugs.winehq.org/attachment.cgi?id=80004 expose divx This might be enough to use the custom filter. I'm not convinced that's quite the reason for the black screen, though... -- 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=59142 --- Comment #24 from garrett m <garrettm4@protonmail.com> --- If you need me to do any new tests (or redo them), let me know. At least on Windows 10/11, registering blizzard.ax fixes the "black screen" issue. At first, I noticed that Wine didn't list blizzard.ax in the +loaddll log when the cinematics were playing, so I figured it might be a similar issue since registering lavfilters will allow them to play with v1.29.2 and v1.27b on wine 10.20. However, when testing more carefully with a clean prefix, it seems wine does load blizzard.ax when launching the game but unloads it after reaching the main menu and then never tries loading it when manually playing a cinematic. Anyways, there does seem to be a separate bug for v1.29.2 since the game does not open a new window to play the cinematics (uses a fullscreen borderless window) and currently requires another app to be focused on top of the game window first and then returning focus back to the game window will allow the cinematic to become visible. -- 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=59142 --- Comment #25 from Zeb Figura <z.figura12@gmail.com> --- (In reply to garrett m from comment #24)
If you need me to do any new tests (or redo them), let me know.
At least on Windows 10/11, registering blizzard.ax fixes the "black screen" issue.
Makes sense. If you could please test the patch from comment 23, and get a new log if it doesn't work, that'd be appreciated. -- 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=59142 --- Comment #26 from garrett m <garrettm4@protonmail.com> --- Sure. Is there a guide on how to apply patches and compile wine test builds? I haven't ever needed to do this before, but I'm happy to learn how and help with testing. (I have compiled various github projects with make, cmake, or meson for use on Arch but I've never worked with gitlab or wine before.) -- 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=59142 --- Comment #27 from Patrick Hibbs <hibbsncc1701@gmail.com> --- (In reply to garrett m from comment #26)
Sure. Is there a guide on how to apply patches and compile wine test builds? I haven't ever needed to do this before, but I'm happy to learn how and help with testing. (I have compiled various github projects with make, cmake, or meson for use on Arch but I've never worked with gitlab or wine before.)
There is. Wine uses autotools for it's build process. So if you're comfortable with make and github, then the process is mostly the same for wine: 1) Grab the source from https://gitlab.winehq.org/wine/wine.git 2) Install the build dependencies. 3) Apply the patch to the source with git am. 4) Run the build process. If you need a more in-depth explanation, there's always the build guide on the wiki: https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine Feel free to ask if you need more help. -- 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=59142 --- Comment #28 from garrett m <garrettm4@protonmail.com> --- Sorry, I forgot to give the patch a try due to the holidays. Just tried the final Wine 11.0 release and the video issue still persists (LAVfilters is still required to play videos and WC3 v1.29 will only play audio with a blackscreen). I'll try building Wine with the patch and testing tomorrow. -- 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=59142 --- Comment #29 from Zeb Figura <z.figura12@gmail.com> --- (In reply to garrett m from comment #28)
Sorry, I forgot to give the patch a try due to the holidays. Just tried the final Wine 11.0 release and the video issue still persists (LAVfilters is still required to play videos and WC3 v1.29 will only play audio with a blackscreen).
I'll try building Wine with the patch and testing tomorrow.
Sorry to pester, but have you had a chance to test yet? I can also provide a pre-built winegstreamer.dll if that would make things easier. -- 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=59142 --- Comment #30 from Zeb Figura <z.figura12@gmail.com> --- (In reply to Zeb Figura from comment #29)
I can also provide a pre-built winegstreamer.dll if that would make things easier.
Eh, not really actually, because this also needs changes to the Unix side, and it's a lot harder to be sure that the same .so will work on a different machine. -- 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=59142 --- Comment #31 from garrett m <garrettm4@protonmail.com> --- Apologies, I got distracted but should be able to get the patch tested once I get the compilation stuff figured out. So, I've got all the make dependencies listed on https://archlinux.org/packages/extra/x86_64/wine/ installed. I've downloaded the Wine source files with `git clone https://gitlab.winehq.org/wine/wine.git`. But now I'm having trouble actually finding the documentation on how to apply the patch (the "Git Wine Tutorial" doesn't cover this). I'm also struggling to find the compile-time build options in the WineHQ Wiki. I'd like this test build to live in /opt so it doesn't conflict with the existing Wine installation. If I could get some help with those two things, I'll get this tested ASAP. -- 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=59142 --- Comment #32 from garrett m <garrettm4@protonmail.com> --- Okay, I believe I've got the patch applied and Wine configured and built correctly: git clone https://gitlab.winehq.org/wine/wine.git ./wine-src cd wine-src git am ../2500-winegstreamer-Support-the-MPEG-4-part-2-format-in-Di.patch mkdir ../wine-patched cd ../wine-patched ../wine-src/configure \ CC="ccache gcc" i386_CC="ccache i686-w64-mingw32-gcc" x86_64_CC="ccache x86_64-w64-mingw32-gcc" \ --enable-archs=i386,x86_64 --disable-tests make I then renamed the existing .wine prefix to .wine_backup and made a new .wine using the patched Wine by running '~/wine-patched/wine winecfg' and then '~/wine-patched/wine regedit' to configure everything the same as before. I then launched the game with '~/wine-patched/wine /path/to/"Warcraft III.exe"'. Unfortunately, the patch didn't seem to work and the opening cinematic is just a black screen with audio. Registering LAVfilter, fixes the cinematics in v1.27b but not 1.29.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.
http://bugs.winehq.org/show_bug.cgi?id=59142 --- Comment #33 from Zeb Figura <z.figura12@gmail.com> --- (In reply to garrett m from comment #32)
I then launched the game with '~/wine-patched/wine /path/to/"Warcraft III.exe"'. Unfortunately, the patch didn't seem to work and the opening cinematic is just a black screen with audio. Registering LAVfilter, fixes the cinematics in v1.27b but not 1.29.2.
Can you please attach a new log with the patch? Same channels as before, WINEDEBUG=+quartz,+gstreamer,+mfplat. -- 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=59142 --- Comment #34 from garrett m <garrettm4@protonmail.com> --- Created attachment 80260 --> http://bugs.winehq.org/attachment.cgi?id=80260 log: patched wine, WC3 1.27b, WINEDEBUG=-all,+quartz,+gstreamer,+mfplat I should have remembered to do that, doh! P.S. I used '2>&1 | tee wine-patched.log', as suggested by Mużyło. -- 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=59142 --- Comment #35 from garrett m <garrettm4@protonmail.com> --- Ignore the new attachment's description, I only used 'WINEDEBUG=+quartz,+gstreamer,+mfplat', not 'WINEDEBUG=-all,+quartz,+gstreamer,+mfplat'. (I was copying the text from a previous attachment and didn't notice till after I submitted...) -- 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=59142 --- Comment #36 from garrett m <garrettm4@protonmail.com> --- Friendly, bump. If there is anything I can do to help let me know. Thanks! -- 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