• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Nvidia unofficially, officially caught cheating in Crysis 2

Its not stunning quality and NO cards can play it at all, its an increase in gpu demands, with a reduction in performance, for NO IQ improvement in the slightest.

This is the problem, Crysis 1 on super mega ultra tweaked settings played like dog turd on current cards then, but looked better than anything before by a long margin and for a good couple years afterwards, things got closer but I don't think it was surpassed by anything.

Crysis 2 now needs, in max settings, stupid hardware for really good framerates, but it doesn't look any better.

If Nvidia added all that tesselation performance and the difference was visible across many many different textures and area's, and Nvidia lost less performance than AMD, thats one thing. When they add it to things that make no difference at all, and it kills performance for the singular reason of killing performance they are harming AMD users and critically, harming Nvidia users.

You buy a £350 580gtx, maybe 2 of them, then the company you gave the money to kills your performance JUST to harm people who bought AMD hardware. Honestly its beyond ridiculous, its pathetic and it should be widely known.

IF AMD do the same, hurt their own performance just to hurt Nvidia aswell, or hurt Nvidia only performance in any of the ways Nvidia did I'd be all over them, its bad business, its screwing your own customers, its screwing the industry.

How much time was wasted make flat objects take several times more gpu power to still be flat objects, when the same people could have been working on improving the damn game?

+1
 
How much time was wasted make flat objects take several times more gpu power to still be flat objects, when the same people could have been working on improving the damn game?

This is the main issue, if the extra GPU power gave us extra detail people wouldn't be complaining, but they are making GPU's work much harder to give the same flat objects.

What's sad is Nvidia's own development guide highlights the fact that sub pixel polygons hurt performance and that adaptive tessellation should be used and yet it's seemingly ignored in Crysis 2.

Read from 7.1.3.

http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter07.html
 
Last edited:
This is the main issue, if the extra GPU power gave us extra detail people wouldn't be complaining, but they are making GPU's work much harder to give the same flat objects.

What's sad is Nvidia's own development guide highlights the fact that sub pixel polygons hurt performance and that adaptive tessellation should be used and yet it's seemingly ignored in Crysis 2.

Read from 7.1.3.

http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter07.html

So is this a Crytek issue or are those evil fiends at Nvidia to blame for this?
 
I don't care who's at fault it's just stupid.

That amount of tesselation is not needed, it adds nothing and wastes power over NOTHING.

It's balls, utter balls.

And the fact the tesselated ocean appearse when you look at a puddle is just lol worthy.

Good job failtek.

Yup absolutely stupid... the problem with the puddle thing tho as I mentioned occlusion testing can be as hard on performance as just rendering the whole thing in the first place, and other methods like individual liquid sheets can potentially end up with scenarios which are even worse on performance in some cases than just rendering the whole one instance.

This is one of the scenarios where proper useage of tessellation or other ROAM type algorithms are at their most suited, drawing a high level of detail only around the viewer and reducing detail at a distance even when you need to draw the entire object.

Its so poorly and uninformed in implementation I struggle to believe Crytek had anything to do with it and even nVidia even assuming an agenda to make performance very bad on AMD (there are much more elegant tricks nVidia can and have used for this end that aren't likely to be caught out) - I'm starting to wonder if the high res DX11 patch was infact partially or entirely outsourced to an inexperienced studio - its the kinda level of work you'd expect from an intern/work experience person.
 
What's sad is Nvidia's own development guide highlights the fact that sub pixel polygons hurt performance and that adaptive tessellation should be used and yet it's seemingly ignored in Crysis 2.

Read from 7.1.3.

http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter07.html

Thats a good link and highlights how these issues can come about in the first place if someone indiscriminately applies tessellation over the top of a console port of the game.

Was going to go into detail on T-Junction issues but easy for people to get the wrong end of the stick (as what I'd be describing goes against the more basic comments on it in that article) as to why there are issues with getting the right level of detail over an entire object if someone doesn't really know what they are doing and why that results in higher levels of tessellation to ensure smaller details are tessellated correctly when adaptive methods aren't used due to the extra effort/knowledge required.
 
Last edited:
You asking a mis-leading question, as it's obviously not just one party involved is it...


2949d4620e0ac3f3100e883a9b8e124c.jpg


Or is it???:D
 
That's nice. If I was asking about high end cards of the past then perhaps we could talk about the old tech 5870.

Well your wording should have been more clear of that fact because the way it was put anyone not knowing prior would think it never was high end.

A 5870 is old high end (and always had poor tessellation performance), how does it perform on 69x0 cards?
 
Last edited:
So is this a Crytek issue or are those evil fiends at Nvidia to blame for this?

You asking a mis-leading question, as it's obviously not just one party involved is it...


How is that a miss leading question, it fairly straight forward, and the answer is this is a crytek issue and there is no proof at all that Nvidia had any hand in it at all.
 
How is that a miss leading question, it fairly straight forward, and the answer is this is a crytek issue and there is no proof at all that Nvidia had any hand in it at all.

Uh, he was trying to pigeon hole the culprit to only one party only.
As for the second part, Crytek surely isn't that incompetent, and even if they were, don't you think they would go to Nvidia for some 'developer support'?

Got a bridge to sell if your interested...
 
If you want a stupid conspiracy theory, how about....

AMD software shows up Nvidia in tessellation shocker.


just keeping to the theme of

NATIONAL SENSATIONALIST HEADLINE DAY.
 
Last edited:
Back
Top Bottom