Razumen - that looks excellent! The lighting is very nice and the setting looks very interesting. Can't wait to play it.

Tribal - thanks for playing the map, hope you enjoyed it! Yeah, the progression is a bit cryptic, but I'm the kind of guy to destroy everything breakable on principle so it didn't occur to me that it could be a problem for others. 

Get it here as usual: https://github.com/kduske/TrenchBroom/releases/tag/v2.1.0 

Does anyone know how to do this? Hexen 2 has paks in a different directory for mission pack monsters. I thought copying over the pak file to data1 would be a bandaid solution, but it just crashes Trenchbroom. Do I have to specify an absolute path for these special entities or is there a cleaner way? The vanilla entities load their models fine in TB.

Also, is there way to specify the skin to use for each model, H2 has certain monster variants that use the same model but different skins. Not as big of a deal as above if I can't, but would be nice.

Not too familiar with the FGD format. 

Nevermind about the skins, figured that out. 

And you need to create a new fgd for the mission pack. You can reuse the existing fgd by including it. If you do create an fgd for the mission pack, please make it available to us so that we can include it.

You might get lucky if you google for it, maybe someone has already created one. 

Thanks! I must've missed that part of the manual. 

Get it here as usual: https://github.com/kduske/TrenchBroom/releases/tag/v2019.1

This release contains experimental Quake 3 support. You can load Quake 3 maps with shaders. But patches and brush primitives are currently dropped and md3 models are not displayed in the editor. 

Time to find my old maps! 

I haven't touched TrenchBroom in well over a year and am out of the loop, but now I'd like to slowly but surely get back into mapping, if real life allows.

When I last used TB, I kept running into problems with texturing. Using Valve format would often result in bizarre problems and I had to convert everything I was working to Quake format, but even then, copying and moving brushes would often result in completely messed-up texture properties. This was one of the reasons why I gave up on mapping for a while, as it was incredibly time-consuming to have to manually fix the texturing on individual brushes; it almost defeated the purpose of copy+paste.

I don't know if there are any differences between the versions of TB for the various OSs, but those of you using TB on Linux, how is texturing in TB these days? And how stable is Valve format in the latest iteration of TB?

I apologise if this sounds like one of those things one could find out for oneself, but I am reluctant to go through the same process again of needing to restart or redo hours (or days/weeks/months) of work and completely spoil the fun of mapping for myself ... again. 

There have been a few changes and fixes for Valve 220 texturing last year, but I'm not sure if these are related to what you are describing. Did you submit bug reports for these problems? 

http://www.speeed.ga/pic/why.jpg

I cannot get the map to compile.
The directory has full permissions

Thanks 

Well, export map has no map name?

I haven't used the built-in compiler in a while but the manual says:

Exports the map to a file. This file should be different from the actual file where the map is stored. 

I guess I would have submitted bug reports (I have submitted a few over the years), but my memory is a little hazy; as I said, I've been out of the loop for a while.

I do remember using ericw's tools to convert a few maps to Quake format the last time I was actively mapping and I think it was on either ericw's or your advice, since at the time, the were some problems with Valve format and regular Quake format was a lot more stable.

I seem to recall that when using Valve format, selecting a bunch of adjacent brushes and giving them the same texture values wouldn't work and would result in horribly misaligned faces (e.g. with rockwork or even just fairly simply architecture, like a brick texture wrapped around a tower).

But I also remember that even when using Quake format, textures wouldn't stay properly locked or would come out weirdly flipped when I moved copied brushes around (I think especially when flipping them). This was especially annoying when I had spent a lot of time fiddling with exact angles and X/Y values to get textures looking right on angled surfaces, only to find them completely messed up when I copied and moved the brush in question somewhere else.

I'm sorry that all of this is rather vague. 

You've set up your compile so that it does absolutely nothing, you need to specify what each tool has to do.
Go into the Trenchbroom help (F1) and look at the Compiling Map section, there's an image suggesting how you should set up compiling. 

without having proper steps to reproduce. But the fact that noone has submitted bugs in the issue tracker tells me that there are not a lot of people who experience such problems. 

probably something stupid, but
having an odd issue with TB Version 2.1.0 RC1 release
started dinking around in a map. Was going dandy. Was compiling with Necros GUI. Dandy. Then I noticed changes made weren't making it into the compiled map. Stopped for a bit. Turned PC off. now when I try to load map, I get notification "unexpected end of file".
windows 10 home

Pls let me know if any input to resolve. Not a big deal with this particular map as its tiny 

the fact that noone has submitted bugs in the issue tracker tells me that there are not a lot of people who experience such problems.

Fair enough. :) Thanks again for responding. Well, I guess worst case scenario is that I do run into these issues again, in which case I'll submit bug reports. 

We are usually quick about fixing those. Thanks! 

what does the $ mean? 

$(MAP_BASE_NAME)-compile.map $(MAP_BASE_NAME).bsp 

Starting symbol for placeholder string.
For example, in line above substring $(MAP_BASE_NAME) will be replaced with your map name. 

And to be clear, TrenchBroom will do that substitution automatically. You shouldn't actually type your map name in there. Instead, type $(MAP_BASE_NAME) exactly as it is showing you. 

I forget, but I thought it was ${BLAHBLAH} with braces? 

Yah I didn't have the manual handy, just copying what they said above. But it is in fact braces like ${MAP_BASE_NAME} 

being ignored cuz I'm dumb? Or did it just get skipped over in the midst of the $$$