Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
EDuke32
EDuke32
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 92
    • Issues 92
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #141

Closed
Open
Opened Jan 14, 2021 by Dino Bollinger@Doom64hunterContributor

Duke3D: Demo recording and playback crashes the game

Since commit 687000e2, demo recording and playback is non-functional. The game immediately crashes when trying to record a demo, and may crash when trying to perform demo playback. This is because the demo playback uses the same storage method as savegames, which were altered with that commit.

Backtrace for the recording crash: demo_crash_bt01.txt

Backtrace for the playback crash (from a different user): demo_crash_bt02.txt

Errors in the console when trying to play a demo:

sv_loadsnapshot: snapshot size: 4734602 bytes.
ud: 344
ud: 0 ms
sws: 3077626
sws: 3 ms
rsd: spec=blK:scri, idx=12, mem=000000007D1C9692
     (compressed): read -1, expected 16384!
     read: No such file or directory
sv_loadsnapshot: doloadplayer2() returned -5.
There were errors opening demo 1 (code: 5).
Edited Jan 14, 2021 by Dino Bollinger
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: terminx/eduke32#141