CVARs:Display

From ZDoom Wiki
Jump to: navigation, search

These CVARs control various aspects of ZDoom's renderer and options relating to the in-game display.

See the CVARs article for general information on how to access and edit variables.

Game options

Default: false
When false, rocket explosions are drawn with normal translucency. When true, rocket explosions use additive translucency instead, producing a brighter effect. This affects the death state sequence of any actor with the DEHEXPLOSION flag.
Default: 0
If this cvar is non-zero, it draws a crosshair. If this cvar is negative, the crosshair is translucent, otherwise it is opaque. The specific crosshair drawn depends on the value of this cvar.
Default: "ff 00 00" ██
This is the crosshair's color if crosshairhealth is false.
Default: false
By defaults mods may use A_SetCrosshair in a weapon definition to designate a crosshair to use for that weapon. If you want to override this and force the game to use your own selected crosshair, set this CVAR to true.
Default: false
Set this to true if you want the crosshair to temporarily enlarge each time you pick up an item.
Default: true
When true, the crosshair's color reflects your current health. Green is healthy, red is near death, and intermediate colors are somewhere in between. Set this to false, if you want the crosshair to have a constant color (specified by the crosshaircolor cvar) instead.
Default: false
Set this to true if you want the [crosshair]] to always appear the same size at all resolutions. Leaving it at false causes the crosshair to be drawn normally.
Default: 0
Affects the palette flashes that happen in certain circumstances, notably in Hexen and Strife. The value is combined from several palette flash flags.
Default: false
If true, ZDoom uses accurate palette flashes for delayed poisoning from Strife's damaging floors.
Default: false
If true, ZDoom uses accurate palette flashes for the Bloodscourge and Wraithverge weapons.
Default: false
If true, ZDoom uses accurate palette flashes for frozen death.
Default: false
If true, ZDoom uses accurate palette flashes for poison damage.
Default: false
Because ZDoom allows the framerate to go above 35 FPS, monster movement is interpolated by default so they move more smoothly and take advantage of the additional frames. However, the actual AI that moves them is still limited to the normal 35 tics per second rate. In some situations, this may cause jerky or inaccurate movement when ZDoom attempts to interpolate. This option can be enabled so that monsters will only visibly move at the 35 FPS rate.
Default: 0.75
Defines the level of alpha transparency for lost souls and other actors with the SoulTrans RenderStyle. Values are clamped to stay between 0.25 and 1.
Default: true
When true, teleporters will create an MiniWikipediaLogoIcon.pngUnreal-like zooming effect when you use them.
Default: 1
Selects the type of screen wipe to use. There are currently four possible settings for this cvar:
  • 0:No wipe
  • 1:Melt
  • 2:Burn
  • 3:Crossfade

Chase camera

Default: 90.0
This is how far away from the player the chasecam likes to be, but it will get closer as necessary to avoid going inside walls.
Default: -8.0
This is the base height above the top of the player's head at which the chasecam will be positioned. Looking up and down will move the camera in the opposite direction so that the player stays at approximately the same height on the screen. Large values of this CVAR (either positive or negative) will produce strange output.
Default: false
If this CVAR is true, then demos will automatically start with the chasecam active.
Default: false
If this CVAR is true, the player automatically goes into chasecam mode when dying. This use of the chasecam is not considered a cheat.

Decals

These CVARs affect decals.

Default: true
When true, whenever something bleeds, it has a chance of leaving blood spots on nearby walls. Setting this to false might help performance on low-end machines.
Default: 1024
This is the maximum number of decals that can exist in the game at one time. Decals are graphics that are placed on walls in response to blood splatter and projectile impacts. Setting this to 0 will disable decals entirely. This CVAR can be set to a maximum value of 2,147,483,647 which would allow an infinite number of decals for all intents and purposes. Be aware, however, that hundreds of decals visible on the screen at one time can cause lag even on fast computers.
Default: true
Set this to false if you don't want exploding missiles to leave scorch marks.
Default: true
ZDoom clips decals to sidedefs. In order to hide this, the game will create as many duplicate decals on adjoining sidedefs as needed to make it appear that there is only one unbroken decal on the wall. Set this cvar to false if you don't want this.

