not too complex, just too messed up and off grid. qbsp probably shows warings too? 

in an asshole-esque manner...


you should probably post further mapping questions in the Mapping Help thread. 

MAPPING HELP FOR... oh thx Drew. 

and post a link.

Also:

What vis.exe are you using? Is it made by AguirRe? AKA Mr Bengt Jardrup? If it doesn't say that in the text when you run the tool, its just not good enough.

We will get this fixed, if you persist.

To get the tools, google "aguirre quake" And it will be the top link. ;) 

Canadian Royal whiskey - OMG. OMG - Canadian Royal Whiskey - Oh My God! - Im sooo00 drunk :S 

if you dont know how to run the tool, then tell us. Cause when i first started I didnt know, you know, I was just using WC process window. Which is bad. Mkay. 

I've been using the vis that i got from this site that allows you to use multicore processors to compile vis. Also, I use QuArK to make and compile maps if that matters any 

I tried deleting some brushes that i used for architectural details on the ceiling of the messed up room and it fixed the vis problem somehow - It still works fine even after expanding the map beyond that room. 

I tried deleting some brushes that i used for architectural details on the ceiling of the messed up room and it fixed the vis problem somehow - It still works fine even after expanding the map beyond that room. 

> Also, I use QuArK to make and compile maps if that matters any

Ladies and gentlemen, I think we have found the source of the problem. Quark is evil in that it uses floating point where other Quake tools - including build tools - use ints. What this means is that brushes that line up correctly in Quark may not do so in anything else owing to rounding errors.

The Quark website itself contains a heads-up about this: "Unique high accuracy of brush- and texture-alignment in map-editor. (May require special build-programs)". 

"Unique high accuracy of brush- and texture-alignment in map-editor. (May require special build-programs)".

So it's broken then? Having 'high accuracy' for Quake is completely unnecessary, it'll only introduce errors like the one mentioned. 

Yeah, "broken" in other words. ;)

I described Quark as "the Lotus Notes of Quake tools" once, and I still stand by that description today. It does a little bit of everything but none of it very well, and more often than not in a way that's incompatible with other tools. 

i use quark a lot but never for mapping. it's wide variety of tools and accepted formats is great for converting stuff though.
the model editor in 4.07 is pretty decent for previewing models too (except it doesn't work for grouped frames) since it loads up so quickly. 

Using it for conversion, but couldn't get my head past the interface, so ended up using a pile of buggier and archaic tools.