Special Early QA testing - new Unity version

Which version of Unity 2018.2 are u using here?
Maybe use 2018.2.14f1 as they did a change for TLS although it is for IOS. Maybe it fixes it for Fedora also.

 

It is version 2018.2.14f1 that we are using

 

Hmm bad news then, it seems the Fedora GNU/Linux players have a problem. They can not get the EULA when logging in.

 

@BurningToad

This I do not see on my other non Fedora systems: It does here on my fedora system.
I see this error every time I do the login.

Code:

Frame 317: 102 bytes on wire (816 bits), 102 bytes captured (816 bits) on interface 0
Ethernet II, Src: IntelCor_d7:ed:67 (38:de:ad:d7:ed:67), Dst: IntelCor_0a:2f:ee (00:1b:21:0a:2f:ee)
Internet Protocol Version 4, Src: 192.168.2.113, Dst: 208.81.240.54
Internet Control Message Protocol
    Type: 3 (Destination unreachable)
    Code: 3 (Port unreachable)
    Checksum: 0x80d8 [correct]
    [Checksum Status: Good]
    Unused: 00000000
    Internet Protocol Version 4, Src: 208.81.240.54, Dst: 192.168.2.113
    User Datagram Protocol, Src Port: 5055, Dst Port: 37603
        Source Port: 5055
        Destination Port: 37603
        Length: 40
        Checksum: 0x8830 [unverified]
        [Checksum Status: Unverified]
        [Stream index: 14]
    Data (32 bytes)
        Data: 00000001382b6ba72443757d01ff00000000001400000000...
        Text:
        [Length: 32]

 

Yeah so it looks like the QA client is not setting up the TLS connection to your webserver to do the login. I see no TLS messages at all.

 

Been running about as OK as the Live release for me on my old Windows 7 system here .. turning on the debugger, there is a constant warning message tho:

Particle System is trying to spawn on a mesh with zero surface area


Update: after flipping the debugger off/on a few times and loading into a few scenes, I'm getting some LONG hitches of several seconds at a time - RAM usage on the process is 21 GB - so maybe a memory leak.

OS: Windows 7 (6.1.0) 64bit
CPU: Intel(R) Xeon(R) CPU W3550 @ 3.07GHz (8) System RAM: 24573
GPU: NVIDIA GeForce GTX 670 GPU RAM: 1979
SotA.QA.Win.64.760.Date.11.02.18
Area: POT_desert_metropolis_01_template/Bladewyke
Area Display Name: Bladewyke
Loc: (158.6, 36.0, 271.3)
Debug: UE9UX2Rlc2VydF9tZXRyb3BvbGlzXzAxX3RlbXBsYXRlfEJsYWRld3lrZXwoMTU4LjU2NCwgMzYuMDIsIDI3MS4yOTcpfCgwLCAtMC43OTMsIDAsIDAuNjA5KXwyMy4wNjY3MnwyMi43NTAwN3wxNS4xNw==

 

This is very weird, I can not find out why the Fedora Sota QA system is not establishing a TLS connection. firewall is disabled.
All my other distro's are doing it correctly.

 

Could it be a version difference with openssl?

[edit] On Ubuntu 18.04.1, I get OpenSSL 1.1.0g. On Fedora 29, I get OpenSSL 1.1.1 FIPS.

 

could be yeah. But they all sbould support tls 1.2. very weird issue.

 

Perhaps Unity is trying to use FIPS if it's available? Do you know of any way to disable FIPS?

 

Gentoo:
feeyo@DevRig ~ {0} > $ openssl version
OpenSSL 1.0.2p 14 Aug 2018

Add (/boot/grub/grub.conf) fips=0 to kernel boot arguments.

EDIT: That does not do the trick, it seems FIPS is integrated into fedora on loads of system packages.. It is not possible to remove.

 

This is what I am missing on fedora, there is not TLS at all when booting up or doing the login:

Code:

49    5.621505431    192.168.2.100    54.155.190.206    TLSv1    407    Client Hello

52    5.657789151    192.168.2.100    54.155.190.206    TLSv1.2    232    Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message

54    5.682243444    192.168.2.100    54.155.190.206    TLSv1.2    343    Application Data

62    5.946415438    192.168.2.100    54.155.190.206    TLSv1.2    135    Encrypted Alert

 

Why does everything work fine in 2018.1 and not 2018.2?

 

Unity did some TLS changes. I remember reading it somewhere.

Yah:

Modern SSL/TLS support in .NET
The .NET 4.x Equivalent scripting runtime brings full TLS 1.2 support to all of the .NET class library APIs, on all Unity platforms with Mono and IL2CPP. Unity will now work properly with the operating system to access the local certificate store and make secure socket and HTTPS connections work as you would expect.

 

I am compiling openssl 1.1.1 now on my gentoo box, see if it also fails to start sota.

EDIT: No still works, even with latest openssl-1.1.1 (no fips tho)

 

So anyway, to come back at the test client. I do not see any weird glitches. The only glitches I noticed is the shield animations being in the character. Performance wise, seems playing ok. Only memory usage is higher then production.

 

I'll check it out tonight. Curious how well it works under Ubuntu LTS.

 

I could install Ubuntu on my gaming PC but that's a pretty crappy solution.

 

Fedora heavily patches its OpenSSL build. Did you do a checkout of their 1.1.1 repository?

https://src.fedoraproject.org/rpms/openssl/commits/master

I'd probably suggest filing a bug with Fedora, as it sounds like they broke something.

 

If you want to be more like Fedora, install Debian not Ubuntu.