Heads-Up Display (HUD)

Default: 0
Determines whether inventory and weapon tags are shown when using invnext, invprev, weapnext, and weapprev. Possible values are:
  • 0: Don't show anything
  • 1: Show inventory tags
  • 2: Show weapon tags
  • 3: Show both inventory and weapon tags
Default: 0.75
Controls how transparent the console is when it is lowered.
Default: false
Controls scaling of the fullscreen hud. At resolutions of 640x400 or above, setting this cvar to true will cause the icons to be scaled to approximately the same size they would be at 320x200. If this cvar is false, the icons will always be drawn without any scaling.
Default: 5 (██ gold)
The color used to display weapon and inventory tags when scrolling through them.
Default: 10
This CVAR determines the size of the view window. Valid values are in the range 3-12 inclusive. Attempts to set this cvar to values outside this range will be truncated. 10 shows the normal status bar at the bottom of the screen. 3 is the smallest view window, and 12 is full screen. 11 is also full screen, but includes a small overlaid heads-up display (which can be changed to the alternate HUD with hud_althud).
Default: false
If this CVAR is true, the mugshot will show the infamous "ouch face" when the player is healed by at least 20 points while taking damage, reestablishing the bogus behavior found in vanilla Doom.
Default: false
When this CVAR is true, the status bar will be scaled so that it covers the entire width of the screen in higher resolutions. At low resolutions this may look ugly, but at high resolutions it should look good enough.

Alternate HUD

The following variables all affect the alternate HUD.

Default: false
Controls whether the alternate HUD is used in full-screen HUD mode (screenblocks 11).
Default: 2
Scale of the alternate HUD.
Default: 25
The percent value of the maximum below which the current ammo count will be displayed in red (██).
Default: 50
The percent value below which the current armor rating will be displayed in yellow (██). Greater values are displayed in green (██).
Default: 100
The percent value of the maximum below which the current ammo count will be displayed in green (██). Greater values are displayed in blue (██).
Default: 25
The value below which the current armor rating will be displayed in red (██).
Default: 50
The value below which the current armor rating will be displayed in yellow (██).
Default: true
If true, the berserk icon is shown instead of the health icon when the player has a PowerStrength active. If false, the health icon is displayed regardless. This also requires a berserk icon to be defined and valid (PSTRA0 by default in Doom games).
Default: 100
The value below which the current health total will be displayed in green (██). Greater values are displayed in blue (██).
Default: 25
The value below which the current health total will be displayed in red (██).
Default: 50
The value below which the current health total will be displayed in yellow (██).

HUD statistics

Default: false
Toggles whether the player's tally of found items is displayed.
Default: true
Toggles whether the player's tally of killed monsters is displayed.
Default: false
Toggles whether the player's score is displayed.
Default: true
Toggles whether the player's tally of found secrets is displayed.
Default: false
Toggles whether the player's accuracy and stamina are displayed.
Default: 0
Selects whether a timer is shown in the upper-right corner of the screen. The time can show the level time, hub time, total game time, or system time; and the precision can go from hours and minutes only to also showing seconds. When set to level time, the precision can even go to milliseconds.
  • 0: Off
  • 1: Level time, down to milliseconds
  • 2: Level time, down to seconds
  • 3: Level time, down to minutes
  • 4: Hub time, down to seconds
  • 5: Hub time, down to minutes
  • 6: Game time, down to seconds
  • 7: Game time, down to minutes
  • 8: System time, down to seconds
  • 9: System time, down to minutes
