After this latest jam it has come to mind that almost every brush in say: Skacky's or sock's maps are func_detail. greatly decreasing vis times obviously. I wonder if it would be possible to have a toggle button similar to texture lock where as you create brushes they are added as func_detail automatically. I think ideally this would be added to the map "under the hood" and not displayed in the editor by default. I also think it should be independent of groups/layers.

Or perhaps a "Seal Brush" command would be smarter? Every brush is automatically func_detail (again behind the scenes) and you select brushes and remove this attribute as needed to seal your map.

Posting here for discussion first before entering this on Github. 

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

I have a submission for a "Default Entity Hotkey"

One hotkey for turning a brush into the desired brush entity and another for placing the desired point entity.

:) 

...or copy behavior from JACK, where you can set what default brush is. You basically type func name and every new brush will be automatically set as specified func.

It's more universal this way, so you can use it in Q2 HL etc. 

I guess the best way to do this currently is to use layers correctly and select "all in layer" and make them func_detail all at once. I'm just not in the habit of using layers. I only use them for large areas and troublesome brushes. 

To upgrade TB2 from build 2f3c498 to RC4, can I overwrite or is it better to do a fresh install? 

NP 

could you add support for Kingpin loc 

When trying to open any map, I am get this error.

Failed to copy the file (AppData/Roaming/TrenchBroom/TrenchBroom.log to "My Documents/trenchbroom-crash.log (error 3: the system cannot find the path specified.)

I can get to this path that TB cannot find so I am confused here. Is there a way to reset where TB thinks the log file is or can tell TB to generate a new one?

Thanks for any assistance. 

It looks like TB actually crashes every time you are opening a map, and then fails to copy the log. Does it really happen with any map file? Can you post the log file? 

What does "I am get this error" mean, exactly? Is it a dialog? Can you please post a screenshot? 

Yes it is crashing every time I open a map, even a brand new one. I sent you a message on Twitter so we can discuss at a better pace.

I am get this error was a typo and I meant: "I am getting this error." Which is an error dialog window that prompts when I try to load any map, old or new. 

I don't use Twitter that much, and I need to track issues in a single place. 

It looks like you moved your user data directory to a network location and that's not supported by the underlying library that TB uses. 

Yes that would be what occurred although not my intention of course. I submitted an issue on GitHub.

Thanks! 

 

I realise you have release packages on github but are there plans for official packages via distro repos? (debian/fedora/arch) or via copr/aur perhaps? 

I'm all for it once we reach 2.0.0. But I don't have the time to do it. 

I only ask because I can't compile on this machine & TB doesn't work via wine.

Thanks for all your efforts. Scale tool pls! :d 

Those don't require compilation, do they? 

Very nice editor im looking forward to use it.
However i would like to request support for pk3(zip) for loading texture packages and loading textures from q3 map files and if possible basic shader support too. 

I am waiting for this myself but I don't think this is close yet. The GitHub has and open ticket for it though. It would open up the editor to a ton more games that used the Q3 engine.

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

I've been waiting on Quake 3 support for years at this point. Not gonna pressure the man because he makes his program in his spare time and it's pretty rad so whatever. We can keep hoping. Only time will tell, and hopefully we can finally put that decrepit old Radiant in the ground. I'd honestly be curious to know what makes it so complicated. All I know is something something surfaces. 

 

I'm sure it will be worth the wait. You haven't disappointed us so far. 

What causes this error? I was trying to snap this brush to grid but I got that error. Snapping to integer worked fine.