If you want me to keep at it, how am I supposed to fix all the vis errors? 

 

---- WVis 2.31 ( XT build 1.01 ) ----
Modified by Bengt Jardrup
Multithreading enabled by Willem
Further mods by Tuna, rebb
Detail code by Alexander Malmberg <alexander@malmberg.org>

File: Bre01.bsp
LoadPortals: couldn't read Bre01.prt
No vising performed. 

Found out what was happening, but there's a bug when near the waterfall, I get this odd HOM bug. how do I fix it? 

You could always post some screenshots of the area and maybe a wireframe view of the area? 

I'm thinking about restarting my map. sorry for disappointing you guys. :(
http://i.imgur.com/6DhWfpp.jpg
http://i.imgur.com/xlNQjBP.jpg
http://i.imgur.com/1JZbjsd.jpg
http://i.imgur.com/dInzwny.jpg
http://i.imgur.com/OYdaLCb.jpg 

You should make the map file available to one of the more experienced mappers here. I'm sure someone can tell you how to fix these problems. Maybe ask negke or necros, they are good at diagnosing technical problems. 

May I suggest to change the waterfall to something more in line with the red sky ? Bloodfall, or lavafall, with a river of hot blood/lava around the crates...

Would feel more "out of this world" ! 

Best thing to do is check to make sure vertices in the affected area are grid snapped. Make sure there are no mixed faces. Also is the map sealed off from the void? Sometimes a map which is unsealed has weird vising issues, plus be careful with brush entities as vising can sometimes occlude them in areas you definitely don't want them to be occluded from.

SW has a nice idea too, one of more experienced mappers may be able to diagnose the problem. It make be a simple case of rebuilding a few brushes in the area also. 

If anyone wants it, grab it here:
http://www.mediafire.com/download/6adm32byjk3a1sl/bre01_old.zip 

I'll have a look too, maybe its a problem with the tools. I would also recommend compiling the map with TyrUtils and see if the problem persists. 

 

 

What texture were wads used? Some of thos I can't find. If you make the "bad" bsp available they can be extracted.

One thing I noticed that seems a little weird is that, in the rock areas around the waterfall, you have "tri-souped" using brushes with non triangular tops. Looking down from the top I would split these into two triangular brushes. 

No matter what happens, keep going. Nobody expects miracles in your first map and neither should you - this is your first test bed for ideas. 

No matter what happens, keep going. Nobody expects miracles in your first map and neither should you - this is your first test bed for ideas. 

plugging bsp holes and bug fixing takes a while. I had problems where entire areas would scrunch into a mess with weird shapes.

I ended up redoing whole areas and brushes. Also I found that when you have too many overlapping brushes it tends to cause serious problems. 

offcut.wad by sock (found in ivory tower pak)
Quake101.wad
kdmtex.wad found here:https://www.quaddicted.com/webarchive/kell.quaddicted.com/
idbase_ultimate.wad 

https://www.quaddicted.com/webarchive/kell.quaddicted.com/ 

Make sure to go to Map Properties, then check the "Force integer plane points" check box. 

It keeps on error20.
E
ven a big box around it keeps args on the non-convex face. I can't compile it.
I'm afraid there are too many shape-brushes that are used as hull-brushes. Then there's always a leak-error. 

I used TxQBSP 1.13 to compile the map, and I thought it worked fine. 

>>> Parts of the map are outside the 4096 limit.

txqbsp_xt generated 33 warnings, mostly point-off-plane but some r_cutnodeportals also