Default: true
Toggles whether the weapons in the player's inventory are displayed.
Default: true
While the automap is active, the coordinates displayed correspond to the position of the cursor at the center of the map. If false, the coordinates remain set to the player's position.
When follow mode is on, the coordinates of the cursor and of the player should be the same except potentially for the Z coordinate. The cursor's Z position will always be that of the sector floor at this point; whereas a player might be flying, jumping, walking on things, or present above a 3D floor or 3D middle texture.

HUD colors

The various hudcolor_* variables use TEXTCOLO color values:

code color code color code color code color code color code color code color
0 reddish brick ██ 1 tan ██ 2 gray ██ 3 green ██ 4 brown ██ 5 gold ██ 6 red ██
7 blue ██ 8 orange ██ 9 white ██ 10 yellow ██ 12 black ██ 13 light blue ██ 14 cream ██
15 olive ██ 16 dark green ██ 17 dark red ██ 18 dark brown ██ 19 purple ██ 20 dark gray ██ 21 cyan ██
Default: 8 (██ orange)
The color used to display on the automap the time spent in the current visit of a level in a hub.
Default: 6 (██ red)
The color used to display the labels for the various statistics optionally shown as determined by the hud_show* variables.
Default: 3 (██ green)
The color used to display the values for the various statistics optionally shown as determined by the hud_show* variables.
Default: 6 (██ red)
The color used to display on the automap the hub spent in the current hub, or in the current level outside of a hub.
Default: 10 (██ yellow)
The color used to display on the automap the level name.
Default: 5 (██ gold)
The color used to display on the automap the total time spent in the current game.
Default: 3 (██ green)
The color used to display on the automap the player coordinates.
Default: 5 (██ gold)
The color used to display the optional timer on the normal view of the alternate HUD.

Scoreboard

These variables affect the scoreboard in multiplayer. The various *color variables use TEXTCOLO color values:

code color code color code color code color code color code color code color
0 reddish brick ██ 1 tan ██ 2 gray ██ 3 green ██ 4 brown ██ 5 gold ██ 6 red ██
7 blue ██ 8 orange ██ 9 white ██ 10 yellow ██ 12 black ██ 13 light blue ██ 14 cream ██
15 olive ██ 16 dark green ██ 17 dark red ██ 18 dark brown ██ 19 purple ██ 20 dark gray ██ 21 cyan ██
Default: true
Controls whether the scoreboard is shown in cooperative mode.
  • sb_cooperative_headingcolor (integer)
Default: 6 (██ red)
The color used for headings on the cooperative scoreboard.
  • sb_cooperative_otherplayercolor (integer)
Default: 2 (██ gray)
The color used to display other players' names on the cooperative scoreboard.
  • sb_cooperative_yourplayercolor (integer)
Default: 3 (██ green)
The color used to display your own name on the cooperative scoreboard.
Default: true
Controls whether the scoreboard is shown in deathmatch mode.
  • sb_deathmatch_headingcolor (integer)
Default: 6 (██ red)
The color used for headings on the deathmatch scoreboard.
  • sb_deathmatch_otherplayercolor (integer)
Default: 2 (██ gray)
The color used to display other players' names on the deathmatch scoreboard.
  • sb_deathmatch_yourplayercolor (integer)
Default: 3 (██ green)
The color used to display your own name on the deathmatch scoreboard.
  • sb_teamdeathmatch_enable (boolean)
Default: true
Controls whether the scoreboard is shown in team deathmatch mode.
  • sb_teamdeathmatch_headingcolor (integer)
Default: 6 (██ red)
The color used for headings on the team deathmatch scoreboard.

Intermission screens

Default: false
If this CVAR is true, the user has to manually end the 'entering level' page with the +use command. By default, this screen is automatically left after 140 tics (four seconds). In a network game, this effect is enabled if any player switches this on. Note that custom intermission scripts can use the noautostartmap keyword to achieve the same effect; this CVAR being false will not override the presence of this keyword.
Default: false for Heretic and Hexen, true for other games
When false, intermission statistics are printed as absolute values such as "7 of 9" as in Heretic. When true, intermission stats are printed as percentages such as "50%".
Default: true
If true, show the total time spent on the current game during the intermission tally screen, in addition to the time spent on the completed level. If false, only the time spent on the completed level is shown.

