CambriaRising
Member
Any fix for the black spot artifacts caused by tessellation? The Hitman fix didn't remove that part of it for me.
can someone explain what double buffering and triple buffering does?
Double buffering means that your framerate will be locked to a multiple of your monitors refresh rate.
So if you have a 60hz monitor your framerate will be either 60, 45, 30, 15 or 0 with no gradient in between.
Triple buffering unlocks the framerate up to your monitors refresh rate but can introduce some (very) mild input lag. It's the way to go unless you're super sensitive to that stuff.
thanks. that helps.http://en.wikipedia.org/wiki/Multiple_buffering
Double buffering sucks, because if you can't maintain a locked 60, it will drop all the way down to 45, or 30, or lower. Always an even number like that. Even if you're hitting 59fps with DB on, you will be seeing 45 frames per second.
Use Triple Buffering unless you have an extremely good reason not to.
Tessellation fix for nvidia users.
Download nvidia inspector
Open nvidia inspector
Delete Tomb raider 2013 profile
Find hitman absolution profile
Link tombraider.exe
Change if you want af, aa and so on
Press apply button
And now hopefully you have no crash anymore with tessellation on. Have worked for me now an hour with no crash, use to crash before after 1-2 minutes after activating tessellation.
Thanks goes to a guy on steam for this fix.
I got that far
If it wasn't for this thread, I would think it was a great port as well. I haven't had a single problem and I've been playing all day.But...but...PC Gamer tells me this a great port
http://www.pcgamer.com/2013/03/05/tomb-raider-pc-settings-overview-any-port-in-a-storm/
If it wasn't for this thread, I would think it was a great port as well. I haven't had a single problem and I've been playing all day.
Anecdotal evidence proves me to be in the minority, unfortunately.
Click the tool icon opposite "Driver Version".
http://en.wikipedia.org/wiki/Multiple_buffering
Double buffering sucks, because if you can't maintain a locked 60, it will drop all the way down to 45, or 30, or lower. Always an even number like that. Even if you're hitting 59fps with DB on, you will be seeing 45 frames per second.
Use Triple Buffering unless you have an extremely good reason not to.
So everyone is getting huuuuuge framerate drops during cutscenes with TresFX? Am not alone in this right? GTX 670
Yes, you are correct. My mistake.If I'm not mistaken, there's a slight misunderstanding here. With double buffering the framerate must divide evenly into the refresh rate, so assuming you have a 60Hz display and your PC can't keep up at all times, 60fps (60/1) becomes 30fps (60/2), which becomes 20fps (60/3), which becomes 15fps (60/4), and so on.
PS. For extra credit, relate this to how/why doublebuffered applications always render at an integer divisor of the monitor refresh rate -- ie 60Hz, 30Hz, 20Hz, 15Hz, 12Hz etc.
Go on![]()
Is just plain "Tomb Raider" the same as what you guys are calling "Tomb Raider (2013)" in Nvidia Inspector? Because I don't see a "Tomb Raider (2013)
I'm on 314.07![]()
Is just plain "Tomb Raider" the same as what you guys are calling "Tomb Raider (2013)" in Nvidia Inspector? Because I don't see a "Tomb Raider (2013)
Results may vary. Runs practically flawlessly for me on a GTX 590, 16GB, i7-2600k @ 4.4ghz. Except for TressFX, but everyone knows that. Maxed out (w/out TressFX) mostly locked 60, except for some HUGE areas. Not a single crash in ~6 hours of gameplay. Even with Tessellation and Exclusive Fullscreen enabled on an Nvidia card, which seems to be causing most of the crashes/issues. I also have not even had to mess with Nvidia Inspector, thankfully, it all just works.Soooooo I'm a bit late to this party, but with my 670 seems like I'll hold off til a driver update *and* an actual game patch, based off that nVidia quote a few pages back.
Soooooo I'm a bit late to this party, but with my 670 seems like I'll hold off til a driver update *and* an actual game patch, based off that nVidia quote a few pages back.
Soooooo I'm a bit late to this party, but with my 670 seems like I'll hold off til a driver update *and* an actual game patch, based off that nVidia quote a few pages back.
So everyone is getting huuuuuge framerate drops during cutscenes with TresFX? Am not alone in this right? GTX 670
so, anyone here know what in the world the 'High Precision' setting is/does?
Just guessing from the name (I don't have the game yet) I'd say it uses 16 bit per component (instead of 8 bit) buffers for the rendering/postprocessing. If so, you should see the largest difference in HDR effects, and maybe some postprocessing-induced banding without high precision.
.High Precision: This poorly defined name describes a feature that adds darker shades and different intensities of light to the game. In short, it makes the game look more realistic. Major performance hit.
Wow, screens do NOT do TressFX justice. It's so impressive I actually sacrificed 1080p for it. With a GTX 560M it's either Ultra 720p or High 1080p
Wow, screens do NOT do TressFX justice. It's so impressive I actually sacrificed 1080p for it. With a GTX 560M it's either Ultra 720p or High 1080p
Whatever floats your boat, man, but damn.
Ok I can launch the game fine now....
It was fraps for some reason. If I had fraps open, the game wouldn't launch. Without it, it launches fine, then I can alt-tab and open fraps fine. Weeeeeiiiird.
Are you using SweetFX?
If you are, there is a clash with the overlay and SweetFX. I know there was this issue with MSI Afterburner. Not sure about FRAPS.
I don't use SweetFX and run into the same issue. It's definitely some sort of weird bug.
But...but...PC Gamer tells me this a great port
http://www.pcgamer.com/2013/03/05/tomb-raider-pc-settings-overview-any-port-in-a-storm/
Nope no SweetFX. I also seem to remember the game not liking Steam BP mode.