March 6, 2013 at 09:38 #462AnonymousInactive
First of all, if this should be in a new thread let me know to start it.
I don’t know if it’s a bug, but when I use the library in Unity3D, as it tries to execute this line (or any appendGlobalIncomingPacketHandler):
It throws this error:
ArgumentNullException: Argument cannot be null.
Parameter name: path1
System.IO.Path.Combine (System.String path1, System.String path2) (at /Applications/buildAgent/work/3df08680c6f85295/mcs/class/corlib/System.IO/Path.cs:112)
NLog.LogFactory.GetLogger (NLog.LoggerCacheKey cacheKey)
NLog.LogFactory.GetLogger (System.String name)
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for NetworkCommsDotNet.NetworkComms
SimpleMesh.startNetworking () (at Assets/Scripts/SimpleMesh.cs:112)
SimpleMesh.Update () (at Assets/Scripts/SimpleMesh.cs:125)
Since the error comes from Nlog, I’ve disabled logging, but it’s still happening. Searching about this error, it seems that Unity doesn’t work properly with the properties used by some libraries.
I’ll try to work on it to avoid this error but I thought it should be OK to let you know about it.March 6, 2013 at 09:59 #464
Interesting error. As far as we were aware people had been using the v2.2 alpha successfully in unity 3d. I’ll see if one of the developers can look at this in the next couple of days.
In the mean time if you find a solution please let us know.
MarcMarch 7, 2013 at 07:59 #465AnonymousInactive
No luck with this.
The same error is thrown whenever I use any method of the library. I’ve tried disabling logging with no luck, and to try in different versions of Unity.
I’m using unity indie, windows 7 64bits and the built-in MonoDevelop.March 7, 2013 at 10:14 #466
That would make sense. The error is caused during the initialisation of comms which happens before logging is disabled/enabled. It is possible to prevent the error from happening by manually removing the logging functionality but we are ‘today’ looking for an alternative which would allow the logging to be used with unity.March 8, 2013 at 15:21 #467
We have a working fix that allows NetworkComms.Net to work correctly in unity but at the loss of any logging functionality. We are continuing work to make logging available as soon as possible but I may end up requiring some changes to NLog. If you want the current fix please let us know.March 9, 2013 at 07:57 #468AnonymousInactive
I’ll wait until the final version comes out to use it with Unity since the log feature is a great one.
In the meantime I’ll keep playing with it in the other plattforms 🙂
Thanks a lot!March 11, 2013 at 20:32 #469
ok, this has been completely fixed. It will be part of the v2.2 release (hopefully within the next week). If you would like another alpha copy before then let me know.
MarcMarch 11, 2013 at 21:39 #470
Scratch that, after some further testing there are still issues. It runs successfully and outputs ‘some’ logging data but for some reason it does not seem to log everything. This appears to be a problem with the nlog framework as the comms code executes without issue. I’ll try to get in touch with the NLog guys and see if we can work out what the problem is.March 14, 2013 at 16:19 #485
Ok, all Unity3D issues have now been fixed and will be in the v2.2 network library release.March 17, 2013 at 22:03 #505
Just to update. We have now released v2.2.0. If you use the .net2.0 build all features should be working.
- You must be logged in to reply to this topic.