Special Early QA testing - new Unity version

Hello!

We have just published new builds on QA, number 760. These builds are currently the same as Live, there is no new content or features compared to the current live builds. However, these builds are on a newer version of Unity, 2018.2, versus the current live builds, which are on 2018.1. We would appreciate if we could get help in testing to see if any serious new issues come up. Also, just to be clear, these builds are still running on the QA server. We copied data from live to QA in the last day or so.

Things to watch for would be crashes, graphical artifacts, sound or input issues, etc. Basically, engine related things. Please do not post any bugs about the actual game, gameplay, etc, unless you notice a difference between this QA build, and the current live builds.

We are also interested in any performance differences that you may notice.

*** For now, please keep all observations and issues in this single thread, we are not opening up the normal bug forums yet, due to the different kind of testing that we are currently interested in.

When we publish new QA versions, I will post in this thread so that you know there are new things to test!

Those of you new to testing on the QA Server please note the following:

• Do not post screenshots or video outside of the QA forums (or QA on Discord) of anything from the QA server.
• The same Rules of Conduct apply on the QA server as they do on Live.
• The QA server is an early snapshot of the upcoming release, which means the build on that server is going to be broken and incomplete. That is why we need your help!
• We usually copy over data (your character for example) from the Live server to the QA server, which means when you login you will see your Live character. Any changes or progress made on the QA server will NOT affect your Live server character.
• To report bugs for QA, please use the /devbug chat command, which will link you to the appropriate QA bug forum. While the Bug button and /Bug chat command still work, they will direct you to the Live bug forums for the previous Live release.
• (This will be done closer to R60 release) The draft of the instructions (to be posted in the R60 QA Feedback forum by Starr) you will see early on may include items that won’t actually make the release or conversely it won’t included items that will make the release. In other words the early draft of the instructions will be an early draft.

Here are instructions on how to download and install QA builds:

You can play by downloading a new SotA Launcher(QA) installer to download a separate QA copy of the game. It exists independently from the regular live version of the game and installs to a separate folder. Alternatively, after the links, there are instructions to play using Steam instead.

Windows: https://d2sx9mrt4zumaq.cloudfront.net/Installers/SotAInstaller(QA)-1.2.0.exe

Mac: https://d2sx9mrt4zumaq.cloudfront.net/Installers/Shroud of the Avatar - Installer(QA) 1.1.0.pkg

Linux Package: https://d2sx9mrt4zumaq.cloudfront.net/Installers/shroud-of-the-avatar-launcher-qa_1.1.0_amd64.deb

Linux tar.gz: https://d2sx9mrt4zumaq.cloudfront.net/Installers/shroud-of-the-avatar-launcher-qa_1.1.0.tar.gz

If you want to play through Steam:

WARNING: Playing both the normal and QA versions through Steam could use up to 7 GB+ of data download via steam each time you move back and forth between versions.

To install the QA client via Steam, follow these instructions:

• Right click on the game in your game library
• Go to Properties
• Click on the tab at the top that says BETAS
• Enter the beta access code "SotAQATesting" and hit Check Code.
• Select "qaclient" from the dropdown menu
• Steam will switch the install to the new branch
• To return to playing the normal client, follow these instructions:
  • Go back to the properties beta tab and select "none - opt out of all beta programs" and it will switch you back to the normal install.

 

Are all QA clients using 2018.2 (Linux)?

 

Patching up now. Will try on Windows. But I see all three platforms have patches.

@BurningToad is Vulkan enabled on all three in QA?

 

All clients/platforms are using the same Unity version, as they have been for a few months now. Vulkan is not enabled on any platforms at the moment.

 

Thanks.

 

@BurningToad
Can't login (I also can't post to the bug section):

 

This contains the live version, so the bug forum is closed. They just want reports in this thread.

 

a lot more hitching in the first few seconds of being in scene than on live; takes severe effort to swing the camera around. tried four scenes: south fetid, stinging tree, the vale overworld, and holtrot. this may be from debugging stuff you don't have in live (anymore).

hitching in combat is TERRIBLE. worse than before the recent fix. in fact i was waiting for one to clear when i realized it was a crash to desktop. was in the ruined arch sample dungeon.

edit: actually, did an os update just before this test that switched default schedulers, that may be the culprit. testing.

edit 2: confirmed, hitching mostly gone using bfq instead of cfq. may be the same as live, i'm just looking for it too much now to be sure.

OS: Linux 4.19 ManjaroLinux 18.0.0 64bit
CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (4) System RAM: 15989
GPU: GeForce GTX 970/PCIe/SSE2 GPU RAM: 4096
SotA.QA.Linux.64.760.Date.11.02.18

 

shield of crystal vfx have collapsed into my body.

 

Still can't connect....

 

is that encryption SSL issue again on Fedora?

 

Thanks, I will do some testing Today if my kids let me

 

The same issue as the last time they tried 2018.2.

 

Will do some patching later on, on my fedora system to see if I can reproduce that problem you are having. But first doing my Gentoo SotA patching.

 

I have the same with Death Shield and Shield of ICE.
11/03/2018 13:26
Title:
Reproduction Rate:
Blocker?
Details:
Steps to Reproduce:
User Specs:
OS: Linux 4.19 Gentoo 2.6 64bit
CPU: Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz (12) System RAM: 32115
GPU: GeForce GTX 1080/PCIe/SSE2 GPU RAM: 8192
SotA.QA.Linux.64.760.Date.11.02.18
Area: HiddenVale_Forest02_Tier5
Area Display Name: Deep Ravenswood
Loc: (-78.5, 32.3, -71.5)
Debug: SGlkZGVuVmFsZV9Gb3Jlc3QwMl9UaWVyNXx8KC03OC40NjcsIDMyLjI3OSwgLTcxLjUxMil8KDAsIC0wLjI2NiwgMCwgLTAuOTY0KXwtMTM4LjQyMzF8MC43NTUzMDkzfDUuNjMwNDY3

 

The IO scheduler you are talking about (CFQ, BFQ) are both crap on the IO scheduling part, just go for noop scheduler.

 

i had planned to test that one, i simply went back to bfq because i knew it didn't have the problems the switch to cfq caused and didn't want to fuss with it right then.

 

Yes same on my Fedora's (28 and 29) systems

Code:

NetworkingPeer: Connecting to "208.81.240.54:5055"
Network storage reset
Network storage reset
Error Downloading Agreements Version: Unknown Error
 
(Filename: ./Runtime/Export/Debug.bindings.h Line: 43)

Network storage reset

 

PS I have tried all three system CryptoSettings none work. (LEGACY, DEFAULT, FUTURE)
Disabled SELinux -> No luck.

 

your copypasta has gone awry, toad