Fog in WinQuake

[TimeServ]

Quake's lack of color variance makes any palette changes or attempts to fit it into 8/16-bit generic color palettes suffer too much. Maybe the fog might look better if your fog colormaps tried fitting to a Quake palette color ramp per distance instead of a straight up blend or something like that.

I've never really felt that fog was a good thing to have on standard Quake maps but people seem to want that feature.

[JasonX]

What about black fog?

[mankrip]

Black fog looks nice.

[leileilol]

I remember the days when black fog was called 'light diminishing'

now get off my lawn!

[mh]

You could do cheap and cheesy (but fast) fog by blending miplevels 1, 2 and 3 of textures with your chosen fog colour. It actually looks OK in hardware with trilinear interpolation, but I'd guess it would look awful in software.

[mankrip]

And wouldn't work for anything but BSP surfaces.

[mh]

Well I did say cheap and cheesy.

[TimeServ]

Kinda what I was talking about.. also this technically isn't fog.

[ceriux]

actually it kinda is. just set a view distance and have it stop rendering after that distance or something. i have no idea how it's supposed to work in C. but that actually looks pretty nice.

[dreadlorde]

How about some volumetric fog first?

[leileilol]

How about some volumetric fog first?

q3bsp is thataway

[mh]

For volumetric fog you really need to start putting entities into your map so that you can define which surfaces are fogged. Then I'd guess that you need to change mnode_t::contents and mleaf_t::contents so that they can take bitwise values instead of their current single values, and |= them with CONTENTS_FOG in your BSP compiler. Oh, and also update the BSP compiler so that it won't explode when you do this. And define a func_fog entity that sets the fog parameters correctly.

Whee, such fun!

[TimeServ]

It's really too bad the software renderer is the worst code to go through...

[Spike]

For volumetric fog you really need to start putting entities into your map so that you can define which surfaces are fogged. Then I'd guess that you need to change mnode_t::contents and mleaf_t::contents so that they can take bitwise values instead of their current single values, and |= them with CONTENTS_FOG in your BSP compiler. Oh, and also update the BSP compiler so that it won't explode when you do this. And define a func_fog entity that sets the fog parameters correctly.

you can't do volumetric fog with just contents, it makes no sense. you need to consider the fog plane, and which fog region to use, rather than a simple 'its fogged' flag.

Q3bsp has a list of fog regions, and each surface can be in at most one fog region. Meaning each surface is fogged based upon its distance from the view, and its distance from the fog plane (if its on the other side of it from the view). So for q3 its 'just' an extra pass with special texture coords, drawn after each mesh (drawnormal(); if (surf->fog) {glColor4f(surf->fog->colour);updatetexcoords();drawindicies();}, basically). Keeps it simple.