Latest News Posts

Social
Latest Forum Posts

NVIDIA GeForce Users Stonewalled with Tomb Raider

Posted on March 5, 2013 5:10 PM by Rob Williams
Bookmark and Share

It’s not a good day to be a just-released AAA game, it seems. EA’s much-anticipated SimCity has been experiencing a number of game-breaking issues, and as we can now see, Crystal Dynamics’ Tomb Raider isn’t too far behind – at least for NVIDIA users. Complaints have been spreading through the Web from those experiencing issues with the game, and a common factor between most of them has been the use of a GeForce card. Our own Brandon Mietzner, who is currently reviewing the game, is one of those victims.

Tomb Raider 2013

We pinged NVIDIA to find out if the company was aware of the wide-spread issues, and not surprisingly, it is.

We are aware of performance and stability issues with GeForce GPUs running Tomb Raider with maximum settings. Unfortunately, NVIDIA didn’t receive final game 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.

Please be advised that these issues cannot be completely resolved by an NVIDIA driver. The developer will need to make code changes on their end to fix the issues on GeForce GPUs as well.

As a result, we recommend you do not test Tomb Raider until all of the above issues have been resolved.

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 think it’s safe to say that this is why we didn’t see a mention of Tomb Raider in NVIDIA’s latest GeForce driver release. While it’s nice to see that NVIDIA isn’t at fault here, it’d almost be better if it was the one with control over the problem, as game developers are not always quick with patching up important issues. From NVIDIA’s wording, it seems that lowering the game’s detail could help solve the issue – but that’s hardly a fix. Let’s hope the real fix comes sooner than later.


  • Kayden

    I did try lowering my game to the preset of High and even though it didn’t crash like it normally did with the Ultimate (no tressfx), it did softlock several times while salvaging or in combat but the worst was when Laura sat down and she read her first diary entry it took around 15 seconds for it come back even though the audio was playing so I would say it’s still not playable.

    I do appreciate that Nvidia is talking to us about it though, not something that normally happens and is greatly appreciated.

    • http://www.facebook.com/deathspawner Rob Williams

      I am thinking that NVIDIA had little choice but to come out and say something, because it doesn’t look good with a brand-new game only has issues on YOUR GPUs.

      Was there ever a time when games came out and they just worked? I think I am so used to trouble-shooting every game I play lately, that I forgot the times when it could have been easier.

  • Otavio Galileu

    My 680 sounds like an airplane when I’m running the game. It just manages to reach 59fps on the benchmark with all settings maxed (except for the hair, which seems to cut around 8 to 10 fps from the performance). But while playing the game I can notice some areas where the performance suffers much more.
    There was also a part where if my tessellation was turned on the game would crash.

    • http://www.facebook.com/deathspawner Rob Williams

      Oi, I was hoping the 680 would be able to max this game no problem, but I guess it is kind of a good thing that we’re still getting games that push our hardware hard.

      I’m going to hold off for a week or so before I dive in, ideally until after this current mess is sorted out.

      • Kayden

        I think it’s cause Nvidia had no prep like you said before, if they had I think the drivers would have something in place for it. This happened to me on another game when I didn’t realize my card didn’t support the DirectX version it was trying to run. It is something I think Nvidia can fix and just hope it’s sooner rather then later, I would like to see how that tech looks and performs.

  • http://www.facebook.com/people/Xeridian-Darkmoon/100000549499324 Xeridian Darkmoon

    I’m pretty sure this is payback to Nvidia for stealing files and employees from AMD! lmao
    You don’t see the TressFX hair with anything but AMD cards anyway and the physics of it is amazing!

  • http://www.facebook.com/people/Xeridian-Darkmoon/100000549499324 Xeridian Darkmoon

    Just a thought for everyone, most of the new games that will come out for the next gen consoles will be PC games ported down to the consoles and optimized for AMD cards since the new consoles ALL have AMD chips in them. Have fun with those GTX Titans! :D

    • http://www.facebook.com/deathspawner Rob Williams

      Haha, it’ll be interesting to see.

  • anonymous1436

    of course, if both the d3d api and the driver api were more closely adhered to by game devs/driver devs, this would happen much less often. Also, all those speed hacks added to drivers destroys compatibility once a title is old enough to leave the attention span of developers (game and driver).

  • DarkStarr

    Sorry but….. I am just here for the lulz. I enjoyed the comments greatly.

Recent Tech News
Recent Site Content
Advertisement