Proper Skybox Behavior?

[KillPixel]

The sky isn't blocking visibility of geometry behind it, is this normal?

Code: Select all

textures/wtest1/devsky
{
	qer_editorimage textures/wtest1/devsky
		
	surfaceparm noimpact
	surfaceparm nolightmap

	q3map_sunExt 1 1 1 300 45 60 3 16
	q3map_lightmapFilterRadius 0 8
	q3map_skylight 100 3

	skyparms textures/sky/desertsky - -
}

• [lvlshot]http://www.killpixel.com/safe/skybox.jpg[/lvlshot]

[cityy]

Yes, it is, unfortunately..

[obsidian]

In real life, you'd be able to see a structure that stands up higher than the room you're in. Skyboxes are designed to simulate that.

[KillPixel]

Kind of a surprising limitation, bummer.

[cityy]

It gets even better when you try to work out vis and the geometry beyond the skybox starts flickering depending on the player position.

[dONKEY]

There are three common solutions.
You either make the second room deliberately visible form the out side and extend the sky box around that geometry as well,
or make vis your bitch so the offending geometry cuts culled, a simple right angle passage between the two rooms would help, for example, rather than the straight line of sight.
or add details higher up in the lower area that block the player from being able to see the unwanted geometry. Quite often this last approach can lead to interesting details in your maps. You can let your imagination fly because these details never interfere with play.

[AEon]

Nice reminder of how to cope with with this issue dONKEY.

[cityy]

There are three common solutions.
or add details higher up in the lower area that block the player from being able to see the unwanted geometry. Quite often this last approach can lead to interesting details in your maps. You can let your imagination fly because these details never interfere with play.

This is the approach I like the most. Most detail in my maps is in the ceillings.. it's kind of controversal because it's practically invisible most of the time but tends to work best with quake gameplay, as dONKEY says.