
Larnu
Published
Lowered FPS to 30, reduced TDP to 8 and GPU to 800Mhz
The default controls are not ideal. I suggest either downloading a community one or creating your own. Other than that, no issues experienced so far.
As at least one other has mentioned, sometimes there were boundary issues. Closing and starting the game seemed to solve this the couple of times it happened.
Opening Movie doesn't play, and pulseaudio settings need changing to fix crackling. After that it plays almost flawlessly.
Significant cracking when I first played the game. Setting e_sync
to off didn't help. I, instead, found this youtube video and copied the settings out. Unfortunately, the site they used isn't available any more, but the video is high enough quality to get the data from. I don't know which specific setting(s) fixed it, so I have no included my settings file. Trial and error may be required if you experience cracking.
Note: I've been playing Windowed. When returning from the PC being locked, the game had a black screen and a there was an error hidden behind it, stating the game couldn't be resized. Clicking the error left it black. I maximised and then restored the window and the game was back.
When on Auto Detect for the key guide (tells you what button to press in tutorials, menus, etc) and using a controller, the game thinks you are always using an Xbox Controller. I was using a PS4 controller, which meant having to change the setting specifically to that in the settings. This means if i were to swap the keyboard, it wouldn't tell me the correct controls (though the keyboard binding are all over the place, so I suggest sticking to controller).
The opening video doesn't play. You can watch it out of the game if you really want to.
Not a "significant" bug, but if playing windowed, the game does appear to treat using the mouse to click outside the window as input when it was the active window (subsequent mouse clicks aren't treated as input). Like wise, selecting the game's windows (with the mouse) is treated as input, so alt
+tab
is recommended. This, however, could well also be a "feature" on Windows too.
Now Borked - Black screen, resizing doesn't fix
Used to start fine, now fails. An error pops up saying "Failed to resize the window size", which used to go away after a maximise and restore. That doesn't work any more. Game is definitely running as you can hear the sound, just no audio. Nothing has changed on my PC apart from updating the graphic drivers. Trying mf-install did nothing, as did trying GE and older versions of Proton. Rebooting also still didn't work.
Initially resolved this as shown in the prior message, however, this caused cracking in other applications. Unfortunately, I can't remember what I did to fix it in the long term.
My previous message says that this became borked. This was actually due to a config file in the game, that had invalid parameters in (no idea how, as I hadn't editted any). The solution was to delete said config file (config.ini
) for the game.
With 300~ hours on Windows, I've really enjoyed ED. As a background game it's great. Carriers are going to make exploration more enticing.
protontricks 359320 dotnet40
The game initially loaded at a lower resolution and in Full screen mode. I changed the game to Borderless first, which made the game area smaller on screen (which made me realise it was at a lower resolution), however, when I changed the game to use my screen's native resolution the window didn't grow in size. You have to change the resolution first, and then switch to borderless.
Note I'm still running Ubuntu 19.10, however, I'm planning to upgrade soon. And will note if upgrading has any impacts.
Worked flawlessly. Any problems I did encounter, Windows users were encountering too at the same time, so weren't Proton related.
No tinkering required
Some audio was lost (such as noises for my weapon and enemy's, but not other player's) after extended play. Not sure this is proton specific though, as a Windows player in the same lobby reported the same issue a little later. Restarting the client fixes.
Not a seamless experience if using multiple monitors, but otherwise flawless.
Regardless of if the game was running Fullscreen, Borderless (or as Hitman calls it "Exlusive") Windowed or windowed, the cursor was bound to the game area. When using multiple screens, this was annoying as you could only interact with other applications by using Alt+Tab, rather than moving the mouse off the screen. Also, if you were playing the game on a screen that wasn't your primary screen, then the game would disappear on Alt+Tab (still running in the background). When you return to it, it would either flick back to your primary monitor or it would be on the prior, but your cursor would be bound to the primary (and interacted with Hitman as if it were on the correct screen).
Trying to install the game yield 0 bytes/0 bytes installed
Copying the files from a Windows install resulted in the game not launching.
Often when launching the game I get a Network Error, however, Googling does imply this may be game related and not due to the fact it's running on Linux. Multiple retries (in short succession) get around this, but less than ideal.
This didn't run for me at all on 19.10. I assume that updates and new drivers fixed this.
Limited to 30FPS
When windowed the mouse was misaligned to where the game thought it was. Full screen did not have this issue
Honestly, the fact that the game doesn't automatically pick up the 1280x800 screen resolution (and defaults to 1280x720) is a poor reason this game doesn't show as fully supported in Steam for the Steam Deck. Changing the resolution is something a PC gamer might/should expect. Sure, put it in the notes for how supported it is, but it runs flawlessly and the store should reflect that.
Works Flawlessly.
When using Esc
in game, and then closing the menu, the mouse is no longer bound to stay within to the game window and so when moving the character around it can exit the game window, if using a multiple monitor set up. Opening and closing the Esc
menu fixes this.
Works flawlessly without tweaking
In a multiple Screen environment, when using Windowed Bordleress, only the right side of the window allowed the mouse to move outside of the game, trying to move out of the left side cause the mouse to hit a barrier. Fortunately, I tend to play on my Left most screen, but noticed it when i had it on the Centre Screen for a bit.
As others have mentioned, the game wouldn't connect to multiplayer when I had a local bridge connection on. I have 3 connection managers on my device, eth0
(base Ethernet), br0
(Bridge for LXD Containers to connect to the domain), lxdbr0
(Bridge for LXD Container not connecting to the domain). I had to disable lxdbr0
, with sudo ifconfig lxdbr0 down
for multiplayer to work.
Seems that the game does not like local bridge networks, but is fine if the bridge is exposed to the wider network/domain. Considering it's unlikely I'm using a local container while playing, not a real problem.
Flawlessly, as in for the expected experience for the game. Multiplayer has significant bugs, however, this is early access. Those bugs are not related to the player on Linux, as I am playing with 3 Windows Users, and anyone that isn't the host will experience some "features" while the developers work on improving the experience. The game does warn you that Multiplayer is far from flawless, so expect it.
This is why I only gave Multiplayer the rating Acceptable, as it can be quite detrimental to the play experience. Regular host restarts of the game (not disconnecting the server and restarting it) every few hours are recommended to keep your friends happy, as the longer the host's game is running, the more "features" begin to happen.
No longer works since Update 5
Played this plenty in Update 4 and prior, almost 200 hours. Always had to use Proton 5.0-10, as that was the only one that worked, but Update 5 just causes the game to fail to start, and actually full on crashes Steam too.
With 5.0-10 the splash screen appears for 30+ seconds, disappears, then about 30 seconds later, Steam will show I can launch the app again, followed a couple of seconds later by Steam crashing. For other versions of Proton, such as 6.3-7 or 6.19-GE-2 you don't get a launch screen. The game fails to launch after a couple of seconds, followed promptly by Steam crashing too.
%command% -nosplash -DisableSeasonalEvents
Sometimes mouse input wasn't detected. Alt tabbing in and out resolved
Sometimes I would get 2+ hours hours of gameplay, others I was lucky to get 5 minutes. Last 2 days, game crashes after a few minutes and is unplayable.
I never had an issue with playing the game in Update 7 and prior; I had well over 300 hours (I didn't play Update 8). 1.0 has been entirely unstable for me unfortunately. Occassionally I can get a couple of hours game play, however, since Sunday the game will more often crash after a few minutes of play.
I can leave the game running on the Main Menu indefinitely, but as soon as I decide to start playing I can end up crashing with no warning. No errors, nothing. I can be in the wilderness, just running along, I can be in a factory, powered or not, the game will just crash.
I've tried (forced) running in vulkan, dx11 and dx12, lowering my graphics, changing proton version (GE, non-GE, older GE, Experimental), nothing stops the crashes.
Performance, unlike some have reported, for me has been fine in for vulkan, dx11 and dx12, and the game doesn't stutter or lag prior to the crash, it just quits instantly. I wish I knew why, as this is a game I thoroughly enjoyed when it was in Early Access, and now it's finally out, I can't.
Incredibly disappointing.
Game would sometimes detect mouse location but not clocks on start. Alt tanning out and back in always resolves.
Late game, FPS could drop in 20FPS or lower at times. Likely due to high volume of items to render.
My prior submission the game was crashing, a lot. Despite the errors being seen it was related to a major known issue with vertical conveyors, which has been since fixed.
Since then, apart from FPS stops in some areas, the game has been fine. I think I've encountered less crashes than Windows players on the same server.
Unlike others, I've had no isses using DX12, and infact have been using since the majority crash bug fix. Considering I'm using an older GPU, this surprised me.
Game is, at least for me, the most stable it's ever been.
Make sure you enable touchscreen controls in the input settings, otherwise you can end up not being able to target with the controller.
I've also had times where I've selected an item to purchase in th Merchant and a different item was purchased. Unsure if this is a game bug or a touchscreen/input related problem.
Sometimes the game "forgets" big text is enabled, normally on the main menu; this makes the fonts quite small and could be difficult for some to read.
As a native game it works fine, with great battery life on default settings. Not knowing that enabling thouchscreen is a "must" prior to playing my first couple of runs resulted in some frustrating game play the first couple of times playing, but once you enable that it's a much better experience.
If the game added a "disable mouse" feature, then that could likely fix a lot of the input issues I have experienced.
Repeated crashes. Unable to play.
Couldn't get into a game. Every time the game got to 100% for loading the game environment it crashed. Once got to select a spawn location, however, before I selected one the game also crashed.
Occassionally crashed at Main Menu as well.
Borked. Doesn't start at all
Pressing play doesn't present anything. Then it goes back to Play. I have tried with Proton 5.0-9 and 5.11-GE-1-MF, same result.
Terminal doesn't even appear to give an error, it appears to load the game, and then just closes it.
mf-install
The game, regardless of the controller type, will always display Xbox controls. Overwriting (make sure you make a back up first) of the platform.steam
and platform.steam.manifest
files in ./SuperNeptuniaRPG_Data/StreamingAssets/
with with platform.ps4asia(.manifest)
or platform.switch(.manifest)
fixing this. This isn't just a Linux issue mind. Oddly, ps4
is actually ps4asia
prompts, as X is back and O is confirm.
This game would not launch at all with the latest version of Proton. I had to force the game to instead use 4.11-13 and then use mf-install to get past the black screen.
The game defaulted the keyboard input. When in this mode it does t accept any input from the controller (SteamDeck). As such it meant that opening movies couldn't be skipped nor the menus used; it made it appear the game was unresponsive. You need to you the touchscreen to change the setting.
If the game defaults to keyboard input, it appears to not work; use the touchscreen to change the settings if this occurs.
Music does not play out of the box
To fix the music I converted all the files in the Music folder (.../steamapps/common/Sweet Transit/Content/Sounds/Music
) to an mp3 file using ffmpeg, such as shown in this answer on Ask Ubuntu, removed the wma files, and then changed the extension of the mp3 files to wma. That appears to "trick" the client enough to play the files. You may (as I did) want to make a backup copy of the Music folder prior to fiddling.
Initially kept stating that C++ needed to be installed, and click "Install" resulted in the game closing. Switching the GE fixed this.
"Ghost inputs" have sometimes been detected, for example, I could be in a menu, and the cursor moves up a couple of menu items.
In Proton 7.0 the game could not be played, a message box asking for a C++ library to be installed would be presented, and then when clicking install the app closed. Launching the game using GE-Proton resolved the issue.
The game is very demanding from a GPU perspective on high settings, which is surprising when it looks pretty similar to Octopath Traveler. Without fiddling you will be lucky to get more than 2 hours battery life on high settings, and won't get a constant 60fps (I was getting a max of 52). Lowering the quality of the graphics, or switching to FSR would be an idea if you want good better battery life.
The game also constantly defaults to showing the keyboard controls on screen, not controller. As soon as you press a button (not use the analogue sticks) this changes for the current dialogue/battle, but it's frustrating that it will random switch back to showing keyboard controls. I don't know if that's a "feature" unique to the Steam Deck, Proton, or just PC players in general; hopefully it's a bug in the game itself. From a developer perspective (as in SE) they could simply make a game option where you can choose a default game input device for on-screen prompts.
Graphical problems make the game unplayable.
The right hand side and bottom of the screen constantly flickered older frames, or (on older versions of Proton) flicked black. I didn't progress far in to the game as it made the game unplayable.
Input felt laggy, or sometimes required 2 clicks even though the first was obviously detected (as it would make a noise to denote the selection was made).
Tried running in Proton 5.0, 4.11 and 3.16. All had graphical problems in the same region, though the behaviour differed.
Changed basically everything.
30FPS
The official layout does not work outside of the main menu. Had to createy own layout emulating a keyboard.
That it appears that the Steam release has an official control layout and it doesn't work was frustrating. I lost a lot of time trying to get it to work. I ended up creating my own layout and that worked great; it's like the game doesn't support controller properly.
If you are playing, my community layout is "A Quintessential layout for study". Hope it gives you a better experience.
After the initial experience, when I went to play again I was unable to play the game; only menus responded. I tried changing controller configuration again, switching back to the one from the Developer, turning off Steam Input API, nothing. I could play the game once and since then it's borked.
I'll reach out to the Developer (if I can) and see if they respond, as I'm not the first and I doubt the last who will have this issue. If I post a 3rd review, it'll at least be good news... Clearly I spoke too soon after being excited to get the game working, and I did get some enjoyment out of it before it was booked again; that only rubbed more salt in the wound.
Left Trackpad menu, Left Joystick Menu, bumper changes, select button, left trigger. Published as "Bartending at your fingertips"
FPS limited to 30. TDP limited to 7 Watts.
My only complaint is that the use of the mouse for the jukebox is a little clunky, and you also have to use the mouse to navigate some menus.