Visibility: Difference between revisions
Jump to navigation
Jump to search
Mblackwell (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
The [http://www.eduke32.com/wiki/index.php?title=Player_Member_Functions Player Member Function] "visibility" allows you to edit this on the fly through Cons. If not constantly set it will put itself back at the value specified in DEFAULTVSIBILITY. This is useful for many effects, including creating a lantern, or flashing the screen when you fire (as with the [[flash]] command or EXPLOSION2), but without making the shading/fog fully bright. | The [http://www.eduke32.com/wiki/index.php?title=Player_Member_Functions Player Member Function] "visibility" allows you to edit this on the fly through Cons. If not constantly set it will put itself back at the value specified in DEFAULTVSIBILITY. This is useful for many effects, including creating a lantern, or flashing the screen when you fire (as with the [[flash]] command or EXPLOSION2), but without making the shading/fog fully bright. | ||
Eduke 2.1 did not save this in the mhs file resulting in a game stuck on fullbright. | |||
Revision as of 05:24, 10 January 2005
Visibility is distance shading/fog used in the BUILD Engine. It is originally set to whatever number DEFAULTVISIBILITY in USER.CON is defined as. 0 is considered fully bright (no fog). The higher the value
The Player Member Function "visibility" allows you to edit this on the fly through Cons. If not constantly set it will put itself back at the value specified in DEFAULTVSIBILITY. This is useful for many effects, including creating a lantern, or flashing the screen when you fire (as with the flash command or EXPLOSION2), but without making the shading/fog fully bright.
Eduke 2.1 did not save this in the mhs file resulting in a game stuck on fullbright.