What changed in EDuke32, build by build

(e.g., beginning to jump, or landing on ground); Reproduced with the input being tied to framerate while SO interpolation is toggled on. This involves the following modifications: - PF2_INPUT_CAN_TURN and PF2_INPUT_CAN_AIM are now additionally set from various DoPlayerBegin* functions, allowing the player to continue turning/aiming as usual (right before the next call to domovethings), even in specific instances of player action changes. - If PF2_INPUT_CAN_TURN/PF2_INPUT_CAN_AIM was set before and after calling pp->DoPlayerAction from domovethings altogether, ensure that the player's oq16ang/oq16horiz is updated by making an appropriate call to DoPlayerTurn/DoPlayerHorizon. This is done in case a call to DoPlayerTurn/DoPlayerHorizon is missed. This change is not applied for a dead player, though.

in 1a3c9e3a15ba788607dfd96ebcc75a2198be6d69 was a mistake. The interpolation should still apply, albeit not while the viewing angle is changed via the player's own input. We should also continue interpolating in coop view.

interpolation of player turning/aiming/movement, while being carried by a sector object, without SO interpolation. This is a continuation of 73a0aa394e906a65633d61f3c749c9b9b7e66aaa and bf31bc2987a3eccd31d343622327bd4ee0f9c5a1, aiming to fix a jitter in case the player is continuously getting pushed by a wall (e.g., on the boat in level 5). Basically, this moves the relevant assignments from track.cpp:MovePlayer and MovePoints to player.cpp:DoPlayerMove. Unless a call to one of these functions has been missed, pushwall and clipmove can be called from player.cpp in the following instances, which should be covered: - Via DoPlayerMove, which is the function getting the fix now. - Via DoPlayerSlide, which is called in the beginning of DoPlayerMove. - Via DoPlayerCurrent when called from DoPlayerCrawl/DoPlayerWade, followed by DoPlayerMove. - Via DoPlayerCurrent when called from DoPlayerDive, followed by DoPlayerMove if the player doesn't stop diving.

so OSD commands can have an effect from here

(with SO interpolation turned on). It would be nicer to have something better structured than the given hack, but this currently seems to work, while not breaking the sprites on the boat in the beginning of level 5.

Move ratio calculation out of inner loop.

is now required. Previously, it would be called from faketimerhandler, which in turn is called from the engine.

if any of its sectors is impacted by CopySectorWalls. Fixes a possible flicker with the drill at the end of level 2.

separate checks of the form sop->xmid == INT32_MAX

for now, due to possible jitters. Currently leaving remote-controlled SOs.

from faketimerhandler. This should fix the timing of playing an RTS file's sound and sending the corresponding message.

by the player. Make sure looking up/down is still smooth.

don't move as smooth as possible in multiplayer

PACKED macro. This is more consistent with the current Duke3D codebase, and further fixes build with older versions of MinGW GCC, in which attribute packed is broken without specifying -mno-ms-bitfields.

SW 1.2 after minor adjustments. Originally recreated for sw-src-and-build-addendum-20190129.7z.

and also as currently in use in EDuke32-OldMP.

While it is understandable that avel and horz came from Duke3D, having both q16horiz and q16horz in the updated SW_PACKET struct can be confusing, and the alternative notation is more consistent with the original struct field names of angvel and aimvel, as well as the differing uses of the name angvel still present in player.cpp.

test for PF_MOUSE_AIMING_ON only if PEDANTIC_MODE == FALSE

one of the players toggled mouse aiming in the middle of a game, and it worked even worse in Master/Slave mode. Additionally, tying input to frame rate made the problem disappear.