You can add an issue on github, though. 

Thanks for the response. 

Stupid question, but is this a new feature in TB2? What is it for? It turns out it gives me a workaround for the copy+paste bug, but I am just curious as to what it was actually intended for. 

 

in 3, 2, 1 ...

Currently I have TB2 working on my Linux Mint computer, which I installed using SleepwalkR's instructions from earlier in this thread (sorry for the extensive quotation):


You need to compile it yourself. First you need to get the sources using git. Open the terminal and cd into some directory under which you want to have the sources. An example would be the ~/Documents directory. You do not need to create a sub directory for the sources, git will do this for you. Make sure you have git installed:

sudo apt-get install git

Then clone the sources:

git clone https://github.com/kduske/TrenchBroom.git

This will create a directory named "TrenchBroom" under your current directory, so if you did cd into ~/Documents, the sources will be in ~/Documents/TrenchBroom. cd into that directory.

Now you have to switch to the branch that contains the actual sources for TB2. You are currently on the master branch, which contains the TB1 sources.

git checkout develop

It should answer with a message such as this:

Branch develop set up to track remote branch develop from origin.
Switched to a new branch 'develop'

To ensure you're on the right branch, issue the "git status" command:

git status

It should answer with a message such as this:

On branch develop
Your branch is up-to-date with 'origin/develop'.
nothing to commit, working directory clean

Now read the build instructions in the Build.txt file and follow them. If you run into any problems, report back.


This is the only version of TB I have on this current setup; I have not installed TB1 on this computer since installing the OS.

Now I would like to install TB1 (so that I can use it for things that do not currently work in TB2), but I am not sure how to go about it. I am scared of e.g. following the instruction on Andy's Blog and replacing things that are currently up-to-date with older things... or something (I cannot really articulate my fears more precisely as I have no real idea how any of this works).

So given that I've done everything SleepwalkR describes in the post quoted above, what should I do to install TB1?

PS: Sorry for the barrage of questions from me in this thread. I do try to figure things out for myself first, but end up just getting more and more confused...

(PS: SleepwalkR, the grouping function is a brilliant addition! Thank you.) 

The build instructions for TB1 I found on github are very confusing to me compared to how easy it is to compile TB2 from git. I did attempt it months ago, but it gave me no joy. 

Also, TB1 doesn't really work well on Linux 

Can I compile TB1 with cmake, or is it necessary to use Code::Blocks? And do I need to install an older version of wxWidgets than the one I used for TB2? Because those seem to be the two points where the build instructions for TB1 are different from TB2.

(I would really like to have TB1 on this system as well, because there are things I currently simply cannot do with TB2, such as precise clipping to create convex and concave shapes. My plan is to use both versions of the editor in the mean time, until the bugs in TB2 are fixed. Or is there something else that runs on Linux that I can use a complement to TB2 in the mean time?) 

SleepwalkR wrote earlier that you can do this with the Tab key, but either I've misunderstood something, or it is not working. When I have two panes open (a 3d pane and a 2d pane), then pressing Tab does not seem to do anything. I was expecting it to change the 2d view from top-down to side view and front view.

Have I misunderstood? 

 

 

Just rebind it something else. 

Just looked at keyboard preferences, and it wasn't bound to Tab by default, but to Space. That works fine. Thanks for suggesting rebinding it; that steered me in the right direction. 

Can I compile TB1 with cmake, or is it necessary to use Code::Blocks? And do I need to install an older version of wxWidgets than the one I used for TB2? Because those seem to be the two points where the build instructions for TB1 are different from TB2.

To compile TB1, you do need to use Code::Blocks and to use the older 2.9 version of wxWidgets, afaik.

Note, the TB1 build instructions don't have you install wxWidgets 2.9, it's just downloaded, extracted, and compiled. I would follow all of the steps in an isolated directory like ~/tb1 so you don't mix up the copies of wxWidgets, but other than that it should be safe and not conflict with TB2. 

Those are exactly the things I was wondering about. 

I changed the binding to space for exactly that reason ;-) 

Hmmm... Not to get to far off the main thread topic, but on Linux I like to use TrenchBroom 2 compiled from the develop branch along with NetRadiant compiled from Xonotic's git.

Also on Linux I'm trying to like Jackhammer, but as great as it seems its TOO Hammer/Worldcraft for me.

From my recent experiences swapping the same basic quake maps between TB2 and NetRadiant I've yet to see any ill effect from editing some part of the map in one and loading it back into the other editor. They seem to compliment each other very well.

@total_newbie as long as you have the dependencies installed(read COMPILING) compiling NR is easy as inputting 3 lines into a terminal.

git clone git://git.xonotic.org/xonotic/netradiant.git netradiant
cd netradiant
make

See if that fills your need until TB2 alone is a bit better for you. I now prefer TB2 over all, but still like to use NR from time to time for making fast rocks or spheres with its brush tools or for working with a q3map. 

Will definitely give that a try soon. I can also see myself eventually switching to TB2 only, but this is the kind of interim solution I'm looking for.

Thank you very much, once again! 

Hey guys, just to let you know: I'm putting TrenchBroom development into hiatus for a couple of month. I have to finish my PhD thesis and TB2 distracts me too much. I'll pick it up again as soon as my thesis is submitted, which should happen in the fall.

I was hoping to release TB2 before this time, but unfortunately I didn't make it. I'll still be around and maybe I'll do a bit of work here and there, but there won't be a release until the fall, I'm afraid. 

Make TB2 your thesis! Problem solved!

We can call you Kristian Duske Doctor of Mapology 

I second that! lol. At least the TB2 develop branch functions pretty well in its current state. Good luck with the thesis. 

Well, let's just say if I had put half the amount of work into my thesis that I put in TB2, I would have been finished in three years, not five ;-) 

 

A very understandable decision. One request though, since I don't know anything about compiling. Could you put an installer up for the current version of TB2? That way we can already start playing with it :)

Or maybe someone else can make a Windows installler from the develop branch? 

If I publish the current state, then I would probably get a lot of issue reports and questions, drawing me back in. I'd rather not. Sorry.