-
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
- Thread starter drunkenmaster
- Start date
Well that was what the article was about and explains in detail.
You didn't have to do any digging.
I was looking beyond the article for something beyond very loose circumstantial evidence that would explain it one way or another - we have nothing beyond "well its a (slight) advantage to nVidia so they have to be behind it" being used as the basis for blaming nVidia in the article and in this thread.
This is the point - the game wasn't designed for tessellation on the consoles, so assets were unlikely to have been built from the ground up with opptimised development for tessellation and likewise it wouldn't have been an engine focus - in which case its quite credible that when it comes to the PC version rather than rebuild/rework a whole load of stuff they've just haphazardly slapped tessellation ontop of geometry wholesale.
Neither was ATI sponsored Dirt 2 & 3 but they don't use silly amounts of tessellation.
But so far every NV sponsored game that uses tessellation use huge amounts of tessellation on objects that make practically no visual difference to.
If ATI sponsored Crysis 2, don't think for second that the tessellation would be like that.
Last edited:
Which proves my point that if AMD can control how much tessellation is being used in a sponsored game then NV damn well can to.
It's not Nvidia's fault AMD suck at tesselation
Both don't do a great job at tessellation imo, though yes, AMD do perform poorer than nVidia. However, seeing as it's not yet used in games enough to be a main selling point, I'm honestly not that bothered about it, even though I am an nVidia user.
You can clearly see that the point has gone way over his head.
That doesn't prove they had any control over it in this game tho - also as I said there is no proof they purposely reduced the level used or how widespread either.
So NV had no control over all the other NV sponsored games with tessellation either which also have silly amounts on silly objects.
Its all just coincidence.
Just way over your head.
Way too many under informed views expressing themselves as fact on here. I don't usually get involved in discussions like this as people really do have set views and you can't fight the internet but...... There is no need for that amount of tessellation on a model like that, there is literally no need at all. Take it from experience making things like this day in day out, you would be laughed out of any office with an atrocity like the example picture tommybhoy provided.
Only 1 of 2 options to look at here
1, Cryteks entire modelling staff were fired because they did not use what is now (and always was really) standard modelling techniques to account for tessellation (it existed well before it was used in games) and were replaced by chimps trained to press the tessellation at level 10.
2, Something fishy is going on
Only 1 of 2 options to look at here
1, Cryteks entire modelling staff were fired because they did not use what is now (and always was really) standard modelling techniques to account for tessellation (it existed well before it was used in games) and were replaced by chimps trained to press the tessellation at level 10.
2, Something fishy is going on
- Joined
- 18 Oct 2002
- Posts
- 33,188
Yes, and that would harm Nvidia performance........... how?
Under using something to not kill performance on ANY hardware, not bad. Purposefully overusing something to kill performance, on ALL hardware, just worse on AMD hardware is ridiculous, its pathetic, and its underhanded and worst of all they are 100% happy to hurt NVIDIA users just so they can hurt AMD aswell.
Rroff, it would be great if you could just once admit it.
SO tesselation wasn't designed from the ground up in Crysis 2, an Nvidia sponsored title, which Nvidia paid $2mil plus for, and as you yourself say, give LOADS of support, techs, equipment, time and coding help.
Yet the best Nvidia's guys could come up with was using excessive power to over tesselate objects that make no IQ improvement at all yet hurt performance, and despite the delay to add DX11, no one noticed in all this?
What a happy place it must be in your head, naive and unaware of anything bad going on in the world.
Sorry but, AMD, with a simple driver option can turn down the maximum level of tesselation. One of the main points and usages of tesselation is that it can EASILY be turned up and down by the dev, at any point, less use in the distance.
You're talking about basically MINUTES of work to turn down the tesselation levels, limit it, and limit the performance hit.
I'll make a flat out no questions about it accusation/statement.
Crysis 2 dev's could have released the patch with tesselation disabled, working much faster, with no drop in IQ, they have BEEN PAID to sabotage performance by adding in lots of absolutely woeful in quality tesselated objects that remain almost completely flat just to sabotage AMD performance worse than Nvidia performance.
Nvidia have paid a company, and their own people, to spend likely dozens/hundreds of hours creating needlessly complex models with no IQ improvement. This time could have been spent creating prettier models that kill performance AND increase IQ dramatically.
Theres no two ways about it, its that, or every single person at Crytek and Nvidia are completely flat out incompetant.
Did Nvidia pay Crytek $2mil to "help" them on this title, send guys over to help on tesselation and go "we could spend a while tesselating that tree, or that character model........... or that flat concrete slab and flat wooden planks"............ and then actually decide to tesselate FLAT objects legitimately, or did they purposefully do it to kill performance and hurt AMD?
Last edited: