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.