Juan Blanco
Juan Blanco
Hey @cjcurrie Thanks I have seen your comments in discord, I need to figure out this, as Unity should not have an issue compiling as this is a referenced assembly.
Also that class is private, this should not happen. ```csharp private static class Common { [MethodImpl(MethodImplOptions.AggressiveInlining)] public static ulong umul128(ulong x, ulong y, out ulong high) { // Split the...
@cjcurrie This looks an issue with Unity compiler for sure, are you using IL2CPP?
Yes as it is the one used for logging, for many years. Unity should not have used their namespace for private naming as it is internal as a naming conflict,...
I am considering moving to another common logging framework, but keeping this for backwards compatibility in older versions.
@Oberhaim on master latest I have changed the logging, although is not released yet
Thanks, Ill try to reproduce it today.
Yes I forgot to update this, this is the normal timeout behaviour, one fast for connections, and the second is much longer to allow the continuous reading.
@rasoulMrz you just need to disable the check for package versioning in unity.
Just click on the dll / asset and there is a tick box in the properties.