trying to fix small things like this, that most people will never notice.

but they will notice if it's not fixed. :P 

The details are everything.

If there's one misaligned texture, people will think you're sloppy. If there's one overlapping-brush-2-brush-flicker, they'll think less of the map as it ruins the Sustainment of Disbelief.

Even the smallest detail (to chamfer or not to chamfer) can make a big difference in the overall fluidity and coherence of that area.

The details are everything. 

It's easy to get obsessive and waste a lot of time getting everything perfect.

A good release stands on its own, warts and all. 

It's easy to get obsessive and waste a lot of time getting everything perfect.

I'm trying for not too many warts.
It's getting closer. 

Do I just put the brushes in an empty map, run bsp and light and then place it in a different map using info_notnull or something like that? 

Do I just put the brushes in an empty map, run bsp and light and then place it in a different map

yes, be sure to place the bsp in your progs folder.

using info_notnull or something like that?

i use the Quoth mapobject_custom entity, has mangle and such.

At least thats what i do, not sure if vanilla progs handles this so easy.. 

yes, be sure to place the bsp in your progs folder.

you can use progs/map.bsp or maps/map.bsp and both will work for the model path. only sounds are hardcoded to be in sound/xxxxx 

in fact, it's generally good practice to put any external bsps in a subfolder so you can keep things clean. unless you want to use a pak file in which case it matters less. 

Okay, thanks. Now, how do I place the external bsp into my map? 

how is the newest remake going? 

Trying to open some .map files saved with WC in Radiant but keep getting.

parse error at '[': expected '#number'

The maps are also BSP2 sized.
GB, you have experience with this? 

WC uses a different .map format from Radiant.

I don't know if WC has other limits that could possibly be BSP2 related; the only thing I think I have heard is that it can't properly display maps that are bigger than 8192x8192.

There is a converter program by a person called Scrama, I believe, you might have some luck using the quakeone.com forum search. It is somewhat obscure though. You will also have to convert the texture wads between WC and Radiant. :-s

If it only needs to be done once, using some converter is acceptable, but daily WC <-> Radiant conversion in any halfway productive environment, eg in a team setting, isn't very good for the workflow. I have lovely memories of this problem from RMQ. 

I thought the only difference was .rmf
yay! 

It's for something of a spinoff map... 

I'm not 100% and can't check right now, but I think TB will load this map fine and save it as a standard .map file. Although the texture alignment info will be fucked, naturally. 

Actually, I just remember I did use TB for exactly this in the past... must have been some hazy late night troubleshooting, haha. I'll try that! :) 

That is good to know. 

Actually, it's still not working in Radiant, exact same issue... like I said, I was probably only half awake, lol. 

I search "worldcraft" I get a dozen of useless pages about World of Warcraft. Sigh. 

thread: http://quakeone.com/forums/quake-help/servers-coding/3997-half-life-bsp-q1-5.html

dl: http://scrama.3dn.ru/load/0-0-0-24-20 

So it still exists? Someone should archive that :-p 

not sure how to extract textures from those rmf files though. But you probably have access to the wad3 files. 

And the new one isn't in Russian :P
http://quakeone.com/forums/quake-help/servers-coding/3997-half-life-bsp-q1-8.html#post49563

I'll put it in the wiki :D 

I'll get out mah ruler! 

I have tons of maps and map scraps that were created in Worldcraft (1.6) and I've never had any problems opening them in Netradiant.