Renderer

Default: 0
Controls how blood is drawn. Supported values are:
0: Blood is drawn as sprites
1: Blood is drawn as both sprites and particles
2: Blood is drawn as particles only
Default: false
When true, the game is limited to 35 FPS, as it was originally in Doom. When false, the game frame rate will be as high as your machine is capable of (within the limits of vid_maxfps, if set). You can use this in conjunction with vid_vsync to control whether or not the maximum frame rate is restricted to your monitor's refresh rate.
Default: 0
Controls how bullet puffs are drawn. Supported values are:
0: Puffs are drawn as sprites
1: Puffs are drawn as particles
Default: 1
Controls whether or not rockets and grenades leave trails of smoke behind them, as determined by the ROCKETTRAIL and GRENADETRAIL flags. Supported values are:
0: No rocket trail
1: Particle trail
2: Sprite trail (spawning RocketSmokeTrail or GrenadeSmokeTrail in the wake of the projectile)
3: Both particles and sprites
If an actor has both the ROCKETTRAIL and GRENADETRAIL flags, it can have both particle types trailing it, but only the rocket smoke sprites.
Default: true
If this CVAR is true, the game will be displayed fullscreen. Otherwise, it will be drawn in a window. Some video cards may require that you have fullscreen false in order to run ZDoom.
Default: 1.0
Controls the amount of gamma correction applied to the display. 1.0 is equivalent to no correction, while larger numbers translate into a brighter display, and smaller numbers translate into a darker display. 0.0 is invalid and will be rejected. Negative numbers are technically invalid but will be accepted solely for the novelty value doing so provides.
Default: 1.0
Controls the blue component of gamma correction. A value of 0 is ignored, otherwise it is used as a multiplier to the gamma value.
Default: 1.0
Controls the green component of gamma correction. A value of 0 is ignored, otherwise it is used as a multiplier to the gamma value.
Default: 1.0
Controls the red component of gamma correction. A value of 0 is ignored, otherwise it is used as a multiplier to the gamma value.
Default: true
Setting this false will disable the display of 3D floors.
Default: 0
Clears the framebuffer between each frame. Several values are possible:
  • 0: By default, do not clear the buffer. This allows the DoomWikiLogoIcon.pnghall of mirrors effect to happen in certain conditions. Since the variable is not archived, it is reset to this value whenever ZDoom is run.
  • 1: Fill with black. This prevents HOMs and will generally make the affected area less noticeable.
  • 2: Fill with white. As with black, though the areas will generally be more noticeable.
  • 3: Fill in alternation with black and white, making the areas flash and helping them be more noticeable. This is roughly similar to Boom's TNTHOM "cheat".
  • 4: Fill with each color of the palette in sequence, creating a pulsing effect.
  • 5: Fill with a random color. Seizure warning!
