Bug Tracker – Bug 942

Spectator Desync With Lowered Sectors

Last modified: 2019-02-28 21:55:27 CST
Bug 942 - Spectator Desync With Lowered Sectors
Summary: Spectator Desync With Lowered Sectors
Status: RESOLVED FIXED
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: (old) 0.6.x
Hardware: All All
: P1 normal
Assignee: Odamex Bug Reporter
URL:
Depends on:
Blocks:
 
Reported: 2013-01-11 01:22 CST by HeX_Vulture
Modified: 2019-02-28 21:55 CST (History)
0 users

See Also:

Attachments

Odamex 0.6.2 with file "class219.wad" and doom2 (242.23 KB, application/octet-stream)
2013-01-11 01:22 CST, HeX_Vulture
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 HeX_Vulture 2013-01-11 01:22:46 CST
Created attachment 424 [details]
Odamex 0.6.2 with file "class219.wad" and doom2

If you lower a sector that is normally raised a block the sector from raising by standing on it, it will normally raise back up on exiting the sector. However, you can break the sector from raising back up if you lower it, stand on it, then spectate. The client acts as though the spectator's body that is no longer there is still in the game.

I do not know if this effects the clients of other players. I have produced a simple demos that demonstrates exactly what I am talking about because it can be a bit hard to comprehend.
Comment 1 HeX_Vulture 2013-10-22 11:59:56 CDT
If you lower a sector that is normally raised and block the sector from raising by standing on it, the sector will normally raise back up upon exiting the sector. However, you can get the sector stuck from raising back up if you lower the sector, stand on it, and then spectate. The client acts as though the spectator's previous "body" that is no longer in the game is still there blocking the sector.

Modified for sanity reasons upon revisiting this bug... even I could not comprehend what I was trying to say at first @_@.
Comment 2 HeX_Vulture 2019-02-28 21:55:27 CST
This appears to no longer be an issue in Odamex 0.8.0. Tested with class219.wad