FurMark 1.14.0 Released

FurMark 1.14.0


FurMark 1.14.1 available HERE!!!

FurMark 1.14.0 DOWNLOAD

Webmasters: hotlinking is not allowed, please use the post url as download link.


Useful links:

A maintenance release of FurMark is ready to stress and overheat your GPUs (and your PSU!). This new version brings minor changes, check the changelog for all details

FurMark, main user interface

FurMark 1.14.0 changelog:

- added support of desktop GeForce GTX Titan Z, GT 730, GT 720.
- added support of notebook GeForce GT 700M series, GTX 700M series, 800M series
  and GTX 800M series.
- added support of Radeon R9 295X2.
- added new command line parameter to enable the dynamic camera scene (/dyn_camera)
- added new OpenGL hardware dependent limits to online score submissions. 
- GPUs are no longer sorted by bus ID (this sorting was done at the init of FurMark). 
- updated: GPU Shark 0.9.0 and GPU-Z 0.7.9.
- updated: ZoomGPU 1.9.0 (GPU monitoring library)

FurMark logo

4 thoughts on “FurMark 1.14.0 Released”

  1. Sven Bent

    /dyn_camera switch seems to not work here

    i tried enabling dynamic camera in the .xml file but as soon as i used nogui=0 it start up in benchmark mode with normal camera
    however if i let it start up with a gui the dynamic camera is set under options

    i tried deleting the xml to get a clean slate and starting furmark with “furmark.exe /dynamic_camera”

    the gui started but dynamic camera was not set under options

    i tried again with “FurMark.exe /dyn_camera /NOGUI” it started up and went straight into stresstestmode but with no dynamic camera.

    I cant figure out how to get this to start automatically (NO GUI) with dynamic camera.

  2. Sven Bent

    it seems to me to be related to the nogui command/xml tag

    even just running the basic burn-in test with the fully rotating torus is impossibel if you specify Nogui eiter in the xml or by command line

    nogui forces it to be either burn-in og extreme burn-in options set

  3. JeGX Post Author

    Thanks for the test. It’s fixed in FurMark that should be released very shortly.

Comments are closed.