About Receiving Help from the Support Board: While all members may answer questions posted in the Support board, you should only rely on responses posted or confirmed by support moderators and website administrators. Any solutions provided by members of the community that are not verified by a staff member (as indicated by a light-green background) are provided as-is, and we cannot take responsibility for any of the results of said actions.
About Responding to Support Threads: If you feel you know the answer to a question, you are welcome to respond to the thread and politely offer assistance. Please be courteous and try to provide detailed and helpful solutions to users who may not be as advanced as you. We ask that you refrain from posting one-sentence solutions.
* Topics denoted with the [OPEN] tag are awaiting a response from the end user. You are welcome to post in these threads if you are experiencing a similar issue so we may provide further support.
* Topics denoted with the [RESOLVED] title have been successfully answered and confirmed by a support moderator and the end user, and should be used as a reference. These topics are locked.
* Topics denoted with the [CLOSED] tag were either inactive for more than 30 days or the end user did not respond to a suggestion and confirm if the issue was resolved. These topics are locked.
[RESOLVED] Broken Brushes and Geometry Error Detection
Here are a few methods I use to try and fix broken brushes:
- Save and re-open the map in Constructor a few times. Somehow this occasionally fixes some issues
- Select all vertices and Quantize (it's one of the tools) with a grid spacing of something like "1/2/2/2/2/2/2". This is good when stuff overlaps and breaks
- Try using different DIF exporters. Constructor has a few built in, and
my site
will convert them all into something MB can use.
- If all else fails, copy half of the map into a new file and map2dif both halfs. Save the working half and repeat this until you find what broke.
Or if you like solving problems the brute force way you can use
a map splitter
which will make a ton of maps; this makes it easier to narrow down the problem but it takes a while.
or use quark which instantly shows up all broken polys and brushes, so you can check them off in constructor
"matan, now i get what you meant a few years back when you said that "the level in mbg is beyond me" after the last rampage i noticed things were insane, and now i truly feel that too" - Dushine, 2015.
[RESOLVED] Broken Brushes and Geometry Error Detection
