monsoon
Published
-anticheat_settings=SettingsDX12.json
Frequent crashes starting a day ago. Crashes every 2-3 minutes. After setting the -anticheat_settings=SettingsDX12.json launch option, the game appears more stable; only one crash in 4 hours.
-anticheat_settings=SettingsDX12.json switches Apex to use the DX12 beta. I don't know why that would help with the crashes, but it seems to work for me.
Support for Linux has been removed.
Linux users will get an error "Failed anti-cheat backend check."
See: https://answers.ea.com/t5/News-Game-Updates/Dev-Team-Update-Linux-amp-Anti-Cheat/td-p/14217740
Excerpt from the post:
We’re sharing today that Linux (and Steam Deck using Linux) will no longer be able to access Apex Legends.
In our efforts to combat cheating in Apex, we've identified Linux OS as being a path for a variety of impactful exploits and cheats. As a result, we've decided to block Linux OS access to the game. While this will impact a small number of Apex players, we believe the decision will meaningfully reduce instances of cheating in our game.
Played with a keyboard and one controller. Worked without issues. Haven't tried connecting a third or fourth controller.
Worked well, no tinkering required.
Works without issues.
No issues to report. Game works perfectly without tinkering. Installed CKAN using the AUR to manage mods. With a modest mod list (less than 10 mods), startup load time takes about 5 minutes, and subsequent loads are typically less than 10 seconds, but the increased load times from mods are not specific to Linux.
Works perfectly out of the box.
Played 5 hours of the retail version, not the demo. No issues to report. Performance is fine; I get a constant 144fps at 1080p.
Ran perfectly, with no tinkering required.
Frequent crashes
Game locked to 90fps, despite 120fps being selected in the settings. 90fps would normally be fine for a game like this; but there's very noticeable frame stutter.
Frequent and random crashes. Sometimes it happens during gameplay. Sometimes it'll crash on the initial loading screen. The crashes freeze my entire system, requiring a hard reset. systemd logs show the following whenever it crashes:
kwin_wayland[760]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kwin_wayland[760]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
kwin_wayland[760]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
kwin_wayland[760]: kwin_scene_opengl: Can't enable invalid framebuffer object!
During some sections, framerate was lower than should be expected from my system (Ryzen 5 3600, GTX 1070). Dropped to about 50. Tends to last for only a few seconds. Overall still playable.
In fullscreen or borderless windowed mode, the game stutters heavily in cutscenes and menus.
This can be fixed by running the game in windowed mode. Use your window manager to fullscreen the game (F11 if using KDE Plasma).
Heavy stutters when running in fullscreen and borderless windowed mode.
Apart from the issues with fullscreen mode, which can easily be fixed, the game is very playable.
I play vanilla, no mods. I also played using Proton 8.0-4, which performs better than the native version.
The game has a native build, which works decently well. However, screen panning using the native build has some performance issues in certain cases. With a colonist's Bio tab open, panning the screen using middle-mouse drag will cause the framerate to drastically drop. If I wiggle my mouse around, panning repeatedly, the framerate can drop to <10 FPS. During normal gameplay, this issue typically manifests as a large and very noticeable stutter. I'm using a Ryzen 5 3600 at the time of review. I imagine those with better CPUs might experience this panning issue to a lesser degree.
The panning performance issue does not happen using Proton. I'd recommend using Proton despite the game having a native build.
Game works without tinkering. Online co-op works without issues.
Game will not start. Crashes silently back to library.
Tried Proton Experimental, 8.0-5, and 7.0-6.
No issues when run in DirectX 8 mode
Game only launches when launched in DirectX 8 mode. The game's launcher on Steam allows you to select this, so no tinkering required. No issues otherwise.
Game initially crashes silently to desktop, whether normal or DX8 mode is selected in the launch options. The configuration tool only renders a black screen as well. I suspect it has something to do with Wayland. I eventually got the game to start successfully through some manual configuration tweaks.
I eventually got the game to launch by:
- Launch the configuration tool in DX8 mode.
- The tool will render only a black screen.
- Hit enter. This will launch the game. Presumably because the "start game" button in the tool is focused.
Somehow, when the game started successfully when launched via the configuration tool. Subsequently, the game can be started by selecting "Play DirectX8 version" option.
However, the game starts in 640x480 resolution. The resolution can only be set via the configuration tool (which doesn't work), and can't be changed in-game. I manually set the resolution by editing the config file. The config file can be found at:
steamapps/compatdata/251290/pfx/drive_c/users/steamuser/Saved Games/FALCOM/ED_SORA2/ed6_win2.ini
Set the following variables to change the resolution:
[Video]
Width=1920
Height=1080
Since the configuration tool doesn't render, any configuration changes need to be changed using this file instead.
Have played for about 5 hours so far. No gameplay issues. Video cutscenes work on my system. Controller inputs work.
Game could not launch in fullscreen. In the launcher, setting the game to launch in windowed mode worked.
Game was capped at 30fps on the native version. I wasn't able to increase the cap.
The game related issues I had were:
- Game could not launch in fullscreen.
- Game was capped to 30fps. Proton version might work better, but I didn't try it.
But the biggest issue I had was that the game somehow messed up the config for my second monitor. My second monitor went black and stopped displaying anything. Restarting didn't help. xrandr showed that the display was still detected, but perhaps it wasn't receiving a signal. I managed to get it working again with:
xrandr --output DisplayPort-1 --off
xrandr --output DisplayPort-1 --auto
This brought the display back, configured in mirror mode. Then I went to the KDE Plasma's display configuration and repositioned the second display. Somehow the display was set to overlay exactly over my first one, which normally isn't possible.
Anyway, as you might expect, I didn't bother trying to launch the game again. I don't recommend this game. If you go ahead, I would recommend to launch the game using Proton first instead of the native version; I presume running the windows build will be less likely to mess up your linux system.
Game crashed once. Happened during local multiplayer when one player, using a controller, joined the game. Joining and leaving the game normally works; it only crashed this one time in 90 minutes of play. Not a significant issue.
Works out of the box
No issues to report. During the first few days there was a bug where the game selects the first audio device, rather than the one configured as the system default. A patch has fixed this issue, and the system default audio device is selected now.
No issues apart from a minor audio bug
Game selects the first audio device, which may not necessarily be the system default audio device. I have to change the application's selected audio device on each launch.
Adding another report to correct my previous report. I had mistakenly thought that the audio bug was fixed. It's not, the audio issue is still present.
