PlayableShow Details
Unknown
Native version crashes immediately with nothing displayed. Switched to proton experimental and it works fine.
This game shouldn't be listed as platinum when it's so broken. It is possible to get it to work though - with a lot of tinkering.
--use-angle=vulkan
Firstly the game starts full screen, but with 75% of the window hidden (this might only affect nVidia cards). That basically makes it impossible to even interact with the menus or do anything. This can be solved in X11 by adding --use-angle=vulkan to the launch parameters.
Secondly, the game has serious performance problems which make it close to unplayable. I have a very powerful system but the game has this stuttering and frame delay which makes you feel sick and gives you a headache. The reason for this is that Steam launches the game with Proton for some reason and it's poorly optimised (even though there is a native version).
Older versions of Proton run it better, for example in Proton 7 I can consistently get 160fps, but it does still eventually suffer from slow down after about 30 minutes of playing, and you have to restart the game. It also suffers from some flickering of what's underneath the game (other windows, the deskop, the taskbar).
The native Linux version of the game runs really well. It's locked to 60fps but never dips below that, so the best thing to do is choose "Steam Linux Runtime 1.0 (scout)" in compatibility.
However, the third issue is that the Linux native version had the SteamWorks integration broken in the last update the developers did in 2021. This means achievements won't unlock, and you can't take screenshots or use the Steam overlay.
The reason they broke it is they updated the version of nw.js but didn't recompile Greenworks to a version that's compatible with it. Some people suggested downloading a recompiled Greenworks that someone created in GitHub, but that didn't fix it for me.
There is a beta version of CrossCode available called nwjs_old, which runs perfectly and in which the Steam integration works. But it's very disappointing that I have to use that. It's been 4 years and the developers have no intention of fixing this, even though their game is listed as native support but is broken. It should be very easy for them to fix - just updating the library used in the game. Shameful for them to have broken it and then leave it broken for this many years.
The version of nw.js in the old beta release of CrossCode doesn't have good support for controllers, so you have to use keyboard and mouse, but I think mouse is probably better for aiming anyway.
Had to enable steam input for input to be correct (matching buttons on screen)
The main reason for transfering over to Hotfix was so achievements would populate, otherwise it wouldn't. Once steam input was figured out, it's worked perfectly, achievements and all.
Stuttering/Inconsistent frame pacing
Out of box experience from Steam is tolerable and playable, frame stutter is a problem and inconsistent but still playable for most cases. I wanted to find a way to keep achievements and cloud save uploads enabled without having to switch back and forth from Native [using Steam Linux Runtime 1.0 (Scout)] to Proton to upload and sync every time. I tried another variant of Proton (GE-Proton9-27) and that didn't work, so I then forced Proton Experimental (as of 6/8/2025) and it actually seems to have fixed it. Frame pacing seems to be on par with Native Linux version and appears buttery smooth. Just for reference so it's easier to identify what Proton version would be useful in case future versions of Proton Experimental break fix, the current latest Proton version to available to force is 10.0-1 (beta). Hopefully this helps anyone trying to play in the future!
Forced the usage of the native version. Default is proton
Achievments don't work on the Steam Deck when using the native version. They work fine unless you manually force the native version
Unless you go out of your way and use the native version the game will run perfectly. If you use the native build achievements don't work, but everything else still works.
DXVK_HDR=0 %command%
- According to Valve the controller may not always be sufficient. I'm a good bit in and haven't noticed such a thing. Maybe there's hotkeys for directly opening the map or inventory, idk.
- If need be, the back buttons are unused and can be mapped to hotkeys or macros.
- While I mostly didn't touch the keybinds, for certain quests/tests I did temporarily change the L2 bumper (shield) into a toggle to make them easier.
- I didn't bother disabling HDR mode, not sure if the colors are right, but they seem fine to me.
- Proton version works equally well.
- I'm not sure if steam cloud is saving the games, I didnt try another computer. Saves are in
~/.config.
After about 30 minutes of playtime, the game started getting really stuttery with some frames taking over 100ms. Since the game runs in an embedded Chromium instance, I fixed it by adding these flags to the chromium-args key in the game folder's package.json:
--enable-features=UseOzonePlatform --ozone-platform=wayland
This forces it to use native Wayland instead of XWayland, which fixed the stuttering for me.
When running through XWayland, any change to the window size made the game unplayable. Switching the game to run through native wayland fixed the issues.
As mentioned, after about 30 minutes on the default settings, the game became very laggy.
Although this is a native Steam OS game, the video was off on my 4:3 monitor. It wasn't centered. I had to use GE7-20 and to get fullscreen.
Had to use GE to get it to work.
Works perfectly, native or wine'd win version.
On the steam version gamepad input works more or less fine. However, if you are launching the itchio version via proton, gamepad input will not work.
This game is fully compatible with Steam Deck, even the official statement is only 'playable'
Great game, and flawless native. :)
The game runs fine on native but fullscreen doesn't work, forcing proton fixes the fullscreen issue
Oversaturated colors because of the forced HDR on the Steam Deck OLED, but can be fixed using "DXVK_HDR=0 %command%" as a launch parameter.
DXVK_HDR=0 %command%
Colors are oversaturated because of the HDR on the Steam Deck OLED. There's no way to turn it off unless you specify "DXVK_HDR=0 %command%" as a launch parameter.
Runs smoothly
Native version doesn't unlock steam achievements.
Change Compatibility to use Steam Linux Runtime
Stuttering when not using Linux Runtime
Much like the Steam Deck reports, changing the Compatibility to use the Steam Linux Runtime makes the game way more playable. Could be my Chromebook, but there's still the tiniest of stutter, but it's not too horrible (moreso if I'm using an external display). If it isn't changed, there's a horrible stutter that happens.
The native version of the game works like a charm once you apply the fix for the achievements.
To get the achievements working on the Linux native version, go to the following link: https://github.com/awaken1ng/crosscode-greenworks/releases/tag/v1.4.2-3
Download "crosscode-v1.4.2-3-nwjs-v0.63.1-gw-v0.15.0-sw-v1.58.zip" and unzip it. Replace the files in the game install folder with the ones in the zip file.
There have been reports on ProtonDb that Vulkan can be used if you set the option "--use-angle=vulkan". This however does nothing because the game sets "--in-process-gpu" which disables the Vulkan option.
Launching it OOTB causes the colors to become extremely saturated. It's playable, but the game was never designed with this much saturation in mind. The trick is switching to the native Linux version by selecting 'Steam Linux Runtime 1.0 (scout)' in the compatibility settings. The color saturation will be as intended by the developers.
--use-angle=vulkan
Did some searching online after having minor performance difficulties with Proton and found out that CrossCode could run well by using a compatabilty tool (Steam-Play-None) that tricks Steam to play it natively as it should. You can find it either on the Proton QT or the Github. Played for a maybe 3 hours and runs flawlessly with no stutters or screen tears. Looking forward to play the game more because of that fix! The only drawlback is to switch back to Proton and load up the game after to recieve your achievements since it doesn't work natively. Hope this helps!
Steam Recommended (Proton) and Steam Native (Linux Runtime/Steam-Play-None) all seem to run exceptionally well now with no performance issues anywhere.
Steam Deck properly manages power usage and can easily get 4-5 in this game without any tweaks or toggles.
Steam Deck controls doesn't work correctly.
Follow the steps below to get controls working.
- Download https://dl.nwjs.io/v0.63.0/nwjs-v0.63.0-linux-x64.tar.gz
- Replace the game files with the ones from the downloaded archive.
- Rename the executable file "nw" to "CrossCode".
Delete steam_appid.txt to make sure steam doesn't think you are running the steam version of CrossCode.
Instructions above were taken from https://steamcommunity.com/app/368340/discussions/0/3272436223684818200/
only chiavements not appearing with the native version unfottunately. But activating Proton helps.
not sure if this is a controller issue but occasionally after the keyboard appeared on the screen and disappeared I had no input on my controller anymore
achievement only appeared after activating Proton. But native worked great so far and doesn't make my PC so loud.
I had stutter issues at 40fps, but smooth on 60fps. Native Linux version seemed to have better performance and stability as Proton crashed occasionally, but I had no sound.
Had to use Steam-Play-None or else it the performance was pretty meh (lot of stuttering)
Pretty bad stuttering; Steam-Play-none fixed the issue
Steam achievements do not work when using the native version; booting the game in the Proton version does sync your achievements
The game is set to run with Proton by Valve, but it has a native version that runs better. I enabled it by changing the compatibility layer to Steam Linux Runtime. The problem with the native version is that achievements won't unlock but the game still keeps track of them so you can always disable the compatibility layer (which defaults it Proton), run the game and once you reach the main menu all earned achievements will unlock.
Framerate limited to 60FPS and TDP to 6W. At one point there's a section with a rain effect that tanks performance but it's a quest hub and you don't spend too much time in it.
nw.js uses Chromium underlying and Chrome on Windows uses ANGLE to provide OpenGL ES support. By default the game uses the Direct3D 11 ANGLE backend and, while it isn't possible to use OpenGL due to (I believe) wine and driver restrictions, it's possible to set the ANGLE backend to Direct3D 9.
For that, edit the package.json inside the game folder and add --use-angle=d3d9 at the end of chromium-args.
It seems that micro stuttering is common running the game under Proton, this might help.
I didn't test throughly though.
Unfortunately the native version of the game won't run onLinux properly with Steam Overlay support.
From my own experimentation, nw.js 0.35.5 (based on Chrome 71.0.3578.98) is the last version that runs the Steam Overlay without changes while nw.js 0.36.4 (based on Chrome 72.0.3626.121) is the first version where it doesn't work and I couldn't figure out why.
It should be possible use the nswj_old beta to downgrade to a previous version (apparently based on Chrome 50). However the fix to the controller was only merged in Chrome 99/100, which might mean not having proper controller and Steam Input support.
Your choices for this game are basically:
- Play the native version as-is without Steam overlay integration (no Steam input and no achievements)
- Downgrade the nw.js version by swicthing to the beta branch
nwjs_old, usable Steam overlay but the game controller API is buggy when detecting the Steam Input Controller and you might need to remap keys. - Swicth to Proton but you might have to deal with micro stuttering
For 3, it's possible that swicthing the ANGLE backend from D3D11 (the default) to D3D9 (legacy but porbably faster) could help.
Switched from native to forced proton, controller doesn't work otherwise
Early access customer here, unhappy at having to use the Wine version because developers can't be bothered to fix broken Linux controller support. If you have controller problems (which you will under Linux) then you need to force Proton compatibility, windows controller mapping works fine.
--use-angle=vulkan
Fullscreen would only show the bottom left corner, hid the rest of the game no matter if you move or resize the window
Using proton causes screen tearing issues, and occasionally crashes (once every ~4h roughly), but allows for full screen support and achievement syncing.
Всё отлично работает!
Присутсвует нативная совместимость с linux, отдельного выбора совместимости не требуется. Просто включаешь и играешь!
By default Steam runs the Windows version of the game using Proton, which works, but has horrible microstutter. If you go and force the Proton version to Steam Linux Runtime, it installs the native Linux version instead, which is much smoother.
Native works fine, no Steam overlay though.
Overlay doesn't work, which means Steam Input might not be enabled and you may run into controller issues depending on your controller.
