J.A.C.K or Worldcraft or Hammer exports it from rmf,vmf,jmf etc. into a .map file format before sending it to qbsp.exe

Trenchbroom works with .map directly so doesn't need an actual export.

Bonus:
Rmf - Rich map format used by Worldcraft and older Hammer versions.
Vmf - Valve map format used by newer Hammer versions (Source engine)
Jmf - Used by J.A.C.K and its predecessor Jackhammer (same thing, was recently renamed)

There are alternate x versions: rmx, vmx, jmx that are used for autosaves if you have it turned on. 

Hi!

I'm using build "2f3c498 RelWithDebInfo" on Windows and I'm trying to get Trenchbroom to launch Quakespasm, but alas, I get the error message "W LoadWadFile : couldn't load gfx.wad".

I set Quakespasm's game path in Trenchbroom to
"C:/Users/Esrael/Desktop/Games/Quakespasm"
and did the following engine configuration:
"C:/Users/Esrael/Desktop/Games/Quakespasm/quakespasm.exe"

Why does Quakespasm refuse to work, even if Trenchbroom finds all the entities from the id1 pak files just fine while I'm editing the map with the above mentioned settings? Am I doing something wrong?

Mind you, Quakespasm does work, when I launch it outside the editor. Of course, I could test my map this way, but I want to be able to use all the features of Trenchbroom. Has anybody had similar experiences? 

@Esrael

its an issue with the betas.

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

If youre comfortable with building from source, the issue has been fixed but hasnt been released yet. 

That might be a bug in TB. The "couldn't load gfx.wad" error means that the engine couldn't locate the id1 directory in the current working directory.

As a workaround, try adding "-basedir C:/Users/Esrael/Desktop/Games/Quakespasm" to the "Parameters" text field in TB's Launch Engine window. 

Wow, thanks for the fast response guys! =)

The workaround seems to be working like a charm, so in the mean time, while I'm waiting for the release with the bug fixed, I'll just use that. 

Thanks Ericw! First time I've seen that mentioned! 

anyone willing to walk me through building TB from source?

Ive never built from source or anything in this order.

Downloaded Visual Studio and everything, but I think I dont have the proper versions.

Got to this point and had to give up.

CMakeError.log just goes on and on like this:

"Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: cl
Build flags:
Id flags:

The output was:
The system cannot find the file specified"

command prompt is telling me about vcvarsall.bat, which has to do with visual studio?

:cries in corner: 

Is there any chance of seeing a new beta release any time soon? It's been a while since the last one, and although I imagine the goal might be to hit full release with the next update, there have been a lot of changes since the last one. For some of those, it's fixing bugs that I myself created and would rather like to enjoy the fruits of having the fixes.

I know I could compile it myself, but as I understand it the process is quite complicated due to the need to compile several different things seperately and so on. I'm not really that level of user unfortunately, so yeah... It won't kill me if I have to wait until full release for TB2, but a new beta would be nice. 

Agreed on the build being complicated. Tried to tackle it and had to give up.

Fortunately, Ericw came to the rescue with a recent build.

https://ci.appveyor.com/project/kduske/trenchbroom/build/2.0.0-appveyor-65/artifacts

now, GO MAP. or...yknow. hangout. up to you. 

Still working on TB, but at a very slow pace. I'm swamped with RL things. 

It's totally understandable that you're busy SleepwalkR, and it's even easier for me to be cool with that thanks to the ericw and the link mukor posted :D 

Is it okay to submit bugs that are from that interim build that was just posted? I found this but I'm not sure if it's okay to create an issue for a 3rd party build of the program. 

I'd say submit the bug, I'll take the blame if it's an invalid bug for some reason ;)

(That build I made is the current latest code from release/v2.0.0 and it's built by TrenchBroom's CI system, so there shouldn't be anything weird about it.)

FWIW I think I hit that bug of things going off grid as well, haven't had a chance to investigate it though.. 

Does anyone use TB on macOS 10.8 or below; would you care if TB required 10.9+? 

Personally, I try to avoid using 3-point clip whenever I can. I find it not very intuitive and often end up clipping out the part that I wanted to keep. It's quite common for me to have to do multiple tries to find the correct camera angle that will make the clip tool perform like I intended. In many cases it's faster to just do it in vertex mode. 

Hopefully this will help de-mystify what the third point is for, at least to the point where you understand it as well as I do (I'm moderately sure this is all it can do).

Here's a standard, 2-point clip:
http://i.imgur.com/7Mkebev.png

Then... Bam! 3rd point:
http://i.imgur.com/tvD7hDK.png

Try it yourself. Drag the 3rd point around and watch as the angle of the clip changes. Obviously this is a very basic example, but the general idea of it is that you can change the angle of your cut with this method.

I find it most useful for when TB doesn't "get" what you're trying to do because the 1st and 2nd points are too vague, since you can easily direct exactly how you want your cut to work using it.

Another cool trick is placing all your points on a flat plane, like so:
http://i.imgur.com/RuVVxLs.png
http://i.imgur.com/w730DjK.png
The third point tells TB that you actually want a horizontal cut, so you can easily perform that style of cut.

Here are some more fun cuts:
http://i.imgur.com/lqmFJRF.png
http://i.imgur.com/hxoVyW9.png
http://i.imgur.com/rkOTdiv.png

Hopefully that helps people figure out what the 3rd point is for. 

Thanks Pritchard, that does help clear things up! 

Bonus points for knowing the shortcut if you wish to use an existing face as a clipping plane! It'a in the manual ;-) 

 

A good tip is...unless you need another brush to snap a clipping point to, isolate the brush to be clipped.

If you try to place a clipping point at the edge of a brush where it meets another brush, sometimes itll get placed on the other brush.

I switched my "Hide" "Isolate" and "Unhide" to H I and U for this and other reasons. 

Thank you, Sleep, for implementing issue 1465 "Always show edges of selected brush" and 1460 "inspector keys open inspector window when closed"

Didnt even consider theyd be in the build eric provided so they were a very pleasant surprise to run into.

"Oh hey thats me!" 

I made some good progress on 1499 recently and things are looking better. Hopefully I'all be able to provide new official builds soon. 

Is going to be magnificent.