Bug Tracker – Bug 1067

Door become invisible when you spectate

Last modified: 2019-12-22 21:37:32 UTC
Bug 1067 - Door become invisible when you spectate
Summary: Door become invisible when you spectate
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: 0.7.x (Old)
Hardware: x86 (Windows, Linux, etc) Windows 2000/XP/Vista/7
: P1 normal
Assignee: Odamex Bug Reporter
Depends on:
Reported: 2014-04-11 16:40 UTC by capo
Modified: 2019-12-22 21:37 UTC (History)
4 users (show)

See Also:


invisible door (151.80 KB, application/octet-stream)
2014-04-11 16:40 UTC, capo
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 capo 2014-04-11 16:40:08 UTC
Created attachment 490 [details]
invisible door

When i join a game and try open door and same time i go spectate, door stay invisible, when i try join game again and go throught this door its impossible. So door are closed but invisible. There is also no sound animation when door close when i am spectator.
Comment 1 HeX_Vulture 2016-09-07 13:51:14 UTC
This still happens to a certain extent. I played a Doom 2 map01 DM server and went to the exit. I opened the exit door and spectated while the door was raising. The door got stuck in the raising animation client side but appeared to still act correctly server-side. When I joined the game and went back to the door it seemed to have caught up with the server because the server told it to close.

Now, if you spectate while the door is opening/closing and then join the game quickly before the next server-side action is sent, the door will appear stuck. However simply using the door again causes it to resync.
Comment 2 Ralph Vickers 2016-11-15 01:09:37 UTC
Can confirm. This behavior is true on any type of moving sector. I tested it on doom2 map01 with the doors, lowering floors, and lift.
Comment 3 capodecima 2019-01-02 23:35:46 UTC
Still there.
Comment 4 Nick 2019-02-17 08:47:14 UTC
Fixed on my fork:
Comment 5 capodecima 2019-02-22 10:50:23 UTC
bug is gone, please close :D
Comment 6 HeX_Vulture 2019-12-22 21:37:32 UTC
author confirmed fixed