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.
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.
Comments
The game will not allow itself to start in a vm, but I was able to get the command line it used to start the AOCClient from the process explorer.
I don't know what process is giving that message. I have not seen it in any of my testing.
@idiom444 Make sure you are running AOCClient.exe from Steam using Proton Experimental even if you are running the launcher in Bottles.
Not sure if necessary but I do have Proton EasyAntiCheat Runtime installed in Steam.
Edit: For non-flatpak Steam users, I believe you could set the launch option to the below and it will find the port and then run the client with the correct options.
I'm using flatpak steam so I can't confirm
lsof is not very friendly on my system for some reason so I had to modify the command line a little. This works for me to pull the no realms error.
I originally added the to the end thinking that would help. But When I commented out the entire variable the AOCClient.exe magically worked lol.
Found this solution on some random reddit threads related to EAC.
The error message I was seeing was literally a wine popup of some sort.
I am now also at the no realms error and can't wait for Friday!
Thank you so much man this is awesome.
I can confirm that running the Launcher in Bottles and then running the AOCClient.exe from Steam works with the following settings:
Launch Options:
Proton Version experimental
--proton LauncherTetherPort=XXXXX (where XXXXX is the udp port below)
XXXXX is obtained by running netstat -ulpn | grep wineserver
-u show udp only
-l listening ports
-p program name
-n only show numeric values
So running Launcher from Bottles and logging in from there. Then switching to Steam and running the Client works.
If you get an Error:10 this means authentication has failed so there is not passthrough from the Launcher to the client (or the UDP port is incorrect)
https://youtu.be/qBRI6M6BzqE
I can confirm this works and I could load in the game and can join the server with created character on PTR Server. Sadly I can´t share you visuals for now because of NDA, but I can speak about it.
The game freezes for me after seeing my character ingame. But others have the problem on windows too. I guess it is not Linux specific.
I will test around and check if we have an other proper way to get this work. Tried to use Bottles with the launch parameter but this throw an error. Maybe because of the EAC Runtime. I will test umu-launcher and try stuff out.
Thank you to @icedown for this nice find! I guess next weekend we finally can play
PS: I also updated https://github.com/ValveSoftware/Proton/issues/8212, so maybe we get a fix which translates to ge-proton or something.
Here is a video from the little time I was on the server prior to shutdown. Yes I am a noob, and I was just testing out stuff and watching log files on other screens to see if anything was having issues. I have absolutely no idea what I am doing in game.
https://youtu.be/PEZbVjBsXAs
EAC should be included in all their runners.
Good point, my first time using Bottles, didn't see any EAC in settings or Dependencies...
I got it all to work except when I login on the launcher, I get a weird small popup that shows an OK button, but the rest is glitched with the launcher background. Nothing was able to be selected/copy/pasted from the window.
I assume it's some sort of login error, but I know that I am using the correct creds, so no clue what the error would be...
Using ZorinOS for reference, which is essentially Ubuntu 20.04.6 LTS.
I don't think that this is the issue with the launcher. I think that issue may be an odd function call to spawn the process. I am not very familiar with bottles but I'm going to try to do it from steam alone next time. If i can get the libraries setup correctly, steam proton might support running from just the launcher.
Yeah that would probably be ideal, if the right recipe was found
I noticed Funkychicken used the "custom" bottles environment, I got to this point using the "gaming" environment.
I just tried a "custom" one and when using all the same configs and dependencies, I get white login screens, but do see this error - happens prior to me logging in (ofc, because I have white windows now) while the other popup happened after login.
First thing I tried, before finding this post, was to install the launcher on Steam, it all worked except WebView2 would not install, so I went a gooooglin' (also, I don't google) :P
Okay finally got to see what this error said, I had to disable DXVK and VKD3D so the popup windows did not glitch, at least Cloudflare works on this bottle, for whatever reason:
I also tried setting it up in Steam only and installing webview2 worked for me when I just copied what Bottles was doing. The download URL and launch arguments can be found in the yml file for the dependency. https://github.com/bottlesdevs/dependencies/blob/main/Essentials/webview2.yml
Interesting, so you ran it as such? Did you use Proton-Experimental compatibility for both the WebView2 and AOCLauncher executables?
I used steamtinkerlaunch but as long as that will put it in the correct prefix that should work.
I will say that game is freezing shortly after logging into a character with correctly rendered UI but not 3D rendering.
Have you watched Funcky's video?
https://youtu.be/qBRI6M6BzqE
Yep. I'm running the launcher first via bottles, then AOCClient.exe with as the launch options via steam. Error code 406.
Netstat can detect the launcher's open port just fine from the terminal too, so it's not that.
I can get through to the character creation menu and then back to the splash without "Connecting...", but when I go to select a realm, the list is empty.
I'm also having this issue, but apparently so are Windows users, so could be server issue! Lots of problems right now it seems going on. Hopefully it'll get fixed. Not sure if Windows users are having the exact same issue tho.
The game runs pretty bad on the SteamDeck. Haven’t fully tested it yet, so your mileage may vary.
I was getting the same thing. I made a couple changes and am now loading in and have been able to kill an enemy.
I installed dotnet472 and added to the launch options of AOCClient.exe not sure which did the trick.
Wow!!! I also added to launch options and was able to load into the game
I haven't had time to figure out why Steam isn't evaluating the command yet.