Bug I can't solve

Options
After updating to Unity 4.6, I have been having a bug which I can not solve. I do not believe that I made any changes to my network code that could cause the issue I am having. Rather than try to explain my issue I made a video that shows it http://youtu.be/ch61qcWylQ4 You can also get game logs and possibly relavent code:
Log 1 : https://www.dropbox.com/s/mg5ufsx2751273f/output_log.txt?dl=0
Log 2 : https://www.dropbox.com/s/1bw5sdsu4fgllei/output_log%281%29.txt?dl=0
NetworkManager : https://www.dropbox.com/s/w6fngubwn921b4j/NetworkManager.cs?dl=0
NetworkPlayer : https://www.dropbox.com/s/2ztda5fd86tsb8z/NetworkPlayer.cs?dl=0
PlayerController : https://www.dropbox.com/s/tzkr1s9s1tdqiuj/PlayerController.cs?dl=0

Comments

  • vadim
    Options
    You have a lot of "You have missing MonoBehaviours on your gameobjects!" errors in your logs.
    I think it's better to get rid of them first.

    Can you please describe shortly the bug, it's not quite clear from the video.
  • Right I know that is the problem but I can not figure out what started making those errors appear. It only happened after I updated to 4.6. The bug is that one player can join fine, but then another player that joins will at first be able to see from the position of the original player but not move it, then after choosing a team gets their own player, but then I believe the original player sees from the perspective of the new player but can not rotate camera or move.
  • vadim
    Options
    Try to downgrade to previous Unity version.
    But I'm pretty sure that reason is some project corruption. Aside from Photon errors you have Unity warnings: "The referenced script on this Behaviour is missing!". Start with eliminating these warnings. Check this link for instance http://answers.unity3d.com/questions/34 ... ing-2.html
  • I was able to find the source of the Unity errors, but I am still having my issue. There are no errors or warnings.
  • vadim
    Options
    Did you try to revert Unity version? To make sure that bug is related to update to 4.6?