FluidMark 1.4.0 PhysX Benchmark Released

FluidMark 1.4.0 PhysX Benchmark, multicore CPU

For fanatics of PhysX-based fluids, FluidMark has been updated and this version brings many improvements.

FluidMark 1.4.0 DOWNLOAD

You can download PhysX FluidMark 1.4.0 here:
Webmasters: hotlinking is not allowed, please use the post url as download link.
Download FluidMark 1.4.0 Version 1.4.0 (2011.11.08)

FluidMark 1.4.0 release highlights

The PhysX engine is now based on the version, the latest iteration of the v2 branch of the SDK. The startup dialog box has been simplified and two benchmark presets have been added:

  • Preset:1080: with this preset, the settings are the following: 1920×1080 fullscreen, duration of 60 sec, 60000 particles, heavy additional graphics load and multithreaded PhysX synchronized on the rendering.
  • Preset:720: with this preset, the settings are the following: 1280×720 fullscreen, duration of 60 sec, 30000 particles, moderate additional graphics load and multithreaded PhysX synchronized on the rendering.

The additional 3D workload allows to smooth results and above all, makes scores more coherent especially when there is a dedicated PhysX GPU. This score is with a GTX 580 alone (actually there is a second GTX 260 but it’s not used for PhysX) and this one is with a GTX 580 (3D) + GTX 260 (PhysX). We clearly see the impact of an additional PhysX card.

Multicore CPU is better managed (with and without the multithreaded PhysX checkbox). When Multithreaded PhysX checkbox is disabled and Built-in CPU multicore is checked, FluidMark creates only one thread for rendering and PhysX and uses PhysX built-in multicore CPU support:

FluidMark 1.4.0, PhysX built-in multicore CPU support

FluidMark 1.4.0, main GUI

When Multithreaded PhysX checkbox is enabled, FluidMark creates one thread for each fluid emitter for PhysX CPU and does not use PhysX multicore support. The results are the same than with the ones with built-in multicore support.

Another new thing is the score submission procedure. Now there are three ways to submit a score:

  • 1/ just click on the Submit button: an anonymous score is send to oZone3D.Net server.
  • 2/ Fill up the nickname field and click on the Submit button: the score is send to oZone3D.Net server along with the nickname, in pseudo-anonymous mode.
  • 3/ Create an account on oZone3D.Net and use this account to submit the score: the score is send to oZone3D.Net server and at the same time is linked to your account. Rank tables will only display non-anonymous scores.

FluidMark 1.4.0 PhysX Benchmark, score box

FluidMark 1.4.0 main scores page is available HERE.

And for Radeon users? If you have a second GeForce card for PhysX, just install the PhysX Hybrid Mod 1.05ff. It works very fine (I used it during the dev of FluidMark 1.4.0: I have a Radeon HD 6870 as main renderer and a GeForce GT 240 for PhysX). Now if you have only one Radeon card in your PC, don’t panic, PhysX can also run in software mode and can exploit all CPU cores.

What is FluidMark?

FluidMark is a fluid simulation benchmark based on NVIDIA PhysX engine. The fluid simulation uses the SPH or Smoothed Particle Hydrodynamics method where interparticle forces are considered (SPH requires more CPU or GPU horsepower!). FluidMark support both CPU and GPU PhysX and in CPU mode, multi-core CPUs are supported (see HERE). FluidMark uses an OpenGL 2 renderer for drawing the 3D scene.


FluidMark 1.4.0 changelog

  • New: added two benchmark presets (1080 and 720).
  • New: PhysX built-in CPU multicore option added.
  • New: score submission with oZone3D.Net account.
  • Update: the additional graphics load option covers now the whole screen and not only the upper-right corner.
  • Update: revamp of the main startup dialog box (now a bit simpler to use).
  • Update: compiled with PhysX SDK
  • Bugfix: fixed a nasty deadlock that hung FluidMark sometimes at the end the tests.

The pixel shader used for the additional graphics load (More graphics load checkbox) is based on the Nautilus demo (ShaderToy).

