That's kind of the hack I was thinking of. You can make a GUI that's just one layer with an alpha of 0 so it's essentially not there, but still responds to mouseovers and such.

I haven't even tried most of the funky moving stuff, I'm still revamping the PDA. :) 

Lun, just make a new dm map. We don't need another dune mod fiasco. 

Deathmatch or glory.
or else,
its just another story. 

Don't talk like that Headthump, he may start thinking about Pissboat or Quake4 and become suicidal. 

I wouldn't want that on my hands; normally, I just drive people to drinking. 

http://www.planetdoom.com/meanarena/doom3_editing.html 

has anyone seen it?
http://www.quake.de/q3tod3/ 

I love innapropriate ports. 

Automated map porter...Kinda cool still. 

Or is the D3R vertex edit mode fundamentally broken? Splitting faces it shouldn't, crashing after snap-to-grid, horribly deforming perfectly valid brushes... 

And I don't know how to snap vertices to the grid if they're not on it already...Is there a quick and easy way to do this?

Also, I don't know how I managed it, but I had D3 applying two different diffuse textures to one face. Does anyone know how I could've possibly done that, and how to fix it or not do it again in the future?

BTW, they really should fix the patch editing...I can't see patches I've created in the camera view unless I restart the editor. 

Don't use vertex edit for anything but patches. For brushes, 3D clipper is your friend. Seriously :I 

Try CTRL+G and see if that will snap the verts to the grid. You may have to select the vert first, not sure (that's if it works at all, it works in GtkR, that's all I know). 

That's what I was lookin for...I'm usin verts for patches, and when you create patches, sometimes the control points in the middle don't fall on gridpoints. Ctrl-G snaps points to grid, it appears to do all verts on the selected object.

Now if only I could figure out how I applied 2 materials to the same patch :-\ 

You can't 

alphamaps -- like you would do with Quake Arena terrain (see the manual on qeradiant, I don't believe I have seen it used for non terrain but Paul Jaquays says there is no reason it can't be used that way).

Also, I don't know if the method carries over to Doom3; those martian landscapes were certainly done in a high end modeler like Maya. 

But that's not the problem I have...let me find a place to stick the screenshots, and I'll show you: I have 2 textures visible on the same surface. I want to know how I did that, and how to get rid of it...Or at least not do it again in the future. 

I'm still a lowly Quake SP mapper though I am using Q3 bsp format on my latest stuff. I'm experimenting with alpha maps (for the first time!) in hopes of making my rocks prettier. 

Am I the only one with extremely slow glass when editing/playing in windowed mode, or am I doing something wrong? 

It's really fucking slow for me. Explosions and heat distortion too. r_skipPostProcess 0 required. I'm running an ATI Radeon 9600Pro with the latest Catalysts. 

r_skipPostProcess 1, of course. 

After familiarizing myself quite well with GTKRadiant in preparation for Doom3 editing, I'm quite disappointed to see that D3Radiant is nothing like it.

More than half of the textures don't load, texture alignment is a bitch, so on and so forth. Bleh. You'll find me trudging through the D3World forums for the next month while I try and crank out blitztest.map.

(PS this is a not so subtle cry for help. Please. I need tuts.) 

Sort of. The blending is done by using vertex painted models.

Put vertexcolour in a material stage, and that stage's RGB data will be multiplied by the vertex colour. Black vertex = black texture, white vertex = normal texture. Add another stage using inversevertexcolour instead, and you can blend between the two stages by changing the vertex colour from black to white (or shades of grey). This is nice because it's very flexible, but you do need a modelling app.

Take a look at rock.mtr to see how it works in practice. 

To fix broken textures, get this:
http://www.pcgamemods.com/7464/

Bleh, I was going to write lots of stuff here and then I figured most of is was stupid, so fuck you hitler. 

Just use GtK 1.5. It's a lot better.