waverider Posted April 22, 2020 (edited) Hey, I'm currently working on a map, where I've had some issues with bleeding errors. I've now managed to (almost) remove them to the point that they're now barely visible. From what I've heard, the best (or only) method is to move around vertices a bit until the problem disappears. Is this the best or only way to do it? The map I'm making is a Boom map and it has no unclosed sectors according to DB X. It did have an unclosed sector though in the vicinity of where the bleeding errors now appears, but I was pretty sure I had removed it. Is this a common problem even with mapping for Boom? I know I've seen it in vanilla maps but don't think I've seen it in a Boom map before. And could this be an unclosed sector even though DB X doesn't report it? Or is the only solution to fix this indeed to keep moving around vertices until the bleeds disappear? Here's a picture of the error: https://web1.storegate.com/share/Jok7gUH I would be grateful for help! Thanks. /W Edited April 22, 2020 by waverider 0 Quote Share this post Link to post
Kappes Buur Posted April 22, 2020 (edited) Without being able to inspect the map in an editor this is going to be a guessing game. And I have three guesses: A missing texture which causes HOM A linedef with the wrong sector index A linedef is doublesided when it should be impassible If it were a node problem you would see a slimetrail, so moving the vertices around may not solve anything. Your best bet at getting this resolved is to upload the pwad. DBX is an improved version of DB2, and it is recommended for lightweight computers. However, if your computer is medium to high level competent than UDB is recommended. Here is another reason why: Map Analysis DBX Map Analysis UDB Edited April 23, 2020 by Kappes Buur 2 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.