Possibly Media Foundation related.

Is there any workaround for it?

There's a chance a nasty workaround like https://github.com/ValveSoftware/Proton/issues/1102#issuecomment-419678627 might help, but that needs several libraries from a Window 7 install to attempt and is not easy.

https://github.com/jzengc/wine/tree/proton_3.16_mf

this might work

Can I pass the 1st chapter in the demo? if so i can test that MF branch, I just might buy the game and test it too.

The red PC still causes the game to break.

https://github.com/ValveSoftware/Proton/issues/838#issuecomment-447379664
Another fix

<Link removed by moderator>

This build has mf support i think? Try it with the fix.
Source :
https://www.gamingonlinux.com/articles/theres-a-brand-new-steam-play-beta-version-out-with-faudio-also-a-steam-play-whitelist-update.13143/comment_id=143171

@james-munson please don't upload and link windows dlls like that, if they were distributable, we'd use standalone installer instead.

@kisak-valve I think it's better to remove this link https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-457803041.

<Link removed by moderator>

This build has mf support i think? Try it with the fix.
Source :
https://www.gamingonlinux.com/articles/theres-a-brand-new-steam-play-beta-version-out-with-faudio-also-a-steam-play-whitelist-update.13143/comment_id=143171

Do I need to create the compatibilitytools.d folder by myself?

I answer myself, yes.
Why do they know these folder names?
I'm redownloading the game, if it works, I can save lots of money from buying hard drive.

@nsivov that's not my upload.
@laichiaheng ?
https://github.com/ValveSoftware/Proton#install-proton-locally

sudo mkdir ~/.steam/steam/compatibilitytools.d/
and extract that build into that folder

Is it possible to build Proton with the latest wine-staging? The performance of Proton is really worse than wine-staging, Proton always runs at 4Xfps, no matter how low the setting is, wine-staging almost runs at 60fps always.

<Link removed by moderator>

This build has mf support i think? Try it with the fix.
Source :
https://www.gamingonlinux.com/articles/theres-a-brand-new-steam-play-beta-version-out-with-faudio-also-a-steam-play-whitelist-update.13143/comment_id=143171

Bad news, it doesn't work.

try this version of wine
https://github.com/spinozaure/wine/

or

https://github.com/kakra/wine-proton/releases

https://github.com/kakra/wine-proton/releases/download/wine-proton_3.16-4.0-unofficial-1/wine-proton_3.16-4.0-unofficial-1.tar.xz

, unpack within existing "Proton 3.16 Beta" folder.

Steam isn't able to download any Proton now, weird.

@james-munson I tried the 2nd method, and It didn't work.

Downloading the game will do more testing
did you try this?
https://github.com/ValveSoftware/Proton/issues/838#issuecomment-447379664

@james-munson Yes, I did, the game crashed.
Do I need to copy the 32bit dlls to SysWow64?

did you update dvxk?

32bit to normal system 32 and 64 in SysWow64

@james-munson Yes. It always stuck at 10% loading page, then it crashes.

32bit to normal system 32 and 64 in SysWow64

No, In Windows-64bit, System32 stores 64bit dlls, SysWow64 stores 32bit dlls.

having the same issue, just gets stuck on loading no matter what i try

@james-munson Windows is the only way to go, I just bought a 500GB SSD to install Windows 10 for this game 30min ago, now I'm going to install Windows 10.

https://www.reddit.com/r/linux_gaming/comments/ajyx51/resident_evil_2_playable_with_the_latest_dxvk_and/

@james-munson Damn! I just spent my money on SSD to play this game, I didn't have to spend that much! I can install Linux on this SSD though.

@james-munson Are you able to play this game now?

@laichiaheng no, not even with the newest dvxk, a guy on the that reddit post might have a fix.
I crash once i get in game after the trucker cut scene

"The solution was to export the CLSID branch, rename the paths in Wine's notepad, and then re-import the corrected .reg file.

I'm going to see how it's doing with that. "

Not sure how to do that.

DarkeoX
Check for the prefix registry, look at the "mf.dll" and "mfReadwrite.dll" paths under HKEY_CLASSES_ROOT\CLSID.

The Python thingy messed up in my install. Used "%SYSTEMROOT%" in the path but somehow Wine appends it as a relative path to the game's dir and of course can't find the dlls.

I had to export that branch of the registry, edit it in Wine's notepad not to mess up encoding and stuff, rewritting all "%SYSTEMROOT%\System32mf.dll" occurrences to "C:..." proper ones.

The solution:
https://github.com/doitsujin/dxvk/issues/886#issuecomment-458487008

With proton I can't play the game at all, when starting the game a black window opens and then directly closes and that's it. I also cant start the game using wine-staging from command line, because it then says it can't initialize the steam api even if steam is running. Only way I can run this game is by running the windows version of steam in wine-staging and then I also experience the bug described here that it can't load the second chapter.

You can't play with Proton because it has DXVK 0.94, and RE2 works only with newer versions. Replace DXVK files in the Proton folder with DXVK 0.96 if you want to play with Proton.

Thanks replacing the libraries in the dxvk folders helped, should I replace the libraries in the fakedlls folder as well or what is that copy in the fakedlls folder good for?
Also the game seems to run more smooth in wine-staging, couldn't steam add an option to use system wine instead of proton in the steam play settings? Also the save games seem not to be compatible, I could not load my wine-staging-windows-steam gamesave and had to create a new one.

The loading fix seems not to work for me, proton crashes when trying with the mf fix..
re2proton-crash.log

Ok I finally got it working, the problem was I _commented_ out the lines in the install script, should have read the instructions more carefully.. :upside_down_face:

[RE2] Savegame import not possible because of region mismatch

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2313.
@Mershl posted on 2019-02-05T19:34:24:

Compatibility Report

• Name of the game with compatibility issues: RESIDENT EVIL 2
• Steam AppID of the game: 883710

System Information

• GPU: GTX 1080
• Driver/LLVM version: nvidia 415.27
• Kernel version: 4.19
• Proton version: 3.16-6

I confirm:

• [X] that I have checked whether there are updates for my system available.

Symptoms

Resident Evil 2 saves contain the regional settings they were created in. At startup it performs a region check (reading sCountry, Locale and sLanguage from registry, eventually more) and marks the saves invalid if the regions do not match.
Setting the regional settings in the Windows Region&Language panel to match the ones used to create the savegame solves this issue.
Editing the wine prefix managed by Proton for RE2 does not solve this issue as the fields are (automatically) reset to "United States"/"ENU"/"409" after the edit.

Reproduction

• Enable Steam cloud saves for RE2 on a Windows machine with a region setting different than United States. Start game and save.
• Install RE2 via SteamPlay. First dialog ingame should mention "This save data is not compatible and cannot be used".

This Savegame problem is probably the same I mentioned before why I can't load my wine-staging saves using proton and vice versa.

I'm having an issue were my game crashes as soon as the first Leon cut scene starts with a new game my exact setup steps are from

https://github.com/doitsujin/dxvk/issues/886#issuecomment-458487008

1. Install game
2. Launch the game so proton creates the prefixes
3. export WINEPREFIX=$/.steam/steam/steamapps/compatdata/883710/pfx
4. ./install-mf-64.sh
5. place "mfplat.dll"

Also if I re-install the game and don't follow steps 3 and 4 the game runs just fine then gets stuck on the indefinite loading scene before the credits start.

steam-883710.log

You don't have to re-install the game if something went wrong, just delete steamapps/compatdata/883710/pfx folder and launch the game again so Steam could generate a new clean wineprefix.
Are you sure you have run winetricks mf? Do you have file ~/.cache/winetricks/win7sp1/windows6.1-KB976932-X64.exe? Have you edited installcab.py properly? Does your Linux distribution have python2 as a default Python interpreter?

@SergeyLatyshev
Yes I ran winetricks mf, I edited lines 129 to 137 in installcab.py and I used python2 to install it

Can't get past the countdown timer by the end of the game. The countdown disappears and the door to progress has an invisible wall, which makes the game impossible to finish. Using DXVK 0.96.

--

Update: Latest Proton 3.16-7 broke the game saves. Probably related to region/keyboard/time changes by Proton since the game performs a region check for each save. Seems to be a problem with every Proton update. Same as https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-460790101

Yupp, save games are broken. Can't seem to get it working no matter how I edit things.

I can save the game without problems with Proton 3.16-7

@laichiaheng the problem is that it is impossible to load save data created with an older Proton version, so everyone who played the game before lost all their progress.

Same story with saves created on Proton vs saves created on Windows though.

@doitsujin Yes, I saved the game in Windows 10 and Proton3.16-6, and I still can load and save them in Proton3.16-7

@laichiaheng I suspect your regional setting in Windows 10 is equal to the default setting in Proton.

Do we have a workaround to overwrite the regional settigns in a proton prefix? They keep reseting back to US for me.

I didn't do anything to the region setting, it automatically selects my region for me.

Deleting your wineprefix path for the game (ex. Steam/steamapps/compatdata/883710) and let Steam create a new one by starting the game through Proton again seems to be a workaround for the save compatibility issue and the game loads properly. Not a fix, but it's a way to get the save working again.
If you're doing it, make a backup of the old wineprefix path to prevent losing saves.

Edit: It seems that you have to at least continue your save on Windows and delete the prefix to go back to playing the save again on Proton after it rebuilds the prefix, not only deleting the prefix. It works but it's a bad workaround.

Still, the Leon B campaign endgame countdown's still not working here.

Deleting the prefix doesn't fix the problem for me.

@SleepingSloth If your still having problems. Are you sure the mfplat file is the correct version? and not using windows 10 version of mfplat?
The mfplat must be from windows 7 and version 12.0.7601.23471 that's the only one that currently works.

