I wouldn't call TB2 in beta really. It's more of an alpha. There are a lot of feature just plain missing, and many things do not function 100% correct just yet. You can't really use it to make a map. 

To the issue tracker. That would be very helpful. 

sorry dude I have been really busy, you did mention to add things to this thread though. I'll try and keep stuff github as well (though I still get a bit confused on where things are on there). 

 

...but I can't get the stable release of TrenchBroom 1.1.1 to work properly. The two main issues I'm having are crashes when either choosing the vertex tool or trying to drag and drop certain entities. I didn't quite know where to put these issues, nor could I find any fixes for them. Sorry if I'm not posting in the right places. 

And set OpenGL instancing to force off. That should fix the vertex tool. As for the other issue, I need more info, such as your OS and steps to reproduce. 

The OpenGL setting fixed the vertex tool for me. My OS is Windows 7 64 bit, my graphics accelerator is built into the processor, an Intel 4000 HD. I saw the entity issue on the GitHub issue tracker, and supposedly a driver update should have fixed the problem, but I'm sure my drivers are up to date. 

Which entities crash the editor when you try to drag them? 

I rolled back the driver to a previous version which seems to have fixed it for me, but the entities that previously crashed the editor were the ones that are represented by a 3d model. Now the editor runs fine, thanks for all your help!! 

this editor.......
from this to this took 30 minutes.

Literally just built one section of that inner circle bit, started rotating, then just lopped off a few bits that were poking out. And yes, that is a 32 sided outer circle and a 16 sided inner one.

I feel like I have been waiting my whole life for this editor. 

should have mentioned to not deceive anyone, this is with the beta of TB2. 

That is amazing, it looks so perfect, you just rotated, no errors? 

This proves once more that SleepwalkR is but a giant troll. Being able to create nice curves and angled architecture used to be a real skill; in TB you just press rotate and it's done. Even the greatest noobs like skacky and mfx can now pull things off. Disappointing. 

Anytime I try anything so crazy in TB ends with me getting some wandering vertices and stuff and the next time I load up the map it turns into my worst nightmare of fixing.

Unless nightmare time has been fixed? 

This looks great!
With the geometry inside this ring, is it possible now to compile it with "vanilla" qbsp?
(without max_windings raised?) 

Making Quake editing easy ;-) 

hipshot: yep, all rotation. you can set the origin of the rotation in TB2, so I move that into the center of the ring and set the rotation angle to 11.25 and rotate as I paste copies.
I simplified a bit of course, there is some preparation:
First you build the section a little wider than it should be.
Then you make two copies and rotate them to both sides of the original.
Next, use clipping to remove excess brushwork so there is no of very little overlap.
Now, delete the two extra copies and you can start copying the original again.
mfx: no clue... haven't switched back from rebb's compiler since you mentioned it last time. i would suspect no, though, because when I check this out with r_drawflat and r_showtris, I can see some faces have absolutely tons of edges... 

What do you mean? 

It's a product of the compilation process, not the editor. :)

Essentially, all the rotated stuff creates so many intersections with the floor that you end up with faces that have large numbers of edges.

You can see this when you turn on both r_drawflat and r_showtris: you find a surface that shares the same colour which is 1 face, and then count all the edges from showtris. 

other editors have rotate functions, too. always had. there's more reasons than the editor that people usually don't try that, like the near 100% likelihood of point on plane or winding errors and the heinously messy geometry that results. 

mfx: I checked and this map does compile with normal compilers. the map where I was getting this error was a much crazier map that I was using for testing.
With the added brushwork on the ground, there are now extra splits on the faces which reduce the number of edges on each face.
I suspect that if I started seeing winding errors, I could just easily go into areas with that kind of problem and force qbsp to split those faces either by offsetting textures a small amount or by placing brushwork in the middle to cause intersections. 

thanks for checking necros. i was asuming the same. 

http://leray.proboards.com/thread/3529/trenchbroom-quake2-addon 

Thanks for posting, fifth! 

Uh... Why do I keep getting this?

Unloading existing map file and textures...
Loading file D:\Games\Games\Quake\id1\maps\test3.map
Assuming floating point plane coordinates
Malformed map file: expected token of type string, but found integer number at line 6, column 51
Loaded map file in 0.003000 seconds

Even in the autosave map?