Too many bugs in UNet

Unity 5.2.2

Code (CSharp):

1. public class MyNetworkManager : NetworkManager
2. {
3.         void Start()
4.         {
5.             NetworkServer.SetNetworkConnectionClass<MyConnection>();
6.             StartServer(); // Or StartHost();
7.         }
8.         public override void OnServerAddPlayer(NetworkConnection _conn, short _playerControllerId)
9.         {
10.             PeonConnection conn = (PeonConnection)_conn; // Error!!!
11.         }
12.  
13. }
14. public class MyConnection : NetworkConnection
15. {
16. }

 

Dont called OnStartClient, OnStartServer, OnStartHost in custom NetworkManager

 

Dont worked DontDestroyOnLoad, RunInBackground, AutoCreatePlayer in custom NetworkManager without offline scene.

 

God, why do I moved from uLink on to uNet?

 

Look, man, instead of complaining here publicly on the forums, you might want to look into some UNET HLAPI manual and examples, because you are clearly on the wrong path here. A lot of people are working with UNET and don't have any problems with it.

 

Good afternoon! Does it look like I'm not know much uNet? A most people are working with UNET use standard solutions. If you make a step away from the standard solutions, the bugs occur. I have listed the real bugs, which since 5.1. You can try them all.
Here's yet another bug. Crash at the serialization of complex class with standard ClientRpc-Command

Code (CSharp):

1.  
2.  
3. public class Player : NetworkBehaviour {
4.  
5.     [Client]
6.     public override void OnStartLocalPlayer()
7.     {
8.  
9.         base.OnStartLocalPlayer();
10.  
11.         MyClass my = new MyClass();
12.  
13.         CmdSendData(my);
14.  
15.     }
16.  
17.     [Command]
18.     public void CmdSendData(MyClass _my)
19.     {
20.         Debug.Log(_my.ToString());
21.     }
22. }
23. [Serializable]
24. public class MyClass  {
25.  
26.     public MyClass1 aaa;
27.  
28.     public MyClass()
29.     {
30.  
31.         aaa = new MyClass1(this);
32.     }
33.  
34. }
35.  
36. [Serializable]
37. public class MyClass1 {
38.  
39.     public MyClass aaa;
40.  
41.     public MyClass1(MyClass _owner)
42.     {
43.         aaa = _owner;
44.     }
45.  
46. }

Unity just crashes without error messages and any useful information in the logs.

 

The arguments passed to commands and ClientRpc calls are serialized and sent over the network. These arguments can be:

• basic types (byte, int, float, string, UInt64, etc)
• arrays of basic types
• structs containing allowable types
• built-in unity math types (Vector3, Quaternion, etc)
• NetworkIdentity
• NetworkInstanceId
• NetworkHash128
• GameObject with a NetworkIdentity component attached

taken from http://docs.unity3d.com/Manual/UNetActions.html
I dont see anything about sending classes here.

 

I know that. Do you think it normal that Unity crash without error messages and logs? ))

 

Thanks for the answer. I hope that issue with basic types arrays reading/writing to the NetworkReader/NetworkWriter will also be resolved.

What about the previous real bugs?

 

Some time ago I created a theme in Russian gameDev forum. There's gave an UNet overview. And examples of network architecture with a split source code client and server objects and their networking. With custom class serialization. Maybe it would be useful to someone. Sorry for my English.

Registrar of custom object types: NetworkCodec.cs (NetworkCodecType.cs, NullableStreamObject.cs)
Usage is as follows:
Register:

Code (CSharp):

1. NetworkCodec.Add<MyClass>(MyClass.Write, MyClass.Read);

or:

Code (CSharp):

1. NetworkCodec.AddAndMakeArray<MyClass>(MyClass.Write, MyClass.Read);

Using:

Code (CSharp):

1.  
2.         NetworkCodec.Write<MyClass>(writer, myClassObject);
3.         MyClass myObject = (MyClass)NetworkCodec.Read<MyClass>(reader);
4.  

 

File uploading dont work in edit mode

Client with custom command and custom class serialization: Client.cs
Server with custom NetworkConnection: Server.cs (ServerConnection.cs)

Example project: uNetExample.unitypackage

 

