Cant wait till this is out! Those new brush tools look stellar! Keep up the mad work SleepwalkR! 

So, I've just installed TB again on my Linux system (Linux Mint) after a break of several months, using (as before) this guide: http://andyp123.blogspot.de/2013/03/running-trenchbroom-quake-editor-on.html

Said guide works perfectly, but I understand nothing of it (I just follow the instructions and Ctrl+C & Ctrl+V the commands, but have no idea what any of them really do).

Keeping in mind how utterly tech un-savvy I am, would someone be so kind as to explain how I can switch from what I have now (TB version 1.2.0 Build 460, according to Help --> About) to TB2?

(I know it is still unfinished and probably buggy, but so is TB1 on my system -- and if I were to use TB2, I could maybe give SleepwalkR some meaningful feedback, as opposed to complaining about a version of TB that is no longer going to be updated...)

Thanks in advance, and thanks again to SleepwalkR for creating and constantly improving TrenchBroom!

(By the way, is this the right thread, or should this go in Mapping Help?) 

Feedback for the linux version of TB2 would be very appreciated, as it's practically untested right now. It does build and run, but that's all I have tested.

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. 

Thank you for the quick and detailed response, SleepwalkR. However, I am possibly even more of a layperson than you assume...

I have already installed TB using the guide I linked to in my previous post (similar to your instructions, but even more detailed), so I am skipping ahead to this part of your instructions:

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

When I do that, I get the following:

error: Your local changes to the following files would be overwritten by checkout:
Linux/BuildNo
Please, commit your changes or stash them before you can switch branches.
Aborting

Help? Please keep in mind I have no idea what it means to commit or stash changes or how to do so. This entire git thing is a mystery to me... 

or if you want to save bandwidth: git reset --hard
But be aware that this might delete stuff depending what you put inside the directories.


I just built and when I clicked through the options the shortcuts had a conflict (Ctrl-I was assigned twice).

Would be nice if the default building would exclude the tests, it took long enough already. :o) 

As Spirit said, please just follow my instructions and don't skip.

Spirit, yes, agreed. 

Thanks, sorry -- didn't realise I was being an idiot. :-/ Am following the instructions word for word now. It's taking a while. Will report back whether successful or unsuccessful. 

I get the following if I try to run
cmake .. -DCMAKE_BUILD_TYPE=Release
or
cmake .. -DCMAKE_BUILD_TYPE=Release -DFREETYPE_INCLUDE_PATH=/usr/include/freetype2/freetype
as per Build.txt:

cmake .. -DCMAKE_BUILD_TYPE=Release -DFREETYPE_INCLUDE_PATH=/usr/include/freetype2/freetype
-- Build type Release
-- Using static wxWidgets library
-- Could NOT find FreeImage (missing: FREEIMAGE_LIBRARY FREEIMAGE_INCLUDE_PATH)
-- Compiler is GNU
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
FREEIMAGE_LIBRARY (ADVANCED)
linked by target "TrenchBroom" in directory /home/totalnewbie/Desktop/TB2/TrenchBroom
linked by target "TrenchBroom-Test" in directory /home/totalnewbie/Desktop/TB2/TrenchBroom

-- Configuring incomplete, errors occurred!
See also "/home/totalnewbie/Desktop/TB2/TrenchBroom/build/CMakeFiles/CMakeOutput.log". 

sudo apt-get install libfreeimage-dev

What is the output? 

Thanks for the response, SleepwalkR! I ran the above command and it installed libfreeimage-dev. I guess I must have accidentally not installed it initially -- no idea how I missed that step (since I seem to have done everything else).

I'm running the cmake --build . command right now, and it all seems to be going well (but it's taking a while).

Sorry for the stupid questions and mistakes. I am just so out of my depth -- I feel like a drunken elephant that someone is patiently trying to teach to shuffle cards. Or something. As in, no matter how good the instructions and how patient the instructor, I am bound to screw something up anyway. 

total_intermediate 

I just crashed the TB1 renderer alt-tabbing from Quakespasm, and got this:

http://www.quaketastic.com/files/TB666.PNG

Also, TN - this is how everyone starts. Don't be scared of making mistakes; that's how you learn. 

Hehe, I am actually planning a name update at some point (once I finally release something*), albeit in a slightly different direction ... but I really like your suggestion!

*That's going to be a while still, at the rate I'm going (currently aiming to break a six month hiatus ... will probably need to re-learn everything I learnt six months ago when I touched a level editor for the first time in my life. I have been a non-mapping mapper for far longer than I have been a mapping mapper).

And thanks very much for the kind words of encouragement in your second post, ijed. 

makes the devil's maps - what else is new? 

Thank you for your help, SleepwalkR. I seem to have a working (or at least semi-working) TB2 installation now.

