Permabanned
- Joined
- 15 Sep 2010
- Posts
- 2,691
Were you able to keep a straight face while you were typing that up.
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.
Were you able to keep a straight face while you were typing that up.
Greg you would be proud...
I hate you. I hate the things you like!!!
Surprised nobody has quoted a few good men yet
LMAO, If I was in the lav and he jumped in, I would have jumped straight out and C4'ed the ******
The biggest problem with this thread and including myself, is we are all dug in so deep, no one is prepared to budge an inch.
Nvidia have GameWorks, AMD have Mantle, Nvidia have Tessellation, AMD have TressFX... This is bad, that is bad and no one is listening to the others argument. Rightly or wrongly, we believe what we know and dismiss things that don't suit. (We are all doing it).
Some very valid points from both parties but I feel we should call it a day and talk about how well Manchester Utd are doing
Ohhh and welcome back Suarez.
Is it just me, or do the smilies seem a bit naked without the santa hats now?
geeeez, why can't we all just get along, Mantle will be awesome for AMD owners, Nvidia owners shouldn't be getting upset just because Mantle will enable AMD cards to perform more closely to their superior cards, Nvidia has already got mantle performance in the way of raw power and don't need a wind up handle mantle.
ManuelG said:
We are aware of major performance and stability issues with GeForce GPUs running Tomb Raider with maximum settings. Unfortunately, NVIDIA didn’t receive final code until this past weekend which substantially decreased stability, image quality and performance over a build we were previously provided. We are working closely with Crystal Dynamics to address and resolve all game issues as quickly as possible.
In the meantime, we would like to apologize to GeForce users that are not able to have a great experience playing Tomb Raider, as they have come to expect with all of their favorite PC games.
I have quad SLI gtx 690 and only 1 GPU seems to be working with the game, the other 3 gpu's are not working at all!
ManuelG said:
Yes, we are aware of this issue as well with Tomb Raider.
Nixxes
Developer Representative
Eidos Official
Default PC Patch Released - 1.0.718.4 - March 9th 2013
We have just made public a new version of the PC version of Tomb Raider, build 1.0.718.4. This patch will be applied by Steam automatically when you next start the game. If your game does not update, please restart the Steam client.
This update addresses a variety of issues that we either found out about shortly before release or immediately after.
Fixes include:
- Addressed some stability and startup issues on machines that have both Intel and NVIDIA graphics hardware.
As posted by Boomstick in another thread, Nivida are going to talk about Gameworks and other stuff on the 5th.
http://semiaccurate.com/2014/01/02/maxwell-gives-us-glimpse-project-denver-debacle/
We have improved performance in batman:ao by 30% on all AMD cards. We locked AMD out from optimizations in gameworks, not for greed or for money but because we decided to help our close friends at AMD so that they could better allocate their time concentrating on other more important projects like mantle. Gameworks is the start of a growing friendship between nvidia and AMD. We love you AMD!! Gameworks!!
Disclosure: I'm the author of the story being discussed here. I'm jumping in to clarify the question of whether AMD "handed" me this story.
When I attended APU13, AMD told me there were discrepancies in Arkham Origins related to GameWorks, yes. I checked game reviews and noted that the published results for AO were extremely odd.
Once I returned home, I set up test beds using AMD and Nvidia hardware that was previously provided for standard reviews. I tested a Sandy Bridge-E and a Haswell box, and later built a Windows 8.1 system on an Ivy Bridge-E to confirm that I wasn't seeing issues that were tied to Windows 7.
After AMD told me about the problem, I reached out to Nvidia with some questions on GameWorks and attempted to contact WBM. I also tested GW performance in multiple additional titles. AMD did provide some assistance in setting up and using their own GPUPerfStudio monitoring program on Radeon cards, but did *not* provide the results I published. I gathered the raw data myself, on systems I built and configured myself. The content and focus of the article were chosen by myself. It was my idea to test AO directly against AC and I decided to look for problems in ACIV and Splinter Cell.
One question that's been hotly debated here is the impact of FXAA. It should be noted that with FXAA off (no AA whatsoever), the R9 290X runs at 152 FPS vs. 149 FPS for the GTX 770. In other words, it's not that FXAA is running slowly on AMD cards, but that AMD cards run slowly, period. The only way to change this is to turn on MSAA, which hammers the card hard enough for the R9 290X to brute force its way past the GTX 770.
I received absolutely no compensation or consideration of any kind, implied or overt, from AMD. I was paid a standard fee by ExtremeTech for my work. The hardware I used for this comparison was hardware I already had on hand. It is not my property, but the property of my employer.
Disclosure: I'm the author of the story being discussed here. I'm jumping in to clarify the question of whether AMD "handed" me this story.
When I attended APU13, AMD told me there were discrepancies in Arkham Origins related to GameWorks, yes. I checked game reviews and noted that the published results for AO were extremely odd.
Once I returned home, I set up test beds using AMD and Nvidia hardware that was previously provided for standard reviews. I tested a Sandy Bridge-E and a Haswell box, and later built a Windows 8.1 system on an Ivy Bridge-E to confirm that I wasn't seeing issues that were tied to Windows 7.
After AMD told me about the problem, I reached out to Nvidia with some questions on GameWorks and attempted to contact WBM. I also tested GW performance in multiple additional titles. AMD did provide some assistance in setting up and using their own GPUPerfStudio monitoring program on Radeon cards, but did *not* provide the results I published. I gathered the raw data myself, on systems I built and configured myself. The content and focus of the article were chosen by myself. It was my idea to test AO directly against AC and I decided to look for problems in ACIV and Splinter Cell.
One question that's been hotly debated here is the impact of FXAA. It should be noted that with FXAA off (no AA whatsoever), the R9 290X runs at 152 FPS vs. 149 FPS for the GTX 770. In other words, it's not that FXAA is running slowly on AMD cards, but that AMD cards run slowly, period. The only way to change this is to turn on MSAA, which hammers the card hard enough for the R9 290X to brute force its way past the GTX 770.
I received absolutely no compensation or consideration of any kind, implied or overt, from AMD. I was paid a standard fee by ExtremeTech for my work. The hardware I used for this comparison was hardware I already had on hand. It is not my property, but the property of my employer.