|
|
| (5 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| {{langsp}} | | {{APH|How To Take Artistic Screenshots}} |
| == Introduction ==
| |
| This article covers the creation of artistic [[screenshot]]s which are higher in artistic quality than typical screenshots. The objective of this article is to approach screenshot creation more along the lines of photography.
| |
| | |
| == Graphics quality ==
| |
| Modern graphics hardware is often capable of much higher quality rendering than what it commonly runs at, as gaming usually involves a compromise between image fidelity and rendering cost. Various tricks such as [[Anti-aliasing]] can help hide jagged, step-like boundaries at the edges of polygons, but at the expense of lowering the framerate on less expensive hardware. However, taking screenshots is not about performance. Instead of rendering images perhaps thirty or forty times a second, our aim is to render a single image which is to be displayed for perhaps minutes at a time - so the aim is to jack your graphics card's settings up as far as they'll go.
| |
| | |
| === NVIDIA ===
| |
| {{warning|Any {{nvidia|4}} cards made after GeForce GTX 745/750/750 Ti, GTX 800M/900 series and any newer NVIDIA cards made after that (or after Maxwell architecture) with latest drivers will lose ability to use other anti-aliasing techniques (CSAA for example) other than in-game MSAA or post FX methods like FXAA, TAA, etc... (through injectors like ReShade, ENB, built-in NVIDIA Control Panel or in some third-party games/branch).<br><br> Furthermore, if you are using ReShade to take screenshot, you must disable MSAA and use it's own AA method (FXAA, SMAA, etc...) to make sure depth buffer access is working properly, which allows you to add effects such as [[SSAO|ambient occlusion]].<br> Alternatively, you can use NVIDIA DSR to run the game in 4K resolution, then downscaling it to 1080p, anti-aliasing in the process. This will provide the best result, at the cost of performance on lower-end and older GPUs.}}
| |
| | |
| {{nvidia|4}} graphics cards currently command around 84% of the market (as of Q1 2023), up against arch-rival {{AMD|3.1|nt=AMD}}'s {{AMD|3.1}} (formerly ''{{ATI|4.1|nt=2}}'' prior to acquisition) with 12%, and Intel with 4%. On an NVIDIA GeForce 6600, for example, there are graphics settings which are not directly accessible through Source's in-game configuration screens - there is an additional "8xS" anti-aliasing setting which is definitely worth pursuing for taking screenshots, due to the significantly improved image quality when rendering masked textures such as foliage, fences and gratings. In newer cards, such as Maxwell series and above (GTX 745/750Ti, 800M/900 series and newer, and/or later driver updates) lose ability to use other anti-aliasing techniques such as CSAA.
| |
| | |
| Examples of some of the anti-aliasing levels available are shown below:
| |
| | |
| {| border="0" cellpadding="4"
| |
| | [[File:screenshots_howto_noaa.jpg|thumb|200px|center|No anti-aliasing ]]
| |
| | [[File:screenshots_howto_4xaa.jpg|thumb|200px|center|4x MSAA anti-aliasing]]
| |
| | [[File:screenshots_howto_8xsaa.jpg|thumb|200px|center|8xS (CSAA?) anti-aliasing]]
| |
| |}
| |
| | |
| * For more comparison, [[Anti-aliasing#Source|see this page]].
| |
| | |
| First of all, start the game with the mod of your choice and set everything except anti-aliasing to as high as it will possibly go; ''Model detail'', ''Texture detail'' and ''Filtering mode'' will make the most visible differences. An example screenshot is shown below:
| |
| | |
| [[File:AdvancedVideoSettings-AntiAliasing.png|thumb|373px|none|Advanced Video Settings (on a NVIDIA GTX 750Ti)]]
| |
| | |
| Next, quit the game, right-click on the desktop and select NVIDIA Control Panel, then click on the ''Manage 3D Settings''. Choose Global Settings or Program Settings (then select '''Half-Life 2'''), if you haven't added it, click on Add and locate {{code|common\Half-Life 2\hl2.exe}}. Done. We now want to select the highest anti-aliasing mode available, so in the Settings (Global) or Specify the settings for this program (Program settings), click on ''Antialiasing - Mode'', select ''Enhance the application setting'' (or Override, if available) then click on Antialiasing - Settings, choose the maximum that the card would support it. In the original author's case, this is to "8xS" (1x2SS + 4x MS). In older NVIDIA cards, 32x CSAA is the maximum. In the this case (and pretty much anyone else with modern PCs) with latest drivers and newer graphic cards (such as GTX 750Ti, 800M/900 series and newer, including all RTX cards), "8x" MSAA is the maximum supported (without using unofficial tools like NVIDIA Profile Inspector to force SGSSAA or other AA methods). Another example screenshot is shown below:
| |
| | |
| [[File:NVIDIAControlPanel - Half-Life 2 Profile (AA highlighted).png|thumb|372px|none|NVIDIA display properties on GTX 750Ti, Windows 11.]]
| |
| | |
| Click on ''Apply'' buttons, close the NVIDIA Control Panel, and restart the game. In the author's case, bringing up the [[console]] and typing <code>"mat_antialias 8"</code> appears to be necessary to enable the "8xS" anti-aliasing. Once this is done, there should be precipitous drop in framerates, so type in <code>"sv_cheats 1"</code> and load your map - the game is now ready for screenshots!
| |
| | |
| === ATI/AMD ===
| |
| {{Update|If you have a modern AMD Radeon or some ATI GPU, try to update the information if needed, then remove the template once you done it.}}
| |
| [[WP:ATI Technologies|ATI]] and [[WP:Radeon|AMD Radeon]]'s Adaptive Anti-Aliasing performs a similar function to NVIDIA's "8XS", smoothing transparent edges of textures. It can be enabled through the Catalyst Control Center in the usual manner. All ATI cards above the X800 Pro range support AAA; however, X800 Pro cards have the feature locked by default. Following [http://www.elitebastards.com/page.php?pageid=12254&head=1&comments=1 this guide] will help you enable the option. Note that the level of Adaptive AA is taken from the level of regular AA.
| |
| | |
| With the Catalyst 6.2 drivers, "High-Quality AF" is also an option, again accessible from the Control Center. This will improve texture filtering, making textures at long distances and high angles appear sharper.
| |
| | |
| == Targa (TGA) & uncompressed screenshots ==
| |
| The standard screenshot function in Source compresses the output to lossy {{wiki|JPEG}} images, which, while great for quickly uploading to the web and to save bandwidth, JPEG can result in a loss of quality for any subsequent editing.
| |
| | |
| To save screenshots in an uncompressed {{wiki|Truevision TGA}} format which can easily be opened by most, decent image-editing software (such as {{ps|4}} or {{gimp|4}}), it is recommended that you type something like following into the console: {{code|"bind F4 screenshot"}}, which will save a TGA screenshot every time you press the {{Key|F4}} key.
| |
| | |
| == Removing the crosshair and HUD ==
| |
| Sometimes when taking screenshots, the aim is to give a visual, near-photographic impression of the map without the presence of any game interface elements. In single-player Half-Life 2 (and most other games and mods), the primary elements are the HUD (head-up display), the crosshair and the weapon model. Fortunately, there are console commands to remove all of these - <code>"cl_drawhud 0"</code>, <code>"crosshair 0"</code>, <code>"r_drawviewmodel 0"</code> and <code>"impulse 200"</code>.
| |
| | |
| == Environmental shots ==
| |
| For this, enable the <code>"god"</code>, <code>"notarget"</code>, and <code>"noclip"</code> commands at the console - the player character will then effectively become an invisible, free-floating camera. Try to find interesting angles which give a flavor of some of the more interesting sections of your map. Treat it as if you are using a real camera and you are visiting a real place, with the aim of taking aesthetically pleasing photographs rather than merely documenting what is there - with the advantage of effectively infinite film, no need to focus or choose exposure settings and the ability to float the camera absolutely anywhere in the world in order to get the best shot.
| |
| | |
| Countless millions of pages have been written on real-world photographic techniques, so it is impossible to condense it all into a paragraph here - perhaps the best approach is to experiment, and most importantly, to expect to throw many of your shots away in the pursuit of getting that one, "perfect" image.
| |
| | |
| == Action shots ==
| |
| For screenshots which illustrate gameplay and other dynamic aspects of a map, it can be advantageous to record a "demo" of normal gameplay (essentially a film of everything which happens) and then to take screenshots during its playback - it is much easier to capture fleeting details such as gun muzzle-flashes, explosions and other events this way.
| |
| | |
| More information is available on the [[Demo Recording Tools]] page, which documents Source's highly versatile demo playback facilities.
| |
| | |
| Another technique is to actually slow down game time by typing <code>"host_timescale x"</code> into the console, x being the desired time scale (i.e. 0.5 scales time speed by half). With this technique, it is possible to orchestrate brilliant battle scenes.
| |
| | |
| == Going beyond the monitor's resolution ==
| |
| [[File:DearEsther4096.jpg|thumb|400px|right|Screenshot of {{Dear Esther|1}}.<br>Note that the screenshot shown here are 2048x2048, due to wiki limitations preventing the thumbnail from generating properly. You can view the [https://developer.valvesoftware.com/w/images/archive/c/cb/20230517133525%21DearEsther4096.jpg original image] here. (click to enlarge)]]
| |
| | |
| Using this method, you can ignore your monitors resolution and instead hit the limits of your graphics card's maximum resolution, which is now limited to your HDMI/DisplayPort version supported by your GPU in most cases on modern GPUs.
| |
| | |
| Using the NVIDIA Control Panel to create custom resolutions, you can force these a new desktop resolution and then start the Source Engine in window mode with the resolution settings in the command line. If there is a similar method for ATI/AMD graphics cards is yet to be documented here.
| |
| | |
| Open up the NVIDIA Control Panel and navigate to Display -> Change Resolution -> Customize... -> Create Custom Resolution
| |
| | |
| Here, you can set your resolution of choice, but keep in mind that not every resolution will work. Also, lowering the refresh rate (or enable Display Stream Compression) will enable you to achieve even higher resolutions. With a recent graphics model (such as NVIDIA GeForce RTX 30 and 40 series or AMD equivalent), for example, 8K is possible at 30Hz (120Hz with Display Stream Compression (DSC)), as long you have HDMI 2.1 capable GPU, while 4K is possible up to 144Hz (240Hz with Display Stream Compression (DSC), HDMI 2.1).
| |
| | |
| Only few resolutions will be supported, so it will fail with the error message "Custom resolution xxxx x yyyy at 60Hz (32-bit) is not supported by your display."
| |
| Nevertheless, the custom resolution will remain until you click OK. At this point, you will most likely end up with black screen, unable to see your desktop. Using remote control tools such as TeamViewer or similar VNC tools, you can stream the video to another display or computer.
| |
| | |
| Once you can see your high resolution desktop again, boot up your Source game with the new resolution in the command line:
| |
| *For {{src13|4}} (or earlier): {{code|hl2.exe -width xxxx -height -yyyy -windowed}}
| |
| *For {{l4dbranch|4}} and above: {{code|game-name.exe -width xxxx -height -yyyy -windowed}}
| |
| | |
| After starting the game, it is often possible to revert to your old resolution with the game still running at a higher resolution.
| |
| | |
| == Post-processing ==
| |
| {{cleanup}}
| |
| Uploading an otherwise unmodified JPEG version of a screenshot will result in a dark, impenetrable mess. There are, however, some simple tasks you can perform in post-processing which will make the screenshot appear more as it did in-game.
| |
| | |
| If you wish to turn off the game's post processing you can do it with <code>mat_postprocess_enable 0</code>. Maps sometimes have unnecessary vignettes, or you may even wish to make your own take of the look of the map.
| |
| === Gamma ===
| |
| The images a typical computer game saves in a screenshot and what it actually displays on screen are usually subtly different, thanks to something called ''gamma''. A way of describing a display's brightness response for a given input value, a game's output gamma is generally different from a typical computer desktop's gamma. A game such as Half-Life 2 will typically brighten low- to midrange-values much more than a normal computer graphics application - in Source, this is controlled using the in-game ''Brightness'' dialog box.
| |
| | |
| To make your screenshots look as they did while you were playing the game, it is thus best to use an external graphics editing program such as Photoshop or, in the case of this article, examples from the free, open source [http://www.gimp.org/ GIMP] will be used. | |
| | |
| [[File:screenshots_howto_postprocess_original.jpg|thumb|540px|none|Original screenshot]]
| |
| | |
| As can be seen above, the original screenshot is far too dark. So, bring up the ''Levels'' dialog box (''Layer: Colors: Levels...'') and increase the applied gamma from 1.00 - around 1.30 seems to be a good number for typical screenshots:
| |
| | |
| [[File:screenshots_howto_postprocess_gamma_dialogue.jpg|Levels dialog in GIMP]]
| |
| | |
| For particularly dark images, it can be useful to apply "overbrightening" by decreasing the input level's maximum from the standard 255 to something lower - a gamma of 1.3 combined with a maximum input level of 200 can work wonders on screenshots portraying night-time or underground scenes.
| |
| | |
| Your image should now look something like the following:
| |
| | |
| [[File:screenshots_howto_postprocess_gamma.jpg|thumb|540px|none|Screenshot after gamma correction]]
| |
| | |
| === Sharpening ===
| |
| If you wish to reduce your screenshot's size, it can be useful to then apply a relatively small amount of sharpening. First, scale it down to the appropriate size (''File: Scale Image...'') then bring up the Sharpen dialog (''Filters: Enhance: Sharpen...''). A value of 10-30 is usually about right - if set too high, black and white fringes may start to appear around edges and other details.
| |
| | |
| [[File:screenshots_howto_postprocess_sharpen_dialogue.jpg|none|Sharpening dialog in GIMP]]
| |
| | |
| Finally, your screenshot should look something like this 400x300 File:
| |
| | |
| [[File:screenshots_howto_postprocess_final.jpg|none|Final screenshot]]
| |
| | |
| === Saving as JPEG ===
| |
| To save your masterpiece, go to ''File: Save as...'', select the destination and type in the final filename (to save as JPEG, simply end the filename with a ".JPG") and press OK. To see what the lossy JPEG compression will do to your image, click on ''Show Preview in image window'' - increase the quality if necessary to remove compression artifacts. Advanced options include 'progressive' (image blurs in when loading, and file is often slightly smaller too) and different {{wiki|subsampling}} methods (for more accurate colors at the expense of {{wiki|file size}}).
| |
| | |
| == Conclusions ==
| |
| When combined, the above techniques can be used to greatly improve the images with which you show off your latest work. While they won't cover the cracks in a poor-quality original, they can definitely help differentiate your efforts from the crowd. So have fun, and happy screenshotting!
| |
| | |
| Also, please note that if you are planning to upload screenshots in this wiki, due to MediaWiki limitations, only 4K (3840x2160) (or possibly smaller) images will be able to have thumbnail displaying properly.
| |
| | |
| == See also ==
| |
| * [[Anti-aliasing]]
| |
| * [[Screenshot]]
| |
| * [[Panorama Creation]]
| |
| * [[Image Hosting Sites]]
| |
Note:Archived rest of page history of page How To Take Artistic Screenshots
Important:These pages are linked often from page history logs so Special:WhatLinksHere will not show anything.