InsideQC Forums

Changes
- Fix off-by-one bug of mod list in map properties dialog.
- Snap vertex coordinates if close to integer coordinates.
- Add logging on all platforms.
- Properly merge spawnflags when loading fgd or def files.
- Properly set the size of point entities from fgd files.
- Fix crash bug when ...

qbism wrote:The built-in fgd files. The menu item says "corner" but the label says "path_corner", if that matters.

Thanks for the report. This will be fixed in 1.0.3.

Dr. Shadowborg wrote:Something tells me that the Mobility Radeon X300 in my laptop is too outdated to run this. :/

Sorry, but yeah.

does this editor not have a compiler? i havent been able to find the compile option for my map. (iv made a quick test map)

No, the editor doesn't come with builtin compilers. It's on my todo list, but it's not a high priority.

but so far! im loving this more than i ever did worldcraft! amazing ...

I would test q3 .maps with this editor; I'm not a coder though and don't know the format itself too well.

Okay. I'll get back to you when I start on the Quake 3 support, but it'll be a while.

Can I suggest looking at Hexen 2 support as well? If this editor supported H2, I would potentially want ...

Changes
- Fix issues with texture caching when removing wad files.
- Correctly display long spawnflag names.
- Improve clip plane guessing when less than 3 points are available.
- Fix crash when calling "Center Camera on Selection" when nothing is selected.
- (Hopefully) fix off by one issue in ...

For releases you should provide a source zip -- downloading 64MB of git repository is a pain compared with a 10MB (pure guess) source package.

You're right. The repository contains 3 years of history, two rewrites, and a bunch of now useless binaries. Once I automate the release process, I will ...

Right now it outputs standard Quake maps. It will read Valve 220 maps, but it will disregard the per face texture axes. I would certainly like to support Quake 3, but I would need someone who knows the format well and who would be willing to test the editor as I'm not familiar with Quake 3.

Today I am releasing TrenchBroom 1.0 for Windows and Mac OS X. TrenchBroom is a modern cross-platform level editor for Quake.

FEATURES
- True 3D editing, no 2D views required
- High performance renderer with support for huge maps
- Vertex editing with edge and face splitting that will not create ...

Customizable hotkeys is on my radar, but it's not a very high priority.

Haha, okay now I understand all the confusion. This is not what the groups in TrenchBroom are like. Grouped objects do not move together. I guess the term is already connotated with that meaning because many programs define it that way. Maybe layers is the better word then. I'll consider that.

The groups feature in this editor is currently just standard func_groups with names. Visgroups (from Hammer I suppose) are different in that they allow you to add entities to them, too, which is currently not supported in TrenchBroom. The planned features are:

- allow entities to be added to groups ...

Okay, I understand. So the main complaint is the fact that it's named "groups" instead of "layers". I'll consider a name change when I start implementing the missing features for groups then, but again I feel that the term "layers" is a bit misleading here. Thanks for the feedback and explanations!

Okay, but the point of PS layers is that their order matters. How does the order of layers affect the editor? I don't think "layer" is a good metaphor for what this functionality does because it applies that the layers have some sort of natural order...

Yeah, support for alternate Quake map formats is also on the to-do list.