that what i mean, All experience from other members become README..... ( sory 4 my BAD ENGLISH )

And you mean that i'm pretending to be the owner of this readme? Not gonna happen since without the mod there will be no readme , i'll just drop the info at the first post and link it to original posts so people could find the info rightaway if they happen to visit this thread.
I could leave it as is, but i already know that some people had difficulties navigating through the primary thread by darthcyclonis. I suppose it's trivial to include the most important info at the first post in such threads, that's why i made that FAQ too. If someone knows a better way to do it, let me know...

Hi everybody reporting my experience with the 257.. Drivers.
1. THe clock memory of my main card went up to the following values GPU Clock 400 mhz and the Memory Clock to 1275 mhz like if I'm running dual monitor setup.

2. When I run Fluid Mark 1.2 the app starts and everything seems to be working but suddenly the particles in the floor flash and disappear and the benchmark keeps running,( Please tell me if this is normal?)

3. I run Batman Arkham Asylum with everything in High and PhysX On and everything runs smoothly all the papers fly around and so on.

4. Please Correct me in the following Does Physix is Running on my machine? Why Fluid Mark Doesn't Work? Why the clocks of my card are running as if I have Dual monitor Setup? and Please tell me how to setup the other fake monitor setup if I need to do this?

Hi everybody reporting my experience with the 257.. Drivers.
1. THe clock memory of my main card went up to the following values GPU Clock 400 mhz and the Memory Clock to 1275 mhz like if I'm running dual monitor setup.

2. When I run Fluid Mark 1.2 the app starts and everything seems to be working but suddenly the particles in the floor flash and disappear and the benchmark keeps running,( Please tell me if this is normal?)
...
Why Fluid Mark Doesn't Work? Why the clocks of my card are running as if I have Dual monitor Setup?

1. This is auto-overclocking + auto-downclocking mechanisms enabled in the bios of your GPU i suppose. It should go up when you launch any PhysX app, and go down when you close it. Not sure if it works fine for you, but for me (9800GT Eco from Zotac) it worked well when i tested it on older drivers (196-197 series). If you mean that clocks went up permanently for you, perhaps it has something to do with its bios. This may be unfixable without using 3rd party apps in OS runtime...

2. In FluidMark 1.2 you should set 3 emitters and 60000 particles (default settings). It goes crazy with more particles in GPU mode, you can find more info about this here: http://www.geeks3d.com/20100524/phys...you-must-know/
Or just do a full 60 seconds run in FluidMark 1.1...

Quote:

Originally Posted by KillerCheese

Okay, so how do I use the 257 drivers?

I just installed 257 after uninstalling my old Nvidia drivers and PhysX, but I can't get PhysX to work. It doesn't show up in the control panel.

And it won't show up there. It's already enabled, you just have to set up a fake display, and (maybe) extend it.

And it won't show up there. It's already enabled, you just have to set up a fake display, and (maybe) extend it.

I actually have a REAL display hooked up to both video cards.

Quote:

Update: NVIDIA tells us that they will also be "fixing" the 257.15 beta driver on their site, so new downloads of that driver will have the restriction in place

Yes, this is a bug in the latest build of PhysX that was packaged with the driver. We'll be fixing this issue ASAP - the WHQL driver launching in early June won't have this issue. -NVIDIA
For those of you heterogeneous GPU users out there looking to use PhysX, there is some good news that can be salvaged from this however: this won't change the fact that previously downloaded copies of beta drivers lack this restriction. With these drivers you can still have heterogeneous GPUs with PhysX without modifying NVIDIA’s drivers, but you’ll be stuck on these drivers for the time being.

I guess this changes nothing if you still can extend these displays. Or you still can create 1 more fake display and extend it to the real monitor attached to your ati GPU. You can also apply the mod to make non-extended displays "more friendly" to hybrid configs...

Quote:

Originally Posted by KillerCheese

I need the older drivers BEFORE the update

Quote:

Yes, this is a bug in the latest build of PhysX that was packaged with the driver.

Seems very fishy to me... PhysX_9.10.0222_SystemSoftware.msi inside is signed on feb 22, it's not changed since then.

However, i can assure everyone that XP x86/x64 and 7 x86/x64 packages that are currently hosted at nvidia site are dated may 24 *atm*. Read: there are no updates to 257.15 done yet!
And i don't think they will rebuild this 257.15 anyway in future.