Unknown
- 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.
While it takes a few steps to get the Linux-Native version working correctly, afterwards there are zero issues.
/path/to/linux/binary # %command%
Game is Modded using CCLoader v2.22.1
Fullscreening has incorrect coordinates.
Running the game through Steam with mods enabled causes some weird behavior. Instead use the above launch option to launch the game directly through terminal and bypass steam hooks.
If modded, It's worth mentioning if the game crashes on launch, try removing the chromium-args from ./CrossCode/package.json. This file is added by CCLoader
Fullscreening to any resolution that isnt 16:9 offsets the cursor and sometimes prevents the cursor from being positioned over portions of the screen.
Originally running the vanilla game using Proton (any version), the game experiences severe microstuttering after about an hour of play. The native version does not have this issue.
I've heard there are issues with controllers not working out of the box with the Linux-Native version. I can't confirm since I've never tried.
Runs great
The game suffers from screen tearing due to not having V-sync, at least the version I'm running which is a beta doesn't.
Occasional micro stutters.
xrandr --output HDMI-0 --off && %command% --use-angle=vulkan && sh /path/to/.screenlayout/script
As others note, Nvidia GPUs suffer from an odd bug getting the game to properly fullscreen. Fixed by adding --use-angle=vulkan as a launch option.
I have two monitors with varying refresh rates. The game runs perfect (and I mean perfect!) on it's native port as long as all of your monitors follow the same refresh rate. It has fair performance issues (small stutters constantly being the main one) while running two monitors.
I skirt around this by setting my secondary display off for X, and have it run a small script generated by arandr to enable it again properly.
The game warns on first launch that having a high sample rate can cause stability issues, however have never had any issues on the Linux port with that.
While not a report for Proton version, I had tried using it a few times and while it fixes some stutters from dual displays it had a tendency to randomly hard crash after some time. This is likely related to dual displays or a high sample rate being used by my DAC.
Läuft zu 99,99% perfekt
In manchen Dialogen hat das Spiel im Vollbild die Fensterleiste angezeigt und sich gestreckt
Used GE-Proton7-43. No problems.
