Bug Tracker – Full Text Bug Listing

Bug 1226

Summary: Door DR door open wait close (also monsters) got weird behaviour on odamex
Product: Odamex Reporter: capo <jaroslav1.jerabek>
Component: ClientAssignee: Odamex Bug Reporter <odamex-bug-reporter>
Status: NEW ---    
Severity: normal CC: Ch0wW, odamex-bug-reporter
Priority: P5    
Version: 0.7.x (Old)   
Hardware: All   
OS: Windows (Any)   
Attachments: demo with the desync.

Description capo 2017-03-02 20:03:25 UTC
Noticed this bug on map01, it happens when you open door on exit and same time you die and respawn before the door close. Odamex will play the sound effect for closing door but right after the open sound effect as well this is ofcourse bug. This is also the secret close to garden on map 01, typical where imp open the secret in singleplayer. This sound is bugged too.  I figured out this happens only with door (probably) which are able oppening by monsters as well.  I tried change the door in gzdb to disable opening by monsters and sound play normal. This is also the secret close to garden on map 01, typical where imp open the secret in singleplayer. This sound is bugged as well.
Comment 1 Maëllig Desmottes 2019-02-26 12:27:24 UTC
Another EXTREMELY critical bug with the door/close bug is that you can be able not to reopen it during very specific times (when the door action is finished, for instance). That makes vanilla demos desync very easily, and also breaks the gameplay experience.

Please change the severity to "Critical", btw.
Comment 2 Maëllig Desmottes 2019-02-26 12:29:42 UTC
Created attachment 573 [details]
demo with the desync.

The demo attached will break in Odamex ; it was recorded using DOOM2.EXE.

Normal behaviour is the following: I opened the door several times, and I should go through the door, and turn around.

Odamex: I opened the door several times, but doesn't open for a few frames (state == finished, according to DDoor), and then turn around.
Comment 3 Maëllig Desmottes 2019-03-05 11:55:05 UTC
After investigating a little, I made a few testings, and this bug was introduced in Odamex 0.6.0.
Odamex 0.5.6 and lower doesn't suffer from this problem.