mangohud gamemoderun PROTON_ENABLE_NVAPI=1 %command%

There are 2 moments in the game that make it freeze on newer proton versions: Dimitrescu on the phone cutscene and one of the Benevientos scare sequences. I had to manually kill the process and switch temporarily to Proton 7.0-6 to get through these.

Cutscenes didn't work for me on default proton 9.0-4, every cutscene would show a test screen, even the launch cutscene for the RE Engine. Switching to GE-Proton8-26 fixed the issue. Everything else worked flawlessly, except this cutscene problem, which was resolved with older ProtonGE.

game-performance mangohud %command%
I played it first with cachyos-proton but game got stuck after certain cutscene so switched to proton 9.0-4

Some cutscenes are context heavy. I was able to look them up on Youtube but I don't thinka casual gamer would enjoy this.
WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
Game runs perfectly fine at max graphics at 60 fps though I locked the FPS to 40 since it still looks good and saves some battery.
The game doesn't display some cutscenes or videos with the default proton. While GE Proton solves this, it led to crashes (Specifically the dollhouse where you are stripped of your weapons)
There's a part where Lady Dimitrescu's reflection shows the visual when you don't have the codecs for videos.

WINEDLLOVERRIDES="dinput8=native,builtin" %command%
need to use REFramework dll
little stuttering but manual set vsync for 60 helps

gamemoderun %command%
Using Valve's Proton will make certain cinematics have a test screen. I tried to use the latest GE version, but it crashed everytime the cutscene where Lady Dimitrescu gets a phone call ends. Using slightly older versions made the earlier mentioned cinematics freeze the game. Using 8-26 seems to work perfectly, but maybe using something like 9-13 could work.

For me, the game would not launch with any non-GE proton

gamemoderun mangohud %command%
As with the Re7, the game loads cutscenes only with GE-Proton9-4. The game runs very smoothly

Game works OOTB
Finished the game without any issues

Played the game from start to finish, no major issues that I was not able fix. Just had to switch to a different proton version
At one point in the game after a cutscene was finished the game would freeze and crash
A great experience to play on linux

Game worked fine out of the box until the cutscene of Dimitrescu answering the phone, where it freezes. Proton 8.0 fixes it.
Thanks to the few reports trying Proton 8.0 I managed to get past the freezing/crashing point, but it was quite painful after trying many other versions and commands. Proton 8.0.5 doesn't seem to have any drawback so might as well play the entire game on it.
It works like a charm! I didn't do anything, just installed and started to play.
No issues

Make sure your VRAM usage is white in the game settings, even if it's well bellow your GPU capacity, otherwise you will experience memory leaks and the FPS will drop dramatically. Also, whenever your change the graphical settings, quit the game and then re-launch, or it will leak memory as well. Other than that it worked fine, I finished the main game and the Shadows of Rose DLC without any issues.
I've tried everything except Ray tracing, the optimization is good, you can play it on Linux

Game plays really well
After playing some time my game freezed, that was caused by crashing AMDGPU driver that deleted all of it's VRAM data leaving me without screen forcing me to restart via CTL blindly because my screen was stuck on one frame rendered by game. Journalctl shoved me repeated error "amdgpu failed to initialize parser -125". I couldn't find the fix for this unknown error on any forum because people "agreed" that it was hardware specific issue probably caused error during making the card. However updating my GPU firmware seems to fixed this issue for me and it seems it's not coming back any time soon.

MANGOHUD=1 %command%
An in-world video was rendering incorrectly, besides that there wasn't anything I noticed.
Fullscreen acted strangely, borderless fullscreen behaved perfectly.
Completed the entire main story and explored all areas. Ran great at 144 FPS with fairly high settings with the lowest FPS being in the 90s.
Using 'mangohud %command%' in the launch options caused infinite loading. I used 'MANGOHUD=1 %command%' and it worked without a hitch.
Trying to load mods that replaced textures + models didn't work but REFramework and script mods did. I couldn't figure out why.

