Bug #973: [Map Converter] Crashes on linedefs with no front or back - Doomsday Engine - Tracker

Bug #973

[Map Converter] Crashes on linedefs with no front or back

Added by vermil about 13 years ago. Updated about 11 years ago.

Status:

Closed

Priority:

High

Assignee:

danij

Category:

Defect

Target version:

1.13

Start date:

2011-10-31

% Done:

100%

Description

Pretty much what the summery states. The map converter crashes if it encounters such a line.

Vanilla Doom 'converts' such lines to impassable linedefs that block attacks, don't appear on the automap unless the automap cheat is enabled and can't have any vanilla trigger attached to them (well they can have a trigger placed on in a map editor, but the trigger shouldn't function in game).

Such lines in the middle of sectors produce no rendering anomalies at all. Though if the line borders void, it looks like a HOM (as any texture less wall with void behind would).

Labels: Data

History

#1 Updated by danij over 12 years ago

No, this issue is an unrelated but similar issue which also needs special attention. This should be addressed by adding SideDefs as needed and flagging the LineDef appropriately.

#2 Updated by danij over 12 years ago

Lowering priority as such constructs no longer produce a fatal error (they still aren't handled correctly, however).

#3 Updated by vermil over 12 years ago

I made a mistake when I submitted the above report; triggers do still work on such lines, though only from one side, suggesting that despite not having a front/back, that they still have a direction in some way.Dday seems to currently replicate this behaviour.

Also, while Dday can now handle such lines in the middle of sectors without crashing, it still can't handle them if they are adjacent to the void (i.e Dday will abort with a seg violation).