scifista42
Member
Posts: 272
Registered: 05-12 |
Maybe you know it, maybe not. When editing a map, if you move a verticle on another verticle and you have bad luck and editor mysteriously fails to check for this, it may lead to creation of 0-length linedef. Linedef that connects two verticles with the exactly same position. This linedef is not just very very hard to find and remove, but also may cause problems with your map.
It's no joke. This occured to me several times in the past. They're especially annoying if they don't have set a texture and DB2 error checker reports an error, but isn't able to show where it is.
Yesterday I was making a vanilla map, tested it in Chocolate Doom and didn't notice any problems. Then I decided to playtest it again in Zandronum, just because. And when the map loaded and everything seemed fine, I opened the console to activate cheats. And only because of this, I noticed warning message that told me something like:
code:
Linidef 9121 has been removed.
The map contains 1 0-length sidedef.
To remove it, I had to block-select all linedefs in the certain map section, then click-by-click remove all of them from the selection and then press delete. And after that, I had to redraw adjoining sectors to that linedef, because HOMs started to appear in my map in Chocolate Doom (but not Zandronum).
So I'm asking, is this a well known problem which is easy to solve, or did I discover something new?
(And if some of you have doubts, I'm emphasizing that this thread is no joke.)
|
01-01-13 12:45 
