
404Fox
Published
Perfect OOB. Was able to drag and resize the window with no hiccups whatsoever. Playing solo has no issues.
movies don't work, but that's it
freezes for a second very occasionally while walking around the world
"Story so far" won't play. Simply returns to menu. There is likely another movie scene that was skipped when starting the game as well. Otherwise, it is perfectly playable OOB.
Use atfix: https://github.com/doitsujin/atelier-sync-fix/ Just drop next to the game's exe Thanks to the person who brought this up and the person who made it. I hope this can be integrated into Proton so it runs well out of the box. For some reason, this works without needing to add it to WINEDLLOVERRIDES as an environment variable. Even with this fix, some actions like jumping cause GPU utilization to drop temporarily along with the framerate.
Extremely low framerate without atfix.
The default setting for shadows is high, but it seems that this only affects shadow resolution. Setting this to standard/low does 40fps easily with all other settings at their maximum values, and has very little visual quality loss.
The game becomes unresponsive on loading screens sometimes, no screen update. There is no apparent logical cause, you can load and pick up where you left off and it'll work. The game auto-saves very often so it's livable but still quite inconvenient. This is with atfix, did go far enough to test without using it.
Low utilization of 7900XT
Does not fully utilize my hardware. Runs below 30FPS and has GPU and CPU usage below 40%.
The RDNA3 driver is still pretty new, but this game specifically is having this behavior. It also crashes when supplied with DXR parameters.
Sometimes plays
Sometimes does not launch. Sometimes launches on the first try, often it takes a few tries, and worst case it takes several tries. Same with on the Steam Deck.
Lowered settings
In a previous report I made, the game would sometimes hang and only sometimes launch when you press play. As of the past week or so, it's been reliably starting every time. This is the same between PC and Steam Deck OLED.
You might want to adjust the gyro settings, based on feel
In my first play session, it crashed my PC and I had to force shutoff. It has since then crashed itself twice within my nearly 3 hours of total game time so far (not full PC crash).
After the game had crashed my computer, it refused to launch and always showed a "Connection Error - Steam Not Found" and then closed. The game did not start again until I reinstalled it, verifying files and deleting various folders then verifying did not solve the issue.
While full PC crashes can probably be prevented by changing the CPU LLC and perhaps being at a load while running the game, ie. having other applications open in the background, the game on its own can still crash due to bugs anyways. Granted the latter may not necessarily be a proton/linux issue. For reference, I'm using Plasma 6 with wayland session and had no other issues.
Save often. Needs more testing for potential freeze cases.
Opening movie does not play (black screen) but can be skipped with the controls.
Using Ram's AOE skills on Waverunner Coast map might cause the game to freeze. One case was using EFB skill in HDD form which was reproduced 3 times. Seems to be specific to the closed-off version of the map, not the exploration version. Maybe it's a game bug?
Cannot get past black screen that follows the copyright warning when using Proton 6.3-8, 5.13-6 Otherwise, is as reported for 5.0-10.
Playable
Appears to lag slightly sometimes. 60FPS is reported from steam's FPS counter.
Will not exit properly.
Proton 6.3-8
Is a hassle to get started because of Origin, but after that runs reliably
As others have noted, I had to rename OpenAL32 to get audio to work for ME1.
Origin may not reliably start or install. Had to restart twice until it was working perfectly every time. The game (after launching it from the ME:LE launcher) will start in the background as well, and has to be brought into focus.
Borderless mode, and other graphical options must be configured per-game.
Movie playback is broken, but it otherwise runs
6.3-10 & 5.13-6: black screen, does nothing
5.0-10: Black screen on start, will not play opening movie but it can be skipped. Note that the initial install will have set keyboard/mouse controls by default, thus you cannot use the gamepad to skip the black screen until you change that setting. When starting a new game, after skipping the first scene that is just a black scene, the opening for zero dimension can be heard although the screen is simply black. It cannot be skipped but also seems to loop infinitely. You might be in the menu after the unskippable opening? Anyways, its impossible to reasonably start a new game. I loaded my save that was copied in from steam cloud. Did not experience any issues in regular gameplay. CGs and sound play perfectly from the gallery. Movies do not play whatsoever.
Does not work with any version of Proton OOB, from 4.11 to Experimental, and GE 7-31.
Black screen or "Application has crashed"
Crashes with amdvlk consistently on starting, triggers a GPU reset Uninstalling it worked for me
No longer launches after recent update
Got to play for a bit, got a 24-hour denuvo ban, played again, and now the update has broken the game entirely
Downloaded dstorage.dll and dstoragecore.dll versions 1.2.2, replaced in game files. Without this, the loading time is 5 minutes long and has texture issues. When you download the nupkg, you can extract that as a zip and find the dlls in build/native/x64
Works
Controller did not work at the first launch of the game. While playing about 20 min in I tried it again and it started working. After restarting the game it worked from the main menu.
Introduction movie plays with no issues. Windowed/Windowed Borderless works with no issues. The tutorial tells you to use J and I for the two basic attacks. Mouse left/right buttons are also bound and are probably the preferred method over that even though it isn't mentioned.
Laggy in certain areas for no apparent reason. Average framerates tend to vary wildly from 20s up to 90 although frametimes are very consistent and there is no stuttering. This is notable while exploring tartarus or simply being in the protagonist's room. Reducing the graphics settings only alleviates this slightly. It is also necessary to disable reflections to get playable framerates in some areas, they are on by default.
No problems.
Escaping and getting into the window was janky when in Fullscreen mode. Switched to FS windowed and it works no problem.
Getting 80-90 FPS in a battle area, 170+ FPS best case with nobody around. Not entirely sure, but this might be a bit less than when on Win10 LTSB. All settings on the highest option.
%command% --disable-gpu
It's difficult to play this game well on gamepad controls. I'd suggest flickstick or connecting an external KB/mouse.
This game's UI does not scale well up nor down.
Lowering graphics settings is necessary for a high framerate, but this is a pretty old game.
Aside from requiring configuration of the launch command, the OOB experience is poor due to the halfway-there controller input support, and needs configuration to make playing on the deck competitive with M/KB users, and to navigate the menus.
40hz will save you 1-3W of power draw depending on the scene. TDP and GPU clock controls are mostly useless in this case, the game always only draws as much as it needs to reach the frame target. Pushing these values will only cause framerate loss or frametime stuttering. (below 7W/700Mhz)
With the default settings (60hz, 60fps limit), you get 3-4hrs and that can be improved by using the 40hz/40fps limiter.
The initial menu has small text. The rest of the game is very well scaled to the 7" display.
Easily does 60fps stable, or 40fps stable with 40hz setting. No issues with suspend, although I always do it from pause menu or during a dialogue. Will only do preset resolution settings, and 1280x720 is the closest.
If you can tolerate constant small artifacts then its playable aside from any multiplayer functionality.
Entities seem to visually appear/disappear randomly as the camera moves, and is fairly noticable. It is tolerable with 5.0, but higher Proton versions have this to a severe degree such that many large set pieces will be flicker in/out but are still physically present. I tested Experimental, 5.6-GE, 7.0, 5.13, GE-Proton7-49, Proton-6.21-GE which all exhibit the issue to the point it may be unplayable. I tested 1080p, 1440p, 4K, and default, lowest, and highest graphics settings with no changes.
EAC
/home/username/fix.sh %command%
Add input labels, Alt+n controls
Without using a workaround, the game will always crash when trying to start a mission or cutscene.
Currently requires the workaround described by https://github.com/ValveSoftware/Proton/issues/7521#issuecomment-2307604405 Remember that the script must be set as executable and to use {} instead of ()
Works without issue
Can drop to 40-50FPS when many cars are on screen.