lol, well I could have said nothing at all. and I am saying you are correct about Metro 2033 on the latest drivers. the way you were talking it seems like it was in the past that you played so indeed what I said was true for back then.
I rarely ever play a game around it's release date, even if I preorder or buy it on day 1. In my experience, it's always better to wait a month or so. Valve games are probably the only exception to my rule. In the case of metro2033, it was at least 6 months after it was out, and Mafia II was 3+ months after it was out. And when there are benchmarks for games I always tune the settings before playing, which was why I was (still am) adamant that maxed out physx settings didn't cause a huge performance hit in metro and that Mafia II was still consistently smooth through the whole game. (As was already mentioned, Mafia II had performance problems when it was released).
If a game runs like ass, with or without physx, I have no problems admitting to that. BF3 didn't run smooth enough for me on my system with the beta settings maxed, despite several benchmarks around the web showing otherwise. And Batman AA had many situations where my old overclocked gtx260 216 would choke with physx on high.
Tell you what - for the sake of gaming and this discussion I will repay batman. I'll grudgingly force myself to play through that super awesome game again. And when I get to the first scarecrow fight, I'll quit, load up fraps, and record a solid 2-3 minutes of it. And then I'll post it. I anticipate it having great frame rates, but I honestly don't know for sure and I do want to point out I was never arguing about physx performance in Batman AA.
If it truly is so much better and can do amazing things which directcompute or havok can't, then it should continue to matter. If its not better, it will remain a gimmick which NV uses to push their brand.
As so few AAA titles upcoming have Physx support, perhaps it is the latter.
Interesting you put it that way. How many titles are using directcompute?