After playing the Shadows of Rose DLC, I can confirm that this works just as well as the base game.
RADV_PERFTEST='rt' VKD3D_CONFIG=dxr11,dxr WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
THIS REPORT IS ABOUT THE DLC!
Some other reports seemed to indicate that the game had technical issues in the Shadows of Rose DLC. Now that I've played through it, I can only say that for me, the game ran just as well and was just as super stable as the main game. If there are technical issues with this DLC, they did not affect me in the slightest.
REFramework works just as well with the DLC as the base game. Though this DLC forces you to play through it in third-person mode, so the FOV issue is likely to be slightly less crucial than in the base game.

RADV_PERFTEST='rt' VKD3D_CONFIG=dxr11,dxr WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
As others have noted, there are three problematic video sequences that don't work. There's the "Village of Shadows" intro cinematic when you start a new game, which has a follow-up vdeo right before the credits. Those do not work. Then there's also a video which is projected unto a screen halfway through the game. This one does show something, but is transformed and artifacted. All other videos, including the RE7 recap video and credits, work just fine. The video that don't work do not impact story or gameplay, as the entire "Village of Shadows" cinematic is irrelevant, and the projector video does not impede your ability to solve a puzzle.
THIS REPORT DOES NOT DISCUSS THE DLC!
Aside from the video issues mentioned above, this was (at least for me) the single best gaming experience I've had on Linux so far. The game works perfectly from the very first second. Performance is simply incredible. I ran the game maxed out (but with RT disabled), and I hit a consistent 100fps (which is my monitor's sync rate), and my GPU still had a bunch of room to spare. I swear I don't think I've seen the game drop even a SINGLE frame in my entire playthrough, and the latency graph was perfectly smooth. It was honestly incredible. Others have reported stability issues and crashing. I had no such issues whatsoever. Zero crashes, zero performance issues, no sign of memory leaks.
Ray-tracing
I wanted to try enabling ray-tracing since this game has a ton of moody lighting. Contrary to other games I've played with RT, I was actually able to enable RT with the right environmental variables set. However, while in-game, I don't think any of it actually worked. Curiosly it did have a significant impact on performance (enable/disable made a difference of around 20% GPU utilization), but I never was able to observe any RT effects. I think it's borked. However, this game looks amazing without it either way, so it honestly doesn't matter.
REFramework and FOV
I play on a 3440x1440 Ultrawide display, and while the game works flawlessly on this, the FOV is very problematic (I suspect on other screens as well). Within about 30 minutes, I had to save and quite the game because I felt like I was becoming sick. REFramework (https://github.com/praydog/REFramework) thankfully works out of the box on Linux and has a built in FOV solution out of the box. Just download from Github, drop the dinput8.dll
into the game installation folder and include WINEDLLOVERRIDES="dinput8.dll=n,b"
in the launch options. The game will starts with an imgui-style window overlay on the left, and you'll be able to set various options there. I changed FOV from around 80 to a 100, and that was a huge relief. I also reduced the vignette effect via REFramework, since that was overtly present on Ultrawide as well.

Steamtinkerlaunch: -w 3840 -h 2160 -W 2560 -H 1440 -f -e --force-grab-cursor --nested-refresh 165 --expose-wayland --
Memory leak after 20-30~ish minutes of gameplay
Memory leak issues causing eventual full pc slow down
I used steamtinkerlaunch and the launch options here for my setup. I also used gamescope. Mangohud works fine, can get into gameplay with it. There is severe performance degradation after 20-ish minutes where I go from 165 frames at max, raytracing to 85 with constantly spiking frame time, until my entire computer slows to a halt another 30 minutes later. Cannot be fixed without restarting the game. Is probably a memory leak, may be caused by changing graphical settings or gamescope?

Runs well if you get past the splash screen. Seems to have perfomance similar to Windows
Hair seems buggy, which is inline with other RE games played through Proton
Game crashes after splash screen if you launch with Mangohud. Bug seems to persist if Steam is launched with Mangohud even if you disable mangohud for the specific game with MANGOHUD=0
variable

On desktop mode the fullscreen wasn't really fullscreen, it just opened standard window
Had to use Proton GE due to Media Codec issue

Гра працює чудово
Встановлюєте і граєте.

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%
Mirror reflection broken in just a single cutscene

Works great but with one extremely minor bug
A single torch had a bugged red flame when it was in the corner of my screen.

When cinematics should be play,ing the game just shows a colorful screen and nothing happens.
Besides cinematics, the game works like a charm!

Borderless fullscreen caused the game to freeze consistently during the snow path sequence in the cabin basement.
The game freezes at certain points if borderless fullscreen is enabled.
Seems to be Nvidia specific, but I could be wrong.

Great out of box
Very rarely (every 1-2 hours of play) some shadow glitches, psychedilic colors or weird colums/rays
After changing some graphics settings, performance got extremely slow and didn't get back up when lowering the settings again. Performance issues were not caused by the settings themselves but merely by the fact that changes were made. Fixed by restart.
Crashed 2 or 3 times during the full playthrough
Great overall performance. Not perfect but the issues are minor. Glitches and crashes occurred very rarely, performance issues caused by changed graphics settings could be fixed by restarting the game.

i don't know about the negative proton comments i saw (maybe it's RTX related), imo playing this on AMD card the game runs perfect out of the box, i did not have any problem playing with controller and gyro, under wayland and Alt+Tab works great, smooth game all the way.

