Search Unity

no items spawning on client - Warning: not all old messages was acknowledged

Discussion in 'Multiplayer' started by RalfZimmer, Jun 21, 2015.

  1. RalfZimmer

    RalfZimmer

    Joined:
    Jul 24, 2013
    Posts:
    8
    hi
    when I connect to the server I get sometimes the message on Server
    "Warning: not all old messages was acknowledged"

    the client can not connect correctly ins this case

    it is called on client --> public override voidOnStartClient (NetworkClientclient)
    it is called on client --> public override voidOnClientConnect (NetworkConnectionconn)
    after 3 seconds client.connection.isReady is true

    I got no disconnected or error messages on the client. no items are spawning on the client.
    Other players on the Server can Play.

    any ideas?




    greetings
     
    Last edited: Jun 21, 2015
  2. gydronik

    gydronik

    Joined:
    Oct 20, 2012
    Posts:
    8
    Hi. The same problem, you have found a solution?
    Unity5.1.1p2
     
  3. Stoopers

    Stoopers

    Joined:
    Feb 25, 2015
    Posts:
    17
    i have the same problem,.. Unity 5.1.2f1
     
  4. Suvitruf

    Suvitruf

    Joined:
    Sep 3, 2014
    Posts:
    39
    Same S***. Unity 5.3.2f1

    Have anyone found solution?
     
  5. Deleted User

    Deleted User

    Guest

    I think theres a bug related to a client being already ready. So what ive done is i overridden the OnClientConnect so that its empty like so, as well as having auto create player being turned on. Otherwise it wont work properly. 5.3.2f3

    Code (csharp):
    1.  
    2. public override void OnClientConnect(NetworkConnection conn)
    3.     {
    4.        
    5.     }
    6.  
     
  6. UNNYHOG

    UNNYHOG

    Joined:
    Nov 18, 2012
    Posts:
    10

    We are using LLAPI, so i don't have this. We got rejected by Apple because of that recently, so we really want to fix it or at least to understand what exactly it causes.
     
  7. UNNYHOG

    UNNYHOG

    Joined:
    Nov 18, 2012
    Posts:
    10
    Hello,

    This issue was fixed in 5.3.3p3

    Good luck