Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,790
- Location
- Cornwall
Ubisoft, making dice look competent.![]()
Let's not get carried away!
That's just crazy talk!
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.
Ubisoft, making dice look competent.![]()
Aren't they behind the Far cry trilogy? For that reason I can't knock em, It's one of my favourites after Stalker.
Ubisoft, making dice look competent.![]()
Let's not get carried away!
That's just crazy talk!
The Dice vs Ubisoft incompetency fight off.
![]()
I'd say its a pretty close call, Ubisoft handled the poor opening release day well. Lets see if they can continue to offer poor support over the coming months to match Dice.
Well this is all depressing. I hope AMD are able to figure it out.
The Dice vs Ubisoft incompetency fight off.
![]()
I'd say its a pretty close call, Ubisoft handled the poor opening release day well. Lets see if they can continue to offer poor support over the coming months to match Dice.
I wouldn't be running AMD/Nvidia, point though is, it's a disgrace this is allowed to happen in the first place.
The likelyhood is that the gameworks code detects and AMD card and runs a significantly less optimised piece of code for AMD cards to the point where a 290x is on par with a 770gtx instead of a 780ti, which it simply is faster than in any non sabotaging Nvidia game.
1+1=2 but 1+8+69-74-10+8=2 also... if Nvidia are paying a dev to run the second much longer calculation to get the same answer, there isn't a huge amount AMD can do about it.
Yes I'm only guessing that is what they are doing, but firstly the performance difference between AMD/Nvidia for gameworks games alone is ridiculous, and considering Nvidia didn't have this advantage in other Nvidia sponsored but not gameworks using titles suggests they've done something VERY sneaky and they've gone over the top in hiding the code and only get away with using it when they pay the dev's millions.
As someone else said, IF a game dev wants to get millions for stupid effects(there is precisely nothing "fancy" in the game doable without gameworks, it's all pretty bog standard), then add them in as extra for Nvidia users, stop sabotaging AMD users. It's so despicably underhanded, but that is Nvidia for you.
Going out of their way to overuse tessellation in Crysis 2, paying for it, and hurting Nvidia users frame rates with the inefficient usage of tessellation just because it would hurt AMD users more.
I can't name anything AMD has done to hamper Nvidia performance.
Well, it hasn't crashed yet, run at 12 fps yes, crash not yet
Poor release day perf is the staple of a solid ubi game, fc3 was broken for nearly a year before multi card users could touch it.
Off Guru3D:
http://www.guru3d.com/index.php?ct=articles&action=file&id=10533
Full HD (1920x1080)
WQHD (2560x1440)
Ultra HD (3820x2160)

Why does everyone see it as AMD being crippled? The simple fact is AMD are late to the party to optimise it (just like Nvidia would be with an AMD gaming evolved title).
Except the 770 doesn't have 40% less performance than the 290x in this game, the 290x is way down on the 780ti, that is the point.
Yes it wouldn't be this story if it was everything stupid slow, but that isn't the situation. The situation is once again that Nvidia's gameworks = AMD cards being suddenly 30-40% down compared to Nvidia cards. This on code they are pushing on the dev, which is completely locked out from AMD.
The sneakier part is, this isn't the first gameworks title, ultimately with the relatively same code in the various parts of gameworks, IE a physics engine doesn't change completely from one game to another. Why if AMD have optimised as far as they can for gameworks, has it changed this time around. why would Nvidia completely change up their own code, it was either optimised for their architecture before, or it wasn't. Minor changes, sure, big changes, no chance. When you're sabotaging, the code to make extra busy work is very simple, that would be VERY easy to change from game to game causing AMD a whole new set of problems with each new gameworks game.
While Nvidia insist on using absolutely closed code and pushing dev's to use it and locking AMD out from being able to work with the dev's to optimise Nvidia ARE sabotaging AMD.
AMD released tressfx, Tomb Raider used it, the code was absolutely not hidden from Nvidia, and Nvidia were not prevented by the dev's from optimising for it properly.
Jason Evangelho said:In my opinion there’s nothing inherently wrong with a company choosing to closely guard the keys which may unlock a competitive advantage. AMD is upset because they adopt the opposite approach