I think that explains NewHouse's issue as well 

my worldspawn's no_item_offset was set to -1... that must be the reason in here? 

Whenever I move a selection that contains a func_detail, the detail doesnt follow properly. it progressively gets more off grid as the further I move it.

Is it a problem on my end or trenchbroom? do other users experience this? Its a pretty glaring problem that seemingly hasnt been reported, or otherwise im missing it on github.

This happens in the most 2 recent betas, Ive yet to build from source as its something I've never done. Ill tackle the intimidation factor soon enough, I'm sure. 

Yeah - I had that as well. If it's the same thing you're experiencing, it should only happen when you use the "select touching" command: https://github.com/kduske/TrenchBroom/issues/1409

It was fixed a few days after the latest beta came out (spet 6), so you'll have to avoid using "Select touching" until the next beta is released. 

Exactly whats happening. 

Is there any way to "deselect" the current texture, so that TB will create untextured brushes again, like it does before you select your first texture? I've been putting up with it for months because it's really just a pet peeve, but I prefer to build the foundation of my map without texturing and then texture and add detail later. Having to either deal with crappy, distracting textures/colours (I know you can disable texture rendering, but the textures still show up when you actually load the map) or restarting the application when I want to work on a new area is kinda lame.

One advantage of using the default texture to me is that it helps to spot untextured spots; they show up very well since in QS at least they're always fullbright, so it can help me find areas i've missed. 

Currently no.

Ive been meaning to suggest it along with some other texture based ideas/issues.

currently, you can select a face with shift+LMB and then apply that texture to another face with alt+LMB (you can also apply it to a whole brush by alt+double LMB). Id like to be able to "paint" by dragging the brush similar to how youre able to ctrl+LMB and select multiple brushes.

also, while a texture is selected itd be nice to either paint or apply that texture with its current coordinates or default. 

also, while a texture is selected itd be nice to either paint or apply that texture with its current coordinates or default.

Try holding ctrl+alt, it should not copy the attributes in that case. 

currently, you can select a face with shift+LMB and then apply that texture to another face with alt+LMB (you can also apply it to a whole brush by alt+double LMB). Id like to be able to "paint" by dragging the brush similar to how youre able to ctrl+LMB and select multiple brushes.

That's a good idea. Submit a feature request please. 

Also submit a feature request for deselecting the default texture. 

Nevermind, I've already changed it. Deselect everything, then click on the selected texture in the browser and it will deselect. Will be in the next beta. 

 

I've just noticed something: when I load the Arcane Dimensions .fgd into TB, the console lists a bunch of unknown entity definition header attributes. I should indicate that before loading the .fgd I enabled the AD mod in the Map tab. Is this normal? 

And use the def file instead. The fgd is designed for jackhammer 

I had no idea there was a .def file for AD, nor that it was better for TB than the .fgd, which is the default selection in the file browser when picking an entity definition file.

Now I have INFORMATION in the editor itself! 

I have to know these things being on the ad team ;) 

For TB2 I had more success with the Fgd, it provides all of the keys and values I am expecting for AD. Furthermore I tweaked it to show models depending on what spawnflags are present (dangle, megahealth, etc)

I do recall TB having much better luck with .def but something to keep in mind if you using TB2. 

so I can't comment too much on that version. Everytime I dip into it there's something different or new it feels.
I haven't been able to justify making the leap into it fulltime yet as I feel my workflow is better in TB1. 

since Sleep implemented support for WinXP.

Better To Avoid The Fgd
I've read somewhere that .fgds are more "complete" than .defs...
OK then, I'll use the .def instead.

Everytime I dip into it there's something different or new it feels.
Pretty much like any other program under active development... 

I'm a creature of habit. Been making all my maps in tb1 since the first day 

Wow :o i couldn't stand TB1, camera movement etc. was really laggy on my system. TB2 is buttery smooth by comparison. That alone was enough to make me take the leap. 

Never really suffered with TB1. Infact a lot of my maps were made on TB1 when my main PC was a Surface Pro 1. So I made a lot of maps on a tiny 11" screen. Plus the power of a Surface Pro isn't amazing by any stretch of the imagination.

I'm on a pretty decent machine these days and it runs just as good as before 

Only thing i miss from TB1 is the neat search bar. Saw on github sleep is reworking it for the full release of TB2, though.

I figure the more I use the beta the more help i can be to get the final product done sooner, well minus the fact i have no coding skill.

Most of my brushwork has been done in Hammer so Trenchbroom is a breath of fresh air in a lot of ways. 

a lot of my maps were made on TB1 when my main PC was a Surface Pro 1.
Wow... I'm impressed! 

Just setup compile settings, and I was wondering what the "export map" step does. I assume it must do something other than just copying the file. Is this some kind of pre-processing step before sending the map to qbsp?