News | Forum | People | FAQ | Links | Search | Register | Log in
The TrenchBroom Level Editor
Today I am releasing TrenchBroom 1.0 for Windows and Mac OS X. TrenchBroom is a modern cross-platform level editor for Quake.

Features
- True 3D editing, no 2D views required
- High performance renderer with support for huge maps
- Vertex editing with edge and face splitting
- Manipulation of multiple vertices at once (great for trisoup editing)
- Smart clip tool
- Move, rotate and flip brushes and entities
- Precise texture lock for all operations
- Smart entity property editors
- Graphical entity browser with drag and drop support
- Comprehensive texture application and manipulation tools
- Search and filter functions
- Unlimited undo and redo
- Point file support
- Automatic backup
- Support for .def and .fdg files, mods and multiple wad files
- Free (as in beer) and open source (GPLv3)
- Cross platform (Windows, Mac OS X and Linux supported)

Check out a video of TrenchBroom in action here.

You can download the editor here.

If you would like to give feedback, please do that in this thread. If you find a bug or have a feature suggestion, please submit them at the issue tracker.

If you are wondering where the Linux binaries are then sorry, but currently there are none. The Linux version has a few problems which I could not fix before this release. I will get working on those right away so that the Linux version should be available in a couple of weeks, too.

Finally, I would like to thank necros for all his work over the past year. Without his tireless efforts, TrenchBroom would simply not exist. Or it would suck.

Alright, enough of this. Have fun with the editor!

Update: 2.1 here:
https://github.com/kduske/TrenchBroom/releases/tag/v2.1.0-RC1
Features "cool shit".
First | Previous | Next | Last
Thanks For The Response, Ericw 
and thanks for the package search link/info.

Do you mean build TB2 from source, as opposed to using the deb package? Would that bypass the libstdc++6 issue? It'd be great if that would mean not having to do a fresh OS install.

However, I'm not entirely sure how to go about it. I see that clicking on "source" on the TB home page directs you to the TB github page. Does this mean I'd need to use github to build from source?

I used to install/update TB2 via github when it was still in alpha, but around the time of the first beta release SleepwalkR wrote about having switched to git flow, and I don't really what that is or how one uses it (I barely understood how to use github before the switch). Or is git flow just something used for the intermediary builds? 
 
Is it possible to do one of the following in Trenchbroom?

(1) move the camera to a location specified by xyz coordinates.

(2) select the entity/brush closest to some specified xyz coordinates.

----

Compile tools and the quake engine often spit out errors in the form or ABC went wrong at coordinates xyz, but I struggle to find xyz in the editor to locate the problematic brush/entity. 
In TB 2 
Menu > View > Camera > Move Camera to ...

You can't select an object closest to a location however. I'm not sure how accurate that would be, anyway. If it's not unambiguous, it would be misleading. 
 
Move camera to ... is perfect, thanks! I can do the selecting myself. 
Problems With TB 
actually I cant open trenchbroom for basic_string error:
http://prnt.sc/ckez9f

exists a solution? 
What OS And Version Etc. 
 
Os X El Capitan 
 
And What Version Of TB. 
 
The Last Version Before TB2 Beta 
 
That''s No Longer Supported 
Sorry. Use the betas. They are more stable than the older versions. 
@total_newbie 
Sorry for not responding earlier..

Do you mean build TB2 from source, as opposed to using the deb package? Would that bypass the libstdc++6 issue? It'd be great if that would mean not having to do a fresh OS install.

Yes, I meant building from source as opposed to the deb package. I *think* it would bypass the libstdc++6 issue. However, if you did upgrade Linux mint, isn't there an "upgrade" feature in the OS that would avoid having to do a fresh install? Ubuntu has that.

Building TB from source on Linux is a bit involved because you need to patch and compile wxWidgets yourself. TB's instructions are good though.

Re: git flow, the current branch is "release/v2.0.0". So if you are building from source, you would do a fresh git clone, then "git checkout release/v2.0.0", then follow the build instrutions in Build.txt

