I know they aren't official. Just passing along some critique for you. I assume you'd like people to watch these since you're taking the time to upload them ... and 25 minutes is a large chunk of time for a spiral staircase video. That's all! 

Spirit: "http://www.quaketerminus.com/hosted/happymaps/curv_tut.htm"

Nah.

That tutorial looks stupid. Thanks though. 

I agree, Willem. I'm making a better video now; and it will only be 3 minutes long this time. :) 

Nice! 

Willem, I updated the description of that long staircase video to make it clear that it's not a solution.

New description is: "NOTE: I don't actually succeed in creating the spiral staircase in this video. However, I show a technique for creating a perfect circle shape. So, then you use the circle shape as a reference and trace over it with your new brushes for stairs and walls. " 

25 minutes and we don't even get the money shot? 

Alright Willem, he's a 5min version.

Note, that I don't actually use TrenchBroom to create the spiral stairs. I just show how I would do it in another editor, and then import it into TrenchBroom.

"TrenchBroom: Create/Import Spiral Stairs in 5 minutes."
http://youtu.be/LYkqpwxRQjY 

"Key bindings" feature was just pushed to their repository, an hour ago.

https://github.com/kduske/TrenchBroom/compare/master...issue237_customization#L6R330

You can see the list of all the features that will be configurable through the new Preferences->Keybinds window/frame they've recently added as well.

You can see they uploaded new icon graphics for it as well. Icon/picture of a keyboard.

---

And of course, having "key bindings" feature also allows us to define keys for functions that don't have keys bound by default. For example, "Snap all vertices" has no key bound by default in the current version of TrenchBroom, but with new version of TB I could now set a key to this, such as CTRL+N, and use it! 

Would a command that makes a selection (collection of 2 or more vertices, 1 or more edges or 1 or more faces) planar on X, Y, Z be useful to anyone besides me?

Note that this brings up the problem of axis selection again... 

Although I haven't bothered to try recompiling TrenchBroom under windows, I went back to the Linux version, and followed the steps listed in build.txt.

