Open Cuddlypuff opened 6 years ago
Seconded, I noticed no issues either, AMDGPU open source driver on AMD 7790HD Arch Linux and proton 3.7, system info: https://gist.github.com/shikaku2/654059fa5af54028d02f7fa77a0b9fb9
Steam Overlay doesn't render correctly and game window doesn't fit within available space.
Distro: Ubuntu 18.04.1 GPU: Intel Iris Pro 580 Resolution: 1280x720 RAM: 32GB Controller: DS4 Proton 3.7-5 Beta
https://gist.github.com/daasuharo/cb605b8cd50227982a9bfa4dfcb1f635
Runs perfectly-well! Linux Mint 18.3, Nvidia GTX970 with 396.54, Proton 3.7.5 Beta.
Can't continue watching cutscene after pausing (it freezes). It is only possible to skip it. Everything else is okay.
Linux Mint 19 Tara (64 bit) Kernel Version: 4.17.19-041719-generic NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2, driver 4.6.0 NVIDIA 410.73 Proton 3.16-3 beta
The higher the selected resolution in the options, the lower you need to set the anti-aliasing, or the screen will either flicker or turn fully black.
Ubuntu 18.04
Kernel 4.15
NVIDIA GeForce GTX 970, NVIDIA 415.25
Proton 3.16-6 beta
i want to provide an update for this even if its a late one
on proton 3.16-4 this issue happens:
Can't continue watching cutscene after pausing (it freezes). It is only possible to skip it.
on any newer version the game will crash on changing resolution from or to 1920x1080 and it will be much more crash prone, funnily enough the cutscene bug is not present in any version newer than 3.16-4
Hello @davidbepo, does adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
to the game's launch options have an effect? Also, please gather a Proton log of the crash and drag and drop it into the comment box.
adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to the launch options indeed fixes the crash issue, on both proton 3.16-9 and 4.2-7
thanks for the tip, btw
The game crashes every time when I try to increase resolution. steam-235460.log
But adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
would avoid this crash.
$ inxi -bM
System: Host: localhost.localdomain Kernel: 5.2.0-0.rc7.git1.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: 2304 date: 05/03/2019
CPU: 8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2940 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.2.0-0.rc7.git1.1.fc31.x86_64 LLVM 8.0.0) v: 4.5 Mesa 19.1.1
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: 9.92 TiB (85.7%)
Info: Processes: 477 Uptime: 18h 24m Memory: 31.29 GiB used: 20.52 GiB (65.6%) Shell: bash inxi: 3.0.34
Dualshock4 does not work in game, and problems with resolution (1920x1080) as in this report https://www.protondb.com/app/235460#ksn4zsiux steam-235460.log https://gist.github.com/soredake/ed1fa30f885371dda5f331815920a3ae
Proton 5.0-9 steam-235460.log
Proton 5.13-1, same problem in fullscreen. steam-235460.log
Game doesn't detect my savegame that was created under Windows. The game uses a hardcoded path for its saves but also supports cloud saves. Yet every time I launch it, the save slots are all empty on Linux even after copying the Windows save files into the prefix (which Steam actually does itself on first launch - probably sourced from the cloud) for the "steamuser" user.
Tested under both v5.0-10 and 6.3-4
@soredake
Replying to https://github.com/ValveSoftware/Proton/issues/787#issuecomment-663372675
This still occurs in Proton 6.3-8, by the way; though, I patched my executable to replace 800x600
with 3840x2160
(my native resolution)
Selecting this option fixes the issue for me (at the cost of the UI glitching out over an unsupported resolution), but selecting those other options are just as borked as your screenshots
This might be a problem for playing the game on the Steam Deck, by default...
For reference:
Widescreen Patch: https://www.pcgamingwiki.com/wiki/Metal_Gear_Rising:_Revengeance#Widescreen_resolution (Direct link)
MGROverride_1.1.zip SHA256 checksum:
ec05df1884d8f4279b63f9ac099056169c3bb93ff6b88ac8015ad0de9bb4323d
Patched Game executable SHA256 checksum:
23a89ae5a85e0a2fe8a9027421f4ed5cd2540eb58ee6868d6f1fbf85173421b2
Game crashes when setting it full screen on proton 7. Works completely fine on proton 6.3-8.
Ubuntu 20.04.4 LTS Kernel 5.13.0-30-generic resolution 1440x900, 1920x1080 Intel i7-4790K (8) @ 4.600GHz NVIDIA GeForce GTX 980 NVIDIA driver 510
@Robmike27 Are you able to post a proton log? 🙂
@Blisto91 Yeah I'm sorry I didn't post one before. steam-235460.log
Metal Gear Rising: Revengeance on Steam Deck in Desktop Mode
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6198. @jukefr posted on 2022-09-30T04:56:48:
The game launches fine in Game Mode. The game crashes on launch in Desktop Mode.
I think this happens to every Steam Deck as I created a reddit post at first to ask and somebody else seems to be facing the exact same issue.
edit: seems to work with proton 5.0
Played through the first boss with no issues, great framerate, high settings.
System info: https://gist.github.com/Cuddlypuff/a518019d119623d9a1b7552e284c1f6d