Default: 1
Selects which of two algorithms to use to draw sprites and masked textures. Method 0 is the original algorithm used by DOOM. Method 1 is a new algorithm optimized for Pentium IIs and can perform significantly better with that or comparable processors. Ironically, method 0 is slightly faster than method 1 on Pentium III and Athlon processors (though not significantly so).
Default: false
When set to true, segs will be drawn as solid colors instead of textures. This is useful if you want to see how a node builder split a level's linedefs. Otherwise, it just looks ugly.
Default: 1
When set to 0, the "fuzz" effect on spectres and partially invisible players will be replaced with translucency. If set to 1, normal fuzz effect is used.
If set to 2, the "shadow" RenderStyle is used. This emulates the rendering of fuzz in GZDoom when not using one of the pixel shaders.
Default: true
Setting this false will disable the display of mirrors.
Default: true
When false, the game will not draw the player's weapon or muzzle flash, which can be nice for screenshots.
Default: true
Setting this to false will disable all translucency effects in the game.
Default: true
Setting this to false will disable voxel display.
Default: 1
This variable affects how fake contrast (the difference between sector light and wall light to make angles more contrasted) is handled. 0 disables it altogether ("even lighting"). The default value of 1 uses the vanilla fake contrast (only linedefs perfectly aligned with the X or Y axis are affected). A value of 2 ("smooth lighting") generalizes fake contrast to all angles, with values proportional to the angle.
Default: true
Setting this to false will disable the display of fog boundaries. Fog boundaries are sections where two areas with different fog colors meet. If the boundary is not drawn, then it will look like there is no fog at all in front of the boundary. Some old levels may look bad with fog boundary drawing enabled, which is why this cvar is available.
Default: 4000
The maximum number of particles that will be rendered at once.
Default: true
If this CVAR is true, ZDoom uses special code to handle non-power-of-two textures tiling vertically. Setting it to false uses the old behavior where the texture is artificially increased in height to a power of two, each column being prolonged by the data from the next column and the last being prolonged by a DoomWikiLogoIcon.pngtutti-frutti effect.
Default: true
If set to true, particles are drawn. Otherwise, they aren't.
Default: 1.0
Factor which scales the camera-shaking effects of Hexen-style earthquakes. Value can be between 0 (no shaking) and 1 (normal shaking).
Default: true
Set this to false to disable the drawing of skyboxes. Then every sky will be drawn as a standard sky instead of as a skybox.
Default: false
If true, disable railgun spiral if the inner trail color is -1.
Default: 1
Sets the sparsity of spiral particles in railgun shots. The normal amount of particles is divided by this value; a value of 0 disable the spiral entirely.
Default: 1
Sets the sparsity of trail particles in railgun shots. The normal amount of particles is divided by this value; a value of 0 disable the trail entirely.
Default: true
Set it to false to disable shaders for fixed colormap effects (e.g. invulnerability). This should only be necessary for SM1.4 cards with buggy drivers.
Default: false
Forces smoothlighting to the walls in maps.
Replaced by r_fakecontrast in development versions.
Default: true
Controls whether or not short sky textures are stretched so that you do not see them wrap when you look up or down.
This cvar contains the width and height of the current view window. This cvar is read only.

Direct3D

These variables affect ZDoom's Direct3D renderer.

Default: true
Enables a technique meant to minimize input lag with vsync enabled: Two surfaces are alternately locked for read-only access each frame, forcing the driver to stop buffering more than one frame at a time. See xyzw.de/c120.html for more details.
Default: 0
?

OpenGL

OpenGL.png (OpenGL only: not supported by ZDoom)

Default: false
Choose whether to enable OpenGL-based anti-aliasing in the automap.
Default: true
Dead code, declared but not referenced anywhere.
Y and XY billboarding.
Default: 0
Sets the default billboarding mode for sprites. The default value of 0 means to use Y-billboarding (sprites become paper-thin when looked at steep angles from above or below); a value of 1 means to use XY-billboarding (sprites are always facing the camera, which might make them appear at odd angles to the geometry). This is overridden by actors having the FORCEYBILLBOARD or FORCEXYBILLBOARD flags.
Note that some minor graphical glitches should be expected when XY-billboarded sprites are present near 3D floors.
Default: true
This is similar to gl_billboard_mode, but only applies to particles. If true, XY-billboarding is always used for them; if false it depends on the gl_billboard_mode setting.
Default: false
Choose whether fog is rendered based on full brightness. In the software renderer, light level in colored fog is effectively used for fog density. This option looks good for bright, white fogs, and less so for dark, black fogs.
Default: false
Chooses whether OpenGL shaders are used to handle brightmaps. This CVAR is only used with hardware limited to MiniWikipediaLogoIcon.pngshader model 3. If shader model 4 is supported, shaders are always used for brightmaps; if support is limited to shader model 2, they are never used.
Default: false
Dead code, declared but not referenced anywhere.
Default: false
Chooses whether OpenGL shaders are used to handle colormaps. This CVAR is only used with hardware limited to MiniWikipediaLogoIcon.pngshader model 3. If shader model 4 is supported, shaders are always used for colormaps; if support is limited to shader model 2, they are never used.
Default: false
If this CVAR is true, the OpenGL context is created in debug mode. This variable is only relevant during initialization and is not archived; if you want to see its effect you have to set it from the command line: gzdoom +set gl_debug 1 for example.
Default: true
Default: 70
This value is used to compute the distance fog table.
Default: true
Default: false
Chooses whether OpenGL shaders are used to handle dynamic lights. This variable can only be set to true if the GLSL implementation available supports at least 1024 uniform variables and provides shader model 4 features.
  • gl_enhanced_nightvision (boolean)
