thanks dude. i'd kiss you, but i think i have aids 

nt 

yeah... you lucky mathafaka :)

anyway. thanks again for the link. hehe. me is happy. 

ok, q3 mapping for people who are unfamiliar with id's tech advances since the days of q1?
do and don't, baby's first vertical atrium of death, gtkradiant for complete fuckwits, that sort of thing...

I'm asking here because I don't wanna wade through the muck searching for the juicy stuff,hook me up. 

I fight int'l terrorism by not spacing my sentences. Apparently. 

All I can say is: Good luck. I've been mapping for Q1 using QERadiant, so I have a slight advantage, but when I recently started Q3 mapping again I couldn't find anything useful, and no one wanted to help me. 

people suck, mappers doubly so. 

Agreed. But don't Maj I said that, mmkay? 

+Maj

bleh. As you said, mappers suck doubly so. 

-Maj +tell

Triple suckage? 

you suck at the intarweb 

suppose you are a programmer. suppose you wake up screaming in the middle of the night, sheats soaking with cold sweat. suppose you walk out into the kitchen, all shivering. suppose you quickly hop back into your bedrom to put some pajama bottoms on, there's a whole bunch of level monkeys watching you via an internet forum for crying out loud, save the children!
suppose you stand there in the dark, with just one singular thought running through your head.

"I have to make the best level editor known to man, if but some level monkey would take mercy and tell me how it should be designed."

Any takers? No?

Blast! 

and by make, I mean code. 

The two most difficult things are: how do you best represent what is essentially a 3D environment in two dimensions, and then how do you modify a 3D environment with a 2D interface? Radiant does the best job of it so far, but I don't believe for a second that we can't do better.

I would be interested in seeing some interface that does away with the keybaord entirely and uses two mice at once. Have the 3D view fill the screen and put it all in radial context menus. 

Suppose you associated the right mouse with X/Y movement and the left mouse with Z. The camera stays centered on a point in space you move around. When you hold down the right mouse middle button the right mouse allows you to rotate the camera around the point and the left mouse lets you determine how close to that point the camera is. The left mouse right button could open a context menu letting you set things like grid size and sensitivity. The right mouse right button would cover things like setting textures and properties. One of the mouse wheels would have to cover rotating through which brush you're selecting when the point in space intersects more than one. I imagine both left buttons would be used for creating and manipulating brushes.

That's just off the top of my head. There would no doubt be necessary features I've left off. 

 

I have the new version of GTK working fine with Quake, and have found out what I beleive to be causing the problems I have been having with that version of GTK. Basically when GTK 1.3.12 starts up the entity browser has 2 of the 3 main windows collapsed/closed (1 a list of the entities, the next a description plus the keys etc, and the next the values that you entered etc) if I adjust it by slidding down the separator bars so as I can see the other 2, and shut GTK down with the entity browser like that, the next time I start it it will crash, and I will have to reset the registry, then set up my preferences again. But if before I shut down GTK, I put the separator bars back how they were, there is no problem. At least I know how to avoid it now. 

...except for the clipping bug and annoyances with the surface inspector.

Care to expand? I haven't noticed anything yet. 

if but some level monkey would take mercy and tell me how it should be designed.

Congratulations, you've just made Worldcraft.

PS: RPG, you fool, I love you. 

congratulations, you have just jumped to the wrong conclusion. 

wrath; http://www.claudec.com/the_tutorial_Index/q3a/tutorials.shtml 

I win. 

if by win, you mean something else entirely - then maybe. 

When I use the clipping tool, sometimes the 3D view doesn't display which part of the brush it's going to keep after the clipping operation is complete. I have to update the 3D view somehow (like move the camera) and then it will display it.

Also, I used to be able to copy and paste a texture name into the surface inspector window and change a surface's texture that way. Now I can paste it, but when I click "apply" it just reverts back to the old texture name. This is frustrating, because sometimes I spend a lot of time scaling, rotating, and shifting a texture to make it look right, but then I want to try a different texture to see how it looks. 

so, it's supposed to be really, really sluggish - right? I'm not on a monster system or anything, but with a ti500 and 640 mb ram, it shouldn't go completely aquanox on me just because I have one fucking brush out there. panning and moving around in the 3d viewport is right up there with pounding nails through my cock.