It looks very snazzy, but map entities oddly appear as solid coloured blocks, the measurements of my brushes are not shown (an issue I had with TB1 as well) and I had the same issue Spirit mentioned above (Ctrl+I is assigned to both Controls>Edit>Select Inside and Isolate Objects ... Not sure how many of these are issues I should report on your github issue tracker thingie and how many are just due to my doing something wrong.

TB2 also did not recognise that an old .map file I had previously worked on with TB1 is a Quake map, and under Quake it says "Game not found". Do I need to point it to where my id1 folder is, or does it want an fgd file or something? 

usually means you need to locate your quake folder to see them. Probably will make your old maps work too 

Thanks for the explanation. In the mean time, though, I pointed TB2 towards TrenchBroom/build/Resources/games/Quake/ and now it does not allow me to change it again (e.g. to my id1 folder); the path now seems set in stone, even when I close and re-open TB. My entities are still blocks.

Oddly, the Ctrl+I key conflict keeps coming back, even though I keep fixing it (as TB2 keeps ordering me to do). 

hmmm...

view - preferences - choose game? 

I have changed the default key binding for Select Inside so the conflict should be gone now. You can update your sources like so:

git pull

Then rebuild, just like before

cmake --build .

As for the missing models, you have to point TB2 to the directory where you have installed Quake, not to it's own Resource folder.

But it seems that there's trouble with overwriting the preference settings on your machine. It works on my Ubuntu VM, but I'll check with my Linux Mint VM when I get the chance. 

Rebuilding TB2 now. Do you want me to report these things on the issue tracker, SleepwalkR? Or should I post here first?

Since I know so little, I am not always sure how to distinguish between real issues and my own lack of knowledge and experience. 

 

So far, I am having some problems with the clip and vertex manipulation tools -- they both tend to crash the programme (the latter is an ongoing problem for me in TB1 as well). Steps to reproduce: select a brush/brushes --> try to clip or drag vertices around --> TB quits suddenly and without warning.

Then, don't know if I'm missing something, but as noted above, I don't see the measurements of my brushes (which is a problem for me in TB1 as well). In TB1, the measurements would still display in a brand-new map, but upon closing and re-opening a saved .map, I would see no measurements (or entity labels). In TB2, I do see entity labels, but do not
see measurements (even in a brand-new .map file).

The key conflict is of course now resolved, but I still cannot change the path to Quake I had previously erroneously specified (I know you're aware of this; just putting it here for completeness's sake).

Just some comments and a possible suggestion:

The new system for creating brushes had me stumped for a while, but now that I see how it works it seems really nice. Need to play around with it a bit more to get the hang of it and unlearn my TB1 habits, but I do think this is a great development. I have so often accidentally created brushes in TB1; this will give the mapper a lot more control, I think.

Is the new 2d pane (which is something I had been waiting for) fully functional yet? Maybe this is obvious to people with prior experience in 2d-view editors, but I can't seem to figure out how to move and flip things around in 2d, e.g. to switch from top-down to side view.

What I can do is move the top-down view in the 2d pane up, down and side-to-side using the right mouse button -- which is what the centre button/mouse wheel does in the 3d pane. Intuitively, I would expect the same to be the case in the 2d pane. Would it not make sense to have similar behaviour in both panes? (This is currently the case with mouse-wheel zooming -- it works the same in 3d and 2d.) Perhaps there is a very good reason it works the way it does; my apologies if this is a useless suggestion. 

for the bug reports. I have created two issues on the issue tracker:

https://github.com/kduske/TrenchBroom/issues/1007
https://github.com/kduske/TrenchBroom/issues/1007

If you have a github account (they're free), you can subscribe to these issues and be notified when they are resolved.

As for your other suggestions:

To cycle the different 2D views, you can hit the Tab key. Furthermore, you can go to the View preferences and choose a different layout.

I have opted to use the right mouse button for panning the 2D views because the third button is often the mouse wheel, which is a lot more difficult to press and hold. 

Which version of Linux Mint are you using? 

17.1 'Rebecca' 32 bit Xfce is what I am currently using.

Thanks very much for your response, including your explanation of how the 2d pane works. I'm guessing there is no documentation for TB2 yet, right? Just in case I am asking about things on which I should be reading up elsewhere...

As for the brush measurements (i.e. the length in units of side), am I missing something? I know that in TB1 the fact that these measurements disappear upon reloading a saved .map file is a bug, but is it supposed to be like that in TB2? Is there something I should enable or a key I should press? Or is it something that just has not been implemented yet in any version of TB2?

(The absence of visible measurements in TB1 on Linux is one of the reasons I find it very frustrating to use at times. I have to physically count grid squares all the time. Probably good practice for basic addition and multiplication, but makes for slow mapping, particularly when e.g. setting up a lift or moving platform and trying to calculate where it should be placed and how far it should move.)

Thank you again for your patience in explaining things to a complete layperson.