I'm also having the saving issue with Lutris version of Resident Evil 2 now, and it crashes a lot!
It didn't happen to the steam proton version.

I'm using proton 3.16-7 and DXVK 0.96 and my old saves still load.

@mixalis1987 So update since my last post I can now get past the first cut scene but it now just loads indefinitely at the credits I've used the correct mfplat version and it came from a windows 7 laptop.

I also tried this tutorial, no luck.
https://steamcommunity.com/sharedfiles/filedetails/?id=1654060648

@SleepingSloth What first cut scene? The one with the truck driver? And the credits you mention are the ones that start after they drive away from the gas station?
If it's those credits it gets stuck on then the mfplat file wasn't installed correctly. Those credits are a video file not game generated. That's where mfplat comes in.

@mixalis1987 My original issue linked below has been resolved, was the cut scene before Leon walks into the gas station and meets Claire.

https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-463487010

Now I'm having a new issue where the game loads indefinitely at the credits after Leon and Claire drive away from the gas station, my terminal output is identical to Sergeys output linked below

https://github.com/doitsujin/dxvk/issues/886#issuecomment-458487008

@SleepingSloth Can you show me your games directory?

@mixalis1987 Do you want a list of the contents in the steam game folder or of the prefix?

@SleepingSloth Game folder.

@mixalis1987

883710
amd_ags_x64.dll
ISACEffect.dll
ISACMixer.dll
ISACSink.dll
iZotope.dll
McDSP.dll
mfplat.dll
re2.exe
re2_config.ini
re2_config_default.ini
re2_d3d11.log
re2_dxgi.log
re_chunk_000.pak.patch_001.pak
re_chunk_000.pak.patch_002.pak
re_chunk_000.pak
steam_api64.dll

@SleepingSloth Yea looks good.
Does the mfplat md5sum look like this? 2188de5fa5c741fb2b81eb9f37d26ba7

@mixalis1987 Yes

@SleepingSloth It's hard to figure this one out. Usually the infinite loading on that part is an mfplat issue.
This probably has nothing to do with it but we can never be too sure, but did you update the DXVK version for the proton prefix? I'm using 0.96 for steam.

@mixalis1987 Yep, although I don't think that matters much anymore since proton 3.16-7 beta, also someone recently posted a review for the game on protondb with a similar outcome so maybe the issue is distro related.

@SleepingSloth What distro you got?

@mixalis1987 Arch

Hello @SleepingSloth, if you usually use steam-native, does completely closing Steam, then running steam-runtime from a terminal make a difference?

I should think it works on arch. I'm on Manjaro based on arch so theoretically it should work.

I'm using proton 3.16-7 and DXVK 0.96 and my old saves still load.

@laichiaheng What were your locale on both systems?

@julienbenjamin If that message is for me, then my locale is UK.

@Mershl Someone knows if only sCountry, Locale and sLanguage are needed?

@mixalis1987 Sorry, I am confused ; you are not in the same situation as @Mershl i.e. your save game was created with the same locale (UK)?

@julienbenjamin What is the best way to check the save file? All I know is that my steam region is set to UK on both systems, windows and linux.

@kisak-valve I ran the game in steam-native twice, the first time I ran the game I ran the syntax ./install-mf-64.sh in a terminal inside the python-installcab folder the first test that resulted in the previous bug I said had been resolved re-appearing comment about previous bug linked below.

@mixalis1987 My original issue linked below has been resolved, was the cut scene before Leon walks into the gas station and meets Claire.

#2266 (comment)

__TLDR__ the game crashes as soon as the first cut scene starts when Leon is driving to the gas station.

The crash through out a wine: Unhandled exception: page fault on read access I could upload the dump here if that's any help?

The second time I skipped ./install-mf-64.sh completely and just tried to run the game without any winetricks installs that time the game ran fine up until the credits are suppose to play after Leon and Claire leave the gas station it just loads indefinitely, in both tests mfplat.dll was placed in the game folder.

@julienbenjamin What is the best way to check the save file? All I know is that my steam region is set to UK on both systems, windows and linux.

@mixalis1987 Currently, there is no way AFAIK. And this is my current issue: my savegame "should" have the same locale as my Linux system, and I should not encounter the error. Or there is other settings used for creating the RE2 save game file.

I checked all settings and they are all set to UK. I checked in steam, Linux and Windows.

@SleepingSloth Before you ran ./install-mf-64.sh you did run export WINEPREFIX=your steam proton prefix first right? And you should install mf first before running ./install-mf-64.sh because files from that are still needed.

@mixalis1987 Yes, I followed this guide.

https://steamcommunity.com/sharedfiles/filedetails/?id=1654060648

@SleepingSloth That guide is pretty much correct but you do not need to install mf in a default prefix, you need to install mf only in the games prefix and you do not need to edit install-mf-64.sh to use python2 just edit installcab.py and change the top line #! /usr/bin/env python to #! /usr/bin/env python2 then run install-mf-64.sh inside that prefix.

Would you like me to try the installation?

@mixalis1987 I followed that guide and this video https://youtu.be/pcCJSm3IoMY and the suggestions by others on the protondb page, which lead me to the same suggestions you've just mentioned resulting in the wine: Unhandled exception: page fault on read accessissue I mentioned in my previous comment.

@SleepingSloth In the video he does a few things that I never did. I just edited installcab.py to use python 2 and un-commented lines 129 to 137 then I just ran install-mf-64.sh I did not get a windows 7 service pack, the dll's the script uses the service pack that is installed from winetricks mf. The only file missing from mf is mfplat thats why we get that from windows manually after we finish with install-mf-64.sh script . Also he is using windows 10 in the VM when we need windows 7.

When I did it I used this guide

https://github.com/doitsujin/dxvk/issues/886

SergeyLatyshev wrote the steps I used. It even worked for RE7

For anyone interested, regarding this issue, the only relevant registry key is LocaleName. Tested with regedit on Windows.

