R57 QA Server Testing has now begun!

Same here on my Fedora system....

part of the log:

Code:

NetworkingPeer: Connecting to "208.81.240.54:5055"
PhotonNetwork: StatusChange Connect, State=Connecting
Network storage reset
PhotonNetwork: StatusChange EncryptionEstablished, State=Connected
IncomingMessages, Total=1, NumPlayers=1, SceneId=DemoStartupScene
AuthenticateResponse: Ok, Position=0
OnAuthenticateComplete: Ok
Network storage reset
Error Downloading Agreements Version: Unknown Error
 
(Filename: ./Runtime/Export/Debug.bindings.h Line: 43)

PhotonNetwork: StatusChange Disconnect, State=Disconnecting
Network storage reset
Network storage reset

On Production release:

Code:

NetworkingPeer: Connecting to "208.81.240.51:5055"
PhotonNetwork: StatusChange Connect, State=Connecting
Network storage reset
PhotonNetwork: StatusChange EncryptionEstablished, State=Connected
AuthenticateResponse: Ok, Position=0
OnAuthenticateComplete: Ok
Network storage reset
0 : 5a1abe96abb7320cd42f53b5
Found character: Ragnar Shakor

Also @BurningToad SotA QA writes its logfile to the production release directory and not to the QA SotA directory:

Code:

./.config/unity3d/Portalarium/Shroud\ of\ the\ Avatar/sota_log.txt

The argument: -logFile should write it to ./.config/unity3d/Portalarium/Shroud\ of\ the\ Avatar(QA)/sota_log.txt

 

I'm not sure what the issue would be that only affects certain linux distros. It is using the Unity WWW class to check for EULA/TOS agreements. Seems like perhaps a Unity bug in 2018.2? I will look into it more.

 

A new QA build has been published! Build number 728.

 

Could be, or some package (libcurl, wget, ssl, tls) on fedora specific?
As Debian variants and Gentoo are not having any problems.

 

No issues, so far, with regards to logging on Ubuntu 18.04.1.

 

Same problem on 728 build. Can not login with Fedora.

 

728 still has terrible memory usage: loading straight to the hidden vale took 8.5.

 

Probably have to do with: https://www.shroudoftheavatar.com/f...central-brittany-memory-leak-and-spam.138958/
I am seeing those from the start when loading up SotA into any scene.

 

Still can't login. Here's what I see in a terminal:

Code:

[barugon@shaguar ~]$ '/home/barugon/Documents/Stuff/Apps/SotA_QA/Shroud of the Avatar.x86_64'
Found path: /home/barugon/Documents/Stuff/Apps/SotA_QA/Shroud of the Avatar.x86_64
Mono path[0] = '/home/barugon/Documents/Stuff/Apps/SotA_QA/Shroud of the Avatar_Data/Managed'
Mono config path = '/home/barugon/Documents/Stuff/Apps/SotA_QA/Shroud of the Avatar_Data/Mono/etc'
Preloaded 'ScreenSelector.so'
Preloaded 'libCSteamworks.so'
Preloaded 'libMouseLib.so'
Preloaded 'libfmod.so'
Preloaded 'libsteam_api.so'
Unable to preload the following plugins:
    ScreenSelector.so
    libCSteamworks.so
    libMouseLib.so
    libfmod.so
    libsteam_api.so
Display 0 'LG ULTRAWIDE 34"': 2560x1080 (primary device).
Logging to /home/barugon/.config/unity3d/Portalarium/Shroud of the Avatar(QA)/Player.log
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.
[barugon@shaguar ~]$

 

Hi BurningToad and @Undone It seems they did upgrade their mono to support higher .NET, is it maybe possible to use a lower scripting runtime configuration to see if that fixes the WWW class?
They also added support for TLS 1.2, is the query to the EULA/TOS a https request? As Fedora has a few TLS/OpenSSL crypto policies that could break this. I did try to change the crypto policies to support TLS 1.2 but that did not help.
If not, is there a possibility to use UnityWebRequest instead of the WWW class API?

 

A new QA build has been released, version 732! This build is back on Unity 2018.1. For anyone that had memory leak or load performance issues, please let me know if things are improved on this build. Also, the Linux issue shouldn't be a problem on this version.

 

Thank you. I'll try it out when I get home later today.

 

Aww shame, I thought it was 2018.2 they did some major networking fixes.

2018.2.5 of course it out ...

 

Yes disappointing, I was really happy with the Unity upgrade. Performance was pretty good. And was hoping it would fix the hitching on production.
Oh well.

 

on linux: loading still seems slow, memory is not much better: loading straight to overworld, process is 8.2gb.

hitching seems better though

 

It is now possible again to login with fedora. So that seems also fixed with the roll back.

 

..i am getting a red "Server: not implemented" message every scene change

 

When patch 727 was out the game was using 8.1g for me on load-up. The hitching wasn't bad at start-up but after a while it got as bad as on Live.

 

Apparently thats expected atm - due to a WIP

 

2018.2.5 is actually worse than 2018.2.4, it has a crash bug in it, I tried a build with it but didn't publish.