some free open source procedural texture creating tool, looks nice (you could also just use blender though): http://neotextureedit.sourceforge.net/ 

i created my aas file and it seems everytime i make a big complex map the aas wont work whether i use radiants aas conversion or the command creation way. i have a map right now that wont pull up in \devmap through quake; only through the radiant program and the aas file wont work 

Okay. So you compile the map and you don't get an aas file at all? Does bspc give you an error? If the map also doesn't load in q3, do you get an error there? 

So I hit the limit with the latest compile. At almost 15,000 brushes I should have seen it coming. Oh well.

I'd like to continue, as there is still much to construct. Would converting the existing brushwork that doesn't touch the void into func_detail fix this problem?

Thanks. 

You could convert some of it and see if the problem goes away. Might be faster than waiting for someone to tell you if it will work or not. 

And going to sleep when I get home, so I wouldn't test for maybe ten hours at least. 

I hit max map verts on ne_ruins... there didn't seem like much I could do aside from simplifying geometry. The way I got around it was to create external bsp models for ceilings in some areas. 

 

I'm going to rebuild the current map, turning it into a far smaller map (10-20%) of what I originally had planned. Down the line I'll probably try a BSP2 version, incorporating all the stuff I originally had planned. 

Just try BSP2 - it doesn't require anything special apart from these http://www.disenchant.net/utils/ tools and the -bsp2 switch.

If it doesn't work or the vis time turns out to be measured in months then just chop it down to BSP1 as you had planned - it'll only take fifteen minutes to test and could allow you to finish the map as you wanted.

And... if the vis time is stupidly long then detail brushes will solve it, but you will have to go through the map and turn the fiddly bits into func_detail.

My RRP map compiles in under half an hour, and that's slightly bigger than average. 

I thought making a map into BSP2 format was far more complex. Hmm. The map compiles fine...maybe five minutes. Just too many brushes. 

Hello everyone,
I have just installed Trenchbroom on my Mac and despite I have set correctly the path to my Quake 3 folder and defined "baseq3" inside the Map Properties window, Entities don't show up and I get a lot of errors int he console such as: "Unable to find MDL 'progs/player.mdl'", etc.

Ideas? Is Trenchbroom compatible with Quake 3 Arena?

Thank you in advance for any help. 

Quake means Quake. 

I should mention the main risk: no limits means you can just add more stuff indefinitely and never finish. 

How do I do them? I made a info_teleport_destination

and a trigger_teleport but I can no figure out how to link them in trenchbroom. Do I add a key and value? 

target key on the trigger, targetname key on the destination, and set the value the same on both of them. Each separate teleport->destination pair should have a different value. 

http://quakewiki.org/wiki/info_teleport_destination

That should help. Basically you need a key value of "targetname" for both and they both need to be the same. 

I made both the info_teleport_destination and the trigger_teleport have targetname "name"

and it does not work. 

Here is the map. I don't know what is wrong...https://dl.dropboxusercontent.com/u/10224384/teleportmaptest.zip 

and necros is correct. the key on the trigger_teleport should be "target", not "targetname" 

no no...

trigger_teleport: "target" "blah"
info_teleport_destination: "targetname" "blah" 

 

Please tell me if the wiki is broken and not allowing editing. 

when i load the map on devmap it loads then stops and go back to the main menu, there is a aas file and when i try to add bots in map it says aas not found/active 

I went through the wii and no mention of func_plat anywhere. I added target and targetname stuff retrospectively, and I cant figure out how to make the floor move or even how to define the height.