items: use a different CSQC physics code path for smoother motion

Previously it ran physics in whole numbers of server frametimes, which
would cause "jumps" when the updates for a thrown item arrived.

diff --git a/qcsrc/client/items/items.qc b/qcsrc/client/items/items.qc
index 740294b2c1795d4020bed21dce372a1114bd5f25..b7c1b8de08efd206771b6d6211e04455f7f0fdc6 100644 (file)
--- a/qcsrc/client/items/items.qc
+++ b/qcsrc/client/items/items.qc
@@ -42,7 +42,7 @@ void ItemDraw(entity this)
                // which requires running this even if the item is just outside visible range (it could be moving into range)
                if(animate)
                        bobheight = this.origin_z - this.oldorigin_z;
-               Movetype_Physics_MatchServer(this, false);
+               Movetype_Physics_NoMatchTicrate(this, frametime, true);
                this.oldorigin = this.origin; // update real (SVQC equivalent) origin
                if(animate)
                {
@@ -256,14 +256,6 @@ NET_HANDLE(ENT_CLIENT_ITEM, bool isnew)
                //this.angles = '0 0 0';
                set_movetype(this, MOVETYPE_TOSS);
                this.velocity = ReadVector();
-
-               if(!this.move_time)
-               {
-                       this.move_time = time;
-                       this.spawntime = time;
-               }
-               else
-                       this.move_time = max(this.move_time, time);
        }
 
        this.entremove = ItemRemove;