1.7.0

• New: FurMark is now able to get detailed data from GPU-Z (if GPU-Z is running). In both Stability Test mode,
  GPU-Z is used to display additional information (GPU core clock, memory clock, GPU temperature and power consumption).
  In Benchmarking mode, GPU-Z is used to retrieve GPU core clock, memory clock, VDDC and VDDC current. Some data (like
  VDDC and VDDC current) is only available on some graphics cards (like the GeForce GTX 280).
• New: In Benchmarking mode, you can now send your score to your Twitter account (this gadget is experimental).
• New: the main GUI is now always available so you can fire up several tests without the need to start again the application.
• New: main GUI (graphical user interface) settings are now saved and are re-used. Thanks to W1zzard for the idea
• New: in Stability Test mode, each GPU has now its own temperature graph.
• New: in Stability Test mode, you can enable/disable the display of information the I key.
• New: in Stability Test mode, you can enable/disable the fur rendering with the SPACE key. Thanks to David Legrand for the idea.
• New: added new standard resolutions: 800×600 and 1920×1080.
• New: added new interface translations:
  - castilian (thanks to LordIntel)
  - bulgarian (thanks to fellix)
  - polish (thanks to rogalik)
  - slovak (thanks to ufo and Peter H.)
  - spanish (thanks to tech4pcs)
• Change: main startup GUI reorganization.
• Change: improved OpenGL rendering context creation.
• Change: log file renamed to FurMark_xxx.log
• Bugfix: GPU min temperature in temperature graph is now correctly updated.
• Bugfix: in multithreading management.

1.6.5

• Change: workaround for Catalyst 9.1 when Catalyst A.I is enabled: all textures used by FurMark are now in 4-channel RGBA format (in the previous versions, some textures were in 3-channel RGB format…).
• Change: the OpenGL version used by the renderer is now displayed in stability test mode (near renderer’s description)
• Change: by default the creation of an OpenGL 3.0 rendering context is disabled. If you want to enable it, just start FurMark in command line with the /gl3 parameter or use the batch file called Start-FurMark-OGL3.bat.
• Change: small modifications in OpenGL 3.0 context creation.
• Change: workaround for Catalyst 9.1 bug in glGetString(GL_VERSION) when an OpenGL 3.0 context is used.
• Removed: timer check in contest mode.

1.6.0

• New: added a GPU temperature monitoring graph in stability test mode.
• New: added a checkbox to enable post-processing effect in stability test mode. Post-processing effect shader is loaded from the file post-processing-fx.xml. So if you know GLSL programming, you can customize this effect shader. See on Geeks3D.com for a complete tutorial.
• New: added OpenGL 3.0 support. If OpenGL 3.0 is detected, the rendering is done via an OpenGL 3.0 context.
• New: added new interface translations.
• New: added start and end GPU temperatures logging in benchmark mode.
• Change: little interface reorganization to better handle translations with long text blocks.

1.5.0

• New: added GPU temperature log facility. If enabled, a log file (gpu-temperature.xml) is generated
  (in Stability Test mode only) to log degrees celcius and fahrenheit as well as elapsed time.
• New: benchmark results can be logged in a file (FurMark-Scores.txt). This feature is useful in command line when starting multiple tests. See Run-Multiple-Tests.bat for an example. New: added a postprocessing pass in Stability Test mode to make the test more intensive.
• New: in benchmarking mode, score is returned to Windows. Useful for command line scripts.
• New: startup dialog box is available in several languages. If you want to translate FurMark, feel free
  to send the translated xml file (see gui-english.xml in FurMark folder for an example). Of course, your credits will be added on FurMark’s homepage). Current translations: english, french, chinese (traditional and simplified) and german.
• New: added key F9 to make a screenshot (windowed or fullscreen but in Stability Mode only).
• New: added checkbox for Xtreme Burning Mode.
• Change: Xtreme Burning mode is more gpu-intensive…
• Bugfix: improved OpenGL rendering context to support new ForceWare 180.xx series.
• Bugfix: the QXSGA 2560×2048 resolution was not operational.