Here are some screenshots

When you start it normally:

When you rename the game executeable to the launcher the game boots up

But the game stays on connecting forever.

By renaming the launcher and adding serverlist_url=https://serverlist-gujian.gfsrv.net/na.json to the command line arguments - which appears to be all the launcher does - I am able to connect and get in game. I haven't yet had a change to test much but it looks to be basically working.

Thanks for the tip about renaming the launcher.

Fired up a Windows 10 VM, to look at the Command in taskmanager about 5 Hours ago, this is the solution, temporary.

Rename the Game to SOLO_Launcher and adding

For EU
serverlist_url=https://serverlist-gujian.gfsrv.net/eu.json %command%
For NA
serverlist_url=https://serverlist-gujian.gfsrv.net/na.json %command%
as commandline argument fixed it.

Video: https://www.youtube.com/watch?v=A9-2tpqq548

This bypass seems to also work if you bought the game directly from Gameforge instead of Steam. You just don't have to add the command line arguments and instead choose your server in the main menu.

I have created a character but have not yet been able to play it because of an infinite loading screen. I guess it's because the EU server is overloaded?

This bypass seems to also work if you bought the game directly from Gameforge instead of Steam. You just don't have to add the command line arguments and instead choose your server in the main menu.

I have created a character but have not yet been able to play it because of an infinite loading screen. I guess it's because the EU server is overloaded?

Yes, since we have only one server for EU, guess thats expected.

Anyone managed to fix the infinite loading screen?

It's not a server load issue, as the game loads fast and runs fine on a windows VM.

I haven't experienced the infinite loading; I'm able to get into game and play fine. This was on the NA servers. Maybe it's AMD related, since this is on an NVidia Titan Xp?

Another possibility is different command line arguments: I just added the serverlist_url=https://serverlist-gujian.gfsrv.net/na.json to the launch options (i.e. omitting the %command%, so it's added to the end of the argument list, rather than as a prefix).

steam-1558640.log.gz
System Info

I don't know if I should post it here, but if someone stumbles upon this thread for the released (non-beta) version. I got it working by renaming the game to SOLO_launcher and adding (as commandline argument):

For EU (Tested and working)
serverlist_url=https://serverlist-service-live.gujian-live.external.ing.production.k8s.gfsrv.net/serverlist/eu %command%

For NA (Not tested)
serverlist_url=https://serverlist-gujian.gfsrv.net/na_s.json %command%

Found URLs here: https://steamdb.info/app/1418100/config/

Yeah, none of that works, support is a joke and steam community is useless.
Thanks though I didn't notice it was proton. My bad.

On Sat, Jul 10, 2021, 10:57 AM kisak-valve @.***> wrote:

Hello @sixtysixq https://github.com/sixtysixq, Proton is a project
which makes it easier to run Windows based gamed on Linux. Since you are on
Windows, this compatibility layer is not used on your system.

You might have luck posting your feedback on the game's Steam community
forums or https://solo.support.gameforge.com/.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4851#issuecomment-877650952,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUZR3N5HIJFJVEXFBVKPM5LTXBNURANCNFSM45MQHHHA
.

The latest proton experimental version works flawlessly now. Launcher also works now.

My OS is the following:

Distributor ID: Pop
Description: Pop!_OS 20.10
Release: 20.10

I just got the official launched game from steam.

I had to rename the gujianol.exe to SOLO_Launcher.exe, make a backup of the old SOLO_Launcher.exe...

The following command line argument worked for me:

serverlist_url=https://serverlist-gujian.gfsrv.net/na_s2.json

Note: the serverlist_url contains the na_s2.json(which worked) not just na_s.json, that one didn't work for me.

For me the launcher seems to work fine, it's just the character "shader?" that gets a bit messed up when standing on fire or on grass in shadows.. https://youtu.be/YCaTD8lE6hI

For me the launcher seems to work fine, it's just the character "shader?" that gets a bit messed up when standing on fire or on grass in shadows.. https://youtu.be/YCaTD8lE6hI

I don't have the issue in the video, but I do notice shadows on characters get messed up sometimes. Most often when talking to people in a heavily shadowed area.

For me the launcher seems to work fine, it's just the character "shader?" that gets a bit messed up when standing on fire or on grass in shadows.. https://youtu.be/YCaTD8lE6hI

