Void: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (Fixed spelling and poor grammer)
(Removed guesswork/ wrong information)
Line 5: Line 5:
The map can occasionally share it's inside space with the void causing an error known as a [[leak]]. Loading the map's compiled [[pointfile]] plots a course between this void and the closest entity in the map which can help patch leaks.
The map can occasionally share it's inside space with the void causing an error known as a [[leak]]. Loading the map's compiled [[pointfile]] plots a course between this void and the closest entity in the map which can help patch leaks.


The Void is not physical. It isn't a [[brush]], [[entity]] or hard-coded into source but the lack of code, entities and brushes.
The void is not physical. It isn't a [[brush]] or [[entity]] but the lack of entities and brushes.


When viewing the Void from inside the map, it picks colours from the screen pixels nearby. Much like in computers, clicking and dragging something makes it repeat several times without physically being there. With the Void, moving your view can make [[textures]] repeat several times on the Void.
When viewing the void from inside the map, the [[w:backbuffer|backbuffer]] will not be cleared with black. This causes the [[w:Hall_of_mirrors_effect#.22Hall_of_mirrors.22_effect|HoM effect]] to appear. The pixels that nothing is drawn to the next frame will contain what was drawn to them in the past. [[w:Video_post-processing|Post processing effects]] like filmgrain, HDR (bloom) and motionblur will indefinitely add their output to the backbuffer; which can result in a solid color or random patterns where the backbuffer is not refreshed properly.
In HDR mode it also makes the view glow, to the point where a solid colour overwrites the whole page. Usually, it keeps on doing so, until the Void visible is completely white.


The Void is present in both the [[Goldsource]] and [[Source]] engines. It's appearance in other game engines is not entirely impossible though.
By default a clear only happens when the vieworigin is assumed to be in a 'solid', the void is marked as such.


[[Category:Glossary]]
[[Category:Glossary]]

Revision as of 06:24, 21 January 2011

In programming, void is used when declaring a function that does not return a value. void* is a pointer to such a function.

The void is the black space outside the world. It is an infinitely large area of nothingness that surrounds every map.

The map can occasionally share it's inside space with the void causing an error known as a leak. Loading the map's compiled pointfile plots a course between this void and the closest entity in the map which can help patch leaks.

The void is not physical. It isn't a brush or entity but the lack of entities and brushes.

When viewing the void from inside the map, the backbuffer will not be cleared with black. This causes the HoM effect to appear. The pixels that nothing is drawn to the next frame will contain what was drawn to them in the past. Post processing effects like filmgrain, HDR (bloom) and motionblur will indefinitely add their output to the backbuffer; which can result in a solid color or random patterns where the backbuffer is not refreshed properly.

By default a clear only happens when the vieworigin is assumed to be in a 'solid', the void is marked as such.