Another Thing To Try
Go to an older version of the tools. Might be an issue with the version you are running.
Agree
#1021 posted by
madfox on 2018/11/30 21:10:43
I overcome the same phenomenon.
Not to blame the new tools, more my poor mapping skills.
I have several maps I restarted after some months and experienced rare anomilies that earlier tools just lacked to cause.
Sometimes an earlier version of the tools come out clear, while older ones causes homs and leaks.
#1022 posted by
madfox on 2018/11/30 21:11:48
while the newer ones cause home and leaks.
Yeah Madfox Is On Point As Always
#1023 posted by Anom79 on 2018/11/30 22:30:31
http://web.archive.org/web/20160929072512/http://voidspark.net:80/projects/bjptools_xt/
these tools do a great job at compiling sub-grid/float precision verts.
Maybe give them a try.
Sadly the author vanished.
#1024 posted by
ericw on 2018/11/30 23:10:09
If the area is already on grid there's probably not much you can do from the mapper's side (of course even off grid shouldn't break like this); if you can post an issue on github with the
.map or a reduced test case that would help fix the problem.
Alternatively trying older versions is a good idea. Maybe check 0.15.9 which was right before I did some major changes to qbsp (func_detail rewrite).
https://github.com/ericwa/ericw-tools/releases/tag/ericw-v0.15.9
I can't promise a quick fix, I'm taking a break from working on tools right now and I have a backlog of bugs piling up, but I do intend to get back to it and try to fix things at some point.
#1025 posted by anonymous user on 2018/12/01 00:09:32
I tried some older versions and the problems persisted. Will post an issue, thanks.
Good Ol Bengt
#1026 posted by
Qmaster on 2018/12/01 15:32:39
Seems like a vis issue ...just throwing this out but maybe try -fast vis?
It is wierd how switching to txqbsp actually hsndles stuff better in a lot of cases of wierd geometry. You should still at least use ericw's vis and light...so much faster.
#1027 posted by
Orl on 2018/12/01 19:09:34
Not wanting to start an argument over whats better, but I'll say that I have built some of the most absurd, overly detailed and off grid architecture and ericw's qbsp has never given me a weird error or HOM that wasn't specifically my fault.
Some Ideas
#1028 posted by
ww on 2018/12/01 20:42:49
Random HOM like this could happen in q3 if the vis wasn't optimal, sealing or cutting sections up with hint faces could fix it. Also try increasing your engines limits; or dividing your map up so it's not rendering so much at once.
Compile Error For Qbsp
#1029 posted by TdB on 2019/01/17 21:13:41
when I qbsp-compile a(non-trivial, more than 1 room)map with a detail-brush in it, and use the cmd-switch: _forcegoodtree.
I get the error message: "C:\projects\ericw-tools\qbsp\outside.cc:97: Q_assert(p->nodes[1]->planenum == -1) failed.
#### Finished with exit status 1
"