GoldSrc support please. 

 

Any idea where to download map compiling tools for mac? I can only find tools for Quake 1 but not for 2 :/ 

https://github.com/ericwa/ericw-tools/releases/

You want the "Darwin" download I think. 

Oh sorry that's for Quake 1, I misread your question. 

I'm one of those mappers who likes flipping back and forth between a map I'm working on and maps I'm referencing. Is this possible or can I only open one map at a time? 

On Mac and Linux, this is not a problem. On Windows, TB is a single document interface app, meaning you can only open one map at a time. But to offset this, you can open multiple instances of TB for different maps on Windows. 

Thanks. 

I usually have 2 TBs open, you can copy-paste from one to the other, so it's basically the same as having two maps open. 

I got a notification that my feature request (targetname autocomplete) was closed on the issue tracker. I assumed it was being put on the backburner for the drive to expand the range of supported games. So you can imagine my surprise and delight to upgrade to the release version and find it present! It's already proved valuable in creating one short map hack, so thank you for this and all the rest of the work on the editor. 

He implemented it, I only reviewed it. 

With bugfixes and minor improvements: https://github.com/kduske/TrenchBroom/releases/tag/v2.0.1 

But the info_teleport_destination model is displayed about 32 units underneath the the entity's bounding box. 

No that's normal. Set in the FBD that way I believe. Not sure why. Don't go by the model. Go by the Bbox and you're good. 

n/t 

One thing the QuakeC does is moves every info_teleport_destination 32 units upwards from its starting point. I guess that the bounding box is accounting for this but the model isn't/can't? 

Is there no hack to bring the model in line with the bbox? Kind of annoying to look at. 

There might be a sensible way, if it bugs you enough to accept a local fix you could: create a copy of the player model that's raised by 32 units, then reference that copy of the model in the FGD definition of info_teleport_destination. 

I’ll probably try that. Thanks Preach. 

or would you prefer I rather make a post in the issue tracker?

It's not too important, just a separate memory if you will for "open wad" vs "save map"

I find that I reflexively save a map only to find it in my wad folder from when I opened the wad for it.

Still loving TB2. Thank you! 

Create an issue for it. 

brings a couple of mostly minor bug fixes: https://github.com/kduske/TrenchBroom/releases/tag/v2.0.2 

Is the func_door_rotating in Hexen 2 supposed to be set differently as they are in other map editors? I cannot seem to figure it out using the origin brush. 

Ok, I figured it out. One must use different qbsp to make rotating door to work. 

I think I've seen some screenshots of editors that enable you to toggle entity visibility based on their difficulty level/dm spawnflags. I'm trying to finish up my map by making it work in dm too, and I'd like to select all the triggers that don't have the "not in deathmatch" spawnflag set to them, so I could assess whether there are still some triggers that need to be disabled for dm.

In fact, it would be nice to generalize the whole idea: Whenever I select a huge amount of entities (typically with Ctrl+A) and have the entity tab open with all those "multi" value fields and spawnflag checkboxes with squares instead of checkmarks, it would be nice to filter my selection by let's say right clicking the "multi" value field next to the "target" key for example, and then a checkbox dropdown menu would appear at the pointer, where I could select all the values the entities of which I want to manipulate. The same principle would apply for the spawnflag section and maybe even the color section.

So I have two suggestions:

1) Add four more checkboxes in the View "pop-up" menu:
"Show easy skill entities"
"Show normal skill entities"
"Show hard skill entities"
"Show deathmatch entities"
or something along those lines.
2) Implement the above-mentioned idea of filtering a selection

Ok, I lied: a third bonus suggestion:

3) Add one more checkbox in the View "pop-up" menu:

"Show group entities"/"Show groups"/"Show group entity bounds"
or something along those lines. :)

Pretty please! ;; It's always such a hassle to manually hide my groups when everything else can easily be hidden with the click of a button.