I've been out of the loop for a few weeks due to hardware trouble; only got to use the beta now. On my setup at least (Linux Mint 17.3), the mousewheel/middle button seems to have inverted left-to-right (and vice versa) movement, compared to the last alpha build I used (from shortly before the first beta release). Is this intentional? 

But aren't there preferences to chsnge this? 

Would there be any way of merging geometry together? I'm not talking about grouping, just a way of turning multiple brushes into a single brush? 

That performs a CSG merge in TrenchBroom 2. 

How is it coming along with support for Half-Life/CS?
Quake is always fun playing around with, but my favorite engine has always been goldsrc. Trenchbroom is so much easier and faster than the regular editors, so i just want to say thanks for trenchbroom and for the future updates. 

I'm working on other things. 

I want to utilize Trenchbroom as a level editor for my game in Unity. I can do it through OBJ export in TB2. However, I don't know how to load custom textures into it. Any help?

Due to my needs, format doesn't really matter, but I'm using Quake, map format Valve.

I'm using TB 2.0.0 beta, build e439e68, which is at the time newest beta build. 

 

Nothing in the docs about how to load a png or jpg. 

use an app called texmex 

For Quake, that's mip textures packaged in was files. 

 

Nice editor very easy to use for a newbie like me! 

Description: Every time I launch Trenchbroom, my wife needs me to help with something.

Repro Rate: It's happened twice.

Expected Results: Time to stand still when I launch.

At least I got TB2 extracted and launched though... And one time it sat open for a few hours with e1m4 loaded while I took care of other things, so, it was like my computer was mapping! 

My IDE has that same bug! 

This is maybe the best shitpost I have ever seen. 

Sorry for the month+ pause in responding; life interfered. The preferences settings don't seem to help. Opening github issue... 

OK that was pretty funny! 

I have the TB2 Beta installed on my system (Linux), but it's not working so well for me and I'm keen to get back to a map I was working on. The last few alpha builds were more usable for me, so I was wondering if it's possible to use one of those while waiting for the newer stable beta version...?

(I've installed both Netradiant and Jackhammer in the mean time, but they're both very different from TB and I can't see myself getting much done with either of them in the near future. This is not meant as a judgement on the value of those editors; I'm sure they're both great, but I just can't seem to get a grip on either. It's probably a testament to TB's ease of use, though!)

I've just tried to install one of the TB2 alphas by doing the same thing I did before the Beta came out, i.e. the process described here: https://github.com/kduske/TrenchBroom/blob/develop/Build.txt (I suspected that was not the correct thing to do, but I thought I'd try it before asking for help here.)

It worked, sort of. I ended up with "Version 2.0.0 Interim" instead of one of the alpha builds. I can launch the programme, but when I try to open any map projects it crashes.

If I understand the automatically generated crash report correctly, it's trying to access a ".TrenchBroom" directory in my home directory, but ~/.TrenchBroom doesn't exist:

Reason: Exception: Cannot open directory: '/home/total_newbie/.TrenchBroom'

I then tried following the advice in post #2013 above, i.e. I ran

git log

, which listed what I understood to be the last four versions of TB2. So I picked the first one and ran

git checkout f673031f5024e4fe23ff1e24dc86e0de22985c01

That still left me with a 2.0.0 Interim version that crashes for seemingly the exact same reason.

I'm sure this was all really stupid, but is there a way of doing what I was trying to do, i.e. install one of the last alpha builds of TB2 to use while waiting for the new beta? 

You might also check whether there is a file in your home directory called .TrenchBroom - I have changed the storage location for preferences and it's possible that the file being there prevents TB2 from creating the .TrenchBroom directory. 

The main issue was with the inverted mousewheel, which really threw me off -- but I figured out today how to change it back to how it should be, as I commented on github (this was after my having tried to reinstall an alpha build and posting here). I still feel really stupid for having missed that earlier.

The other problems might very well exist between keyboard and chair, which is why I haven't reported them as issues (yet).

One is that I can't get entities to display properly, despite having specified my game path correctly (I think) -- entities still display as coloured cubes.

Another is that some of my brushwork seems to have drifted from where it's supposed to be -- but again, I need to make sure that it wasn't something I did wrong (and I thought that if I could e.g. test the same map in one of the latest alphas and in the beta, I would be able to tell quite quickly if the beta was behaving badly or if I was just being stupid).


As for the missing .TrenchBroom directory, the first thing I did was to check if it existed, and it doesn't. Would it help to create one manually? I assumed that if the programme didn't create it automatically, then my creating it manually wouldn't solve anything... 

you can try to create it manually. But either way, please submit a bug report. As for the other problems, please also submit bug reports. Maybe we can figure it out together. 

Ok, will do. Thank you. I was afraid of wasting your time with unnecessary/inaccurate bug reports. 

and it was just stupidity on my part. I hadn't noticed that although the game path pointed to my Quake installation, the game was specified as Hexen 2 Basically I forgot to specify the game as "Quake" (it's a map file I had been working on before, so I guess I assumed TB2 would recognise it as a Quake map file, and didn't even think that I needed to specify it again).

I'll have another look at the drifting brushwork problem too and if I can't figure out what went wrong I'll submit a bug report.