Game crashes after going up the stairs in the first house (about 30 minutes into the game)
gamemoderun PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%
Does not work, only play on windows.

30 fps cap and fsr balanced
Great game on deck. If you set FSR to UQ you can get a pretty stable 60 fps from my experience (I am using cryoutilities 2.0)

As with any modern RE engine game it's very scalable and stable, controller support OOB. Never crashed and can alt+tab out no problems.

The game is unplayable beyond a certain point.
The game always freezes at the exact same point when reaching the top of the stairs in the forest shack a few minutes into the game. I tried multiple versions of Proton -both mainline and GE- with multiple game configurations to no avail.

40 FPS limited
Most text is very small
Seemed random, sometimes happened sometimes didn't
Crashes every ~30 minutes, without warning
As with most RE Engine games, I've experienced nothing but instability from this game on Deck. It runs great normally, fantastic even, but it's all for naught when the game can't go more than a few minutes before crashing, wasting your time and trashing your progress since last save. Hell, I still have yet to manually save the game ONCE, just because I've wasted so much time making progress only to have the game crash and send me back 20 minutes. Verified? Come on now.
Crash after splash screen
AMD_VULKAN_ICD=RADV MESA_DISK_CACHE_SINGLE_FILE=1 RADV_PERFTEST=aco,sam,gpl,nggc,forcecompress,gewave32,cswave32,pswave32,rtwave64 VKD3D_CONFIG=DXR11 radv_rt=true gamemoderun %command%

Worked great, did a full playthrough. No tinkering, except in game settings.
A mirror was green instead of reflecting. The projector video in the dollhouse was green instead of showing the video.
Experienced a crash with fullscreen. No crashes after switching to Borderless Window mode.
Had to disable vsync to fix mouse lagg.
Proton 8.0-3 was used

gamemoderun %command%
I played fullscreen and it crashed after a minute of playing, I swapped to Windowed and the game did not crash.
I originally tried with Proton Experimental and that works fine too.

Infamous Green Sceen on Mirrors and Film Reel
The game runs pretty flawlessly as is. The only minor issue being that green screen is still there on the mirror and the film reel. It's not game breaking, but it's a bit immersion breaking. Hopefully that gets sorted sometime soon.