On RE2 saves. It seems Proton stopped updating on my computer since 3.16-6 despite it showed its version as newer. So, I installed today Proton 3.16 Beta from 'tools' section, and it got actually updated. But then my save files became incompatible. I didn't use Windows for this game and didn't change locales in Linux, Wine or Proton. My Linux locale is "ru_RU.UTF-8" and in .../steamapps/compatdata/883710/pfx/user.reg there is "Locale"="00000419". What should I change to get my 80 hours of game progress back? If I change anything there to 00000409 (I suppose it's US locale?), it reverts to 00000419 again. I don't see LocaleName option in .reg files.

@SergeyLatyshev Yes, "Locale"=00000419 is en-US. You can find the appropriate code here for yours. LocaleName is a variable from the registry my Windows installation where my save was created ; when tinkering with it I was able to reproduce the error I had with Steam Play. But, yes, LocaleName is not present within Wine prefix.

But what variables must be changed to make the game load my save data? Is it even possible? I tried to change all 00000419 to 00000409 or 00000000, but the game still doesn't want to load my old save files, and all changes in user.reg get gone after I launch the game.

I even tried to replace the whole branch [Control Panel\\International] from Proton 3.16 Beta/proton_dist.tar.gz/./share/default_pfx/user.reg, useless too.

Issues persists between Proton 3.16-4 and Proton 4.2 . Any edits to the locale get reverted on game launch

I updated from 3.16-8 to 4.2, and my saves work. Also, the game performs now considerably better than with older versions of Proton.

Mouse cursor is still laggin ingame, despite marking as fixed in changelog 4.1. On 3.18, it was just flickering and not every click was accepted.

Mouse still laggy, Proton 3.16-4 saves still not compatible with 4.2-3.

@Metaln00b @pastapojken What are your system specs (full specs can be in Steam under Help -> System Information)?

See below

 Computer Information:
     Manufacturer:  Unknown
     Model:  Unknown
     Form Factor: Desktop
     No Touch Input Detected

 Processor Information:
     CPU Vendor:  GenuineIntel
     CPU Brand:  Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
     CPU Family:  0x6
     CPU Model:  0x3c
     CPU Stepping:  0x3
     CPU Type:  0x0
     Speed:  4000 Mhz
     4 logical processors
     4 physical processors
     HyperThreading:  Unsupported
     FCMOV:  Supported
     SSE2:  Supported
     SSE3:  Supported
     SSSE3:  Supported
     SSE4a:  Unsupported
     SSE41:  Supported
     SSE42:  Supported
     AES:  Supported
     AVX:  Supported
     CMPXCHG16B:  Supported
     LAHF/SAHF:  Supported
     PrefetchW:  Unsupported

 Operating System Version:
     "Arch Linux" (64 bit)
     Kernel Name:  Linux
     Kernel Version:  5.0.8-arch1-1-ARCH
     X Server Vendor:  The X.Org Foundation
     X Server Release:  12004000
     X Window Manager:  i3
     Steam Runtime Version:  jenkins-steam-runtime-beta-release_0.20190320.2

 Video Card:
     Driver:  X.Org AMD Radeon R9 200 Series (HAWAII, DRM 3.27.0, 5.0.8-arch1-1-ARCH, LLVM .0.0)
     Driver Version:  4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-f9c594cdf5)
     OpenGL Version: 4.5
     Desktop Color Depth: 24 bits per pixel
     Monitor Refresh Rate: 60 Hz
     VendorID:  0x1002
     DeviceID:  0x67b1
     Revision Not Detected
     Number of Monitors:  3
     Number of Logical Video Cards:  1
     Primary Display Resolution:  1920 x 1080
     Desktop Resolution: 4480 x 1080
     Primary Display Size: 20.91" x 11.77" (23.98" diag)
                                             53.1cm x 29.9cm (60.9cm diag)
     Primary VRAM: 4096 MB

 Sound card:
     Audio device: Realtek ALC1150

 Memory:
     RAM:  15978 Mb

 Miscellaneous:
     UI Language:  English
     LANG:  en_GB.UTF-8
     Total Hard Disk Space Available:  111150 Mb
     Largest Free Hard Disk Block:  28624 Mb
     VR Headset: None detected

 Recent Failure Reports:

@pastapojken thank you! It looks like the mouse issue was not fixed for all configurations/distros/etc. For AMD, I found that the issue is fixed on Ubuntu 18.10 but still had issues on Ubuntu 18.04.

@alasky17

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 5 2600X Six-Core Processor           
    CPU Family:  0x17
    CPU Model:  0x8
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  3600 Mhz
    12 logical processors
    6 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Ubuntu 18.04.2 LTS (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.18.0-17-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12001000
    X Window Manager:  GNOME Shell
    Steam Runtime Version:  steam-runtime-beta-release_2019-01-10

Video Card:
    Driver:  X.Org AMD Radeon R9 200 Series (HAWAII, DRM 3.26.0, 4.18.0-17-generic, LLVM 8.0.0)
    Driver Version:  4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-3c5a9ab 2019-04-17 bionic-oibaf-ppa)
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x1002
    DeviceID:  0x67b1
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 23.54" x 13.23" (26.97" diag)
                                            59.8cm x 33.6cm (68.5cm diag)
    Primary VRAM: 4096 MB

Sound card:
    Audio device: ATI R6xx HDMI

Memory:
    RAM:  16033 Mb

Miscellaneous:
    UI Language:  English
    LANG:  de_DE.UTF-8
    Total Hard Disk Space Available:  937875 Mb
    Largest Free Hard Disk Block:  766089 Mb
    VR Headset: None detected

Recent Failure Reports:

@alasky17 Interesting! The mouse issue doesn't bother me too much as I play with a controller anyways. Will have to look into that though. The saves issue I find more annoying as I feel like there is no guarantee that, after restarting my game from 0 to use compatible save files, the next proton update won't change locale again and cause issues.

Operating System Version:
Ubuntu 18.04.2 LTS (64 bit)

Video Card:
Driver: X.Org AMD Radeon R9 200 Series (HAWAII, DRM 3.26.0, 4.18.0-17-generic, LLVM 8.0.0)
Driver Version: 4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-3c5a9ab 2019-04-17 bionic-oibaf-ppa)`

@Metaln00b if you upgrade to Ubuntu 18.10 and it fixes the mouse issue, I would be super interested! Thanks for the info!

@pastapojken I looked into the locale issue and the locale-change causing incompatible save files is a Windows bug. The reported locale changed between 3.16-6 and 3.16-7 because Proton was fixed so it reports the correct system locale (previously it was reporting US English for everyone), so it shouldn't change again since it is now reporting the correct locale. FWIW if you still have the save game it might work if you set LANG=en_US.UTF-8 in a terminal and running Steam from that same terminal.

@alasky17 OH MAN! THANK YOU! Hadn't honestly done much digging as I assumed it was some convoluted Wine/Proton thing so yeah, it's fixed, thanks! :D

@alasky17 If i update to 18.10, other games that are currenty running may not work anymore.

I just started RE2 with Proton 4.2.3 and I'm having the issue where I'm stuck loading after completing the first scene. I haven't made any modifications to Proton or the game's files, I simply installed it from Steam and hit play

• GPU: RX 480
• Driver/LLVM version: 4.5 Mesa 19.0.0-devel/7.0.0
• Kernel version: 5.0.5
• Proton version: 4.2-3

Was it installed before? That's just the mfplat problem. It must be missing.

On Sat, 27 Apr 2019 14:55 Andrew, notifications@github.com wrote:

I just starting RE2 with Proton 4.2.3 and I'm having the issue where I'm
stuck loading after completing the first scene. I haven't made any
modifications to Proton/the games files, I simply installed it from Steam
and hit play

• GPU: RX 480
• Driver/LLVM version: 4.5 Mesa 19.0.0-devel/7.0.0
• Kernel version: 5.0.5
• Proton version: 4.2-3

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-487287953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHOYDE5BOSYFO7QN6WULLTPSRLMZANCNFSM4GSMTW2Q
.

No, it wasn't. I installed it yesterday. The mfplat workaround shouldn't be required anymore, right?

I think it still is. That file is copyright by Microsoft so I don't think
wine can include it. It's up to us.

On Sat, 27 Apr 2019 15:03 Andrew, notifications@github.com wrote:

No, it wasn't. I installed it yesterday. The mfplat workaround shouldn't
be required anymore, right?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-487288583,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHOYDCUQOGUMUIIKN53ASTPSRMLPANCNFSM4GSMTW2Q
.

I just tried again with the bundled runtime (I was using native libraries via Solus' Steam integration) and had the same issue. This time I got an error message on force-quitting, though

Alright, I'll give that a shot. Thanks!

Let us know.

On Sat, 27 Apr 2019 15:07 Andrew, notifications@github.com wrote:

Alright, I'll give that a shot. Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-487288907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHOYDARJESGV2MIPBTYOUDPSRM3NANCNFSM4GSMTW2Q
.

Yes, that was the issue. I'm not sure what made me think that the workaround was no longer necessary. Hopefully a legal solution to this can be found sometime soon.
Thanks!

@CyanBlob Maybe you should install it with Lutris, it automatically installs all the things that you need to play this game.

I don't think Lutris installs that file either, it's still a copyright
file, they won't risk it.

On Sat, 27 Apr 2019 18:02 小亨, notifications@github.com wrote:

@CyanBlob https://github.com/CyanBlob Maybe you should install it with
Lutris, it automatically installs all the things that you need to play this
game.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-487302871,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHOYDCIWXCZRESL7JTW6S3PSSBLHANCNFSM4GSMTW2Q
.

You need the 430KB mfplat.dll file with the checksum 54b5dcd55b223bc5df50b82e1e9e86b1

@mixalis1987 I play it via Lutris without problem.

@CyanBlob @alasky17 Now i have upgraded to 19.04 and i got the same error like CyanBlob. The problem seems to be the vulkan-driver. Please post the output of vulkaninfo.

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32

VULKANINFO

Vulkan Instance Version: 1.1.97/build/vulkan-tools-35Ffza/vulkan-tools-1.1.101.0+dfsg1/vulkaninfo/vulkaninfo.c:5028: failed with VK_ERROR_INITIALIZATION_FAILED

Running with the parameter in grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1"
I don't know if the parameter is still necessary.

UPDATE:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1"

sudo update-grub
reboot

Now it works, but the mouse issue still exists.

@Metaln00b

Now it works, but the mouse issue still exists.

Hi, I just found out that locking your frame rate to either 30 or 60 fixed the mouse issue.

@aaulia Thanks i will try it. It could be plausible...

I just tried it out and the mouse issue seems to be completely gone! I limited it to 60fps and switched to Wayland. I can try again later on X if requested

Well, i tried it out on X with VSync Off and limited 30 FPS. It seems all Inputs are delayed not only the cursor. The first minutes work and when the PC has a short lagg, it starts to "get the stone rolling". All Inputs are delayed.

Well, i tried it out on X with VSync Off and limited 30 FPS. It seems all Inputs are delayed not only the cursor. The first minutes work and when the PC has a short lagg, it starts to "get the stone rolling". All Inputs are delayed.

Hmm I get that too, occasionally. So it's an X issue? Maybe try with VSync on?

Well, i tried it out on X with VSync Off and limited 30 FPS. It seems all Inputs are delayed not only the cursor. The first minutes work and when the PC has a short lagg, it starts to "get the stone rolling". All Inputs are delayed.

Hmm I get that too, occasionally. So it's an X issue? Maybe try with VSync on?

Wayland is the solution. Vsync or frame limiter can be ignored. Thank you =)

Finally got this running after many hours, turns out the source of my problems was python-installcab, using this (tried various versions) would result in the game crashing after the first cut scene. I nuked the prefix, reinstalled and just put the mfplat.dll in the game directory and it seems to be running fine now.

YMMV, I guess.

Regarding video: Only 1 DLL is required to get full functionality - Windows 7's mfplat.dll.
Can someone at Valve get in touch with someone high enough in the Valve foodchain to have a Microsoft contact, and ask that contact nicely if MS could give Valve permission to redistribute the binary mfplat.dll as part of Proton. Since Ballmer is gone culture at MS has shifted and I'm sure if you only ask nicely you can get that permission which would allow this game and several other recent titles to run flawlessly.

I have the same problem as topic starter. Infinite loading screen after gas station.

steam-883710.zip

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 5.3.0-0.rc0.git3.1.fc31.x86_64 x86_64 bits: 64 Desktop: Gnome 3.33.3 
           Distro: Fedora release 31 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 2406 date: 06/21/2019 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2312 MHz min/max: 2200/3700 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.5 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: AMD Radeon VII (VEGA20 DRM 3.32.0 5.3.0-0.rc0.git3.1.fc31.x86_64 LLVM 8.0.0) 
           v: 4.5 Mesa 19.2.0-devel 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: rtw_pci 
Drives:    Local Storage: total: 11.57 TiB used: 10.16 TiB (87.8%) 
Info:      Processes: 450 Uptime: 10h 20m Memory: 31.29 GiB used: 16.60 GiB (53.0%) Shell: bash inxi: 3.0.34 

@NTMan You're either missing mfplat dlls or you copied the dlls from a win10 install.

@dlove67 specifically what DLL's do you need for it to work? I have mfplat.dll with the checksum '54b5dcd55b223bc5df50b82e1e9e86b1' and I also get the infinite loading screen after the gas station

The problem is mfplat, you need it from Windows 7 and install properly or try this script <Link removed by moderator>

Hello @mixalis1987, the link you posted is legally problematic and has been removed.

@exezin The one I'm using is df1ed3184437cc405312b70805ae5623, but you also need to do a few other things with winetricks. Check protondb for in the info.

I'm not sure but KB968211 may contain mfplat: https://www.microsoft.com/en-us/download/details.aspx?id=16546

@dlove67 yes you must install "mf" package first from winetricks it will install the none copyright dlls that are needed. then use an install method that is around the internet and then take a Windows 7 mfplat dll from Windows and place it in the same directory as the game exe.

@mixalis1987 for some reason installing mf via winetricks actually results in the game not getting past the first cutscene for me, without mf but with the mfplat dll I can get to the gas station but not past the infinite loading screen.

Anyone have any idea what other DLL's I need to put there? The protondb page is a bit of a mess.

@exezin you need to install mf via winetricks, then run a script, you also need to put the x64 mfplat.dll (pulled from C:\Windows\System32 on an x64 windows 7 install). After doing both it should work fine. The scripts needed are noted on protondb.

what @dlove67 is correct. You need to do both, winetricks mf and installing mfplat. The game will not work properly without both.

Go to this page https://github.com/doitsujin/dxvk/issues/886 and The 16th post down will say how to install mfplat and the install script used and what version of mfplat is actually needed.

Interestingly, using that script results in the game not getting past the first cutscene at all, without that script being used and having placed mfplat.dll in the game folder results in me being able to get to the gas station, and I get stuck with the endless loading screen after that.

I'll have a play around and try other mfplat.dll's, seems a few have had luck with other versions.

That is the script I always use also for other games, strange your having problems. Are you sure the dll is the right version?

With MF workaround, the game crashes everytime when I use _the laptop_ inside the _police station_.

mf.dll checksum is 20ecac7791dcba69121631cb627e5a96
mfreadwrite.dll checksum is e8706a051bffc9da9e9b935aaa432aac
mfplat.dll checksum is 2188de5fa5c741fb2b81eb9f37d26ba7

The crash happens because of mfreadwrite.dll from what appears in the crash report. Any ideas beside not doing the workaround right, because I am sure that I did everything right, and it works fine with Resident Evil 7 Biohazard.

You don't need mfplatreadwrite that is installed with the mf package on winetricks.

Install mf from winetricks first then use the script I posted further up and then place the mfplat file you took from Windows the correct mfplat version and place it in the games exe folder.

This my video I made ages ago of me passing that same problem with the steps I just told. https://m.youtube.com/watch?v=JCPgIyZTHA0&t=67s

I can skip this video by pressing escape, then space.

See here:

https://www.reddit.com/r/linux_gaming/comments/ajyx51/resident_evil_2_playable_with_the_latest_dxvk_and/ef7sx31

You ONLY need mfplat.dll, but you need the version with md5sum
54b5dcd55b223bc5df50b82e1e9e86b1

Don't do any winetricks. Just copy that mfplat.dll into your game folder.

You ONLY need mfplat.dll, but you need the version with md5sum
54b5dcd55b223bc5df50b82e1e9e86b1

I have md5sum 2188de5fa5c741fb2b81eb9f37d26ba7, it works too.

You ONLY need mfplat.dll, but you need the version with md5sum
54b5dcd55b223bc5df50b82e1e9e86b1

I have md5sum 2188de5fa5c741fb2b81eb9f37d26ba7, it works too.

And which version is that? The one I cited is the one from Windows 7 SP 1 that's distributed on Microsoft's site and as such is presumably the most recent version.

And which version is that?

12.0.7601.23471

Without mfreadwrite.dll the game stucks, and does nothing for so long. I tried the both version of mfplat.dll, and the both crashed in the middle of the laptop cutscene. I escaped this cutscenes, and I haven't face another problematic cutscene after a few hours of gameplay.

Ahmed, try my wineprefix: <Link removed by moderator>
Delete your existing wineprefix for RE2 from steamapps/compatdata/, unpack this one there, and copy that damn mfplat.dll to steamapps/common/RESIDENT EVIL 2 BIOHAZARD RE2/. Don't forget to delete unnecessary dlls from there if you have copied them before (mf, mfreadwrite, etc.)

Hello @SergeyLatyshev, your link has been removed because it contains copyrighted dlls (mf.dll), which is legally problematic to redistribute.

Thank you all. I don't need to do anything. I already skipped the video, and everything else works just fine.

@ahmed-elsayed2017 whats the md5 of your mfreadwrite.dll?

@ahmed-elsayed2017 whats the md5 of your mfreadwrite.dll?

mfreadwrite.dll checksum is e8706a051bffc9da9e9b935aaa432aac

Hello @SergeyLatyshev, your link has been removed because it contains copyrighted dlls (mf.dll), which is legally problematic to redistribute.

But winetricks installs it. I thought all parts of wine are free to redistribute. Or they aren't?

Winetricks is not part of wine or Proton and my understanding is that project itself does not contain proprietary libraries.

The mfplat dll isn't, so is not included in winetricks mf pack. I honestly don't see why Microsoft copyrighted that file but this is Microsoft we are talking about.

I fail to play it on Lutris after I switching to Ryzen 3700X. Why?

Hello @laichiaheng, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

The whole file is over 1GB

@kisak-valve Here is the log: https://drive.google.com/file/d/1N_aJUc6JfTugJU6iy_oTNAAZCMha_8GG/view?usp=sharing

Looks like your log is saying the game hit a bunch of invalid memory accesses (c0000005). One can kill a game, your log has several hundred. Unfortunately, I don't see any hints besides that.

As a side note, Proton logs tend to compress well, but even compressed this log is larger than Github is happy with.

@kisak-valve other proton games crash, too.
Is it the AMD's bug?

Is it the AMD's bug?

Some AMD GPU cards need a workaround to run DXVK, and Vulkan games, but could you provide more information? GPU, driver version, and Operating System.

@ahmed-elsayed2017

vainfo: VA-API version: 1.5 (libva 2.5.0)
vainfo: Driver version: Mesa Gallium driver 19.1.2 for Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.1-1-MANJARO, LLVM 8.0.0)

vulkan-radeon is installed, this card runs perfectly on my i5-4460 system, but it doesn't work on the 3700X+X470 system now.
The native Linux games run without problem, but the proton games crash immediately.

@doitsujin @ahmed-elsayed2017
I run it in terminal, it is how it behaves.
https://pastebin.com/j04WJVa6
I have confirmed that native OpenGL and Vulkan games run without problem.
I didn't expect that the game would not be launched, it ran perfectly on my i5-4460 CPU PC with the same hard drive, GPU and OS.
Is it the shader cache problem from Steam?

@ahmed-elsayed2017 @doitsujin @kisak-valve
Today, I've tried to play Path Of Exile non-steam version with WINE+DXVK on my PC, it runs perfectly with high fps, so it must be a game specific or Steam issue instead of WINE+DXVK or Proton issue, but how is it possible? There was no such problem with this game.
I can't test the steam version of POE, because it is not playable on Steam in my country, so I don't know if Steam causes this problem.

I just tested this game again and its working fine. It did an update at first before launching and when it did start it crashed however after running again it worked perfect and after the station etc. So I don't think its a game or steam.

@mixalis1987 OK, the game is not compatible with Ryzen 3700X

OK, the game is not compatible with Ryzen 3700X

@laichiaheng Oh and I was planning on upgrading lol. Are you on the new 5.2 kernel? If not it might be worth a try. Or it is in fact a driver issue.

OK, the game is not compatible with Ryzen 3700X

@laichiaheng Oh and I was planning on upgrading lol. Are you on the new 5.2 kernel? If not it might be worth a try. Or it is in fact a driver issue.

Yes, I'm on 5.2 now, I also have tried 5.3, but it still doesn't work.
Please upgrade your CPU, I really want to know which part of my system goes wrong.

OK, the game is not compatible with Ryzen 3700X

@laichiaheng Oh and I was planning on upgrading lol. Are you on the new 5.2 kernel? If not it might be worth a try. Or it is in fact a driver issue.

It is a CPU issue confirmed, another person who upgrades his 1600 to 3600 has the same problem.

@laichiaheng What has AMD got to say about this?

The game crashes sometimes without any warning. Does it store the log file if I don't tell it to do it?

There are sound latency in the game, the sound is slower than graphics for about 0.1~0.5s

There are sound latency in the game, the sound is slower than graphics for about 0.1~0.5s

Never mind, it is caused by the front panel headphone jack of my PC.

System Information

• GPU: RX VEGA 56
• GPU Driver: 19.3~git1910291930.ff6e14~oibaf~b(ppa:oibaf/graphics-drivers)
• Kernel version: 5.4.0-050400rc5-lowlatency
• Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)
• Proton version: 4.11-7

Compatibility Report

Game is playable with Proton 4.2-9 but it skips videos unless installing Media Foundation (cab version).

With Proton 4.11-7 the game either crashes just when you are about to get into gameplay, or you get into the game but the shadows are glitching. Including a video of the shadows glitching

steam-883710-proton-4.2-9.log
steam-883710-proton-4.11-7.log
RE2.mp4.zip
system_info.txt

Video is of shadows glitching

Reproduction

Just launch the game with Proton 4.11.7

System Information

* GPU: RX VEGA 56

* GPU Driver: `19.3~git1910291930.ff6e14~oibaf~b `(ppa:oibaf/graphics-drivers)

* Kernel version: 5.4.0-050400rc5-lowlatency

* Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)

* Proton version: 4.11-7

Compatibility Report

Game is playable with Proton 4.2-9 but it skips videos unless installing Media Foundation (cab version).

With Proton 4.11-7 the game either crashes just when you are about to get into gameplay, or you get into the game but the shadows are glitching. Including a video of the shadows glitching

steam-883710-proton-4.2-9.log
steam-883710-proton-4.11-7.log
RE2.mp4.zip
system_info.txt

Video is of shadows glitching

Reproduction

Just launch the game with Proton 4.11.7

Can't reproduce it with my RX580

but the shadows are glitching

Can you test Mesa 19.2? Might very well be a regression.

Can you test Mesa 19.2? Might very well be a regression.

@doitsujin sure I did some more tests

System Information

• GPU: RX VEGA 56
• Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)
  system_info.txt

Tests with different Kernel and GPU drivers

• GPU Driver: 19.2.1-1ubuntu1~18.04.1~ppa2 (ppa:ubuntu-x-swat/updates)
• Kernel version: 5.4.0-050400rc6-lowlatency
  steam-883710-proton-4.11-7-xswat.log
  

• GPU Driver: 19.1.2-0~b~padoka0 (ppa:paulo-miguel-dias/pkppa)
• Kernel version: 5.4.0-050400rc6-lowlatency
  steam-883710-proton-4.11-7-padokastable.log
  

• GPU Driver: 19.1.0+aco+git1571318481-fe930ad92ab-1bionic1 (ppa:valve-experimental/mesa-bionic)
• Kernel version: 5.4.0-050400rc6-lowlatency
  steam-883710-valveexp-proton-4.11-7.log
  

• GPU Driver: 19.3~git1910291930.ff6e14~oibaf~b (ppa:valve-experimental/mesa-bionic)
• Kernel version: 5.4.0-050400rc6-lowlatency
• GPU Driver: 19.3~git1910291930.ff6e14~oibaf~b (ppa:valve-experimental/mesa-bionic)
• Kernel version: 5.0.0-23-generic
  steam-883710-proton-4.11-7-oibaf.log
  steam-883710-oibafkernel5.log
  

With all these setups, I get flickering shadows and graphical glitches, but the game did not crash with Proton 4.11-7.

Conclusion

The game crashed only with Proton 4.11-7 using 5.4.0-050400rc5 kernel, so that appears to have been a Kernel rc5 issue. The glitching shadows and graphical glitches occurred however with every Mesa driver version I tested, also with an older Kernel.

The graphical glitches I reckon are either a Vega56 specific issue or maybe some specific graphical setting causes it (going to experiment more with that)

I cannot reproduce the problem on my RX 480, but can you try putting the following into a file dxvk.conf next to re2.exe:

d3d11.relaxedBarriers = False

DXVK has a performance hack for this game which otherwise would require AMDAGS to work; if the config file fixes it for you, it's the hack that's broken. Unfortunately this will likely result in a performance loss of roughly 20-30%, but that's really the game's fault since it relies so heavily on non-standard D3D11 extensions.

@doitsujin I tried it but it made no difference, the same graphical glitches/shadow flickering remained with Proton 4.11-7

For reference this is how the game looks like in Proton 4.2-9 for me:
(I assume this is accurate rendering)

steam-883710-proton-4.2-9.log

@AwesamLinux I may have missed this, but have you tried dropping the dxvk version from 4.2-9 into Proton 4.11-7 to isolate this as a dxvk issue? Might be worth a quick check? The dxvk version from 4.2-9 is 1.2.1 and you can pull the release tarball from the github here: https://github.com/doitsujin/dxvk/releases?after=v1.3

After untarring it, you can drop the contents of the x32 folder into your steam folder ...../common/Proton 4.11/dist/lib/wine/dxvk/. and the contents from the x64 folder into dist/lib64/wine/dxvk/.

@alasky17 I tried it now, running with the older DXVK there is no graphical issues. So yes now we can be sure this is a DXVK issue.

@AwesamLinux any chance you can bisect the issue or at least figure out which version is the last one that works?

@doitsujin I tried the pre-compiled DXVK's releases from github up to 1.4.4 (all tested with launch option DXVK_STATE_CACHE=0)

dxvk 1.3.2 GOOD
dxvk 1.3.3 GOOD
dxvk 1.3.4 GOOD
dxvk 1.4.0 BAD
dxvk 1.4.1 BAD
dxvk 1.4.2 BAD
dxvk 1.4.3 GOOD (no graphical issues! :tada:)
dxvk 1.4.4 GOOD

Yay, the issue appears to have been already fixed as of dxvk 1.4.3 :tada:

(Sorry for slow response. I should have tested all the pre-compiled binaries first. I got sidetracked by checking out and compiling 6b5d01c934e48bd3abc12f6643ffa0705ef2c2dd ([meta] Release 1.4.1). And it produced DLL's without the graphical issue, that threw me off completely)

Cool, thanks. Could have been related to the UAV barrier changes then.

Weird that it was working just fine on my card though, and apparently even for some Vega users I talked to.

@kisak-valve The reflection of the mirror is wrong.
CPU: AMD Ryzen7 3700X
GPU: AMD RX580
Kernel: 5.4.3
Mesa: 19.3
Proton: 4.11-10

System Information

• GPU: RX VEGA 56
• GPU Driver: 4.5 (Compatibility Profile) Mesa 19.1.2 - padoka PPA
• Kernel version: 5.4.5-050405-lowlatency
• Distro version: 19.3 Tricia (64 bit) (Cinnamon)
• Proton version: 4.11-11

Retest Compatibility Report

There appears to be a regression as of DXVK 1.4.5. The graphics get corrupted when reaching the main menu like this:

Switching to console you see it spams error message like this:

• With DXVK 1.4.4 the game works with this setup, anything newer than that is broken
• I tried with older and newer Kernels and GPU drivers (including ones that I know had worked with this game before). There was no difference, the game worked with older DXVK regardless of driver/kernel but crashes with anything newer than 1.4.4

Including logs of both successfully running the game, and one of when it crashes.

steam-883710-dvxk1.4.5-crash.log
steam-883710-dxvk1.4.4-success.log
system_info.txt

I had weird graphic glitches like this when I was using AMDVLK + kernel 5.0, but Radv works fine with me. Do you use vkBasalt?

@AwesamLinux can you please retry with an up-to-date Mesa version? I cannot reproduce the problem on my end on an RX 480 using Mesa 19.3.

@AwesamLinux

For starters, purge padoka ppa and mesa comes with it according to instructions noted on Padoka Stable PPA page.

Then use this ppa.

https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

And also Proton docs should mention from this ppa and removal of earlier recommended ppa's imo. @kisak-valve

https://github.com/ValveSoftware/Proton/wiki/Requirements#amdintel

@ahmed-elsayed2017 I don't use vkBasalt

@doitsujin @Leopard1907

I tried a bunch of different random drivers/kernels (only went back to those old ones to see if there would be any difference). But here is the results I got with new drivers:

DXVK | Kernel | Mesa | Did it work?
----- | ---------------|------|-------------
dxvk-1.4.4 | 5.0.0-23-generic | 19.3.1 - kisak-mesa PPA | SUCCESS
dxvk-1.4.4 | 5.2.8-050208-lowlatency | 19.3.1 - kisak-mesa PPA | SUCCESS
dxvk-1.4.4 | 5.4.5-050405-lowlatency | 19.3.1 - kisak-mesa PPA | SUCCESS
dxvk-1.4.4 | 5.4.5-050405-lowlatency | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | SUCCESS
dxvk-1.4.5 | 5.0.0-23-generic | 19.3.1 - kisak-mesa PPA | FAIL (system froze)
dxvk-1.4.5 | 5.4.5-050405-lowlatency | 19.3.1 - kisak-mesa PPA | FAIL (graphics corrupted)
dxvk-1.4.5 | 5.4.5-050405-lowlatency | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | FAIL (graphics corrupted)
dxvk-1.4.6 | 5.0.0-23-generic | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | FAIL (systen froze)
dxvk-1.4.6 | 5.2.8-050208-lowlatency | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | FAIL (graphics corrupted)
dxvk-1.4.6 | 5.4.5-050405-lowlatency | 19.3.1 - kisak-mesa PPA | FAIL (graphics corrupted)
dxvk-1.4.6 | 5.4.5-050405-lowlatency | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | FAILED 2/3 tries (graphics corrupted)
dxvk-1.5 | 5.0.0-23-generic | 19.3.1 - kisak-mesa PPA | FAIL (system froze completely)
dxvk-1.5 | 5.2.8-050208-lowlatency | 19.3.1 - kisak-mesa PPA | FAIL (graphics corrupted)
dxvk-1.5 | 5.4.0-050400-lowlatency | 19.3.1 - kisak-mesa PPA | FAIL (graphics corrupted)
dxvk-1.5 | 5.4.5-050405-lowlatency | 19.3.1 - kisak-mesa PPA | FAIL (graphics corrupted)
dxvk-1.5 | 5.4.5-050405-lowlatency | 20.0.0-devel (git-cabcbb4 2019-12-20 bionic-oibaf-ppa) | FAIL (graphics corrupted)

• Tested with Proton 4.11-11 with the pre-compiled release binaries from the DXVK github
• All these were tested with DXVK_STATE_CACHE=0 option

From what I have observed with DXVK 1.4.4 the game works consistently for me regardless of Kernel or Mesa. With anything later than that there is full screen graphics corruption, or a total system freeze. Curiously the game actually worked once with DXVK 1.4.6.

Any chance you can bisect that problem?

I've heard similar reports about the new demo that was released recently, but no one seems to be able to reproduce that reliably enough to actually get useful information. I wasn't able to trigger this bug at all on AMD or Nvidia, the game just runs perfectly fine even with the Proton-supplied DXVK build.

@doitsujin When I have more spare time I will look into bisecting this, it's not something I have any prior experience with :sweat_smile:

I'll try to add to this, I noticed the game stopped working for me after the update that removed denuvo from it, at least I thought that was the reason cause it coincided with that.

What I'm experiencing are system freezes which need a hard reboot.

In the main location I've been testing (RPD Dark Room) the freezes consistently happen when pointing the camera in a particular direction (back wall, opposite the typewriter).

I've been running some tests changing kernel, mesa and dxvk versions around with no success.
I tried to emulate what worked for @AwesamLinux as close as I could but it didn't work.

I tried combinations off all of these: the latest 5.4.6-arch kernel, 5.4.3-arch, 5.4.3-fsync (from valveaur), DXVK 1.5 and 1.4.4, mesa 19.3.1 and mesa-aco 20.0.0_devel.20191129 (from valveaur), same result with every combination.

I have a couple of _probably not very useful_ logs.

steam-883710.log
steam-883710.2.log

I will try more stuff later but I'm a little lost right now and I tested for hours last night.

System Information

• GPU: Vega 11 (Ryzen 3400G iGPU)
• Driver/LLVM version: Mesa 19.3.1/9.0.0
• Kernel version: 5.4.6-arch1-1
• Proton version: 4.11-11

Did you try another proton version also?

I tried 4.2-9 briefly without the same plethora of combinations, it's the other I had readily available, same result.

Is there any way to avoid the gpu crash ? That would make extensive testing a lot less annoying, but I'm guessing no.

I'm also getting random crashes of the game (the game literally just shuts down, the rest of the system is unaffected) with Proton 4.11-11, TK-Glitch's 5.0rc2, and Glorious Eggroll's 4.19, 4.20, and 4.21-1 and -2. AMD RX 580 with mesa 19.3.1, and 20.0.0-devel from valveaur, kernel's 5.4.6 from Arch and Manjaro, along with 5.5-rc. I've only tried the built in DXVK's and I assume they all use a DXVK later than 1.4.5 (I know the TK-G build uses 1.5). I'll try adding earlier DXVK's and see how it works out. Thing is, I get absolutely nothing in the logs, the game literally just quits itself with no message in the log even with the proton debug option set. I mean there's a log file created, but it literally just ends after "App so-and-so started," no messages during the crash. Always happens within 30 minutes, didn't happen a couple months ago with older versions of proton

Ok, seems I got the game running finally, by using AMDVLK instead of RADV.

edit: I think I've pinpointed it, vulkan-radeon 19.2.7-1 is the last working one, 19.3.0-1 onward breaks it
edit2: I noticed this game is less stable with AMDVLK, I experienced random crashes in my brief testing with it, like when changing graphics settings, while I never had a single crash when playing with RADV for over 8 hours (before it broke, of course).

Hello @dowttie, looks like https://gitlab.freedesktop.org/mesa/mesa/issues/2315 is tracking your issue.

Resident Evil 2 Remake Crashes Constantly on Arch-Based Systems

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3425.
@gardotd426 posted on 2020-01-12T16:17:18:

Compatibility Report

• Name of the game with compatibility issues: Resident Evil 2 Remake
• Steam AppID of the game: 883710

System Information

• GPU: XFX RX 580 4GB
• Driver/LLVM version: Mesa-ACO from valveaur (20.0.0.devel)
• Kernel version: Multiple. 5.4.3-5.4.10-MANJARO and -arch, 5.5rc kernels, custom kernels from Tk-Glitch, all of them.
• Link to full system information report as Gist:
• Proton version: Multiple, but as far as official versions, 4.11-11

I confirm:

• [x ] that I haven't found an existing compatibility report for this game.
• [x ] that I have checked whether there are updates for my system available.

Symptoms

The game crashes within 10-15 minutes of actual in-game gameplay time, no matter what. YES, THE MEDIA FOUNDATION FIX IS INSTALLED. I have like 8 or 9 hours in the game, but I didn't play it for about 3 weeks or so, and now since I've tried to start back up again, I can't play for more than 10 minutes. It was never a problem with 4.11-9. Honestly it keeps getting worse, now I can't even get it to run for 5 minutes. I'm installing Proton-4.2-9 right now to see if that makes any difference, since all the versions of Proton I've tried are either 4.11 or based on 4.11 (like Glorious Eggroll's Proton-GE).

Reproduction

On Manjaro or Arch Linux, with the current 5.4 kernel (5.4.10 as of this writing), install RE2, then after applying the Media Foundation fix, try running the game. It will crash within 10 minutes in the middle of the game. It's not cutscenes, those are fine. It'll just be in the middle of the game, running down the hall or anything like that. It just shuts down/exits, and the logs don't seem to indicate anything other than a problem with Wine.
steam-883710.log

@kisak-valve, I just posted over there and was told it's unrelated and that new reports need to be filed. So I guess I'll go ahead and do that, but like I said it seems like my issue is a Wine issue (so therefore a proton issue) as opposed to a Mesa issue. I just tried again with a fresh Wineprefix and using mainline Mesa 19.3.2-2. No better than mesa-aco from the valveaur repo. AMDVLK makes no difference over RADV. I can't tell much from the logs I attached, but from what I could find by searching seems to indicate it's a problem with proton. But I'll post an issue over at Mesa too.

Right, @dowttie has the same video chipset as the fd.o bug report which was paired with his feedback here. Speaking of which, now that https://gitlab.freedesktop.org/mesa/mesa/commit/c63d04cb57002c636b65cdc5989c0b8aeb5dfe8b has landed in mesa 19.3.2, @dowttie, can you update mesa on your system and retest?

Looking at your log, this looks like a possible line of interesterr:mmdevapi:MMDevice_Activate Invalid/unknown iid {bbf8e066-aaaa-49be-9a4d-fd2a858ea27f}, which is loosely followed by an access violation (c0000005) that leads to the game dying with wine: Unhandled page fault on read access to 000007FFC42A9000 at address 00007F0C6110D6B8 (thread 0040), starting debugger..., so your issue is possibly audio related.

I got the same issue random crash. I tried other older proton 3.16-7
without mf installed and game looked like it was running fine for over an
hour. Then i installed mf again on it and every time I used my controller
it crashed instantly. Same with proton 4.2. But mf worked with proton
4.11-11 and proton 4.21-2-GE but random crashes like before.

I'm on an Nvidia gtx 1080 instead of AMD so I don't think it's got anything
to do with graphics drivers. Must be a wine/proton issue.

And why do my old proton version crash when I use my controller with mf on
them but not on new proton versions?

I completed this game when it first came out on proton 3.16 with mf and
controller no problem....any one?

On Sun, 12 Jan 2020, 21:08 gardotd426, notifications@github.com wrote:

@kisak-valve https://github.com/kisak-valve, the issue being tracked
over on the mesa Gitlab is unrelated to either of these bugs. I just posted
over there and was told it's unrelated and that new reports need to be
filed. So I guess I'll go ahead and do that, but like I said it seems like
my issue is a Wine issue (so therefore a proton issue) as opposed to a Mesa
issue. I just tried again with a fresh Wineprefix and using mainline Mesa
19.3.2-2. No better than mesa-aco from the valveaur repo.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266?email_source=notifications&email_token=ABHOYDDUAZ7PRXFI5EQ2DC3Q5OBGFA5CNFSM4GSMTW22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXEIFQ#issuecomment-573457430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHOYDCYBZJOFB4XHFQHQSLQ5OBGFANCNFSM4GSMTW2Q
.

@kisak-valve That looks like it will solve my issue, I will be away until wednesday, I can test after that.
Thanks for all the help and to everyone working on these projects!

Seems like it's a problem with ACO. If I launch with RADV_PERFTEST=llvm it seems stable so far, albeit with a performance hit. But RADV_PERFTEST=aco worked before, I've always used aco with RE2. So it's something with the recent release(s) of aco that's broken.

@gardotd426 I don't think it is, as I don't have AMD GPU so I can't use ACO and I still get random crashes. However I just used proton 4.21-2-GE again and it looks like it worked fine. Played for like 3 hours no problems. I'm using Manjaro with 5.4.6-2 kernel nvidia drivers 440.44 and CPU AMD Ryzen 9 3900X.

@mixalis1987 it might be the controller thing because I noticed I had a SNES controller plugged in that I wasn't using but steam was registering it. I unplugged it and changed to llvm from aco and it ran for an hour or two. When I get home I'll try it without the controller but with ACO to see if that makes a difference. And yeah, it used to work for me too with Proton-4.21-GE-2 or whatever before all this started. Now it was crashing like everything else

@gardotd426 Tested it again on proton 4.21-2-GE left the game running by itself for an hour then came back and continued playing for about 2 hours and no problems. Don't know if something changed by changing proton versions back and forth or what but looks like it's working again....

Don't know what you mean by controller thing but I only have one controller that I use for all games, steam and none steam games and that's an old xbox controller. Never failed me before...

Seeing as everything seems to be working again I'm gonna leave all as is :)

Right just completed the game on Proton 4.21-2-GE with no problems...

@kisak-valve I can confirm mesa 19.3.2 seems to fix it! I played around an hour without issue, I'll "test" (aka play the game) more extensively later.
Thanks a lot for your help.

Thanks for retesting @dowttie, credit should go to the video driver dev for fixing your issue.

Tracking note: I'm dropping the Mesa drivers label because @dowttie's issue is resolved and @gardotd426's issue has been isolated to ACO, which is a non-default option at https://gitlab.freedesktop.org/mesa/mesa/issues/2341.

Hi there. I could launch the game days ago and today, it always crashes when I try to load it.

Since it gives exactly zero error information - why even..? - when crashing in the UI, I managed to run it with this script, don't know if the directory under steamapps/compatdata/ is even the correct one, since I found no documentation about it.

https://gist.github.com/ShalokShalom/f303003350b68e75b5aadda2d8ae84a3

I run it out of Flatpak.

As you can see, there are two space characters in the name, maybe someone likes to fix that too.
As an error, I got exactly this:

esync: up and running.
./re2.sh: line 5: 47431 Segmentation fault      (core dumped) /home/$USER/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Proton\ 5.0/dist/bin/wine64 /home/$USER/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/RESIDENT\ EVIL\ 2\\ BIOHAZARD\ RE2/re2.exe

Steam updated itself yesterday.

Hello @ShalokShalom, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

It got sorted out with an update.

Thanks a lot for that.

Now, the PS4 controller does not get detected any more.

When playing a new game, after leaving the gas station, the loading screen takes an infinite amount of time and never brings me to the next screen.

When exiting the game, this is the error message:

My system information: https://gist.github.com/ShalokShalom/3b05f57cd643cf40f025fbfba68bf9e7

@ShalokShalom You need to install that Microsoft DLL to get past that.

Thansk @mixalis1987

@kisak-valve Can you help me finding this DLL?

I am quite stressed out by the fact, that I buy dozens of titles and basically nothing of it does work without heavy tweaking. I am quite aware about the fact that this all is still in development and so on, while lots of stuff can simply go upstream and be included by default, no?

The game crash and I get the following error whenever I try to create a new game:

wine: Unhandled page fault on read access to 0000000000000000 at address 00000001421DC60B (thread 0059), starting debugger...

I tried the mfplat.dll fix, I tried GloriousEggroll's custom proton, I tried with and without steam runtime, I tried with DX11 and 12 to no avail.

I am however able to get into an extra mode.

GIST

Did you try an older proton version?

On Wed, 29 Apr 2020, 13:39 patlefort, notifications@github.com wrote:

The game crash and I get the following error whenever I try to create a
new game:

wine: Unhandled page fault on read access to 0000000000000000 at address
00000001421DC60B (thread 0059), starting debugger...

I tried the mfplat.dll fix, I tried GloriousEggroll's custom proton, I
tried with and without steam runtime, I tried with DX11 and 12 to no avail.

I am however able to get into an extra mode.

GIST https://gist.github.com/patlefort/e747e900a4ee0d0ba6ae38b0bd2421db

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-621176407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHOYDDXW34SWMQUEM2KUVLRPANWNANCNFSM4GSMTW2Q
.

@ShalokShalom also, google is a thing, and googling for 5 seconds similarly
finds the same information. Jesus dude your attitude is ridiculous.

On Wed, Apr 29, 2020 at 10:58 AM Matt M gardotd426@gmail.com wrote:

@ShalokShalom this is what ProtonDB is for. You're trying to run Windows
games on an operating system that isn't Windows. If you want 100 percent
compatibility without any tweaking required, use Windows. Obviously. It's
not that complicated. Had you looked for 5 seconds on the Resident Evil 2
page on ProtonDB, you would have seen that this game requires the fix, with
links to the fix. The link can't be shared here. Look for it yourself, it
literally takes 5 seconds. And again, if it's that much of a problem, and
if looking at ProtonDB before buying a game to know whether it will work or
not is too much work for you, then use Windows

On Wed, Apr 29, 2020 at 10:16 AM mixalis1987 notifications@github.com
wrote:

Did you try an older proton version?

On Wed, 29 Apr 2020, 13:39 patlefort, notifications@github.com wrote:

The game crash and I get the following error whenever I try to create a
new game:

wine: Unhandled page fault on read access to 0000000000000000 at address
00000001421DC60B (thread 0059), starting debugger...

I tried the mfplat.dll fix, I tried GloriousEggroll's custom proton, I
tried with and without steam runtime, I tried with DX11 and 12 to no
avail.

I am however able to get into an extra mode.

GIST <
https://gist.github.com/patlefort/e747e900a4ee0d0ba6ae38b0bd2421db>

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-621176407
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABHOYDDXW34SWMQUEM2KUVLRPANWNANCNFSM4GSMTW2Q

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-621239524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y3322GVK7YM4ZLMUFGYDRPAZC3ANCNFSM4GSMTW2Q
.

Hello @gardotd426, so that it is clear, your comment was removed because we can not condone the use of legally problematic workarounds. Please do not tell others to use them.

@kisak-valve, there are other comments on this thread that mention the same
thing. That's why I didn't provide a link.

On Wed, Apr 29, 2020 at 11:09 AM kisak-valve notifications@github.com
wrote:

Hello @gardotd426 https://github.com/gardotd426, so that it is clear,
your comment was removed because we can not condone the use of legally
problematic workarounds. Please do not tell others to use them.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-621273689,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y335MGSGI4REPKN6FQVLRPA7KHANCNFSM4GSMTW2Q
.

@ShalokShalom go to ProtonDB, that's what it's for. As you should always do before purchasing a game intending to use it on an unsupported operating system. Otherwise, use Windows.

There. Removed any mention of anything, even though it's already mentioned in this thread. On the Doom Eternal thread you just said not to share links, and given that it's mentioned already without being removed, obviously I didn't think there was anything wrong with mentioning the same thing, without even giving a name or a link.

It's kinda rude to tell people to use Windows.

@SergeyLatyshev I'm not telling them to use Windows. They are literally on here complaining that the game doesn't work and they buy dozens of games and they don't work perfectly. I find that rather rude.

"I am quite stressed out by the fact, that I buy dozens of titles and basically nothing of it does work without heavy tweaking. I am quite aware about the fact that this all is still in development and so on, while lots of stuff can simply go upstream and be included by default, no?"

If that's such a problem for them, then it seems Linux isn't where they should be buying all their games with the intention to play them with zero issues.

But they have a point. It's very true that many games don't run in Linux without tweaking (sometimes "legally problematic", which means we are far from being able to one-click play in regular Proton). ProtonDB is not a panacea. There are rated "gold" games which don't work on my computer, there are unpopular indie games with zero reports.

On the bright side, many games, having had required tweaking earlier, work now out-of-the-box, like Halo, Doom Eternal or Batman: Arkham Knight. In most cases, all problems are caused by DRM or some bad decisions of devs, like WMF video.

Right. And that's something that we all have to accept, or use Windows (or
consoles). It's one or the other, either we accept this, or we don't use
Linux for gaming. Unless you're a programmer that's going to fix it
yourself. Those are literally the only three options, and complaining about
it on a thread that has nothing to do with that is ridiculous. This thread
isn't about the state of Linux gaming, it's about Resident Evil 2 running
on Linux in Steam. And there is a workaround that is absolutely required,
that can't be mentioned here, but either way it's not a place to complain
about the "dozens of games" you've bought.

On Wed, Apr 29, 2020 at 11:31 AM Sergey Latyshev notifications@github.com
wrote:

But they have a point. It's very true that many games don't run in Linux
without tweaking (sometimes "legally problematic", which means we are far
from being able to one-click play in regular Proton). ProtonDB is not a
panacea. There are rated "gold" games which don't work on my computer,
there are unpopular indie games with zero reports.

On the bright side, many games, having had required tweaking earlier, work
now out-of-the-box, like Halo, Doom Eternal or Batman: Arkham Knight. In
most cases, all problems are caused by DRM or some bad decisions of devs,
like WMF video.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-621287649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y332XWTO2OZ5AS6EAYJTRPBB3VANCNFSM4GSMTW2Q
.

Well, if Valve Proton workers fix the MF problem, this indeed will make literally dozens of games run perfectly:

• American Fugitive
• Blasphemous
• BlazBlue: Central Fiction
• Breathedge
• Call of Cthulu 2018
• Car Mechanic Simulator 2018
• Children of Morta
• Danganronpa V3: Killing Harmony
• Dauntless
• Devotion
• FINAL FANTASY TYPE-0 HD
• GRIS
• Monster Hunter World
• Obduction
• PC Building Simulator
• Postal 4
• Stranded Sails - Explorers of the Cursed Islands
• Team Sonic Racing
• The Outer Worlds
• Yaga
• Resident Evil 3
• Resident Evil 2
• Resident Evil 7
• Darksiders Warmastered Edition
• Devil May Cry 5

• Borderlands 3

  And many more

Hello. The Proton GitHub issue tracker is not a discussion forum. Please keep comments on topic, polite, and kind. Thank you.

Did you try an older proton version?
…
On Wed, 29 Apr 2020, 13:39 patlefort, @.*> wrote: The game crash and I get the following error whenever I try to create a new game: wine: Unhandled page fault on read access to 0000000000000000 at address 00000001421DC60B (thread 0059), starting debugger... I tried the mfplat.dll fix, I tried GloriousEggroll's custom proton, I tried with and without steam runtime, I tried with DX11 and 12 to no avail. I am however able to get into an extra mode. GIST https://gist.github.com/patlefort/e747e900a4ee0d0ba6ae38b0bd2421db — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2266 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHOYDDXW34SWMQUEM2KUVLRPANWNANCNFSM4GSMTW2Q .

I tried version 4.11-13 but no luck. However, I was finally able to run the game and play by running the game in a separate wine prefix through lutris using proton 5.0-6 rather than through steam. I tried deleting the compatdata folder for the game to regenerate it but it made no differences. I also tried disabling steam overlay. So I'm left confused, what could steam be doing differently?

So I need to do illegal steps in order to get a game running and this is why I get no support on it and get insulted and this even gets a pass from the support team.

Insults instead support, great idea, thats how you attract customers.

THIS GAME ISN'T OFFICIALLY SUPPORTED ON LINUX, and nowhere whatsoever does
Valve say that it's supported on Linux. The page on Steam says Windows
only. So what's the issue

On Sat, May 2, 2020, 3:12 PM ShalokShalom notifications@github.com wrote:

So I need to do illegal steps in order to get a game running and this is
why I get no support on it and get insulted and this even gets a pass from
the support team.

Insults instead support, great idea, thats how you attract customers.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2266#issuecomment-623000465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y3322YPX7CY32EFJEQ3LRPRWCPANCNFSM4GSMTW2Q
.

@kisak-valve
Hi, i could play RE2 entirely on first run with Leon.
Reporting MFplat "new" bug that happens only on 2nd run (with Claire): when approaching the main entrance PC and the video should start playing.

with Mfplat.dll hack the game crashes when approaching the video display
without (vanilla Proton) after interacting with the video display, the game bugs: no more HUD, no more possible interaction. Same happens with Proton-GE 5.6-2.
my config

I just played as claire and the pc video is working fine. Using vanilla proton 5.0-7
Also just played 2nd run as claire and it worked. Remember if your processor has a lot of cores I think it was over 16? Then you need to set the game to use only 15 of them. But if it worked with Leon then I don't think that will matter really.

Also just played 2nd run as claire and it worked. Remember if your processor has a lot of cores I think it was over 16? Then you need to set the game to use only 15 of them. But if it worked with Leon then I don't think that will matter really.

I'm on an i5 quadcore, but the game ran fine all along the first playthrough. I tried settings to super low, resetting the Steam cache, changing client to beta, nothing worked.
The game doesn't crash but breaks and no interaction is possible anymore.

I just played as claire and the pc video is working fine. Using vanilla proton 5.0-7
Also just played 2nd run as claire and it worked.
It's not the 1st playthrough video play but the 2nd run video play that breaks btw.

When no interaction is posible that usually is a problem with MF. It doesn't initialize.

here is the breaking bug in action, which doesn't happen on 1st playthrough https://www.twitch.tv/videos/613723077
after i've interacted with the video PC, i can't open doors, open menus, etc.

@Bumbadawg That bug always happens when the video on the pc doesn't start because of the MF. Unfortunately we can't talk much about MF on here. But have you tried to install that again?

@mixalis1987, to be clear, the workaround you're encouraging is interfering with feedback that we can use to improve Proton and Wine.

There's no problem with discussing Media Foundation in general, and the new, open source implementation that is going into wine, but it's not okay to support illegal workarounds in any way.

@kisak-valve I wasn't supporting it. I was just saying what the problem could be. Thats why I didn't mention how to get the fix.

Using Proton-GE 5.6-2 and MF, this gstreamer error pops up in the Proton log
34 005f:warn:mfplat:query_bytestream Unhandled query type uri 35 0060:trace:mfplat:source_stream_added stream-id: 2 36 0060:trace:mfplat:source_stream_added Found existing stream 0xfe8ff40 37 005f:trace:mfplat:process_bytestream_pad_event filter 0xfe8fd70, type "reconfigure". 38 0060:trace:mfplat:watch_source_bus source 0xfe8fd70 message type stream-start 39 005f:trace:mfplat:watch_source_bus source 0xfe8fd70 message type tag 40 41 (wine:32173): GStreamer-WARNING **: 17:41:40.935: ../../proton/gstreamer/gst/gstpad.c:4551:gst_pad_push_data:<asfdemux0:video_0> Got data flow before segment event 42 43 (wine:32173): GStreamer-WARNING **: 17:41:40.935: ../../proton/gstreamer/gst/gstpad.c:4298:gst_pad_chain_data_unchecked:<appsink0:sink> Got data flow before segment event
GL with implementing open-source MF into Wine guys, maybe this error helps the team.

New log about the only 2nd run crash occuring with Claire playthrough when approaching the computer with 5.0-7 (as a reminder this didn't happen on 1st run so it might be a different playback call)
0150:err:strmbase:STRMBASE_DllGetClassObject {41457294-644c-4298-a28a-bd69f2c0cf3b}: no class found in C:\windows\system32\winegstreamer.dll.

@Bumbadawg I'm not the best at diagnosing errors but I did test my game for you and it was working fine. I'm not sure what you have tested so far but have you tried uninstalling the game and it's prefix (make sure no files are left behind) and going through the setup again? Also maybe deleting proton 5.0-7 and getting steam to just set it up again. I think the latter option wont really be needed if the GE version was crashing also but it's worth a shot.
It's very strange that your having this problem, the game is rated platinum on protondb.com

yeah, like i said i understand it could be rated platinum, as far as i went through the whole first run, but this is specific to the 2nd run.
I deleted the game, the pfx, Proton, reinstalled it all, nothing worked, same issue.

Now sometimes in the log i get this when playing the video err:mmdevapi:MMDevice_Activate Invalid/unknown iid

Maybe i require some local libraries winegstreamer relies on ?
I've got the gst ugly/good/bad/base libs, gstreamer/gstreamermm installed.

Super strange, how a game that asks for illegal workarounds and has no legal way of running it and is thus that unsupported by Steam and Valve, is even considered Platinum.

@ShalokShalom there is a legal way of running it:

https://github.com/GloriousEggroll/proton-ge-custom/releases

(Also the legality of other workarounds is more of a grey area, and not necessarily illegal when done by a user. Valve/codeweavers is just using an abundance of caution, I believe)

The game works pretty much fine, on 5.0.7 and 5.6GE versions of proton. I was able to finish fully the first run as Claire, but when I started the second run as Leon, just in the beginning when I enter the police station and touch the RPD laptop (it is red), then I can't go back to menu, open inventory, use any other items, see hud, basically, I can't do anything and I have to exit via ALT-F4 combination. That being said, I can't continue playing the game in the second run. This is very sad, the game is very good, and having it almost constantly running in between of 150-240 fps is quite satisfactory if it were not for such stopping bugs :(

I have found several reports about bugs around this red laptop there, but most of them were causing visual glitches or black screen or anything else. Anyway, I tried to use the same solution which was to set "UseVendorExtensions=Disable" in the re2_config.ini file, but the problem persists. Other people said to try to run with DirectX12, but with 20 fps I couldn't even reach this location, lol. I also had lots of glitches and simple couldn't see where I was going while I was using DirectX12, so, basically, I don't know of any solution to this problem.

Somehow, I was able to reach that laptop with 1-3 fps using directx 12 and almost black screen with no useful information on it, but the problem persists even so. I also have just tried the "windowed" mode instead of a fullscreen one, and yes, no solution still.

here is the breaking bug in action, which doesn't happen on 1st playthrough https://www.twitch.tv/videos/613723077
after i've interacted with the video PC, i can't open doors, open menus, etc.

I can't watch your video, but my symptoms are quite similar, it could be that we have the same bug.

UPD:
The same bug actually also happens to Resident Evil 3, exactly the same behaviour. I started playing the game (RE3) as Gill and was able to complete the first part until the game changes to Carlos. When I had to install C4 detonator and blow up the wall between men and women showers, there was a wall a few rooms, called "STARS Office". Once I press the left mouse button in order to open that door, the cutscene starts playing, and after that - again, no more hud, no more escape/inventory/map stuff is available by pressing appropriate keyboard keys, but some items are interactable still: I can open the safe, can save, but not pick up items and anything else. After that bug has happened, I was able to walk as Carlos out of the room and the game switched back to Gill, but still, even after that switch, the bug was active, though, I was able to save as Gill, and, perhaps, may continue playing without a bug for some time again.

This is definitely a problem.

I have a workaround! So I tried just not to activate this laptop-thing, and just walk-around. The mission was to "Investigate the police office". So, I was walking about the entire office until I found a medallion or a statue, can't remember now. But once I did that, the mission has changed to "Find 3 medallions" and simply I was able to go through and now I am in the parking garage, so, have moved forward quite far. Everything is working fine, so no bugs and problems after. I haven't been trying to activate or even approach the laptop's area as I see no reason in it. Perhaps, it is even non-interactable now.

yep the same MF plat issue i reported above. We found the same workaround it seems =)

Hello,

1) SSAO and HDAO seem to randomly cause major FPS drops. For example, in RPD hall, the normal framerate is 90+ FPS but when the issue is triggered, it barely reaches 25-35 FPS, even in the pause menu. After some time (5, 10, 15 minutes, who knows), it goes back to normal. Switching to HBAO+ and switching back again also makes the trick... until the framerate tanks again some time later. For the record, I have the same issue in RE3 Demo, so maybe it's related to the RE Engine.

I use these launch options: RADV_PERFTEST=aco DXVK_ASYNC=1 gamemoderun %command%

I tried disabling them one by one, same. I tried Proton-5.8-GE-2-MF, Proton 5.0-7 and Proton 4.11-13, same. I tried with and without Freesync, same. I tried with and without TearFree, same.

2) Exactly the same issue as above. Perfect first run, but on the second one, the red latop thing happens.

3) Later during the second run as Claire, after the phone call with Irons, the loading never ends.

Hardware: Ryzen 5 1600AF, RX 570, 16GB RAM
Software: Fedora 32 Workstation, DXVK 1.6-69, Mesa 20.0.7, Vulkan 1.2.128

This issue with the laptop is present even with regular Proton 5.0-9.

I think the workaround is watch the Tyrant video on YouTube and skip the laptop altogether for now as suggested above.

SSAO and HDAO seem to randomly cause major FPS drops.

It turned out it's due to RADV. When switching to AMDVLK, the framerate is lower (80 FPS vs. 100+) but steady.