yes it dropped to 22 minimum with frps i had the fraps fps going for lvl1, lvl2 was low i didnt bother with fraps since it lagged
XS users are not the same as other forums and i do have the fastest single gpu card and a good oc on the cpu
Printable View
Thanks.
In the 12's.... Gasp!
The CPU can fool some of the people but not all of the people. :)
What CPU at what speed do you run Zanzabar?
Nice sig too... "physX and securom (dieing) need to die just say no" :rolleyes:
I am a YES man to GPU PhysX. :up:
I agree with you Zanzabar, just say no to "PhysX"
Due to on the page where I originally typed it, we were still saying things like:
and
I believe at that time, we were proceeding on lack of info, and my statement didn't seem to hold much weight with the boys.
Now in light of some actual CPU PhysX FPS numbers surfacing, it's looking to be more correct.
With the apparent huge performance difference we are seeing, I am now thinking it is more than just an CPU optimization issue. I think it's more of a hardware limitation issue.
GPU's are just way better at PhysX. (Sorry if the 3 lines in my quote took up too much screen space.) ;)
I will try not to let it happin again. :cord:
Maybe its because zanzabar is using older physX drivers that don't lag on the CPU & the other users are using the latest physX drivers are not.
You did not stop to think why zanzabar's minimum FPS are twice as high as others.
You will never be a good problem solver on the PC without talking a methodical approach with choosing to not take both results into account.
This does not prove that the Physics in that game could not de done on CPU, but the Physics in that game using the very unoptimised physX CPU path is crap.
It would not surprise me that NV is slowing down the already rubbish physX CPU path as time goes on to widen the gap.
Yes, I did stop to think why zanzabar's minimum FPS are twice as high as others.
That is why I spacifically asked what CPU, at what speed.
You may be right, it could be just a driver thing, but I would have to see the numbers.
I may not be the best problem solver on the PC, but I did find how to remove the 60 FPS limitation in the game engine we were discussing. :)
That was a positive thing I thought.
ill post up the raw fraps from the 1st 2 fights (they are diffrent i tried to stay as similar i could but its random. i also have the frame record exchange files and can reproduce them all day (i can even do the demo in under 5mins now. and im on the latest drivers it performs worse than the older ones i was originaly on the ones from overlord2
no physX
Frames Time (ms) Min Max Avg
4863 65008 61 77 74.806
physX lvl1 cpu
Frames Time (ms) Min Max Avg
1808 77248 13 34 23.405
physX lvl2 cpu
Frames Time (ms) Min Max Avg
1613 115934 8 25 13.913
as u can see it is taxing but it is not lagging on the lvl1
i missed the request for specs, its an unlocked 720
http://i28.tinypic.com/10i5nis.png
I can't believe the can of worms I opened with my .ini tweak for this game.
For those who are interested, and have QuadCores AND Bioshock you can also get the game to use it's havoc based physics engine to use all 4 of your cores, by default it is set to use 2 cores (or 2 threads as it says in the ini), but you can change this to 4, I believe the maximum value is 8, although I have never been able to test 8 threads for physics.
The Bioshock.ini for Bioshock on Vista and 7 is located in the following location C:\Users\[Username]\AppData\Roaming\Bioshock\
Find the Havoc code and input the following to take advantage of your QuadCore
Also don't forget to set UseMultithreading=True otherwise the setting will not take effect.Code:[Havok]
HavokNumThreads=4
As for batman.... you can change the levels of texture filtering (anisotropy) however I am not convinced the FSAA this game uses is "proper" FSAA, just take a look at the prison bars in the first scene... are those jagglies?
John
the game says clearly "multi sample anti aliasing" so thats some MSAA not FSAA
Sorry man... Sheesh. 12 FPS was shocking to me. I bet most aren't running at my 1920x1200 either?
Thanks for the CPU info zanzabar.
I still need to find the file in Batman to let it use 4 cores on my CPU. I believe I need to find UseMultithreading=True, from what John posted.
Same difference, different day.
Multisample is a type of FSAA as is Super Sampling. You then have different flavours such as Rotating Grids, Ordered Grids these are different techniques used for FSAA. AFAIK Deferred rendering (which this game uses) only supports shader FSAA (win all) or MultiSample FSAA under D3D10 conditions I belive the technical term is a floating point sample "hack", but I am not sure and don't feel like looking it up. The Unreal Engine elected to use Multisample FSAA using this "hack", the requirement of which is a Direct3D 10 Environment (Vista/7 + D3D10 GPU) however the game itself uses DirectX9 shaders (SM3)
John
adding this to the userengine.ini makes it seam smoother, i wish that i had a real bench or time demo
[DevOptions.Shaders]
AutoReloadChangedShaders=True
bAllowMultiThreadedShaderCompile=True
NumUnusedShaderCompilingThreads=4
ThreadedShaderCompileThreshold=4
bDumpShaderPDBs=False
With UT3 physx maps were also slow until I copied over PhysXCore.dll file (don't remember which version but wrong version and it could crash the game) from ageia physx folder to UT3 folder. Wonder if things are the same with this game, using exactly same config file scenario as UT3 and same engine settings etc.
It was a matter of like 25-30 fps vs 90 FPS+ on a 8800GT.
I did not notice any difference Talonman with it set to true or false.
IMHO this game is not quite yet finished, perhaps the full release would not be quite so restrictive to non-nVidia owners and also might have a few more features built in?
John
The best thing Nvidia can do for PhysX is let the advanced effects run on the CPU. It would reduce the amount of whining and it would let people directly see the performance improvements they claim to achieve with GPU acceleration. A lot of non-Nvidia users hate PhysX simply because they are completely blocked from accessing those effects. It would be wiser to let them run it slowly and maybe hook a few more people like that instead of generating all this bitterness.
Only because I thought we were trying to sell that there is no reason why PhysX couldn't run on the CPU in this game, every inch as good as it could on a GPU.
I might have tried to drive my point home a bit too much. Sorry.
When you posted that "NV can fool some of the people but not all of the people", I thought you were inferring that I somehow missed the boat on the animal speed of the CPU and PhysX.
I will try an be more congenial in my responses.
Thanks buddy. :)
I will just keep it False then... Thanks
I agree with you.
People then would turn it off if the frame rates were horrid, but then as soon as they get the nVidia hardware would turn it back on to not only enjoy the eye candy, but also the improved frame rates.
That is a great suggestion, the fact that these features are being "blocked" does suggest some sort of snake oil trick on behalf of nVidia?
John