PlayableShow Details
Unknown
Runs straight out of the box on the latest issue of Proton-GE.
Set TDP to 9, but it isn't really necessary.
Most of the text is fine, but the turorials are hard to read.
Works out of the box from start to finish.
Game runs well, performance is roughly on par with Windows
Every now and then game would crash after a loading screen, but I've never lost any progress so not a huge issue.
No problem with amd card. Glad, that I've chosen amd gpu for linux gaming.
mangohud %command% --use-d3d11
Sound design is bad in this game, perhaps it's not a linux issue at all
For the last mission I installed the 575 driver and it did wonders for the performance, before I had only 2 or 3 settings at medium and others at low and the game struggled to keep 75 fps. With 575 driver I bumped the settings to high and had no problems with framerate.
Rogue City is a very demanding game and likely doesn't benefit from the alleged DirectX12 Proton performance degredations.
DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 2070"
My GPU is a bit dated these days, so you're either having 40FPS or using a performance upscaler - and if you do this, hair gets dotty, and the GI solution is blotchy as all hell.
Seemingly fixed by disabling FSR 3 (Upscaling, but mainly Frame Generation)
I was getting absolutely unplayable crashing, seemingly whenever the game needed to load a new area. I tried out multiple proton commands and versions, but what eventually fixed it was disabling FSR Frame Generation. I also opted for DLSS, which even in Performance mode absolutely beats the pants off FSR3's best upscaling option. If you're getting crashing try disabling FrameGen before delving into any proton tweaks.
Getting around 40-60FPS @1080p on Medium/High Settings using no raytracing (my CPU is far too weak to load the BVH and even light raytracing decimates performance in all games) and DLSS Performance. GI is a bit blotchy but only really noticeable in the police station. Shadows are very aliased and you may sometimes see ghosting (but nothing compared to FSR ghosting lmao).
FWIW I'm not even sure if the command above or GE-Proton are doing anything, but I'm not about to change it since I've got a much more stable game now.
Although the game worked perfectly before, the most recent update causes the game to crash consistently on boot with Proton 9. Switching to Proton 10 (Beta) has solved this issue for me
Works great! I recommend lowering all settings as well as resolution via the TSR resolution scale option in game. Doing so will maintain an unbreakable 30 fps cap, which I recommend setting via the game's competent framerate limiter in the menu (in order to avoid input delay from Steam Deck's built in framerate limiter). TSR is highly recommended, as the other upscalers available produce a much more distorted and incomprehensible image. Lumen ray tracing is completely intact and very impressive on the Steam Deck, despite the visual noise and light lag incurred by the low resolution scale required
You could probably beat the game. But you'd have to restart every hour due to random crashes during loading, or just mid game.
For some reason the further you go into the game the more the audio crackles?
Mouths are molting into eachother. When you watch someone speak, you can see some wierd artifact in their mouth. At first looks like broken teeth but the closer you are the more obvious it is.
No fucking clue what is going on. Some people have no crashes with some minor tweaks. I followed each and every one. Constant crashes. Thread Timeout. When doing research it leads to a problem of i13 processors. I do not have an i13. Tried all versions of proton. Some versions don't even let you start the game.
This does not deserve gold. Silver at best. The game runs sure, but you can't say it runs almost natively. Crashes are everywhere and when you search an issue up it mostly leads to a fix for Windows... Not Linux. Apparently the devolopers completely cooked the code when it comes to upscaling, so crashes could also be related to that. But who knows. It really is a shame cause it's a good game when it works (for an hour.)
the text was small, but in most cases it wasn't a problem
I played the game on the Steam Deck from start to finish. I was surprised that the Steam Deck LCD could get about two hours of battery life and a pretty good picture. There were glitches and image flickering, and I had to restart the game a few times, but nothing that really affected the gameplay (it was fun and satisfying to blow off the heads of the criminals). I lowered the resolution to 720P, set the textures to medium, the range to FAR, and the TSR to 60, and set the rest to low. So this settings give me a stable 30-40 FPS (2/3 of the game), but there will definitely be some drops. This is not a "platinum perfomance", but I highly recommend it for Steam Deck.
MANGOHUD=1 vsync=2 PROTON_ENABLE_NVAPI=1 DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4070 Ti" game-performance dlss-swapper %command%
Severe lag on main menu, it fixes itself after going ingame.
It runs. It's a great game. It WILL crash...a lot. Just be aware
Mouse cursor will disappear at times
Well worth the money...if you don't mind crashing every hour or more. Wouldn't be such an issue if there was a quick save feature. Checkpoint only.
DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce GTX 1660 SUPER" %command%
At first I couldn't get the game to do anything other than go to a black screen. After changing the launch options and starting in GE-Proton I was able to start the game and play. The game does load up slowly when showing the logos at the beginning before the main menu and when the screen goes black before the game begins proper. After that the gameplay and cutscenes are play fast and smooth as they ought to.
With default options the game wouldn't load for me but with the minimal tinkering I mentioned it runs great.
Tweaking the game configuration file
Add the following at the end of your .../RoboCop/Saved/Config/Windows/Engine.ini file
[SystemSettings]
r.ViewDistanceScale=0
r.SkeletalMeshLODBias=5
r.LensFlareQuality=0
r.ReflectionMethod=2
r.DepthOfFieldQuality=0
r.Lumen.Reflections.Temporal=0
r.Lumen.ScreenProbeGather.Temporal.MaxFramesAccumulated=32
Add this line if you wish to disable shadows, (not recommended):
r.ShadowQuality=0
More info about these tweaks:
FPS limit in--game and the Steam Deck at 30 fps.
Text is small, especially on tutorial prompts and pick-ups, but just abour readable and doesn't affect gameplay.
Engine.ini graphic tweaks helps a lot. Otherwise, frame drops cause audio to be out of sync during cutscenes. Visuals dip and slows to ~20 fps causing it to fall behind dialogue.
NPC Mouths during Cutscenes, (a known issue)
Weird mouth bug present on other NPCs during cutscenes which is a known issue. Setting view distance to 'epic' or further .ini file tweaks might help with this.
Between 20-30 fps during game play with instant dips when explosions occur or when traversing areas that are being loaded into the game. Cutscenes at start of game very slow with audio/video sync issues. Engine.ini tweaks seem to help with these issues.
Reminder about Mods: To use mods, be sure to use Blueprint Mod Loader - DML and remember to add a "ModToSpawn" entry to your Engine.ini file for each mod you wish to add.
This worked good once I add the component of C++ I got this game from heroic so it is nice to run it on my steam deck
I got the following error: ] Error
The following component(s) are required to run
this program:
Microsoft Visual c++ Runtime
click winetricks on the heroic game settings
select standard wine prefix, ok
install windows dll, ok
search for latest vcrun (2022)
close wintricks
start the game
Proton Experimental is a no-go with this setup. Hitching occurs where I think the game is loading the next chunk of a level and eventually locks up. Changed to GE-Proton10-4 and no hitching or lockups. Getting between 125 and 155 FPS on highest settings and FSR3 using an XFX Mercury 9070 XT.
Disabling shadows in via the Engine.ini file provides more stable 30 fps.
Add the following to your .../RoboCop/Saved/Config/Windows/Engine.ini
[SystemSettings] r.ShadowQuality=0 r.ViewDistanceScale=0 r.SkeletalMeshLODBias=5 r.LensFlareQuality=0 r.ReflectionMethod=2 r.DepthOfFieldQuality=0
Text is small, especially on tutorial prompts and pick-ups, but still readable.
Weird mouth bug present on other NPCs during cutscenes which is a known issue. Setting distance to 'epic' or further .ini file tweaks might solve this, but I have not yet tried it.
Between 20-30 fps during gameplay with brief dips when explosions occur or when traversing areas that are being loaded in. Cutscenes at start of game very slow with audio/video sync issues. Engine.ini tweaks seem to help, and disabling shadows in particular.
If you want to use mods, be sure to use Blueprint Mod Loader - DML and remember to add a "ModToSpawn" entry to your Engine.ini file for each mod you wish to include.
The game runs fine overall, no tinkering needed to have an enjoyable experience.
The game appears to have some minor performance issues. Changing the graphics settings, even to the lowest, does not seem to make much of a difference at all and I can't seem to get it to run at more than 60 FPS with dips down to the 30-40 range. Not sure if it's related to Linux/Proton or just general Unreal Engine sheanigans.
PROTON_ENABLE_NVAPI=0 %command%
Stuttering, texture pop-in and lag .
Game will be laggy OOTB but forcing Experimental proton and the following command fixes any issues, at least on NVIDIA hardware. However YMMV.
For me, my game went up from 5-15fpa to 70-100. Full Playable.
PROTON_ENABLE_NVAPI=0 %command%
Stable or normal versions of Proton barely work for this game, lots of input lag, fps drops and stuttering. GE-Proton is a must.
Crackling and bugging out on loud explosions
Screen flicker on some textures
Stable or normal versions of Proton barely work for this game, lots of input lag, fps drops and stuttering. GE-Proton is a must.
Switched to launch options to tell the game to use my dedicated GPU, otherwise no issues from start to finish.
PROTON_ENABLE_NVAPI=1 DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 3090 Ti" %command%
Did not launch without launch options, possibly tried to use CPU instead of dedicated GPU.
В целом играбельно пройти сюжетеу можно но не более импут лаг есть и целиться из-за этого проблемно
Зерностость от FSR
Очень сильеыц импут лаг
Были фризы не значительные
При переходе в другую локацию просто черный экран и нет значка загрузки чтобы исправить перезапускаем игру и вы грузитест в новую локацию бывает часто проблема эта
The textures on NPC faces look weird. Some black textures on the teeth as well.
Had really low FPS until switching to GE-Proton9-21
Had one crash on the first mission.
Had to set everything on Low settings and lock the framerate to be able to play comfortably in 1440p. Still enjoying the game.
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_SHADER_MODEL=6_7 %command%
Im Grafikmenü auf Nvidia DLSS umgestellt. Danach lief es flüssig.
Die CPU wird genutzt statt Grafikkarte bis man umgestellt hat auf DLSS
It works.
If you are on nvidia as of March 2025, directx12 games lose 20-50% performance.
With Proton GE 9-26, it just works. The game installs and plays just like on Windows. All settings work, no crashes and no bugs. A perfect experience from beginning to end.
PROTON_ENABLE_NVAPI=1 DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 3060 Ti" %command%
Default game woudnt launch beyond initial startup logos. Specifying GPU in launch options was necessary and changing resolution in game menu. Game started in max resolution and fullscreen window mode, wich caused massive lagging.
gamemoderun %command%
Game would freeze when starting up until I switch to Proton Experimental, and even then first boot takes forever. After the extremely slow first boot, everything works fine there after and subsequent boots are fast. This happened on Windows 11 also, so doesn't seem to be a Linux issue.
Tried proton experimental and proton9 first but it was a bit laggy. changed to ge-proton and lag is gone.
Didn't have to do anything extra the game just runs.
I think in general the game isn't optimized that well and not a Linux/Proton issue but I still enjoyed it.
Changed the executable from RoboCop Rogue City\RoboCop.exe to RoboCop Rogue City\Game\Win64\D3D12\RoboCop-Win64-Shipping.exe, otherwise it didn't launch
I'm gonna classify as slight performance problems because they didn't make the game unplayable by any means; but twice I had a stutter that lasted between 5 and 10 seconds. They didn't occur during action sequences though, just during exploring. Also, during the third visit to the city, I had a bit of an FPS drop, but it was minor.
The thing is, it runs completely fine, I completed the game and even enjoyed it (despite the game having so much ghosting I spent half the time asking myself it wasn't playing Ghost Busters by accident; but then again, it's Unreal Engine using TAA with no other option of anti-aliasing). I'm just not sure if the average user would be fine with, or even think about tinkering with the executable, even if it's not a hard fix.