Default: true
Enables or disables the enhanced nightvision effect which changes how the PowerLightAmp and PowerTorch effects work. If false, they behave like the software renderer and merely give full brightness to everything. If true, however, the light amplification visor shows the world geometry in green and the sprites of monsters and items are in inverted colors; while everything illuminated by the torch lies in a flickering golden light.
Default: 3
If enhanced night vision is on, stealth monsters and other actors with the STEALTH flag or the Shadow RenderStyle can be seen while an effect altering vision with a fixed colormap is active. Possible values are:
  • 0: Enhanced night vision has no effect.
  • 1: Infrared night vision makes stealth monsters visible and shadowed actors easier to see.
  • 2: Both infrared and torch have this effect of making such actors easier to see.
  • 3: Any sort of fixed colormap have this effect.
Default: false
Chooses whether OpenGL shaders are used to handle fog. This CVAR is only used with hardware limited to MiniWikipediaLogoIcon.pngshader model 3. If shader model 4 is supported, shaders are always used for fog; if support is limited to shader model 2, they are never used.
Default: 1
Chooses how distance fog is generated. Possible values are:
  • 0:No fog
  • 1:Standard fog
  • 2:Radial fog
Default: false
Default: 0
Defines how the spectre fuzz effect (RenderStyle Fuzzy or OptFuzzy) is handled. Possible values include:
  • 0: Shadow (equivalent to RenderStyle Shadow)
  • 1: Pixel fuzz
  • 2: Smooth fuzz
  • 3: Swirly fuzz
  • 4: Translucent fuzz
  • 6: Noise
  • 7: Smooth Noise
Default: true
Chooses whether OpenGL shaders are used to handle glowing flats. This CVAR is only used with hardware limited to MiniWikipediaLogoIcon.pngshader model 3. If shader model 4 is supported, shaders are always used for glowing flats; if support is limited to shader model 2, they are never used.
  • gl_interpolate_model_frames (boolean)
Default: true
When this CVAR is true, model frames are interpolated, smoothing up their movement. This also concerns voxels.
Default: 20
The minimum ambient light level.
Default: true
Unused. Only referenced in a disabled part of the code.
Default: true
If true, particles are affected by dynamic lights.
Default: true
If true, sprites are affected by dynamic lights.
Default: 3
Sets the default lighting model to use in maps. Note that the choice made here can be overridden by the lightmode property in a MAPINFO map definition.
  • 0: Uses a standard OpenGL formula.
  • 1: Uses a weak fading keeping sectors relatively bright.
  • 2: A close approximation to the software renderer's display. Uses MiniWikipediaLogoIcon.pngGLSL to handle the increased brightness around the player's viewpoint; otherwise identical to 3.
  • 3: Close approximation of the software renderer, but without the brightening of nearby areas.
  • 4: Emulates the lighting model of the Doom Legacy 1.42 OpenGL renderer.
  • 8: A MiniWikipediaLogoIcon.pngGLSL implementation of the equations used by Id to generate the colormaps, and to brighten the area around the player's viewpoint. Falls back to 3 if shaders are unavailable.
