so you can say "I make teh map look sexeh MOH YEAH!!!"

like duh... :D 

Doesn't bounce 0 mean no radiosity? I'm confused...

: ) 

My comment is, hurrah!

Thank you all the hard work, aguirRe. 

"radiosity" refers to bouncing light, sure, but in our line of work, it's usually paired with light emitting surfaces. So, if you want light emiting surfaces, but don't care about bouncing light, you might use bounce 0.

Yes, i'm very drunk. And i can still type better than you. 

As previously stated, I don't care about light emitting surfaces, since they look crap. 

I typed that header with my nipples. The amazing world of wireless. 

You must have some fucking big bitch tits to be able to type with them. 

Bob has bitch tits -- nope just a set of extremely cold nipples. 

glad to see you on the func_board. Does that mean you are you mapping as much as you code these days? 

You could say that. 

Could you just explain the use of _sun_mangle for me: how are the two parameters used? 

x = yaw, y = pitch, z = placeholder. 

Thanks. I understand yaw and pitch but not 'placeholder'.

Sorry to be dense but I have never used _sunlight before: I am only trying it now after reading some comments by AguirRe in this forum.

I have a rather large (high) set of mountains in FMB12 and lighting them is proving difficult.

As a by the way, is 256 the largest texture size that can be used in Quake1 - I can see some pretty obvious tiling? 

'Placeholder' means just put zero; i believe it's needed becuase the compiler expects a vector, but only actually has a use for two or the numbers.

Re: texture size, first, check this: http://www.celephais.net/stuff/texturefaq.htm

Second, try scaling the texture up, or using more lighting variation to break up the large surfaces. (I know, "lighting variation" is contrary to the whole _sunlight aesthetic. But you could still put in some subtle point lights or antilights to create the needed variety.) 

placeholder is exactly that - it doesn't do anything, it's just necessary to convince the compile utils that you're using a 3-part vector. 

Doesn't HalfLife allow texture randomization? How does it do it? 

(or gals!) 

Proof: http://www.celephais.net/IAmAGirl.jpg 

More proof!

<goetz> http://www.celephais.net/quake/
<goetz> metlslime is that u ?
<goetz> i thought u were male
<metlslime> i'm a hot japanese girl
<Auhsan> woa
<Auhsan> I love you metlslime
<metlslime> this explains why i never get laid, after all, who wants to have sex with a hot japanese girl?
<metlslime> nobody. I wish i was one of those skinny white computer geeks. They get all the sex.
<Auhsan> from their hands
<metlslime> heh
* metlslime cries 

I am just trying to see the difference between using _sunlight or placed light entities in a map.

For some reason, light does not seem to work on my trial, 2055 brush, map. Here is the readout: -

4361 planes 87220
4252 vertexes 51024
2387 nodes 57288
6 texinfo 240
3888 faces 77760
13244 clipnodes 105952
1202 leafs 33656
4808 marksurfaces 9616
17010 surfedges 68040
8506 edges 34024
2 textures 130652
lightdata 0
visdata 0
entdata 176

File: ter2.bsp
3 entities read, 1 are lights, 3888 faces

Light: 0.0%, Elapsed: 0:00
Light: 100.0%, Elapsed: 0:01

lightdatasize: 0
0 switchable light styles

Elapsed time : 0:02
BspBuild [Light complete]

The numbers mean nothing to me. Can anybody spot my (probably obvious) error? 

like you only put on light entity:
3 entities read, 1 are lights, 3888 faces


sunlight needs: _sunlight # for intensity, and _sun_mangle x x x for direction. 

there's a phantom brush which has cropped up in my map which i'm trying to get rid of...

the problem is, the brush doesn't appear in gtkradiant, but when i compile the map, it is there, in quake. there's nothing wrong with the brush, other than it is a phantom... it's not super deformed or huge or any of the common problems...

any suggestions? 

Look in the readme for sunmangle details and some recommendations to start with. The third number, the "placeholder", isn't required at all anymore in my tools (but is accepted for compatibility).

In your log printout, lightdatasize is 0, which means that there is no lights generated at all (the map is probably pitch black). There is one light entity (sunlight isn't counted as a light entity), but for some reason is doesn't generate any measurable light.

Send me the zipped map+wad and what tool arguments you're using and I'll try to find out why it doesn't work. 

I believe texture randomisation in HL is done with a naming convention, so to randomise between 3 textures you would name them
-0texname
-1texname
-2texname

and so on. They probably have to have the same dimentions for this to work. 

Dumb question probably, but you're sure you don't have anything either filtered or hidden in-editor?

If not, try brush-cleanup (either plugins or a button, depending on what version you're running).

You could also try hiding all brushes in the area (select one-by-one and hide) and then doing a "select touching" in the empty space that's left and see if you get anything selected?