22 thoughts on “FluidMark 1.4.0 PhysX Benchmark Released”

  1. JeGX Post Author

    The use of PhysX SDK 3.x is planned but I don’t know yet in what tool I will start to use it (FluidMark, a new PhysX plugin for GeeXLab, Kombustor?)…

  2. Zogrim

    Interesting, what do you mean by “built-in CPU multicore” support ?
    “NX_SF_ENABLE_MULTITHREAD” and “internalThreadCount” options?

  3. JeGX Post Author

    @Zogrim: yep that’s it. Actually FluidMark 1.3.x already used these options but in a slightly different way. With FluidMark 1.4.0 and PhysX, these options seem to work better than with previous versions of the SDK.

  4. nuninho1980

    IMPORTANT issue here:
    I got still error during 1280×720 changed resolution (fullscreen) running desktop 1024×768 (eg) in lastest version physx fluiodmark. :S
    but I got no error for higher resolution (fullscreen) than desktop 1024×768 in tessmark 0.3.0.

    You should fix soon this problem for physx fluidmark and also for lastest furmark.

  5. WacKEDmaN

    thanks JeGX…just in time to test my GTX470, after its manufactures repair (due to it not allowing the system to even power up!..still dont know exactly what was wrong with it..but mustnt have been too much coz they didnt replace the card..just repaired it)

    lets hope i dont kill it again running ur kick ass benchmarks! :p

  6. WacKEDmaN

    hmm..ive just hit the submit score (with nickname) and a box popped up saying “Score submission failed. Sorry…”
    but if i check the online scores, its actually listed in the latest submissions, but not in the “preset” scores section (i ran both the preset and got scores that would have put me in the top 10 cards under the preset scores)

  7. JeGX Post Author

    @WacKEDmaN: yes, since I changed my compiler, I noticed some difficulties to submit scores online, seems networking functions have a bit changed between vs2005 and vs2010.

    To be listed in presets scores, you have to create an account (it’s a really simple operation) and submit with this account.

    N2O allocates more memory for the GPU. Can be useful with large number of particles, like 600’000…

  8. Karambotow

    WTF? in FluidMark 1.4.0 have PhysX Benchmark SCORE: 278 points, 4 FPS (PhysX GPU) Duration: 60000 ms – FPS: Min: 4 Max: 6 (1920×1080)
    and 1.3.1 FluidMark I PhysX Benchmark Global SCORE: 352 points (60000 ms) – GPU PhysX PhysX: 176 (29 SPS) – GraphX​​: 176 (29 FPS) 7 emitters – Particles: 60000 (1920×1080) why?

  9. JeGX Post Author

    Benchmarking mode (presets) in FluidMark 1.4.0 uses totally different settings than in FluidMark 1.3.x. There’s no direct relation between v1.4.x and v1.3.x scores. That why I created new score pages.

  10. JeGX Post Author

    @nuninho1980: yes I saw your bug-report and I will look at is asap (according to other feedbacks, I have the same kind of bug in the latest GeeXLab).

  11. Leith Bade

    If I enable Aysnc rendering on my 5850 with 11.10 drivers Aero locks up and runs at a very slow frame rate.

  12. nuninho1980

    @Leith Bade
    do you not have geforce card (8xxx or newer)? because your radeon card doesn’t have physx support!!

  13. risoka01


    i only get 8fps with my gtx480 preset 1080…

    is there something wrong with 400series physx… ???

  14. nextgen

    I use 6870CF+GT240 to get PhysX hardware accelerate. When PhysX-mod-1.05ff applied, it works on FluidMark 1.0 and 1.2, but it doesn’t work on FuidMark 1.4! Is there some incompatible between FuidMark 1.4 and PhysX-mod-1.05ff? Thanks!

  15. JeGX Post Author

    @nextgen: PhysX mode 1.05ff works fine with FluidMark 1.4.0 (I developed FluidMark 1.4.0 with a Radeon HD 6870 + GeForce GT 240). Once the PhysX mod is installed, you have to replace PhysXDevice.dll in FluidMark folder by the patched one from the PhysX mod (check this article out).

  16. Nex

    Any good reason why this doesn’t support hybrid PhysX using the 257.15 beta driver (the one which does allow PhysX acceleration with ATI Gpu present)?

    note: 1.03 or 1.05ff did not work for me, older 1.1.0 version works perfectly fine with this.

    (small typo in last comment)

Comments are closed.