Default: true
Default: false
Default: true
  • gl_lights_intensity (float)
Default: 1.0
Default: 1.0
  • gl_mask_sprite_threshold (float)
Default: 0.5
  • gl_mask_threshold (float)
Default: 0.5
Default: true
Default: true
Default: false
  • gl_nocoloredspritelighting (boolean)
Default: false
Default: false
Default: false
Default: false
Default: 2
Default: true
Default: true
Default: false
Default: true
Default: false
Default: false
Default: true
Default: true
Default: 1.8
  • gl_sclipthreshold (float)
Default: 10
Default: false
Default: 16
Default: true
Default: false
Default: false
Default: 1
Default: true
Default: 4
  • gl_texture_filter_anisotropic (integer)
Default: 8
Default: 0
Default: 0
  • gl_texture_hqresize_fonts (boolean)
Default: true
  • gl_texture_hqresize_maxinputsize (integer)
Default: 512
  • gl_texture_hqresize_sprites (boolean)
Default: true
  • gl_texture_hqresize_targets (integer)
Default: 7
  • gl_texture_hqresize_textures (boolean)
Default: true
Default: true
Default: true
Default: true
Default: true
Default: false
Default: 2
Default: false
Default: 0
Default: false
Default: 8
Default: false
Default: 90.0
Default: 4
Default: 0.0
Default: 0
Default: 1
Default: 1

Polymost

(deprecated in development versions rbbc3b69+, but still valid in official version 2.7.1.)

Default: 0.0
The global tilt angle. This is only used by the incomplete and mostly-abandoned Polymost renderer.
Default: 0
This cvar controls ZDoom's Polymost rendering.
  • 0 - No polymost rendering.
  • 1 - Draw polymost wall edges over normal render display. This mode is interesting as it allows to see, when looking up or down, how the normal software renderer distorts the view.
  • 2 - Draw polymost walls with wireframe instead of normal render display. Since the polymost renderer doesn't render textures, this mode is the second least usable of the three.
  • 3 - Draw polymost walls without wireframe intead of normal render display. Since the polymost renderer doesn't render textures, this mode is the least usable of the three.
Default: false
If this CVAR is true, the polymost render is done in a small section of the viewscreen, instead of a full overlay. (If r_polymost is 2, the rest of the screen is not updated at all and gets filled with HOMs., so this should only be used with r_polymost 1.) Within that window, Y-shearing is applied when looking up and down. The window itself moves up and down the screen and its borders are more and more broadened the farther away they are from the center.

Video adapter

  • vid_adapter (integer) (OpenGL or Win32 Only)
Default: 1
Defines which screen is used if multiple monitors are available. A list of available video adapters can be obtained by using the vid_listadapters console command.
Default: 0
Which aspect ratio is used.
  • 0: Autodetect appropriate aspect ratio.
  • 1: 16:9
  • 2: 16:10
  • 3: 4:3
  • 4: 5:4
  • 5: 17:10
  • vid_attachedsurfaces (boolean) (Win32 Only)
