BFG10K
Lifer
- Aug 14, 2000
- 22,709
- 3,001
- 126
Yep, I do. What, now you?re dictating what I think too? If you are that?s your problem, not mine.Originally posted by: chizow
Haha ya right, and I'm sure you believe that too.
I won?t concede a point that isn?t true. But then I?ve done a thorough analysis of AA over the course of several months so I know what I?m talking about, unlike you.Considering you won't even concede resolution is more significant than FSAA you actually think anyone is going to believe that?
Yes, they?re equal without developer support.Yet, they are still not equal by any standard. You said they're equal, when they are clearly not. When comparing A to B you can't just dismiss both by using C as your example.
Right, and who do you think will support that? Intel won?t, ATi probably won?t, and Microsoft probably won?t, especially if they make their own physics standard as part of DirectX. That brings us right back to nVidia as the sole vendor that supports it.All that would be needed would be a PhysX to DX11/OpenCL wrapper.
But by your own admission nVidia can?t run the Clear Sky DX10.1 path.It does the same thing as AC and FC2, allows reading of the MS depth buffer for improved AA efficiency which is also supported by Nvidia parts with the necessary DX10 extensions.
Nope, just anything that doesn?t have widespread gaming support.No, that you consider anything not in a settings menu a marketing tool.
What a load of nonsense. Let?s start with the PhysX side of your (ludicrous) claims:Of course not because it not only offered very little difference in IQ (arguably worst), it actually resulted in artifacts/distortion and render errors in many games. Can you say the same of PhysX? Once again, a PhysX title will always be a better game with PhysX enabled vs. without.
http://techreport.com/articles.x/15261/3
In addition, I?ve seen at least one PhysX title generating rendering errors where limbs were getting stretched and contorted in a manner they shouldn?t be. It was ugly when it happened and it sure as hell didn?t make the title better; it made it worse.UT3's PhysX implementation isn't perfect, of course. We encountered a number of bugs, such as objects vibrating in place and occasionally sliding in strange patterns. Planks and stone slabs in the Lighthouse map unrealistically exploded into many pieces, kind of like giant graham crackers.
As for your Truform claim, again that?s woefully inaccurate. I?ve seen examples where it visibly improved in-game characters.
Again, far more games support Truform than nVidia PhysX yet it still failed. It failed because developers didn?t support and it and because more powerful hardware enabled higher polygon counts. This could also happen with PhysX as multi-core becomes more prolific (say 8 or 16 cores) and multi-threaded physics renderers start harnessing that unused power.
But they did support it ? OpenGL titles automatically supported it.Yet it was still marketing because no games supported it. That's your measuring stick is it not? So when you saw the first Hardware T&L demo and no games used it yet, you dismissed it as marketing or the next big thing?
As for your other question, if you can?t understand the difference between a virtually mandatory spec tied to the operating system like DirectX and a proprietry (and elective) spec like PhysX, there really isn?t any point in continuing this discussion with you until you gain such understanding.
Uh, no. Not even close. Havok runs under software and will run on any x86 processor. As for DirectX, any IHV that wants to be in the Windows gaming platform must implement it because it?s virtually mandatory to be in that market.PhysX is proprietary just as Havok is and even DirectX is proprietary in the sense that its not a completely open spec.
Neither apply to PhysX and to even attempt to make that claim is laughable.
Exactly the same applies to DX10.1 with Blizzard, Sega, EA and NHN (et al) getting on board. All this for something you claim offers no benefit.As for developer support, there's plenty of developer support and more added monthly. Epic, GameBryo, EA, 2K, THQ along with all the other devs listed on that nZone PhysX page. Considering the list is growing by the month, its clear PhysX is gaining traction, not losing ground.
Get nVidia to disclose what features they don?t support and then we can continue this discussion.Well once again, what DX10.1 features cannot be accomplished in DX10?
How so? When DX11 comes, it?ll support everything DX10.1 does. That?ll simply leave G8x/G9x/G2xx parts out in the cold and their market share will shrink out of existence as people upgrade.If you're going to claim PhysX is going to die due to lack of industry support, you most certainly need to acknowledge any title excluding 60-65% of the discrete GPU market would be doomed to failure before launch.
Yes it does ? it has everything to do with it. A feature means squat if no-one supports it.Support or adoption rate has nothing to do with a technology's significance, that's just you assigning value without objectively valuating the two.
I?m still waiting for that list of games. Until you produce it, stop wasting my time with hand-waving about how it?s the next great thing. Without game support it means squat.So PhysX isn't part of your buying equation, but that doesn't dismiss the significance of it especially when we have proof of tangible benefits in real games.