From 62281de40a8177f9c2cf728a5ae70743996216b3 Mon Sep 17 00:00:00 2001 From: fickleheart Date: Tue, 19 Mar 2019 23:38:26 -0500 Subject: [PATCH] Fix MAXMOM being above the max value GZT_MOM* could store This caused a lot of """desyncs""" when players were moving between 128-255 FU/T, which was exacerbated by this next commit... --- src/g_game.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/g_game.c b/src/g_game.c index 916b6ce1a..0b52c5280 100644 --- a/src/g_game.c +++ b/src/g_game.c @@ -5258,7 +5258,7 @@ void G_WriteGhostTic(mobj_t *ghost, INT32 playernum) ziptic_p = demo_p++; // the ziptic, written at the end of this function - #define MAXMOM (0xFFFF<<8) + #define MAXMOM (0x7FFF<<8) // GZT_XYZ is only useful if you've moved 256 FRACUNITS or more in a single tic. if (abs(ghost->x-oldghost[playernum].x) > MAXMOM