Glorious Alpha Two Testers!

Phase I of Alpha Two testing will occur on weekends. Each weekend is scheduled to start on Fridays at 10 AM PT and end on Sundays at 10 PM PT. Find out more here.

Check out Alpha Two Announcements here to see the latest Alpha Two news and update notes.

Our quickest Alpha Two updates are in Discord. Testers with Alpha Two access can chat in Alpha Two channels by connecting your Discord and Intrepid accounts here.

Linux Tips, Tweaks and Troubleshooting Thread

1235»

Comments

  • equivocalequivocal Member, Alpha Two
    Artusad wrote: »
    carmstrong wrote: »
    Well I've been goofing with this for hours. I've triple-checked all of the instructions and confirmed I followed them. However, when I go to launch the game via steam I get a launch error from Easy anti-cheat

    Launch Error Settings.json not found.

    running linux mint 21.3

    (Maybe someone answered it already but I'll post a quick solution here)

    I had the same issue because of Steam flatpack version. The flatpack version of steam creates weird shortcuts to the AOCClient.exe like "run/123412341234/AOCClient.exe" and might have other issues too.

    You should try the steam version via terminal (sudo apt install steam). This version correctly sets the paths to the AOCClient.exe and it works for me (Linux Mint 21.3 Cinnamon).

    You might need to start the game twice (when starting it the first time), because of an error/crash, but after that it should work. Something else I encountered: When the game crashes it also requires to be started twice to become playable again (a little annoying but better then nothing).

    ___

    Also thanks to the creators of this thread! The guide was nearly on point! <3

    The weird paths is expected behavior of flatpak apps that don't have explicit permission to a location.

    You can stop the weird shortcut paths by using flatseal to give flatpak Steam access to the bottle but the Steam launch option being posted here won't work in flatpak because of the sandbox.

    It can work in flatpak but is more jank because you need another way to pass the port into the sandbox.

  • Alpha_BarrierAlpha_Barrier Member, Alpha Two
    WildBunnie wrote: »
    Alpha_Barrier wrote: »
    Well, the old "custom" environment stopped loading the launcher at all, so I deleted and setup a new one, this time looked promising, but now Cloudflare cannot verify my connection?!? Not sure what to do with that.

    p0o2b0yzcwi1.png

    Did you end up finding a way to fix this problem with cloudflare? I followed the instructions and ended up with this same problem.

    I just built a new Bottle from scratch and it worked, not sure what caused the issue.
  • MajinBlayzeMajinBlayze Member, Alpha Two
    If you're running both Steam and Bottles via flatpak you need to do a couple of things:
    1. Configure your bottle to install somewhere not in ~/.var Flatpaks can't look at other flatpak's files. I used ~/Games/Bottles/Ashes-of-Creation (make sure both have access via flatseal or KDE settings)
    2. add flatpak-spawn --host into the launch options after the second "$(" I used "eval $(%command% LauncherTetherPort=$(flatpak-spawn --host ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)"
  • WildBunnieWildBunnie Member, Alpha Two
    It seems to be running quite well, i get way better performance then on windows. Here i can play 60 fps in medium graphics with native resolution while on windows i would stutter even on low with lower resolution. My problem right now is that it is using all my ram and going into swap (i have 16gb), maybe its because its inside bottles? How is the performance for you guys?
Sign In or Register to comment.