NCommand.CreateAck excaption

Occasionally, our players would report an network issue and the following call stack would appear in the output_log.txt.

System.IndexOutOfRangeException: Array index is out of range.
at ExitGames.Client.Photon.NCommand.CreateAck (System.Byte[] buffer, Int32 offset, ExitGames.Client.Photon.NCommand commandToAck, Int32 sentTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.QueueOutgoingAcknowledgement (ExitGames.Client.Photon.NCommand readCommand, Int32 sendTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.ReceiveIncomingCommands (System.Byte[] inBuff, Int32 dataLength) [0x00000] in :0
at ExitGames.Client.Photon.NCommand.CreateAck (System.Byte[] buffer, Int32 offset, ExitGames.Client.Photon.NCommand commandToAck, Int32 sentTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.QueueOutgoingAcknowledgement (ExitGames.Client.Photon.NCommand readCommand, Int32 sendTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.ReceiveIncomingCommands (System.Byte[] inBuff, Int32 dataLength) [0x00000] in :0
Exception while reading commands from incoming data: System.IndexOutOfRangeException: Array index is out of range.
at ExitGames.Client.Photon.NCommand.CreateAck (System.Byte[] buffer, Int32 offset, ExitGames.Client.Photon.NCommand commandToAck, Int32 sentTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.QueueOutgoingAcknowledgement (ExitGames.Client.Photon.NCommand readCommand, Int32 sendTime) [0x00000] in :0
at ExitGames.Client.Photon.EnetPeer.ReceiveIncomingCommands (System.Byte[] inBuff, Int32 dataLength) [0x00000] in :0

Comments

  • IlyaIlya
    I've got the same issue! PUN v1.87
    Any suggestions?
  • TobiasTobias admin
    @cyberswine: Which version are you using? Can you update?

    The cause for this exception is unknown for us. Can you provide any info in which situations this happens? Is there heavy traffic or does it happen, when you join / leave rooms or anything such?
  • TobiasTobias admin
    @cyberswine, @Ilya: There is a fix for this exception in the PUN versions v1.88 and up.
    In best case, update to v1.90, the current version. This should avoid the issue.
  • IlyaIlya
    Tobias said:

    @cyberswine, @Ilya: There is a fix for this exception in the PUN versions v1.88 and up.
    In best case, update to v1.90, the current version. This should avoid the issue.

    That's actually pretty great. Thank you. I'll update ASAP.
Sign In or Register to comment.