Accidentally slipped in a CLIP face perhaps? 

Can't be... I have just 2 func_groups and one is rock and one is sky... 

Anyone know what steps I need to follow to do a q3bsp for Darkplaces? Is it just a mapper of using a regular q3bsp compiler and feeding the results into DP? 

I believe it is actually as simple as that. You make a Q3 .bsp, shaders and all, but use Q1 entities (use actual detail brushes instead of the hacked together func_details!). The .map format is slightly different iirc, so you'll need to make sure you're using q3's .map format so the compiler will accept it! 

I mean q3's .map is slightly different than q1's .map! 

aye, i remember there is directory paths and such in there... i think i can get by with using aguirre's map converter which goes both to and from q2 format (which I think is the same as q3 map format?)

as for shaders............. yeah... no clue about that as i never made a q3 map. i guess i'll track down a q3 compiler, i think q3map2 is the current standard? and go from there. 

Why does most Quake-based editors use colored boxes for entities? I can understand for things like lights and whatnot, but I think visual aid is important too like knowing which direction the info_player_start and monsters are facing on the spot. 

What's the difference between them? 

Pika: I wouldn't say "most". It depends on which editor you use; some can be set to show either boxes or 3D models. In Radiant, for instance, it's simply a matter of editing the def file to include paths to the individual mdls.
While it's nice to have the models shown in the editor, it can have disadvantages depending on the implementation. In Quake, it's all about the entities' bounding boxes, and if an editor displays ONLY the model, correct placement becomes awkward. The result is monsters stuck inside walls or items falling out of the level.

adlib: Func_wall is a dynamic map entity which can be used to block off areas on certain skill levels or game modes; it can be removed mid-game, and it doesn't block light and vis. It also starts a texture animation when triggered if the right one is applied.
Func_detail is only for the compiler. It creates detail brushes/architecture that is disregarded when processing the visibility information and is turned into world geometry afterwards. It's a means of speeding up the VIS process, and it needs compiling tools that support it, otherwise you'll get a lot of disappearing stuff in-game. 

Q2 and Q3 (and Q1) .map are different too! Q2 has some extra fields for surface properties per face which Q1 and Q3 don't! 

ok, it was very simple actually, compiled, used quark to convert the map to q3 format (literally just copy/pasted from the q1 map into a new q3 map)

q3map2 is actually much worse than the q1 compilers in terms of handling insane geometry. looked like maybe 5% of the faces were missing in the q3 map.

oh well, looks like it's time to call it. it was a fun experiment, but just not meant to be... maybe i'll use this mesh for a doom3 map or something. 

Please don't tell me you were using the brush version of your terrain in the q3 version. 

Going for Q3BSP and not using meshes would seem a little pointless. BSP is not the way forward for terrain. 

i never made a q3 map before so.... i wouldn't know.

ericw told me about some misc_model thing though... which is apparently some magical way of turning a model into world geometry! 

-haltOnLeak

Stop compiling immediately after writing the pointfile and exit with error code != 0

This lets people detect %errorlevel% in batch files.

Thanks! 

because it was annoying me:
https://github.com/necros0/ne_q1CompilingGui/tree/master/Compiling%20Gui/Compiling%20Gui/bin/Release

just grab the exe file. hard codes the START /B /I /WAIT /BELOWNORMAL into all the compiler commands, so everything always has below normal priority.

At some point, i should probably make some per-compiler thing to choose what priority you want, but... meh, this works. 

I was under the impression that you can't tell if there is a leak until you traverse the entire tree, thus why QBSP doesn't end early when it finds a leak. 

when qbsp writes the leak file, is that not 100% a leak? usually what I do is I watch the output until it says 'writing point file' then once it's done, i Ctrl+C and plug the leak. 

Oh, I see what you're asking for now, ignore me.

I was thinking you just wanted time savings by ending the compiler earlier, but most of the hard work has already been done. QBSP has fully processed and portalized the tree when it detects the leak... but you just want an option to return an error to the console at that point so your batch file can detect it. 

that and so i don't have to actually sit there and watch the output (which I sometimes miss) waiting for 'leaked!' :P

Disregarding the current map, I rarely seal until the end where I do a leak plugging session. But it gets tiring to have to watch console output hoping it won't leak. Dunno if others do it that way or not though... 

Yeah, I don't bother to seal until the end of making a map, but it's really rare for me to get leaks when I don't expect them. 

Yeah, I don't bother to seal until the end of making a map, but it's really rare for me to get leaks when I don't expect them. 

I never work on a map that leaks. 

Sometimes you have to, Rick. Large scale retooling of areas or you're trying something out, etc. Leaks aren't an issue until you want to release the map, really. Only thing they do is slow down your lighting builds... 

I prefer to keep a map sealed as well.

There are so many ways a map can get weird phantom leaks, I like to keep the obvious ones plugged.

For tests I do the big box method - a giant box or two to remove areas from the compile, or just plug holes while I put other areas together.

Really it just depends on which brand of OCD you subscribe to.