|
|
| Line 1: |
Line 1: |
| | ==Random Stuff for Testing== |
|
| |
|
| {{Notice|This guide is currently being revised and is a work in progress.}} | | <pre>{{Fieldset|Page|{{Fieldset|Step||Option1; Option2; Option3; Option4}}}}</pre> |
| ''-- by the S.T.E.P. Team and Wiki Editors''
| |
| :Updated: {{ #time: G:i:s j F Y "(UTC)" | {{REVISIONTIMESTAMP}} }}
| |
| [http://forum.step-project.com/showthread.php?tid=323 '''GUIDE FORUM THREAD''']
| |
|
| |
|
| = Introduction =
| | {{Fieldset|Page 1|{{Fieldset|Step 1||Option1; Option2; Option3; Option4}}{{Fieldset|Step 2||Option1; Option2}}}} |
| == NVIDIA Inspector ==
| |
| | |
| NVIDIA Inspector is a tool created by [http://blog.orbmu2k.de/ Orbmu2k]. This tool provides detailed hardware information much like GPU-Z from all the available hardware senors pertaining to the video card. This senor information can also be monitored via the included monitors which, in turn, can be logged to a CSV file for later viewing. Inspector also provides simple overclocking tools to control the GPU clock, memory clock, shader clock, voltage, and fan speed of the video card; however, not all of these options will be available to all users.
| |
| | |
| NVIDIA Inspector's real treasure is the Driver Profile Settings (game profiles). Inspector includes over two hundred individual game profiles. Using these profiles you can set up individual driver settings for individual games that will be loaded and used when the game is launched. These settings are also more extensive than the settings included in the NVIDIA Control Panel so you have more control and additional settings to fine tune your games.
| |
| | |
| This Guide will not be a step-by-step process of what to set your Inspector settings on. That would be impossible to do with the endless combinations of video cards and system hardware. This Guide will; however, break down each of the settings in Inspector so that you may be better informed about what settings may be best for your system.
| |
| | |
| = Installation & Setup =
| |
| == NVIDIA Inspector Installation ==
| |
| | |
| The wonderful thing about NVIDIA Inspector is that it's a standalone application. There is no installation required. Simply download the tool and run the .exe to launch the program. This means it can also be ran from USB flash drives and used on the go. You can download NVIDIA Inspector here: [http://www.techspot.com/downloads/5077-nvidia-inspector.html NVIDIA Inspector]
| |
| | |
| Thank you [http://www.techspot.com/ TechSpot] for your wonderful service!
| |
| | |
| | |
| == NVIDIA Inspector Overview ==
| |
| ==== Main Screen ====
| |
| {{Gallery | |
| |enable=Yes | |
| |galleryitems={{GalleryItems | |
| |url=http://wiki.step-project.com/images/1/1e/Inspector_main.png | |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| When you open the program this is the first screen you'll see. Here you'll find all your hardware information. You'll also notice two buttons on the upper left side. The first button uploads a screenshot of the app to Techpowerup.org. The second button below that will open your hardware monitors. Further down to the right of the Driver Version box is a button that will open the game profiles plugin for Inspector. Finally, at the bottom there is a banner to allow you do donate, a drop-down box to allow you to switch between multiple GPUs if you're running SLI, and a button that will open the Overclocking pane. Clicking this button will prompt a warning about overclocking, before the pane opens.
| |
| | |
| ==== Monitors ====
| |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/0/0d/Inspector_monitors.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| Clicking the Sensor Monitoring button will open the this screen. Monitors are discussed on the Sensor Monitoring tab.
| |
| | |
| ==== Driver Profile Settings ====
| |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/0/02/Inspector_profiles.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| Clicking the Driver Profile Settings (game profiles) button will open this screen. Game profiles are discussed on the Creating Skyrim Profile tab.
| |
| | |
| ==== Overclocking Pane ====
| |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/2/21/Inspector_overclock.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| Clicking on the Show Overclocking button and choosing "Yes" to the prompt will open this overclocking pane. Overclocking is discussed on the Overclocking tab.
| |
| | |
| = Sensor Monitoring =
| |
| == Sensor Monitoring ==
| |
| Sensor monitoring can be very helpful when testing hardware stability, performing overclocks, mod testing, or when testing new settings or changes to those settings. Inspector includes 14 different monitors for this purpose. These include:
| |
| | |
| *GPU Usage
| |
| *VPU Usage
| |
| *MCU Usage
| |
| *BUS Usage
| |
| *Memory Usage
| |
| *GPU Clock
| |
| *Memory Clock
| |
| *Shader Clock
| |
| *Voltage
| |
| *GPU Temperature
| |
| *PCB Temperature
| |
| *Fan Level
| |
| *Fan Tachometer
| |
| *Power Level
| |
| | |
| Of these, the most useful are going to be determined by what you are using the monitors for.
| |
| | |
| == Customizing the Monitors ==
| |
| | |
| To open the monitors, click on the Sensor Monitoring button located on the main screen on the upper left side. Once opened, the monitors are defaulted to stay on top of all other windows. The default monitors displayed are the GPU Usage, GPU Clock, Voltage, and the GPU Temperature. To change the monitors simply right-click on the monitor window and hover over "Monitors". The monitors which have a check beside them will be the monitors displayed. You may check as few as one or all of them, if you desire.
| |
| | |
| The other settings on the right-click menu are as followed:
| |
| | |
| ;GPUs
| |
| :This allows to you select which GPU you wish to monitor if you're using more than one such as in SLI.
| |
| | |
| ;Monitors
| |
| :Provides a list of all the monitors available.
| |
| | |
| ;Antialiased Graphs
| |
| :Makes the graphs a bit less jagged.
| |
| | |
| ;Always on Top
| |
| :Toggle whether the monitor windows stays on top of other windows or not.
| |
| | |
| ;Capture Disabled Monitors
| |
| :Toggles whether to capture all monitor data or just the monitors you're displaying via the Monitors menu.
| |
| | |
| ;Log Active Monitors to CSV
| |
| :Toggles whether or not to log the active monitors to a CSV file for later viewing.
| |
| | |
| ;Reset All Monitors
| |
| :Resets the monitors to start fresh.
| |
| | |
| ;Hide to Tray
| |
| :Minimizes the monitor window to the system tray.
| |
| | |
| ;Close
| |
| :Closes the monitor window.
| |
| | |
| = Overclocking =
| |
| == Inspector Overclocking ==
| |
| '''''First a disclaimer:''' Inspector and STEP can not be held liable for any possible mishaps resulting from overclocking your video card. Potential problems resulting from overclocking can include anything from voiding your warranty to overheating and bricking your card and everything in between. If you decide to overclock your video card, you do so at your own risk. This overclocking overview is meant for information purposes only. Now, on to the magic...''
| |
| | |
| Overclocking in Inspector is not much different than overclocking in other third party software. Keep in mind, depending on your video card model, not all overclocking controls will be at your disposal in Inspector. Inspector was not written with overclocking in mind; therefore, if you need more powerful and precise options you should look elsewhere. It is also a good idea to have monitors open when overclocking so that you may monitor the effect of your changes.
| |
| | |
| == Overclocking Pane ==
| |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/2/21/Inspector_overclock.png | |
| }}
| |
| |align=left | |
| }}
| |
| | |
| To open the overclocking pane, click the "Show Overclocking" button at the bottom of the main screen. You'll be prompted with a warning asking if you are aware of the risk with overclocking. Clicking "No" closes the windows. Clicking "Yes" will open the overclocking pane. Clicking the button again will hide the pane. Below is a break-down of the items on this pane:
| |
| | |
| ;Fan Control
| |
| :The first thing you'll probably notice is a large vertical slider. This controls the Fan Speed. By default it is set to "Auto". To manually set the fan speed, uncheck "Auto" and move the slider to the desired position. Then click on "Set Fan" to lock it in. In the screenshot, the fan setting is grayed out because the shot was taken on a laptop with no fan control. Any areas you see in the pane which are grayed out is because you either don't have control of these items through the drivers or because Inspector can not control these items on your video card model.
| |
| | |
| ;Performance Level
| |
| :This is a drop-down menu that allows you to select which performance level the NVIDIA drivers use. The performance level is normally changed dynamically by the drivers depending on the GPU load. The main levels are P0, P8, and P12; though yours may differ depending on model. P0 is for high loads such as video gaming, P8 is for loads similar to video acceleration, and P12 is an idle load; when the video card isn't really doing anything. If you have different values, remember that the lower values are higher performance requirements and the higher values are for lower performance requirements.
| |
| | |
| ;Unlock Min & Unlock Max
| |
| :The frequencies available to you by default are locked in via the NVIDIA drivers. Clicking "Unlock Min" or "Unlock Max" will removed these driver limitation so that you may overclock to higher frequencies or underclock to lower frequencies. Clicking these buttons again will relock the frequencies to the driver limitations.
| |
| | |
| ;GPU Clock
| |
| :The GPU clock normally stays grayed out and is provided for informational purposes. This clock can be changed but not individually with Inspector. It is changed by changing the Shader Clock and always remains half the frequency of the Shader Clock. For example, if your Shader Clock is set to 1600MHz then your GPU Clock will be set to 800MHz.
| |
| | |
| ;Memory Clock
| |
| :Measured in megahertz, this changes the frequency of the VRAM. The buttons below the sliders allows for fine tuning of the frequency for both clocks.
| |
| | |
| ;Shader Clock
| |
| :Also measured in megahertz, like the Memory Clock, this changes the frequency of the Shader Clock.
| |
| | |
| ;Voltage
| |
| :Here it is possible to change the voltage to which the video card receives.
| |
| | |
| ;Create Clocks Shortcut | |
| :This is where Inspector shines! Clicking this button will save a shortcut on your desktop to specific clock settings. These means it's possible to have different overclocks for different game profiles or other tasks. Double clicking on one of these shortcuts will adjust your clocks to the preset settings automatically so you don't have to open Inspector and do it manually every time. So if you want a 10% overclock while you're video encoding, a 25% overclock while gaming, and default settings the rest of the time, all you'd have to do is make three Clock Shortcuts and double-click the appropriate shortcut anytime you change between tasks. Easy and brilliant! One of these preset can also be loaded at system start-up by simply placing the shortcut in your Startup folder in your Windows Start Menu.
| |
| | |
| ;Apply Defauts | |
| :This reverts any changes to the clock back to their driver defaults.
| |
| | |
| ;Apply Clocks & Voltage | |
| :This applies the clock and voltage settings immediately.
| |
| | |
| = Creating a Skyrim Profile =
| |
| == Driver Profile Settings ==
| |
| | |
| Driver Profile Settings or game profiles can be opened from the main screen by click the Driver Profile Settings button located to the right of the Driver Version box. Game profiles are the main attraction with NVIDIA Inspector because when used, these profiles will allow custom driver settings for individual games. The profiles will then be saved and loaded once the game is launched. You may be asking what's the difference between the NVIDIA Control Panel profiles and NVIDIA Inspector profiles. The answer is, Inspector provides a more extensive set of settings and options than the NVIDIA Control Panel does. Many of the settings and additional options that are included in Inspector are hidden from the Control Panel for whatever reason but still exist within the driver. Inspector gives you full control over these hidden settings.
| |
| | |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/0/02/Inspector_profiles.png
| |
| }}
| |
| |align=left
| |
| }} | |
| | |
| == Creating a Skyrim Profile ==
| |
| | |
| Over 200 profiles are already included in Inspector and there is rarely a need to create a new profile. This is because the profiles exist within the drivers themselves. Whenever NVIDIA releases new driver version they often come with new or updated profiles. Skyrim's profile is one of these; however, if you ever need to create a new profile you can do so by clicking the "Create New Profile" button on the toolbar of the Driver Profile Settings window.
| |
| | |
| To load Skyrim's profile, open the Driver Profile Settings window. In the text box on the toolbar, type "Elder". You'll see three profile for Elder Scrolls. Click on the profile for "Elder Scrolls V: Skyrim". This loads the pre-configured profile for Skyrim. If you already set some setting in the NVIDIA Control Panel, you'll see those settings here. If not, the settings will be the default ones. Below we'll go through each section in detail.
| |
| | |
| {{Gallery | |
| |enable=Yes | |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/e/e9/Inspector_findSkyrim.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| == Compatibility ==
| |
| | |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/8/84/Inspector_profile_compatibility.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| These settings should general not be changed as they are set to work with Skyrim.
| |
| | |
| ;Ambient Occlusion compatibility
| |
| :Should be set to: 0x00000029 (Elder Scrolls V: Skyrim)
| |
| | |
| ;Antialiasing compatibility (DX1)
| |
| :No setting
| |
| | |
| ;Antialiasing compatibility
| |
| :No setting
| |
| | |
| ;SLI compatibility bits (DX1)
| |
| :No setting
| |
| | |
| ;SLI compatibility bits
| |
| :Should be set to: 0x42C80005 (Elder Scrolls V: Skyrim)
| |
| | |
| == Antialiasing ==
| |
| | |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/d/df/Inspector_profile_antialiasing.png
| |
| }}
| |
| |align=left
| |
| }}
| |
| | |
| ;Antialiasing - Behavior Flags
| |
| : This tells the driver how to use antialiasing. Keep the default setting which is for Skyrim: 0x00000005 (... Elder Scrolls V: Skyrim, ...)
| |
| | |
| ;Antialiasing - Gamma correction
| |
| :This should remain off for Skyrim. Gamma correction can improve color; however, this will have little to no effect in Skryim.
| |
| | |
| ;Antialiasing - Line gamma
| |
| :This should remain as "default" for Skyrim.
| |
| | |
| ;Antialiasing - Mode
| |
| :Mode should be set to "Application-controlled" or "Enhance the application setting". Overriding the application setting has proven to not work.
| |
| | |
| ;Antialiasing - Setting
| |
| :In general, Setting should also be set to "Application-controlled / Off" as this will use the game engine's compatible AA method; Skyrim uses MSAA by default. However, feel free to experiment. When set to Application-controlled, this setting will take the value that is set in the Skyrim Launcher or in the INIs.
| |
| | |
| ;Antialiasing - Transparency Multisampling
| |
| :Use the default; "disabled". Enabling this has been known to cause textures which are not suppose to be transparent to display as transparent including walls, door, and characters. If you want transparency AA, use supersampling as it's higher quality at about the same performance cost.
| |
| | |
| ;Antialiasing - Transparency Supersampling
| |
| :Transparency antialiasing provides AA for transparent textures and will be most noticeable on foliage, trees, and water. 2x is recommended as the minimum; however, adjust according to the performance/quality you desire. Higher values come at more of a performance cost. Sparse Grid Supersampling is better but comes with a bit of a blurring effect so use plain Supersampling if the blur bothers you.
| |
| | |
| ;NVIDIA Predefined FXAA Usage
| |
| :FXAA should be set to disallow for STEP. FXAA is a fast AA method. Although it works, it also softens the textures and hazes the scene so you loose texture quality.
| |
| | |
| ;Toggle FXAA Indicator on or off
| |
| :Leave as default; off.
| |
| | |
| ;Toggle FXAA on or off
| |
| :Leave as default; off. If you want to use FXAA it's recommended you use a FXAA injector. RCRN includes a very nice FXAA injector which is extremely light on performance.
| |
| | |
| ''Note: The ENBSeries v0.139 and above now offers edge antialiasing which is similer to MSAA.''
| |
| | |
| === Performance Data ===
| |
| '''Multisample Antialiasing'''<br/>
| |
| From 0xMSAA to 2xMSAA: ~07% loss<br/>
| |
| From 0xMSAA to 4xMSAA: ~15% loss<br/>
| |
| From 0xMSAA to 8xMSAA: ~30% loss
| |
| | |
| '''Sparse Grid Supersampling'''<br/>
| |
| From 0xSGSS to 2xSGSS: ~01% loss<br/>
| |
| From 0xSGSS to 4xSGSS: ~02% loss<br/>
| |
| From 0xSGSS to 8xSGSS: ~06% loss
| |
| | |
| == Texture Filtering ==
| |
| | |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/1/1a/Inspector_profile_textures.png | |
| }}
| |
| |align=left | |
| }}
| |
| | |
| ;Anisotropic filtering mode
| |
| :Anisotropic filtering is a texture filtering technique that improves clarity of textures when those textures are viewed at an angle such as when walking down a path or viewing water from the shore. It is recommended to force AF through the drivers. When doing this, turn off anisotropic filtering on the launcher. The recommended setting to force anisotropic filtering is "User-defined / Off".
| |
| | |
| ;Anisotropic filtering setting
| |
| :When forcing anisotropic filtering the recommended minimum setting is 8x. Although 16x is best. The performance loss with anisotropic filtering 16x is ~4%.
| |
| | |
| ;Texture filtering - Anisotropic filtering optimization
| |
| :Filtering optimization should remain off for best texture quality.
| |
| | |
| ;Texture filtering - Anisotropic sampling optimization
| |
| :Sampling optimization should remain off for best quality.
| |
| | |
| ;Texture filtering - LOD bias
| |
| :LOD bias reduces the quality of textures as the distance grows from the viewpoint to those textures. Setting this to lower value will increase distant texture detail but will also come at a performance cost. Changing this value could also cause glitches so it is best to leave it set to default. "0.00 / Automatic"
| |
| | |
| ;Texture filtering - Negative LOD bias
| |
| :If using anisotropic filtering, it is best to set this value to "Clamp".
| |
| | |
| ;Texture filtering - Quality
| |
| :Recommended minimum setting here is Quality. High Quality is best.
| |
| | |
| ;Texture filtering - Trilinear optimization | |
| :Trilinear optimization should be set to "Off" for best texture quality.
| |
| | |
| === Performance Data ===
| |
| | |
| '''Anisotropic Filtering'''<br/>
| |
| From 0xAF to 2xAF: ~01%<br/>
| |
| From 0xAF to 4xAF: ~03%<br/>
| |
| From 0xAF to 8xAF: ~04%<br/>
| |
| From 0xAF to 16xAF: ~04.5%
| |
| | |
| '''Texture Filtering - Quality'''<br/>
| |
| High Performance to High Quality: ~01%
| |
| | |
| == Common ==
| |
| | |
| {{Gallery
| |
| |enable=Yes
| |
| |galleryitems={{GalleryItems
| |
| |url=http://wiki.step-project.com/images/2/23/Inspector_profile_common.png
| |
| }} | |
| |align=left
| |
| }} | |
| | |
| ;Ambient Occlusion setting
| |
| :Ambient occlusion is a lighting technique that determines when certain pixels are blocked from the environmental light by nearby geometry, in which case, its brightness value is reduced. This provide you with richer, more realistic shadows in-game. However, AO is very performance heavy. The recommended minimum setting is "Performance". If this to be too heavy on performance, try turning it off and opting for SSAO provided by ENBs. If both are too heavy, the only solution left is to turn it off completely.
| |
| | |
| ;Ambient Occlusion usage
| |
| :If Ambient Occlusion setting is set to anything other than "Off", then this setting should be set to "0x00000001 (... Elder Scrolls V: Skyrim, ...)". If Ambient Occlusion setting is set to "Off" and you plan to use SSAO via an ENB, then this setting should be set to "Enabled". If you don't plan to use Ambient Occlusion at all due to the performance loss, this setting should be set to "Disabled".
| |
| | |
| ;Extension limit
| |
| :Leave as default; "Off". This only has to do with OpenGL games and can cause crashes.
| |
| | |
| ;Frame Rate Limiter
| |
| :This is the driver side frame rate limiter. Unless you wish to cap your frame rate, leave as default; "Off". This can be useful to smooth out game-play to is choppy do to frequent bursts of high frame rates. ENBs also include a Frame Rate Limiter.
| |
| | |
| ;Maximum pre-rendered frames
| |
| :Maximum pre-rendered frames sets the number of frame that the CPU can pre-render before the GPU takes over. Some claim this causes an input delay (in milliseconds) from the mouse and keyboard when set to higher values; however, testing has not confirmed this as the tested showed no change in input response time. In fact, raising this value will actually improve performance. The recommended setting is "8".
| |
| | |
| ;Multi-display/mixed-GPU acceleration
| |
| :This is not relevant to SLI systems. If you only have one monitor, use the "Single display performance mode". If you have multiple monitors, use the "Multi display performance mode". If you have multiple monitor; however, experience some issues with the previous setting use the "Compatibility performance mode".
| |
| | |
| ;Power management mode
| |
| :This should be left on it's default; "Adaptive", which ensures the graphics card changes its speed according to the load it is under. "Per maximum performance" should only be used for troubleshooting purposes.
| |
| | |
| ;Show PhysX Visual Indicator
| |
| :Leave as default; "Off".
| |
| | |
| ;Thread optimization
| |
| :Leave as default: "Auto". This will allow the drivers to choose whether or not to use the multiple cores/hyper-threading of the CPU.
| |
| | |
| ;Triple buffering
| |
| :Set this to "on". Triple buffering improves performance when v-sync is enabled. It does nothing when v-sync isn't.
| |
| | |
| ;Vertical Sync Tear Control
| |
| :Leave on default; "Standard".
| |
| | |
| ;Vertical Sync
| |
| :V-sync is entirely the user's choice. Enabling can create smoother game-play, but can also create mouse lag. Disabling v-sync is generally recommended and can improve performance. The recommended setting here is "Use the 3D application setting".
| |
| | |
| === Performance Data ===
| |
| | |
| '''Ambient Occlusion'''<br/>
| |
| No AO to Performance: ~28%<br/>
| |
| No AO to Quality: ~49%<br/>
| |
| No AO to High Quality: ~55%
| |
| | |
| Maximum Pre-rendered Frames<br/>
| |
| 1 Frame to 8 Frames: ~03% (gain)<br/>
| |
| 1 Frame to 8 Frames with AFx16: ~09% (gain)
| |
| | |
| == Overall Performance Data ==
| |
| | |
| '''Before all edits:'''<br/>
| |
| '''FPS:''' Avg: 58.665 - Min: 51 - Max: 61
| |
| | |
| '''After all edits with no Ambient Occlusion:'''<br/>
| |
| '''FPS:''' Avg: 49.050 - Min: 38 - Max: 61<br/>
| |
| Before to After: ~16%
| |
| | |
| '''After all edits with all recommended settings:'''<br/>
| |
| '''FPS:''' Avg: 33.623 - Min: 28 - Max: 40<br/>
| |
| Before to After: ~42%
| |
| | |
| = Troubleshooting =
| |
| | |
| == General ==
| |
| | |
| There's not much for troubleshooting currently. Troubleshooting will be added upon over time.
| |
| | |
| ==== Transparent Textures ====
| |
| If you start seeing transparent textures in-game, this could be caused by Sparse Grid Supersampling or Transparency Multisampling. To fix this issue set Antialiasing - Transparency Multisampling to "Disabled". You can also switch Antialiasing - Transparency Supersampling to "Supersampling" instead of "Sparse Grid Supersampling".
| |
| | |
| ==== SSAO Not Rendering ====
| |
| Some NVIDIA cards (like the GTX 560 Ti) ceased rendering SSAO outdoors in Skyrim after the official 1.5.24 patch. The problem hasn’t been resolved but NVIDIA is aware of it. For now, you can temporarily switch to Oblivion or Fallout 3 compatibility to get back the SSAO outdoors.
| |
| | |
| = Raw Performance Data=
| |
| == General ==
| |
| Below is the raw data from FRAPS for anyone interested. The system used during data collection:
| |
| | |
| *Windows 8 Professional 64-bit
| |
| *Intel Core i7 2GHz
| |
| *8GB system RAM
| |
| *NVIDIA GeForce GTX 460M 1GB VRAM
| |
| | |
| === Data ===
| |
| '''Mulisampling Antialiasing'''<br/>
| |
| 2xAA //Frames: 1008 - Time: 17813ms - Avg: 56.588 - Min: 51 - Max: 60<br/>
| |
| 4xAA //Frames: 964 - Time: 18609ms - Avg: 51.803 - Min: 46 - Max: 59<br/>
| |
| 8xAA //Frames: 712 - Time: 16703ms - Avg: 42.627 - Min: 38 - Max: 50
| |
| | |
| | |
| '''Sparse Grid Supersampling'''<br/>
| |
| 2xSGSS //Frames: 1494 - Time: 25203ms - Avg: 59.279 - Min: 54 - Max: 62<br/>
| |
| 4xSGSS //Frames: 1400 - Time: 23828ms - Avg: 58.754 - Min: 50 - Max: 61<br/>
| |
| 8xSGSS //Frames: 1450 - Time: 25812ms - Avg: 56.175 - Min: 44 - Max: 62
| |
| | |
| | |
| '''Anisotropic Filtering'''<br/>
| |
| No AF //Frames: 2525 - Time: 42859ms - Avg: 58.914 - Min: 52 - Max: 62<br/>
| |
| 2xAF //Frames: 2462 - Time: 42312ms - Avg: 58.187 - Min: 50 - Max: 62<br/>
| |
| 4xAF //Frames: 2482 - Time: 43609ms - Avg: 56.915 - Min: 46 - Max: 61<br/>
| |
| 8xAF //Frames: 2397 - Time: 42219ms - Avg: 56.775 - Min: 47 - Max: 62<br/>
| |
| 16xAF //Frames: 2374 - Time: 42016ms - Avg: 56.502 - Min: 47 - Max: 62
| |
| | |
| | |
| '''Texture Filtering - Quality'''<br/>
| |
| High Performance //Frames: 2367 - Time: 41375ms - Avg: 57.208 - Min: 48 - Max: 62<br/>
| |
| Performance //Frames: 2370 - Time: 41454ms - Avg: 57.172 - Min: 48 - Max: 62<br/>
| |
| Quality //Frames: 2370 - Time: 41812ms - Avg: 56.682 - Min: 47 - Max: 62<br/>
| |
| High Quality //Frames: 2395 - Time: 42266ms - Avg: 56.665 - Min: 47 - Max: 62
| |
| | |
| | |
| '''Ambient Occlusion'''<br/>
| |
| Off //Frames: 753 - Time: 12657ms - Avg: 59.493 - Min: 57 - Max: 62<br/>
| |
| Performance //Frames: 1750 - Time: 41016ms - Avg: 42.666 - Min: 36 - Max: 48<br/>
| |
| Quality //Frames: 1289 - Time: 42203ms - Avg: 30.543 - Min: 27 - Max: 35<br/>
| |
| High Quality //Frames: 1154 - Time: 43016ms - Avg: 26.827 - Min: 24 - Max: 31
| |
| | |
| | |
| '''Max Pre-rendered Frames'''<br/>
| |
| 1 Frame //Frames: 2949 - Time: 51562ms - Avg: 57.193 - Min: 46 - Max: 62<br/>
| |
| 8 Frames //Frames: 2638 - Time: 44828ms - Avg: 58.847 - Min: 52 - Max: 69
| |
| | |
| With Anisotropic Filtering x16<br/>
| |
| 1 Frame //Frames: 2497 - Time: 48640ms - Avg: 51.336 - Min: 40 - Max: 60<br/>
| |
| 8 Frames //Frames: 2574 - Time: 45563ms - Avg: 56.493 - Min: 47 - Max: 69
| |
| | |
| | |
| '''Before Edits'''<br/>
| |
| Frames: 2485 - Time: 42359ms - Avg: 58.665 - Min: 51 - Max: 61<br/>
| |
| | |
| '''After Edits with no Ambient Occlusion'''<br/>
| |
| Frames: 2044 - Time: 41672ms - Avg: 49.050 - Min: 38 - Max: 61<br/>
| |
| | |
| '''After Edits with all recommended edits'''<br/>
| |
| Frames: 1461 - Time: 43453ms - Avg: 33.623 - Min: 28 - Max: 40<br/>
| |
| | |
| <headertabs/>
| |