I don't have the issue in the video, but I do notice shadows on characters get messed up sometimes. Most often when talking to people in a heavily shadowed area.

Ah, those black bars in the video are due to the recording software, they aren't visible in-game. All I wanted to show with the video was that the game launched just fine and the FPS for my old GTX 1070, with Proton Experimental I didn't need to rename
any exe-files or adding serverlist_url. As for the "shader?" / "shadow?" issues that I mentioned, they can be seen in these pictures (I had to leave, so I didn't get to upload any pictures until now):

@WaCrex For me it looks like the same as : https://github.com/doitsujin/dxvk/issues/1784

System Info
OS: Manjaro Linux
KERNEL: 5.10.49-1-MANJARO
CPU: Intel Core i7-8700K @ 3.70GHz
GPU: AMD AMD TAHITI (DRM 2.50.0, 5.10.49-1-MANJARO, LLVM 12.0.0)
GPU DRIVER: 4.5 Mesa 21.1.4RAM: 16 GB

Issues

• Launcher shows up as a white box running Proton 6.3-5
• Launcher works with Experimental, but will not launch the game
• No change when using the rename/launch options workaround

I get the splash screen with the fancy sword logo, but the app then immediately crashes. I did also try on the linux 513 kernel just to see, but no change.

Logs
steam-1418100.log

Hello @Bragendesh, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

I suspect that you're missing some Vulkan driver support for your video card.

So I kept doing some digging in the logfile and just noticed that you sent your reply... I switched to amdgpu and it works now! I had read that my card wasn't supported at first, but it turns out it is and that amdgpu is basically required for Vulkan to work. Thanks for the reply though, because you were spot on.

If anyone else has a related issue with a Radeon card, this article helps explain how to switch on arch distros.

Does anyone else experience fps dips?

I have a consistent dip in fps every 5/6 seconds. I loose about 50% fps for less then a second before it jumps back again to the normal fps. Happens everywhere. Right now staring at a wall and it goes from 100 fps to 50 fps for no reason for a split second.

Makes it really hard to enjoy playing the game with those consistent frame dips.

Currently also installing the game on my crappy work laptop that has Windows to see if the issue is specific to the game or to Linux.

Here you can see the consistent fps spikes (or dips):

Edit: the issue is not present with Proton 6.3-8. Seems to happen with Proton 7 and Proton experimental.

I can confirm the performance dips happening with Proton 7/Experimental. Thanks for the tip about 6.3-8 which doesn't seem to have the issue mentioned. With my specs matching the system recommended (AMD R5 1600 and RX 580), I was wondering if the performance issues were related to the game engine until I noticed this issue thread. I'll be happy to help with whatever log/trace is required to debug this issue though.

@kisak-valve Can we have a regression tag on this thread, because I tested the latest Proton 7 with the last dxvk version used in Proton 6.3-8, and the issue persisted so the regression is probably in Wine/Proton.

steam-1418100.tar.gz
Had to compress the log as it was getting a bit too big. Reached 37 MB within 3 minutes of running the game.
My system info as gist

Hope this helps.

EDIT: Just for reference, I used Proton Experimental for this log. @kisak-valve

Hello @kisak-valve sorry for tagging you again, but since this is another issue that I am facing in this game I thought it is only appropriate to bring to your notice also.

Even though I am using Proton 6.3-8, I find that the audio sometimes gets cut off at random moments and the game crashes as soon as I trigger a loading screen after that.

The engine log (attached) suggests that it might be related to FMOD but I'm not sure
gujianol.log
.

FWIW, I am using pipewire and do have both pipewire-pulse and pipewire-alsa packages installed.

@kisak-valve here you go!

System info: https://gist.github.com/Sojiro84/f842cb9edd53c7b09ba8d28b427a6221

And the log: steam-1418100.zip

Ran it with Proton Experimental - Bleeding Edge.

Can confirm that the latest Proton-Experimental as on date has fixed the Performance Regression/FPS drops issue. I don't know if the audio issues/crashes are gone too, but they might just be my set up and I'll update the thread in that case later.

Edit: I think I can even say that the performance has improved a lot, at least for me.

Kudos and thanks for the fast response.

Same here, fixed now for me as well.