Bug Tracker – Bug 1238

Player sometimes unable to cross open doors if opened at certain angles

Last modified: 2019-01-06 00:48:19 CST
Bug 1238 - Player sometimes unable to cross open doors if opened at certain angles
Summary: Player sometimes unable to cross open doors if opened at certain angles
Status: NEW
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: 0.7.x
Hardware: x86 (Windows, Linux, etc) Windows 2000/XP/Vista/7
: P5 normal
Assignee: Odamex Bug Reporter
URL:
: 1239 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-05 03:13 CST by Soul Sucka
Modified: 2019-01-06 00:48 CST (History)
3 users (show)

See Also:

Attachments
SSL2 demo showcasing the bug (527.67 KB, application/octet-stream)
2019-01-05 03:13 CST, Soul Sucka 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Soul Sucka 2019-01-05 03:13:44 CST 
Created attachment 563 [details]
SSL2 demo showcasing the bug

When the player is running (or straferunning), if they bump into a door and open it at certain angles (without letting go of the running inputs), they remain frozen in place even after the door is already open for them to cross. When that happens, the player is also shown to be in a running animation in others' POV, in spite of staying completely still in practice. This is fixed by letting go of the running inputs and then pressing them again as normal. This happens in both single-player and multi-player.
Comment 1 Mike Lightner 2019-01-05 09:31:41 CST 
*** Bug 1239 has been marked as a duplicate of this bug. ***
Comment 2 Maëllig Desmottes 2019-01-05 14:05:15 CST 
May be a stupid question, but does this behaviour also happen in DOOM2.EXE (DOS) or Chocolate Doom ?
Comment 3 Soul Sucka 2019-01-05 18:35:13 CST 
It happens in Chocolate Doom as well, but not in ports like Zandronum, for example.
Comment 4 HeX_Vulture 2019-01-06 00:48:19 CST 
(In reply to Soul Sucka from comment #3)
> It happens in Chocolate Doom as well, but not in ports like Zandronum, for
> example.

That makes me wonder if any of the boom or zdoom compatibility options fixes this issue already