Default: false
Controls how the game allocates video memory. False is the standard setting and will always produce a usable display. If you find that there are patches of pure black and pure white on the screen (especially noticeable when a demon is right in your face), try setting this to true. Certain old Windows 95 video drivers are said to need this fix, and it is also necessary under NT 4. Unfortunately, many new video drivers (including those under NT 4) will produce a scrambled display if the screen width is not 512 or 1024 pixels and this is set to true.
Default: "None"
Which mouse cursor to use. This overrides the GameInfo cursorpic value. Default is "None" to use the GameInfo cursor, possible values include "-" (system cursor), or one of the graphics provided by ZDoom: "cursor", "chexcurs" (a waffle), "doomcurs" (the endgame bunny head), "herecurs" (the elven wand), "hexncurs" (the Hexen logo's red X), or "strfcurs" (a sigil logo). It is possible to use custom cursors, as long as they fit the requirements (no more than 32x32).
Default: 8
This cvar is meant to specify the default screen depth, but the setting is currently ignored because only 256-color (8-bit) display modes are supported.
Default: 480
Specifies the default screen height to use if not overridden at the command line by the -height switch.
Default: 640
Specifies the default screen width to use if not overridden at the command line with the -width switch.
Default: 8
Controls how many bits per pixel the fullscreen display gets created with. The game is still rendered in 8-bit, but this is for the benefit of cards that don't support that or work better with non-8-bit displays.
  • vid_forceddraw (boolean) (Win32 Only)
Default: false
Forces the use of MiniWikipediaLogoIcon.pngDirectDraw instead of Direct3D for blitting graphics to the screen or render window. Direct3D is generally preferable as it allows truecolor rendering for HUD graphics, but forcing the use of DirectDraw routines may solve problems caused by faulty drivers or aged hardware.
Default: true
If false, this disables hardware assistance for the 2D layer when using the Direct3D renderer. However, hardware rendering is still used to get the data to the screen, contrarily to vid_forceddraw.
  • vid_hwaalines (boolean) (Win32 Only)
Default: true
Controls whether Direct3D can use antialiased lines. Drivers tend to misreport that they cannot handle antialiasing even when they can, forcing ZDoom to take the issue out of their hands. If the automap displays thick and blurry lines, set this value to false.
Default: 200
If non-zero, this variable limits the frame rate to some arbitrary rate between 35 and 1000 FPS. Note that vid_maxfps 35 is not the same as cl_capfps 1: cl_capfps caps the frame rate by tying the video update directly to the game timer. With vid_maxfps 35, the video update and game timer are running on separate timers, and results will not be as good as with cl_capfps 1, which uses only one timer. You can use this in conjunction with vid_vsync to control whether or not the maximum frame rate is restricted to your monitor's refresh rate.
  • vid_noblitter (boolean) (Win32 Only)
Default: true
Setting this to false will allow the use of the hardware to assist moving image data to video memory. When Randy initially wrote the code to use the blitter, it was faster than not using it. Now the blitter is slower, so the default is true. (Verification needed)
Default: false
Setting this to true will disable PALVERS-based graphics substitution in the 8-bit software renderer.
Default: false
Use this cvar to disable widescreen aspect ratio correction. When it is set to true, the only display ratio available is 4:3 (and 5:4 if vid_tft is set).
  • vid_palettehack (boolean) (Win32 Only)
Default: false
When this cvar is true, the game will refresh the palette every time the screen is redrawn. This can be useful with some buggy video drivers. If the display is fine without it, leave it that way because this can slightly slow things down.
  • vid_refreshrate (integer) (Win32 Only)
Default: 0
If non-zero, specifies a custom refresh rate which overrides Windows' automatic refresh rate selection. This is useful if your video card is trying to run your monitor at a refresh rate it doesn't actually support for the given resolution. Normally this will not be needed, however. This is only meaningful in fullscreen mode.
Default: 0
Set this to a value between 1 and 9 inclusive to display in the upper left corner of the screen the current palette with a preset translation. This is a debugging tool used to detect interference with the system palette from other programs. 1 is the untranslated palette, 2 is translation 0, 3 is translation 1, etc. up to 8 for translation 6. 9 corresponds to the ice translation.
If a translation is not defined (for example, values 6 to 8 in Doom and Heretic), the palette is left untranslated.
Default: false
When this CVAR is true, the 5:4 aspect ratio is available.
Default: false
Set this to false to disable syncing the frame rate to the vertical refresh rate. Not all video cards support disabling vsync, in which case this CVAR will be ignored.
Default: -1
The horizontal (x) and vertical (y) location of the window when in windowed mode. If either value is such that the window would be placed off the screen, it will be forced into a position that keeps as much of the window onscreen as possible. (It will not choose a position less than 0.) This CVAR is only evaluated on startup, and changing it after the window is created will have no effect until ZDoom is restarted.

See also