Tnet Syncing Movement (Jumping Issue)

[WolfTechGames]

It syncs movement smoothly but the jumping turns out to be jittery and looks bad in the end.

1. void Update()
2. {
3.      if(tno.ismine)
4.      {
5.            //Sync Data
6.            tno.SendQuickly(1, Target.Others, transform.position, transform.rotation);
7.       }
8.       else
9.       {
10.              //Interpolate
11.             transform.position = Vector3.Lerp(transform.position, realPosition, Time.deltaTime * 5f);
12.             transform.rotation = Quaternion.Lerp(transform.rotation, realRotation, Time.deltaTime * 5f);
13.        }
14. }
15.  
16. //Interpolate
17. [RFC(1)]
18. public void syncData(Vector3 newPosition, Quaternion newRotation)
19. {
20.      realPosition = newPosition;
21.      realRotation = newRotation;
22. }
23.  
24. //Do Jump
25. if(Input.GetKeyDown(KeyCode.Space) && canJump)
26. {
27.        //Add Force
28.        GetComponent<Rigidbody>().AddForce(Vector3.up * playerJumpForce);
29. }
30.  

[phoenix]

I am guessing that Aren's answer will be similar to others who have similar issues, dont sync the players movements, sync the input triggering the movements.

He talks about this in his FAQ

and also here http://www.tasharen.com/forum/index.php?topic=13615.0

[ArenMook]

Yes, precisely.

Also NEVER EVER EVER send anything in every Update(). It's not only horrible practice as it's tied to the framerate, but you will flood the network doing so. Think about it... someone who has 10 FPS will send 10 updates per second. Someone who has 1000 FPS will send 1000 updates per second. You will flood the network in no time, which means that packets will be sent in batches instead -- causing the updates to be jittery (think receiving 50 packets at a time instead of 1 at a time).