Fixes coming for GeForce owners trying to play Tomb Raider

Tomb Raider

By on March 7, 2013 at 5:00 pm

We’ve already experienced the occasional crash and weird graphical artefact while trying to play Tomb Raider on our GTX670 here, and NVIDIA are on the case — but they need to collaborate with Crystal Dynamics to clean it up.

“We are aware of major performance and stability issues with GeForce GPUs running Tomb Raider with maximum settings,” claims NVIDIA’s Andrew Burnes on the GeForce web site. “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.”

Burnes also clarified that they would need time to collaborate with Crystal Dynamics on the fix. “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.”

15 comments (Leave your own)

Interesting. I’ve got a GTX 670, and I’ve had zero problems with the game. All settings maxed with the exception of TressFX. I’m sitting on 60fps, dipping down to 40 on some scripted events.

My main problem was the lack of camera x-axis inversion for controllers – something that’s becoming a more widespread problem with console ports as time goes by. Finally fixed it by re-wiring my controller, a stupid issue that should be able to be fixed in software.

 

Same here, it’s running very smoothly on ultra settings and I’ve only got a GTX570. Apart from some odd glitchy effects on program startup. Not sure what’s happening there, but once the game gets past the usual logos and onto the main menu screen the glitches never return, so it’s a non-issue.

 

vcatkiller:
Same here, Apart from some odd glitchy effects on program startup.Not sure what’s happening there, but once the game gets past the usual logos and onto the main menu screen the glitches never return, so it’s a non-issue.

I think the glitchy thing on startup might be intentional, it does the same thing on my PC. Just the startup splash screens.

 

Same here. Zero issues and no crashes and I’m running SLI 470s

 
Ralph Wiggum

Add another Geforce owner (SLI 580s) with no problems and TressFX turned off.

 

I haven’t had any stupidly low frame rates, and I’m using a GTX 670, running most settings maxed (aside from TressFX). Main things that got me a nicer frame rate were turning off post processing and tessellation. Turning off tessellation had a very minimal impact on visual quality, and a noticeable positive impact on frame rate.

 

Ive had several problems, but mainly just time to play is not there. But I received a crash when i got out of the first hole and walked across the tree bridge. and i cant click on ‘options’ on the splash screen, crashes. 670 gtx here, but tressfx on. Next time i play ill turn it off.

 

Gotta say, had no problems with sli 570′s, but serious kudos to nvidia for putting this out there. I’ll be impressed if tressfx gets optimized and doesn’t run like poo (can’t save it from looking like poo), but I’m still happy as it is.

 

I’m getting constant artificing with my 670 regardless of what drivers I use (which is meant to be a fix). I do have everything turned on though.

 

Got an GTX 660 Ti, works wonderfully with max settings, whilst disabling TressFX.
Comparing TressFX on and off, having it off made the hair movement more realistic in my opinion.
Oh well some people like eye candy.

 

leondalion:
Got an GTX 660 Ti, works wonderfully with max settings, whilst disabling TressFX.
Comparing TressFX on and off, having it off made the hair movement more realistic in my opinion.
Oh well some people like eye candy.

Yeah – I’m with you on the hair movement. Rendering is really nice, motion – not so much.

 

If you have any problems, try turning tessellation off first. This fixed my crashing straight away. Nvidia can’t really blame Crystal Dynamics for this because (I’m assuming) AMD would have been only provided the final code at release also, and they are not experiencing any issues.

 

kaivaal:
Nvidia can’t really blame Crystal Dynamics for this because (I’m assuming) AMD would have been only provided the final code at release also, and they are not experiencing any issues.

AMD and CD have been working closely together to get TressFX working, and I would think it more likely CD changed something in the code to get TressFX to work for AMD. They left nvidia out of the loop, but not any ones fault, more due to the need to release the game on time.

 

submariner: AMD and CD have been working closely together to get TressFX working, and I would think it more likely CD changed something in the code to get TressFX to work for AMD. They left nvidia out of the loop, but not any ones fault, more due to the need to release the game on time.

It’s quite common for either AMD or nvidia to work with developers “exclusively”. Usually resulting in optimized drivers before the game release then the other “catches up” in performance.

However, this almost never results in a game hard crashing due to lack of input. That’s just bad coding. This is entirely on the heads of Crystal Dynamics. Partnership or not, how do they not test for nvidia hardware in QA before release? A performance drop is one thing, but hard crashes is another thing altogether.

I was playing fine (on a GTX580) for over an hour then everything stops and I couldn’t even bring up task manager to kill the process. This was with TressFX off (found the visual/framerate trade-off wasn’t worth it). Had to launch an invisible command prompt window to reboot the box :/

 

The weird graphical artifact is a Tessellation bug with Nvidia cards, it was also present Deus Ex: Human Revolution which uses the same engine.

Hopefully they can get all this sorted out, would be nice to play the game on my Nvidia card without the TressFX performance hit and constant crashing using DX11 Tessellation.

 
Leave a comment

You can use the following bbCode
[i], [b], [img], [quote], [url href="http://www.google.com/"]Google[/url]

Leave a Reply

PC Gaming Calendar 2014

Follow Games.on.net

YouTube

Steam Group

Upcoming Games

Community Soapbox

Recent Features
Civilization: Beyond Earth

Civilisation: Beyond Earth shoots for the stars but lands on the moon

Firaxis make some great strides, but not everything in the future is always better.

Borderlands: The Pre-Sequel

Borderlands: The Pre-Sequel’s great humour carries it through

It may feel like the world's biggest piece of Borderlands 2 DLC, but the Pre-Sequel has a flavour all its own.

The Evil Within

The Evil Within: It’s a fine line between pleasure and pain (especially on PC)

We check out Shinji Mikami's latest punishment simulator, but buyer beware when it comes to the PC version.

Shadow of Mordor

Choose your own adventure: Why heavily scripted cinematic games need to loosen up

It's time for game developers to sit back and let the players take control.

world of warcraft warlords of draenor

World of Warcraft’s Tom Chilton talks Warlords, paid level 90 boosts, and jumping the shark

WoW's Game Director explains how they've been on, off, and all around the shark since 2004.

Streaming Radio
Radio Streams are restricted to iiNet group customers.

GreenManGaming MREC

Facebook Like Box