I discovered that wx/setup.h was not found because of an incorrect path in the build options->compiler settings->other options panel where the wxWidgets directories are set.
-I$(#WXWIN)/build-debug/lib/wx/include/gtk2-unicode-static-2.9
does not exist after I make wxWidgets, but I instead had gtk 3, so I changed it to
-I$(#WXWIN)/build-debug/lib/wx/include/gtk3-unicode-static-2.9
This started to compile fine, but when it tried to link wxWidgets I got the following error:
"Linking executable: bin/Debug/TrenchBroom
g++: error: /home/andy/Programming/wxWidgets-2.9.4/build-debug/lib/libwx_gtk2u_gl-2.9.a: No such file or directory
g++: error: /home/andy/Programming/wxWidgets-2.9.4/build-debug/lib/libwx_gtk2u_adv-2.9.a: No such file or directory
g++: error: /home/andy/Programming/wxWidgets-2.9.4/build-debug/lib/libwx_gtk2u_core-2.9.a: No such file or directory
Process terminated with status 1 (6 minutes, 25 seconds)"

These libraries are specified in the linker settings tab under other linker options. Changing instances of gtk2 to gtk3 fixes this, but then I get this error:
"ld||cannot find -lgtk-x11-2.0|
ld||cannot find -lgdk-x11-2.0|
||=== Build finished: 2 errors, 0 warnings ===|"

Any idea how to fix this mess anyone? Should I revert all the gtk3 instances to gtk2 and recompile wxWidgets to use gtk2? If so, does anyone know what options I need to use? I will have a look now, but I don't think I'm not most knowledgeable person about this kind of thing, so would appreciate help. 

seems to be the --with-gtk=2 compiler option on configure. Seems I also needed to install libgtk2.0-dev.

I'll try rebuilding wxWidgets with gtk 2 and see what happens. 

What kind of information do you need to support another Quake-engine game, such as Hexen II? Ozkan Sezer and myself might be of some help. I'm on gmail. 

managed to compile and successfully run TrenchBroom under Mint Linux. Turns out you NEED to have libgtk2.0-dev installed for it to work, though wxWidgets compiles fine if you have another version. I had 3.0 already installed and assumed it would be fine, but it wasn't. I ended up compiling wxWidgets with the following settings:
release: configure --disable-shared --with-openlgl --with-gtk=2
debug: configure --enable-debug --disable-shared --with-opengl -with-gtk=2
and then everything just worked fine.

The editor runs fine, though there are a couple of problems I've noticed.
1. text does not render properly in the 3d view, texture view or entity view. When in the texture view, applying a texture causes the names to be refreshed and they render correctly, but soon revert to being mostly not rendered.
2. This is probably just a linux mint problem, but holding alt and dragging moves the window. There might be a way to disable this in mint. 

Thanks for the info, I'll add the --with-gtk=2 option to the configure options. GTK versions are not compatible with each other, sadly. I'll put more emphasis on the fact that you need 2 and cannot use 3.

1. The text problem also happens on some Windows systems. I have no idea what the cause is, and I'm going to replace the current font rendering with texture fonts anyway. Maybe I'll find a way to fix the current font systems in the meantime.

2. You have to disable this behavior for your Windows manager. I don't know how to do it in Mint though. 

I couldn't compile the release build because there were a bunch of warnings about Source/Model/BrushGeometry.cpp using uninitialized variables. Explicitly initializing them to 0 fixes this problem. This never happened in the debug build, so perhaps it could simply be gotten around by supressing the warning/error that arises from the uninitialized variables? However, they do appear to be used uninitialized (buffer >> vertexCount etc.) so maybe it's safer to just initialize?

I had a look for how to disable the alt+drag = move window behaviour in Mint. This was the best I could find:
http://ubuntuguide.net/disable-alt-click-moving-windows-ubuntu-12-04
It hasn't worked for me in Mint yet, but perhaps I just need to restart.

Also, I'm having a problem selecting my Quake directory. I think it's probably a wxWidgets or Mint/Mate problem, because I had a similar issue when trying to set up wxWidgets in Code::Blocks (also a wxWidgets app), but for some reason it won't select any folder deeper than user/home/. My Quake dir is /andy/home/Games/Quake, but it just gives me /andy/home/ when I select the Quake folder. No idea why it's happening, but I had the same problem in code::blocks. I want to know the preference storage location so I can manually edit it to work around the problem for now. 

Hey Shanjaq,

Since Hexen2 uses the Quake engine, I believe it's already possible to make Hexen2 maps in TrenchBroom.

I believe it just comes down to a .def (or .fgd) file for the entities; And TrenchBroom allows you to define a .def file, or .fgd file.

hexen2.def download: https://docs.google.com/file/d/0B0piElswxauhWTVaeDFqUHUtTTA/edit

I copied the Hexen2 .def file to TrenchBroom/Defs/ folder, and I selected it in TrenchBroom, but TrenchBroom could not parse it correctly.

I believe necros made a converter to convert the .def file to a .fgd file. But the download links there are broken. You can see the .def converter here: http://www.celephais.net/board/view_thread.php?id=60622 

The warnings are fixed now. I'll look into the directory issues. 

For anyone who is trying to use TrenchBroom in Linux Mint, I also found out how to disable alt+drag moves window (using Mate... not sure about Cinnamon):

At the terminal, run mateconf-editor
In the configuration Editor window that appears, enter apps->marco-general and change the setting for mouse-button-modifier to "<Super>" to use the super key (probably the windows key) or "none" to disable it altogether. The default is <Alt>, but this is fucking stupid, since lots of applications use alt. 

Regarding the garbled text, could you please scroll the console all the way up and paste the first ten lines where it says whether OpenGL instancing is enabled or not? 

enderer info: Mesa DRI Intel(R) 965GM x86/MMX/SSE2 version 2.1 Mesa 9.0.2 from Intel Open Source Technology Center
Depth buffer bits: 0 < WTF!?
Multisampling disabled
OpenGL instancing disabled

I set it to be forced off because otherwise vertex mode crashes the editor.

Also, I didn't notice until I tried loading some more complex maps, but the 3d view is extremely buggy. I'm getting missing surfaces all over the place, and I think some option I tweaked made all the normal flipped or something weird like that. The depth buffer or render order also seems to be borked. It's a mess on my laptop at least. I want to try it on my Ubuntu machine that has a sensible nvidia card and see if I experience problems there. I notice you have a screenshot on the TrenchBroom site taken in Linux that looks perfectly fine, so I'm guessing it might be an issue with my lame graphics chip.

Oh, a couple of other things:
1. If I click on the window title before trying to use a menu for the first time, the menu appears briefly, then disappears and none of the menus are useable. Could it be a wx or GTK problem?
2. When I quit TrenchBroom, sometimes I get an assert fail "../src/common/glcmn.cpp(60): assert "IsShownOnScreen()" failed in SetCurrent(): can't make hidden GL canvas current"
ASSERT INFO:
../src/common/glcmn.cpp(60): assert "IsShownOnScreen()" failed in SetCurrent(): can't make hidden GL canvas current

BACKTRACE:
[1] g_cclosure_marshal_VOID__VOID
[2] g_closure_invoke
[3] g_signal_emit_valist
[4] g_signal_emit
[5] gtk_widget_map
[6] gtk_container_forall
[7] g_cclosure_marshal_VOID__VOIDv
[8] g_signal_emit_valist
[9] g_signal_emit
[10] gtk_widget_map
[11] gtk_container_forall
[12] g_cclosure_marshal_VOID__VOIDv
[13] g_signal_emit_valist
[14] g_signal_emit
[15] gtk_widget_map
[16] gtk_widget_set_child_visible
[17] g_closure_invoke
[18] g_signal_emit_valist
[19] g_signal_emit
[20] g_cclosure_marshal_VOID__OBJECTv
[21] g_signal_emit_valist
[22] g_signal_emit
[23] gtk_container_remove
[24] g_main_context_dispatch
[25] g_main_loop_run
[26] gtk_main

No idea what's going on there.

This is the graphics chip I seem to have:
VGA compatible controller : Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) (prog-if 00 [VGA controller])
Display controller : Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) 

http://andyp123.blogspot.jp/2013/03/running-trenchbroom-quake-editor-on.html

There are possibly some things I missed, and it's basically just an expanded version of Linux/Build.txt, but maybe it's of use to someone. If there are any problems with it, please let me know so that I can fix it. 

You must use the master branch for the Linux version, it has a lot of fixes. The 1.0.5 branch is pretty much broken on Linux. 

ok, so there is no depth buffer it seems. The wireframe of all brushes is always visible - even when there are other brushes obscuring it, unlike in the windows version, and if I do a simple test with three brushes, it's obvious there is no depth culling. This is probably down to my shitty video card, the drivers or some combination of the two, and I don't expect you to fix it since TrenchBroom is just a personal project and fixing shit like that for one guy running on a Linux notebook from 2007/2008 is not of the upmost importance. Still, if you have any idea what the cause might be, it would be good to know. 

ok, I'll try that and see if it works. 

That's odd, but it could very well be a bug in how I am detecting the available pixel formats on Linux. I'll look into this, so keep that laptop around ;-)