Do you really believe that creating wrappers (MessageBase ) for each message type is comfortably?
Maybe I do not understand something. Ok. I have four classes (A,B,C,D) and I need to pass these classes in different messages in different combinations. Abstract I will have to write 16 message wrappers (MessageBase ) for each combination (A,B,C,D; A,B,D,C; A,C,B,D etc). Correctly? And in each wrapper I will still use methods such A.Write, A.Read in order to avoid duplication. Let's add here mutual use of these classes and their arrays. And we have provided work for a week )).

It is much easier to describe serialization once, a class register in the codec, and then use it in any messages

 

NetworkServer.connections is empty on host.

 

Does it mean the developer has to make the game manually add new connections to NetworkServer.connections?

 

NetworkServer.connections is read only. I think it is a bug, and the client connection on the host just is not added to this list. The manual does not say that such a connection should not be on the NetworkServer.connections.

And about the manual.

NetworkBehaviour.connectionToServer
The NetworkConnection associated with this NetworkIdentity. This is only valid for player objects on the server.
May be: "This is only valid for player objects on the client" ?

 

Felt @seanr could respond for the "bug" mentioned. I may recall it was reported, but no fix for now.

 

Why is an error (!!!) occurs: "UNet Client Disconnect Error: Timeout" on client when the server disconnected?

Code (CSharp):

1. public class FP2PClient : NetworkClient
2. {
3. public FP2PClient() : base()
4.                 {
5.                     ConnectionConfig config = new ConnectionConfig();
6.                     config.AddChannel(QosType.ReliableSequenced);
7.                     config.AddChannel(QosType.Unreliable);
8.                     Configure(config, 1);
9.  
10.                     RegisterHandler(MsgType.Connect, OnConnect);
11.                     RegisterHandler(MsgType.Disconnect, OnDisconnect);
12.                     RegisterHandler(MsgType.Error, OnError);
13.  
14.                     Connect(mServerHost, mServerPort);
15.                 }
16.                 public void OnConnect(NetworkMessage _msg)
17.                 {
18.                 }
19.  
20.                 public void OnDisconnect(NetworkMessage _msg)
21.                 {
22.                 }
23.  
24.                 public void OnError(NetworkMessage _msg)
25.                 {
26.                 }
27.  
28. }

Connect, turn off the server and receives an error. Why is the error?

 

When the client disconnect from server error occurs:

Example:

Code (CSharp):

1. public class FP2PClient : NetworkClient
2. {
3. public FP2PClient() : base()
4.                 {
5.                     ConnectionConfig config = new ConnectionConfig();
6.                     config.AddChannel(QosType.ReliableSequenced);
7.                     config.AddChannel(QosType.Unreliable);
8.                     Configure(config, 1);
9.                     RegisterHandler(MsgType.Connect, OnConnect);
10.                     RegisterHandler(MsgType.Disconnect, OnDisconnect);
11.                     RegisterHandler(MsgType.Error, OnError);
12.                     Connect(mServerHost, mServerPort);
13.                 }
14.                 public void OnConnect(NetworkMessage _msg)
15.                 {
16.                         Disconnect();
17.                 }
18.                 public void OnDisconnect(NetworkMessage _msg)
19.                 {
20.                 }
21.                 public void OnError(NetworkMessage _msg)
22.                 {
23.                 }
24. }

 

Bump @seanr

 

I'm not sending bug reports, because they are not responding. So when the developer's reply to me was a surprise )).
By the way, I realized handovering of players to another server. If anyone is interested, I can put the source code

 

Note that they only respond during business hours. If you send a Wednesday, Thursday, or Friday report, you'll need to wait for more days.

Source: Have sent out tons of report, got back most of them usually on Mondays and Tuesdays, with rare occurrences on Wednesdays through Fridays.

 

I wrote to them not on Mondays and Tuesdays... I wrote to them on August, September, October )))

 

Ah, they probably expected pictures, GIF, steps to reproduce, detailed debug messages, debug dumps, and a very small reproducible Unity project no bigger than 500KB. Anything over the size limit, or there is something missing, the bug report will have (-1 priority level multiplied by how many kinds of missing info the bug report has).

They would then order them from critical priority level 6 (highly reproducible crashes) to lowest priority level 0 (irrelevant, won't fix). If you are hitting priority 3 or lower, you'll be waiting for a while before any responses come in.

/sarcasm