If you're not really comfortable with building from source, upgrading the OS is probably the way to go, but I'm not sure what to suggest really. 
@ericw 
Sorry for not responding earlier..
No worries; thanks for responding -- I really appreciate it!

This clears up a lot. I have built TB2 from source before, back before the release of the first beta, and I seem to recall having to compile wxWidgets back then too. As long as I have good and clear instructions I should manage ... I think. I'll probably screw a few things up along the way and I might ask a few more stupid questions here as a result, but should get it in the end.

Speaking of stupid questions, I have a couple already:

TB's instructions are good though.

Are these the instructions you mean?

do a fresh git clone
Errr, how do I do that again? This is the part where you basically download all the files you then later use to build the programme, right? I remember having done it, but I can't remember how one does it, and Build.txt doesn't seem to say. 
 
Are these the instructions you mean?
No, those are the ones from the "master" branch which is outdated. here is the current build.txt.

Errr, how do I do that again? This is the part where you basically download all the files you then later use to build the programme, right?

Run these commands in a terminal: (this assumes you don't currently have a TrenchBroom subdirectory in the current directory)
git clone https://github.com/kduske/TrenchBroom
cd TrenchBroom
git checkout release/v2.0.0


The "git clone" is more than just downloading the source code, it downloads every branch and change made to the TB source code. It initially gives you the "master" branch in the TrenchBroom directory, which is outdated code, which is why the "git checkout" command is needed to switch to the latest code (release/v2.0.0). 
Thank You! 
That's very clear.

I'm afraid I'm about to post a response to your offer for help in the Mapping Help thread that might make you lose your faith in humanity... 
[CMD]? 
OK, so I've finally installed Firefox on my computer and the help file now displays properly. It mentions a [CMD] key that I believe is found on Macs. The Windows equivalent is [CTRL], correct?
SleepwalkR, is it feasible to make it so that the help file automatically displays the right key depending on the user's OS 
That's A Bug 
Please file it on github. 
OK 
 
Selecting And Editing All Brushes Within A Group? 
When I double click on a group of brushes, I am able to select and edit the individual brushes within that group (e.g. by holding shift and extruding contiguous selected faces).

If I double click on a group and press Ctrl+A then it selects all of the brushes in the group, which is the behaviour I would expect. But then I don't seem to be able to edit the brushes in the same was if I had selected them manually. Is this intended behaviour? 
No 
Sounds like a bug. 
Clipping Again 
When placing clip points in 3D view, could you add an option to trace/glue the points onto the selected brushes only (i.e. the ones about to be clipped). Currently, if there are any obstructing, non-selected brushes the clip points will instead glue to their surfaces, which is usually not desirable. 
 
Im working on reproducing some vert manipulation errors and I'll add it to Pritchards issue report.

Basically, theres times I move verts with arrow keys and the verts deselect. I then have to select them again and can continue moving in my intended direction.

Additonally, "snap to integer" appear broken. Any attempt to "snap to integer" crashes.

This is all on 2f3c498. 
A Follow-up... 
...to the conversation on the "best editor" thread:

SleepwalkR said: "You can select the axis yourself, it's the one you have moved the farthest distance on. Why is that difficult to handle? I'm asking out of genuine interest - maybe I can improve it?"

Maybe a better way would be to select either x or y axis beforehand with a simple toggle key like [ALT] does with the z axis? 
All My Axes Live In Texas 
iirc you can hold shift to lock the axis you're moving the brush. 
#2308 
That was mentioned in the best editor thread. That only applies once you've already begun moving the vert. 
That's What I Meant 
Maybe instead of holding [SHIFT] AFTER you've started dragging a vertex, it would be best to have two different keys to select the axis BEFOREHAND, like for example [SHIFT] for the x axis and the >/< key next to it for the y axis. Or maybe even simplier and more intuitively, [X] and [Y] keys. The latter would imply using the [Z] key for z axis lock, freeing [ALT] for other context-sensitive manipulations. Sleep, does that sound good to you? 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.