- Mar 21, 2004
- 13,576
- 6
- 76
I just realized something.. Mass Effect uses physX!
And I remember things improved when I got the 8800GTS 512 w/ the hacked drivers. (probably lowered max and average fps a little to increase min FPS a lot).
I remember also that the physX on GPU + 8x force AA from drivers caused a blue screen, and people said they had some issues on early physX on CUDA... (i didn't see any without force AA or with only 2x).
The workaround was to disable physX in the ini files.. I am going to look into disabling it and seeing what happens.
From what i hear it does improve quality. Supposedly blowing up a crate for example, has pieces of it flying off in physx, vs it just disappearing without. I will see.
EDIT: oh wait, I just remembered, it was "game automatically uses physX if it detects that it is available"
And I don't recall EVER seeing an item explode the way they describe it does with physX, so most likely I am getting this heavy cpu usage even with physX disabled. I will test it out to see if that is so.
And I remember things improved when I got the 8800GTS 512 w/ the hacked drivers. (probably lowered max and average fps a little to increase min FPS a lot).
I remember also that the physX on GPU + 8x force AA from drivers caused a blue screen, and people said they had some issues on early physX on CUDA... (i didn't see any without force AA or with only 2x).
The workaround was to disable physX in the ini files.. I am going to look into disabling it and seeing what happens.
From what i hear it does improve quality. Supposedly blowing up a crate for example, has pieces of it flying off in physx, vs it just disappearing without. I will see.
EDIT: oh wait, I just remembered, it was "game automatically uses physX if it detects that it is available"
And I don't recall EVER seeing an item explode the way they describe it does with physX, so most likely I am getting this heavy cpu usage even with physX disabled. I will test it out to see if that is so.