
DanZinagri
Published
Controller only worked after disabling steam input. I think the steam input was crashing because anytime i would try to get into the controller settings menu via the overlay it would try and fail to open the window for it. Haven't seen this behavior in other bandai titles so this was new.
Beyond the iniitial controller issues seems perfectly functional.
It was a bit wonky swapping from fullscreen to borderless. It kinda hung for awhile and then eventually started working again, seemingly didn't swap off. Alt-tabbing is fine so i guess its fine?
Steam overlay seemingly wasn't working?
Overall seems to work out of box
At least for me and my distro currently the linux native version causes significant issues.
Fullscreen mode seemed to cause signigicant issues; this is fine on the steam deck as applications are expected to take full control; but for a multi-monitor setup desktop its somewhat bad.
Consistently crashed plamsa KDE and the Konsole leaving me to forcibly restart my PC. It also seemed to start to consume a silly amount of ram as it went on which spiraled into issues with KDE. It ran remarkibly better on proton than on this, which suggests to me this is probably more optimized on the steam deck instead of linux in general.
I was able to regain control of the Konsole if i closed it quickly, and could forcibly reboot the game. But after playing a multiplayer session for 2+ hours exiting left me unable to do much with the taskbar, run menu, or even konsole, so i was forced to simply forcibly power cycle the PC.
Multiplayer played as normal, and all issues were unrelated to this, beyond the time-comittment of being in a multiplayer game.
I think the issue was related to how it handled fullscreen as it seemed to want to take full control of the desktop which in itself would've probably been fine on a single monitor setup, but instead it seemed to fight quite a bit with the desktop manager.
It seems my previous issues have been resolved and i can run it native instead of on proton without issues.
Had to drop some settings from maximum to High as the shaders were taking forever to install and it was stuttering fairly badly. Swapping to slightly below maximum seemed to work better. Otherwise seemed to generally work fine.
PROTON_ENABLE_NVAPI=1 SteamGameId=582660 gamemoderun %command%
I have the standalone account so i needed to use the listed settings. Passing the graphics card seem to help a bit; but GE-Proton8-30 seems to include the same fixes the bleeding edge experimental has. Using experimental i froze on the loading screen; GE worked, but i also added the NVAPI piece.
As mentioned in previous ones the steamID helps trick it into thinking its the steam version so all the fixes can be applied; no idea if needed for GE; but as i'm launching it through steam as a non-steam game i thought i'd add it anyways as previously suggested.
For anyone who is wondering, I did run the installer via lutris before adding it to steam and using it as if it was the same.
Main menu doesn't seem to display server latency anymore and suggests server is down all the time.
Runs fine without any additonal issues beyond basic bugs the game already has.
Main menu took an odd amount of time to load.
Was running it on GE-Proton7-55 but latest update caused the game to launch as a completely black screen. Changing proton versions to 8-3 fixed it, and i noticed a new unity splash logo leading me to believe there was a unity version change that lead to the proton version issue.
Game seems to have a significant issue with modding on linux native.
Workshop mods didn't seem to work on initial tries espeically with any graphical replacers and they would be significantly glitched. So i tried using the nexus; this fixed the base problem but the mod menu only shows a single mod with no title; and i couldn't select individual. Swapping to proton immediately fixed the mod menu so my only conclusion is proton is required for modding. It probably would fix the workshop stuff also but i havne't tested this yet.
WINEDLLOVERRIDES="xaudio2_7=b" %command%
If you run it without the startup command the game won't make it past the opening cutscene as their is some compatability issue with the audio of this game. Using that launch option will fix that, but then the game has the problem in that you'll have no music or sound effects, ambient background sounds and voices are there, but nothing else seems functional.
I would see a weird freeze-frame of the opening cutscene sometimes between loading screens. This wasn't that bad, but was a sign something wasn't right at least.
I tried the various fixes mentioned in here, but it seems like those are unrelated to this issue.
Attempting to run it in Proton7 causes it to crash before the opening cutscene. Proton 8 will make it to the opening cutscene but will have no audio, then crash trying to load the main menu. Experimental will get to the opening cutscene with audio, but will crash trying to load the main menu. Using the launch settings will get you a opening cutscene with audio; but past this point you'll have spotty audio. The actual game seemed playable, but the audio issue bugged me too much.
Game would get oddly hung-up swapping from dedicated fullscreen to borderless-windowed. Eventually the timer would expire and it would revert to previous setting. Putting it in windowed mode first then swapping to borderless-windowed fixed this.
The information as to how to get this to run seems a little sketchy so let me describe what i found. It seems EAC with the last update broke proton and only 7.0.6 works now. GE versions and other proton version all fail to launch. Funny enough if you try to play with the seamless multiplayer mod the game runs fine without problems on just about any proton version because that version does not setup EAC.
As others have mentiond, delete the 1245620 folder in the compdata folder (Steam/steamapps/compdata) if swapping proton versions still does not work as this will force it to re-run its first-time setup for EAC.
IMPORTANT The game seemingly will run on GE proton AFTER you've successfully launched it once on the 7.0.6 version, as long as you don't delete that 1245620 again; i can only assume something fails to properly setup/configure for EAC on other versions.
I had a small oddity in which my usual goto of GE-Proton7-55 didn't work. Tried GE-Proton8-1 and it would launch but i got a green screen where it wouldn't play the starting video. Then i tried Proton 8.0-2 base and it worked. Suddenly GE-Proton8-1 worked also after one successful launch.
Now i did then uninstall/reinstall GE-Proton7-55, rebooted steam, and suddenly it worked. So, Wine/Proton voodoo i guess. But seems like this isn't that picky on version.
Overall seems to run fine.
Run this on just regular Proton 8-3; i had run this on GE-Proton8-11 and i experienced some fairly drastic slowdown on saving. Now its possible that it was just my first time running it caused problems; but its not entirely clear. The game still has a slight hang on saving, but switching to regular from GE reduced it from a few seconds to less than a second.
Running without any real issue. Performance isn't 100% from what i remember from my install, but 99.9% is still pretty good. I saw mentions of crashing doing teleports, and i did 2 teleports within the school and outdoors, and it seems fine for the most part, so maybe proton 8 helped address this, but I don't know as i didn't try between then.
DXVK_ASYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr gamemoderun %command%
After some recent updates the game has a chance of just launching and saying you're out of video memory; i have a 3090 and have launched it before so i know this isn't the case. It seems to be some weird issue in how its compiling the shaders.
The most consistent launch i could get was with 8.0-3. Experimental launched once but after that had issues, and GE was the same. With the launch options i was able to get it to launch twice in a row.
The best luck i've had was deleting the 990080 in the SteamLibrary/steamapp/compatdata and letting it do its 1st-time setup again; otherwise seems like a bit of a roll of the dice if it'll launch currently.
Once it runs its perfectly fine, but its getting over that intial hurdle of actually launching it.
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command%
Thought i'd throw an updated report in here as the last time i tried was on a unbuntu-based distro and many proton-versions ago.
As people mentioned setting the max_map_count helps; i had done this already sudo sh -c "echo 1000000 > /proc/sys/vm/max_map_count"
This is something that is generally suggested for proton gaming, its just not really required until you get to games like this.
Previously i had issues with it giving me out of memory errors which apparently were a combination of nvidia needing to update their drivers and proton needing a few more iterations. I added the NVAPI peice so i could benefit from DLSS and at least at 1440p 144fps things seemed mostly stable; though i won't say it was without a few dips in a couple spots on FPS. So at least for now things seem to be functional.
Overall seems fine; game set me to max settings by default. I did have a few hiccups but it seemingly smoothed out after a bit so i'm going to chalk that up to shader shennanigans.
After launching this about 3 times, the native version just started locking up on launch. Even worse it caused my whole computer to hang for a moment after turning it off, and one attempt completely crashed my steam. Its very odd considering i had played it without issue prior, but suddenly it wouldn't load any more, so i swapped it to proton and it worked fine again.
Newest update breaks all linux/proton compatability it seems.
at lowest settings i maxxed out at 10 fps, and it felt like i was playing in slow motion. maybe on a desktop but not the steam deck
text was default a little bad and UI elements weren't great
game defaulted to upscaling mode which causes everything to appear black, though UI elemnts still show through. disabling upscaling mode allowed things to be viewed.
game is very CPU intensive with some alright graphical load a well, this basically means steam deck's APU is gonna melt trying to do anything with this. i don't think there's anything to be done, but honestly seems promising that it'll probably work on desktop (at least in arch environments)
Not surprised it works. Craftopia even after the update worked and this is likely running a similar engine. Honestly shocked their dedicated server page even has linux instructions for steamCMD so they're probably halfway aware of linux support even if it is proton.
I saw a little bit of slowness a very minor points at the start but cleared up almost immediately so i'm going to chalk that up to shader stuff as it was fully smooth from there.
Proto
Generally fullscreen or borderless mode (because the game doesn't have a real borderless mode) causes the game to minimize. This unfortunately causes the game to become unreponsive. Putting it into exclusive mode seems to allow for a singe click outside of the window, but further will cause the previous issue. Putting the game into windowed mode is seemingly the best option to avoid this, even if its temporary.
Modding can work but i did need to jump through a few hoops to get the unity mod manager to behave as you need to point it to the correct directory.
Setting up the modfinder tool isn't too bad as long as you setup protontricks with .net; and it makes automated setup and limited wine/mono/prontontricks utilization and messing around with zip files easier.
Steam overlay crashes the game; so better just disable that.
I had a weird problem where it stopped building vulkan shaders at about 49% on the first launch. I gave up hit skip and tried to play anyways. Game didn't make it very far. Stopped the game, tried again, it build the shaders fine that time, and it ran without much issue.
Able to run it on ULTRA with the cel shading stuff on, and the game overall seems to be solid. Just be careful if you accept its download for old PSO2 data it'll launch the steam overlay which kills the game. You can download this data via the DLC section (free) via the store page, and just disable the overlay so that can't happen again.
Random sound effects, mostly on attacks or character grunts when doing actions are gone.
I wasn't able to get this to run on anything except GE-Proton8-4. Maybe its one of those anti-cheat issues where you need to effectively nuke/reinstall the comptatdata folder for the game every time you swap it.
Originally the controller didn't work, but seemingly it works now. But i wanted to update this primarily to mention the sound issues. Very minor and otherwise everything else works fine, but its enough to mention at least.
Game launched to a resolution that was nearly impossible to see, it gives a checkbox to make it fullscreen at the top, check that and it'll resize something appropraite to your screen, past that works 100% fine.
After Unity/Die of Death splash logo CPU goes to 100% and title screen never loads.
Unable to run, unfortunately no information seemingly available for this issue.
Likely will need launch options to work correctly as it seems to launch in windowed mode by default with no way to adjust ingame
had a few jitters and slowness.
Wasn't working before, but after a new set of drivers/configs dropped for NVIDIA it seems to be working now.
It seems 8-1 fixes the need for the launch options and allows the game to work; didn't try with non-GE, but i'd hazard a guess that probably works.
I did see mild slowdown, but i experienced this on GE-7-55 also. So it could just be the game, but its still very playable, as thankfully none of that slowness never happened on bosses.
Game lagged a bit, but I wonder if thats not more a shader chaching issue as the longer i played the less bad it got. though admittedly I did eventually turn down the view distance and shadows from ultra to high just to ease it a little.
Friends playing on windows crashed twice, and the second time i had to exit out to the main menu and restart hosting for them to rejoin. No idea if this was something on my end or just their games crashing independantly caused this.
Overall seems fine; as a note it will prompt you to install something (i think it was .net) on the first run as a dependancy to run, but that went without issue for me.
While it supposedly has a linux build didn't try it (though i see some have issues running it). Proton 8 seemingly works fine with no notable issues.
Fullscreen didn't work in the menu, but manually resizing the window worked fine.
Attempted to launch without forcing compatability, application wouldn't launch. So i swapped it to GE-Proton8-3 and it worked.
Taking it out of fullscreen mode didn't really do anything and just remained in fullscreen mode.
I have to assume this game has a non-proton native version. Because without forcing comptability, the game will launch. But oddly enough it seems to pull some weird older save, as its not my most recent save data. Swapping to proton forces it to re-download so i assume its downloading the windows-components.
The non-proton version crashes when I attempt to interact with the menu in any real way as well. Proton Experimental and GE-Proton8-8 seem to work fine though.