Project

General

Profile

Bug #1791

[Hexen] Hub state reset after saving

Added by skyjake about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Regression
Target version:
Start date:
2014-04-30
% Done:

100%

Tags:

Description

See report in the forums: http://dengine.net/forums/viewtopic.php?f=7&t=1769&p=11225#p11223

Steps to reproduce:
  1. Warp to 2
  2. Play your way to the Guardian of Ice
  3. Save the game while in Guardian of Ice
  4. Return via the "sword" portal

Related issues

Related to Feature #1732: Libcommon savegame systemClosed2007-03-20

Associated revisions

Revision f8ee2663 (diff)
Added by danij about 5 years ago

Fixed|libcommon|GameSession: Replacing internal .save Info

Following File::reinterpret() one must manually (re)populate()

IssueID #1791

Revision 44b7eb5f (diff)
Added by danij about 5 years ago

Fixed|libcommon|GameSession: Replacing internal .save Info

Following File::reinterpret() one must manually (re)populate()

IssueID #1791

Revision aac8080f (diff)
Added by danij about 5 years ago

Fixed|World|SectorCluster: Crash with sci2.wad (Doom2) upon triggering the exit crusher

The crash was the result of an incorrect assumption that all sector
clusters will have at least one outer boundary edge. While this is
logically true there are some special cases in which no boundary is
recorded (e.g., the one unique outer halfedge is twined with an egde
originating from a degenerate BSP leaf). In this case, the trigger
is a so-called "control sector" outside the map attempting to update
surface light decorations when it's ceiling plane moved.

Todo for later: There is no need for such a cluster to be observing
plane movement at all. To address this properly we need two things;
1) BSP building algorithm that guarantees topologically sound and
geometrically correct data, 2) more intelligent SectorCluster.

IssueID #1791

History

#1 Updated by skyjake about 5 years ago

#2 Updated by skyjake about 5 years ago

  • Description updated (diff)

#3 Updated by skyjake about 5 years ago

  • Status changed from New to In Progress

#4 Updated by danij about 5 years ago

  • % Done changed from 0 to 100

#5 Updated by danij about 5 years ago

  • Status changed from In Progress to Closed

#6 Updated by skyjake about 5 years ago

  • Status changed from Closed to Resolved

#7 Updated by skyjake about 5 years ago

Marked as Resolved until cherry-picked.

#8 Updated by danij about 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF