Installation on Steam Deck

[copyrite]

I'm investigating the feasibility of moving from Proton powered AML to LXCOMM on Steam Deck, and as I mostly have Windows experience, I'm going to need some hand-holding with this.

I'm following the Startup guide even though I'm using Steam. I extracted lxcomm-v0.4.0-Linux-GNU-x86_64.tar.gz into /home/deck/.local/share/lxcomm/ and am finding that lxcomm there starts something that looks like a mod manager.

I provided LXCOMM with my Steam Web API key. I created it in 2022, so if they have a tendency to expire it's possible this one has already done so. But on surface level, so far so good.

I followed the instructions to obtain steamcmd, with some variations that I'm unsure of. First of all, I did create a user called steam, but doing so didn't create a folder called /home/steam. I switched back to the default called deck, which I believe has root privileges, and was able to obtain the steamcmd Git and build it. (It should be noted that using pacman is not straightforward on Steam Deck, e.g. there's a read-only filesystem that must be circumvented with sudo steamos-readonly disable).

On the Main tab of LXCOMM, I entered the game and local directories. These were, in my case:

• /home/deck/.local/share/Steam/steamapps/common/XCOM 2/XCom2-WarOfTheChosen/
• /home/deck/.local/share/feral-interactive/XCOM 2 WotC/VFS/Local/my games/XCOM2 War of the Chosen/XComGame
  Clicking Apply caused the following dialog to appear:

Error Applying Config

Os {
  code: 2,
  kind: NotFound,
  message: "No such file or directory",
}

Could it be that one of those directories are not quite what LXCOMM expects? If so, maybe for better UX their tooltips could state the name of the directory these paths usually end with.

[PhantomShift]

Oh dear, I completely missed this issue because it was opened in the middle of finals season for me, I am very sorry for the lack of response on this. If this is something you're still interested in I'll definitely invest some time over the weekend looking over this, otherwise I'll be investigating whenever I have free time.

Based on a cursory glance and my spotty memory, your path for the local directory seems a bit off, as it doesn't look like it points inside of an actual wine prefix, but that might be my unfamiliarity with paths used on the Steam Deck. I would imagine it would look something roughly like /home/deck/.local/share/Steam/SteamApps/compatdata/268500/pfx/drive_c/users/steamuser/Documents/<rest of path>. Another important distinction since you did mention you're mostly familiar with Windows is that paths/filenames are case sensitive so that may be another thing causing issues.

[copyrite]

Hey, thanks for responding! I'm still very much interested in getting this up and running, but since I'm now playing something else while I wait for that XCOM urge to return, there's no rush. In fact, I should check again what state my install is in because I was also failing to set up another program (BizHawk) at the time, and that one had suddenly fixed itself presumably due to SteamOS's update.

[PhantomShift]

I suspect that I may have fixed the issue with f6e06b0 (found it weird that you didn't run into any of the actually documented errors!) but I will likely hold off on making a new release until I get around to refreshing dependencies (especially iced) to updated versions. If building and testing on the deck is cumbersome (i.e. installing rust build tools) then you can test with this build provided here whenever you have the time: lxcomm-bugfix-0.4.1_debug.tar.gz

[copyrite]

I got around to doing something about this. First, it's still giving me the same

Error Applying Config

Os {
  code: 2,
  kind: NotFound,
  message: "No such file or directory",
}

as earlier.

Changing the local directory had no effect on the above error appearing. I'd actually be surprised if the path containing compatdata was the correct one, since I thought that's where Proton-driven stuff goes? I'm trying to run this Linux-natively.

Will get back to you once I've tried the bugfix version.

[PhantomShift]

Changing the local directory had no effect on the above error appearing. I'd actually be surprised if the path containing compatdata was the correct one, since I thought that's where Proton-driven stuff goes? I'm trying to run this Linux-natively.

Sorry, I completely misread the situation here. I was under the impression you'd be running through proton since I usually run all games via proton instead of using native Linux builds. I do not fully know the extent of how the Linux build of XCOM2 differs from the Windows one, so there could be issues even with the bugfix version I posted earlier. Thanks for bringing this stuff to my attention!

[PhantomShift]

I got around to installing the Linux native version since one of my family members owns the game on Steam and managed to get mods working after some fiddling. There are a couple of things LXCOMM will need to handle when enabling mods for the Linux native version which I will document for myself here:

• Game files that need to be modified are specifically located in XCOM 2/shared/data/xcomgame, and the relevant mods folder and defaultmodoptions.ini need to be lowercase. Notably, despite XCOM 2/shared/data/xcom2-warofthechosen/xcomgame existing, it doesn't actually seem to be used for mod management, which may need to be noted upon in a guide.
• To not require manually enabling all mods through Feral's mod manager, the profile's Config/XComModOptions.ini needs to also be updated to have all mods marked with ActiveMods=[ModName]

[PhantomShift]

Just released version 0.4.2 (although relevant changes are in 0.4.1) which should hopefully address your use case, along with an update to the startup guide (https://github.com/PhantomShift/lxcomm/wiki/Startup-Guide#native-linux-steam-setup) but I'll be keeping the issue open in case you need troubleshooting help or run into additional problems with getting mods running.