[Bug 60135] New: Media Foundation Source Reader rejects WMV2 to MFVideoFormat_RGB32 unless video processing is enabled
http://bugs.winehq.org/show_bug.cgi?id=60135 Bug ID: 60135 Summary: Media Foundation Source Reader rejects WMV2 to MFVideoFormat_RGB32 unless video processing is enabled Product: Wine Version: 11.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs@list.winehq.org Reporter: chaps-tulip-pumice@duck.com Target Milestone: --- Distribution: --- Created attachment 81723 --> http://bugs.winehq.org/attachment.cgi?id=81723 Issue included in this I encountered this problem while playing Wangan 5DX+, which prevented the game from launching. After having the AI analyze it, it was found to be a bug in Wine. Details of the problem are attached. -- 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=60135 --- Comment #1 from Rafał Mużyło <galtgendo@o2.pl> --- I must say it's a bit of an AI generated bug, but surprisingly well argued. So, is anyone familiar with MF_SOURCE_READER_ENABLE_VIDEO_PROCESSING and WMV2 topics in wine source? For completion, consider adding wine console log with 'mfplat' channel. -- 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=60135 --- Comment #2 from chaps-tulip-pumice@duck.com --- Created attachment 81724 --> http://bugs.winehq.org/attachment.cgi?id=81724 mfplat 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.
http://bugs.winehq.org/show_bug.cgi?id=60135 --- Comment #3 from Ken Sharp <imwellcushtymelike@gmail.com> --- Were you playing on an emulator? Can you provide a link to it? -- 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=60135 --- Comment #4 from chaps-tulip-pumice@duck.com --- (In reply to Ken Sharp from comment #3)
Were you playing on an emulator? Can you provide a link to it?
Using https://teknoparrot.com with https://archive.org/details/wmmt5dx -- 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=60135 --- Comment #5 from chaps-tulip-pumice@duck.com --- After AI patched the game's binary, I played 25 chapters of story mode without encountering any other problems.Very good game, makes me high -- 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=60135 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #6 from Stian Low <wineryyyyy@gmail.com> --- (In reply to chaps-tulip-pumice from comment #5)
After AI patched the game's binary, I played 25 chapters of story mode without encountering any other problems.Very good game, makes me high
Why is patching necessary? Does your tool perform unofficial custom patch or just apply some official patch? Glad your feeling it. -- 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=60135 --- Comment #7 from chaps-tulip-pumice@duck.com --- (In reply to Stian Low from comment #6)
(In reply to chaps-tulip-pumice from comment #5)
After AI patched the game's binary, I played 25 chapters of story mode without encountering any other problems.Very good game, makes me high
Why is patching necessary?
Does your tool perform unofficial custom patch or just apply some official patch?
Glad your feeling it.
The emulator has a custom patch to simulate an arcade environment, but in Wine, video processing still needs to be enabled to prevent crashes when launching the game, so this patch is currently necessary. -- 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=60135 --- Comment #8 from Stian Low <wineryyyyy@gmail.com> --- (In reply to chaps-tulip-pumice from comment #7)
The emulator has a custom patch to simulate an arcade environment, but in Wine, video processing still needs to be enabled to prevent crashes when launching the game, so this patch is currently necessary.
I understand emulator gets past dongle error via arcade simulation and that wine patch is necessary to prevent the game from crashing but why "AI patched the game's binary"? After dongle error fixed by emulator, I/O error now appears. Is that what game binary patch works around or something 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=60135 --- Comment #9 from chaps-tulip-pumice@duck.com --- (In reply to Stian Low from comment #8)
(In reply to chaps-tulip-pumice from comment #7)
The emulator has a custom patch to simulate an arcade environment, but in Wine, video processing still needs to be enabled to prevent crashes when launching the game, so this patch is currently necessary.
I understand emulator gets past dongle error via arcade simulation and that wine patch is necessary to prevent the game from crashing but why "AI patched the game's binary"?
After dongle error fixed by emulator, I/O error now appears. Is that what game binary patch works around or something else?
Set “mIcCardRw,” “mIcCardVender,” and “mForceFeedback” to 0 in the `Fsettings.lua.gz` and `Gsettings.lua.gz` files in the game's root directory. -- 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=60135 --- Comment #10 from Stian Low <wineryyyyy@gmail.com> --- (In reply to chaps-tulip-pumice from comment #9)
Set “mIcCardRw,” “mIcCardVender,” and “mForceFeedback” to 0 in the `Fsettings.lua.gz` and `Gsettings.lua.gz` files in the game's root directory.
So its actually just a settings override than actual binary/exe hack. I'll give it a try to reproduce. Thanks for extra helpful 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=60135 --- Comment #11 from chaps-tulip-pumice@duck.com --- Created attachment 81733 --> http://bugs.winehq.org/attachment.cgi?id=81733 Patch.xz
(In reply to chaps-tulip-pumice from comment #9)
Set “mIcCardRw,” “mIcCardVender,” and “mForceFeedback” to 0 in the `Fsettings.lua.gz` and `Gsettings.lua.gz` files in the game's root directory.
So its actually just a settings override than actual binary/exe hack. I'll give it a try to reproduce. Thanks for extra helpful info.
This is the exe hack to prevent the game from crashing before it reaches the main menu. The patch sets MF_SOURCE_READER_ENABLE_VIDEO_PROCESSING=TRUE on the game's existing Source Reader attribute store. With the original executable, SetCurrentMediaType(MFVideoFormat_RGB32) returns 0xC00D5212 and the game enters its DebugBreak error path. With only this attribute changed, Wine inserts the video processor and the game continues into normal gameplay. -- 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=60135 --- Comment #12 from Stian Low <wineryyyyy@gmail.com> --- (In reply to chaps-tulip-pumice from comment #11)
Created attachment 81733 [details] Patch.xz
Thanks for clarifying. Your attached patch confirms your tool indeed modifies the game binary wmn5r.exe. Binaries mods are probably typically considered less supported and less worthwhile to debug. Your patch seems to be flipping switches that wine may be able to handle itself if able to make it past the init errors onto main menu/gameplay.
Set “mIcCardRw,” “mIcCardVender,” and “mForceFeedback” to 0 in the `Fsettings.lua.gz` and `Gsettings.lua.gz` files in the game's root directory.
Using https://teknoparrot.com with https://archive.org/details/wmmt5dx
archive.org link you provided does not contain Fsettings.lua.gz nor Gsettings.lua.gz but found to exist for a different download link which has the settings already default 0 so your instructions seem inconsistent and confusing: - mIcCardRw = 0 - mIcCardVender = 0 - mForceFeedback = 0 Perhaps confusions/difficulties we seem to be having may be caused by LLM/tool lacking something fundamental and essential among humans. Regardless there may be enough to proceed with further testing for now which I will delay for a bit later. -- 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=60135 --- Comment #13 from chaps-tulip-pumice@duck.com --- (In reply to Stian Low from comment #12)
(In reply to chaps-tulip-pumice from comment #11)
Created attachment 81733 [details] Patch.xz
Thanks for clarifying.
Your attached patch confirms your tool indeed modifies the game binary wmn5r.exe.
Binaries mods are probably typically considered less supported and less worthwhile to debug.
Your patch seems to be flipping switches that wine may be able to handle itself if able to make it past the init errors onto main menu/gameplay.
Set “mIcCardRw,” “mIcCardVender,” and “mForceFeedback” to 0 in the `Fsettings.lua.gz` and `Gsettings.lua.gz` files in the game's root directory.
Using https://teknoparrot.com with https://archive.org/details/wmmt5dx
archive.org link you provided does not contain Fsettings.lua.gz nor Gsettings.lua.gz but found to exist for a different download link which has the settings already default 0 so your instructions seem inconsistent and confusing: - mIcCardRw = 0 - mIcCardVender = 0 - mForceFeedback = 0
Perhaps confusions/difficulties we seem to be having may be caused by LLM/tool lacking something fundamental and essential among humans.
Regardless there may be enough to proceed with further testing for now which I will delay for a bit later.
In my version, these two files appear automatically after launching the game once; they are indeed not included in the 7z file. When I delete these two files, the values for these three switches in the file`s automatically generated files are set to 1. -- 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=60135 --- Comment #14 from Stian Low <wineryyyyy@gmail.com> --- (In reply to chaps-tulip-pumice from comment #13)
In my version, these two files appear automatically after launching the game once; they are indeed not included in the 7z file.
When I delete these two files, the values for these three switches in the file`s automatically generated files are set to 1.
Thanks for further clarifying expectations. Curious if MR-11398 has any effect on mfplat behavior: - https://gitlab.winehq.org/wine/wine/-/merge_requests/11398#note_147852 MR-11398 supports failing for D3D11_CREATE_DEVICE_VIDEO_SUPPORT which allows UnityPlayer.dll to support software video processing which fixes videos for many Unity games. Curious if MF_SOURCE_READER_ENABLE_VIDEO_PROCESSING behavior may be related/dependent upon D3D11_CREATE_DEVICE_VIDEO_SUPPORT and if the game supports fallback behaviors similar to UnityPlayer.dll. Although WMV2 to MFVideoFormat_RGB32 may still be an issue regardless and may need to be fixed. Some of Unity games failed for NV12/I420 to MFVideoFormat_ARGB32 without MR-11398 which helped clarify the actual bugs which may also help for wmn5r.exe. I'll test soon. Thanks again for feedback. -- 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