how do you guys do it? sure there is tyrlite's skylight feature, but that only lights from one direction for the entire map. if you need sky light coming in from more than one direction, you're screwed.

I've seen some people place a bunch of small lights along the sky-ceiling of their map, which seems like a good idea. My question is, what values are appropiate? and how many lights? 

The intensity and quantity of lights will of course vary between rooms and their sizes. Normally if I'm not using Tyrlite's skylight, then I use just one light for the sun, with a light value of around 200, and a wait value that's usually around .2, but sometimes more or less. Smaller, low-intensity lights (and anti-lights) get placed around to add ambience and enhance the shadows cast by the "sun" light. These smaller lights usually have a light value of around 75 (or -75 if it's an anti-light) and varying wait values, but generally .25 to .4.

Now here's the part where someone comes along and tells me how oddly I go about lighting outdoor rooms. 

play with it until it looks good. (This sometimes takes a while.) 

(This sometimes takes a while.)
And the award for 'Understatement Of The Week' goes too...

:D 

"delay" "3" lights have no falloff (just like sunlight) - might try that.

But the real thing is to use radiocity sunlight 

to check out the enhanced sunlight feature of my Light at http://user.tninet.se/~xir870k .

It makes an attempt to make outdoor sunlight more realistic and specifically doesn't require an excessive minlight value to balance the hard shadows of the normal sunlight. 

if all you want is different sunlight mangles in different rooms, you could use q1rad, put the bounce to 0 (effectivily disabling the radiosity stuff) and then use the env_sky or what ever the ent is to do different lighting in each outdoor area.

erm... did that make sense? 

Mirrored plane

got that when compiling a map with the q3map tool... 

This is not a mapping question but anyway, does anyone know how to stop the player from tilting when strafing? It feels like the dude is standing on a skateboard. Thanks! 

try messing with the various cl_* variables. One of them probably controls it. 

cl_backspeed 400
cl_bob 0
cl_forwardspeed 400
cl_pitchspeed 250
cl_rollangle 0
cl_sidespeed 350
cl_upspeed 200
cl_yawspeed 250

I think it's the cl_rollangle 0 that does what you want. Experiment for best results. 

sv_friction 

edgefriction -4 

That was fun. 

I tried edgefriction -4 but it didn't seem to do anything. :/ What is it supposed to do? 

walk up to an edge. 

I see now. Coagula was not a good map to try that on. 

 

----+----+
5499 brushfaces
7363 csgfaces
4291 mergedfaces
---- SolidBSP ----
----+----\
*** ERROR 42: Didn't split the polygon in SubdivideFace

ok, get this error in bsp, and i'm wondering how on earth you pinpoint this sucker down. 

You'll have to locate faces that have low texture scaling values, < 0.2 is usually problematic.

If you can't find the offending value(s), you can use my ConvMap utility at http://user.tninet.se/~xir870k to set a minimum texture scaling value. Beware that this might make some textures look misaligned. But that might still be easier to fix than manually finding the culprit face(s).

The best thing is if your editor can help you trace bad scaling values, e.g. I think QuArK can do that. 

looks like i already ran into that problem... :) thanks again, aguiRe!

i'll try the convmap approach. 

Is there a way to swing this, or do I just have to shuffle all my texes into one .wad file? I tried adding a "wad" key to a brush with two filenames, and adding one key to two different brushes, but neither worked. 

but fisrt, a wad is not a property of a brush, it's a property of the worldspawn.

the main problem is that radiant has a small area to type the value of a key-value pair, so really long strings (like two wad paths concatenated) might be too long to type in.

Solution: do it in wordpad. Radiant handles this approach fine; i guess it's just the text entry field that is too short. 

Or you could put the wads near where you compile your maps, and use relative pathnames. 

Yeah you just add the .wad to the worldspawn, and separate different wads by ;
eg id.wad;rogue.wad


"the main problem is that radiant has a small area to type the value of a key-value pair, so really long strings (like two wad paths concatenated) might be too long to type in."

Nah, not true, I've had 5 wads typed in there, miles of room left. But you may have that problem if you leave the window the default size I guess, I have mine almost full screen