Comments on: PhysX FluidMark 1.2 ready for download

By: Zogrim

Zogrim — Mon, 24 May 2010 11:58:32 +0000

JeGX
Thanks) Don’t forget to send that to PhysX dev. engineers

By: JeGX

JeGX — Mon, 24 May 2010 11:31:25 +0000

I just wrote a short post about the problems we encounter in hardware PhysX mode. I hope to find a solution soon...

By: ContainForum

ContainForum — Sun, 23 May 2010 09:07:43 +0000

Hybrid PhysX or just regular?

I still havn’t got a replacement for my 5870 so I’m stuck with 8800GT.

By: Zogrim

Zogrim — Sat, 22 May 2010 20:30:50 +0000

Anybody else can confirm the dessapearing issue in Hardware mode?
Yep, same happens with me

By: GenL

GenL — Sat, 22 May 2010 19:54:20 +0000

applejack
And knowing the fact that most PhysX stuff is just an “eyecandy” which does not affect the gameplay, that would be far better than syncing every render frame with every physic frame, imo.

Anybody else can confirm the dessapearing issue in Hardware mode?

By: applejack

applejack — Sat, 22 May 2010 17:43:04 +0000

when I wrote “…skip physx frames in order to match the speed of rendering…” I was referring to “the speed of GAMEPLAY…”

By: applejack

applejack — Sat, 22 May 2010 17:36:25 +0000

GenL said:
“BTW, for me the most amazing thing in this version is Async mode. It shows that it is possible to make CPU-PhysX to not affect the gameplay framerate”

while Async mode does not affect rendering framerate, CPU processing does slow down the physx simulation/animation itself, thus changing the gameplay experience and physics authenticity.

I assume you could make it skip some “physx frames processing” in order to match the speed of rendering, but then again things can get worse as precision greatly decreases, hurting gameplay eventually.

By: ContainForum

ContainForum — Sat, 22 May 2010 16:54:24 +0000

Works with my Phenom II X6 1090T! Could have been a good contender with Cryengines physics. And could have been used in many games in multi core CPU mode.

Best thing about it is that it uses all 6 of my cores.
Too bad I don’t think developers would include multicore support for their PhysX implementations in games.

By: xDee xDee

xDee xDee — Sat, 22 May 2010 05:18:05 +0000

GenL

Yeah you’re right that the particles do disappear once you unlock the emitters and go above 7 or 8.

I’m having an issue that no matter if I use 1 emitter or 7 I get the same scores. Go figure that one out. This happens no matter what resolution I run it at also. Even weirder! And hardware PhysX is working.

It’s not just with FluidMark that this happens, it happens with FurMark also! It’s very annoying!

By: GenL

GenL — Fri, 21 May 2010 20:05:23 +0000

Great news and great job, JeGX!

However, i think there is a bug when you try to use many emitters in GPU mode. When i set it to 9, 10 or 11 – all particles dissapear after a few seconds. 8 or less is fine, 12 or more – no particles at all. Everything is working in CPU mode though.

I’m not sure if it is a real bug, but i can’t see any way it would be another trick from nvidia drivers. Because the particles won’t appear again until i restart the whole application, also i didn’t see anything like this anywhere – no reverse gravity, the particles just dissapear.
Can anyone confirm this? Perhaps it would be same even for nvidia users…

BTW, for me the most amazing thing in this version is Async mode. It shows that it is possible to make CPU-PhysX to not affect the gameplay framerate. I remember there is such a possibility in CryEngine2 – to skip physics frames whenever its framerate is lower than a render framerate.
But of course, we won’t see it in any PhysX game, just like a proper multi-core support, duh.