Bug Tracker – Bug 1244

Demo Desyncs If DOOM2.WAD Is Not Present with Odamex.exe

Last modified: 2019-01-18 14:49:26 CST
Bug 1244 - Demo Desyncs If DOOM2.WAD Is Not Present with Odamex.exe
Summary: Demo Desyncs If DOOM2.WAD Is Not Present with Odamex.exe
Status: NEW
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: 0.7.x (Old)
Hardware: All Other
: P5 minor
Assignee: Odamex Bug Reporter
URL:
Depends on:
Blocks:
 
Reported: 2019-01-17 14:00 CST by HeX_Vulture
Modified: 2019-01-18 14:49 CST (History)
1 user (show)

See Also:

Attachments

CTF2 Demo (257.97 KB, application/octet-stream)
2019-01-17 14:00 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 2019-01-17 14:00:15 CST
Created attachment 566 [details]
CTF2 Demo

When a demo is recorded and played back, fast forwarding the demo results in errors being displayed. The scoreboard displays no playernames and the entirety of floor textures disappear. The texture error resolves itself when the player dies, but names continue to not display.

Attached is an example demo and a video displaying the error.
Comment 2 HeX_Vulture 2019-01-17 21:50:49 CST
UPDATE:

The demo works fine if doom2.wad is present in the same directory as odamex.exe. I normally do not have the iwads and pwads in the same directory as odamex, I have them in separate directories from each other and from Odamex. Interestingly, having the pwad not present is not an issue, it only breaks if doom2.wad is not present.
Comment 3 HeX_Vulture 2019-01-17 21:54:51 CST
https://www.dropbox.com/s/dyog6vb7mb1v7n4/ctf3.mp4?dl=0

Video demonstrating comment 2
Comment 4 HeX_Vulture 2019-01-18 14:48:38 CST
More development. Issue is much more minor than thought.

1:50 PM] Hekksy: the good news is that the demo itself is not actually broken
[1:50 PM] Hekksy: it can be resolved simply by putting doom2.wad in the same directory
[1:51 PM] Hekksy: that said, I've been having doom2.wad in a different directory from odamex since before the introduction of the waddirs command, how did i just now find this?
[1:51 PM] Hekksy: I'm going to test 0.7
[1:54 PM] dr_sean: It's possible that the issue is more of a buffer overflow bug that happens to be affecting the waddir related code
[1:59 PM] Hekksy: it does not happen in 0.7
[1:59 PM] Hekksy: even using the same cfg from protobreak
[2:01 PM] Hekksy: and using the same netdemo i just recorded with 0.7, breaks with latest master