LordOcidax
Member
Patches come out early on steam, At least for Rise.
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
DX12 update for Tomb Raider out now
- Thread starter Xyber
- Start date
DeepEnigma
Gold Member
i have a similar pc, its no stuttering for me apparently just crashing
But i got a 20% boost on dx12, from 44~ to 52~
Im running very close to locked 60 in the area I'm testing with dx11, runs worse in dx12 due to pauses but can't get RTSS to show me the fps in dx12.
SliChillax
Member
Any pics showing VXAO compared to the normal game?
capitalCORN
Member
Just tried the benchmark for dx11 and dx2 on my 3770k and 780ti(all factory settings atm).
All settings very high except for high on texture quality, sun shadows, shadow quality, and level of detail(settings reduced due to rampant stutter due to VRAM). Also no AA.
DX12 nets a small 3-5 fps average on the benchmark. Averaging 55+fps on the aggregate.
Might try again with overclocking.
All settings very high except for high on texture quality, sun shadows, shadow quality, and level of detail(settings reduced due to rampant stutter due to VRAM). Also no AA.
DX12 nets a small 3-5 fps average on the benchmark. Averaging 55+fps on the aggregate.
Might try again with overclocking.
You know if you don't know, you could just not answer.
VXAO implementation needs more direct link to nvidia's software (like sli profiles) as of this moment uwp isn't feature advanced enough...
EDIT: Here is the correct info
How was I wrong? The windows store uses UWA, which Nvidia's software cannot access?
SliChillax
Member
Crashes on start for me too, i7 5820k 980ti 16gb ram. Was working wonderfully before the patch.
My apologies i interpreted your comment incorrectly.
Gormenghast
Member
It's now expected that DX12 runs worse than DX11 on Nvidia. The signs have been there for months.
It would be more interesting to see:
- How AMD performs
- To run the benchmark in the Steam version and UWA to see if they perform differently
It would be more interesting to see:
- How AMD performs
- To run the benchmark in the Steam version and UWA to see if they perform differently
Dictator93
Member
According to NV, they fixed it and re-released the latest WHQL branch.
VXAO is off in DX12.
Gormenghast
Member
With the latest AMD driver (16.3) installed, I'm getting slight improvements on an R9 Fury (1080p):
DX11 Overall: 57.91
Mountain Peak: 60.00
Syria: 58.48
Geothermal Valley: 55.34
DX12 Overall: 59.27
Mountain Peak: 58.09
Syria: 59.87
Geothermal Valley: 59.95
The Geothermal Valley definitely felt quite a bit smoother on DX12 (at least in the benchmark, haven't tried it in gameplay yet).
With the previous driver, I did get about 8FPS less on average with DX12, though, so I guess those who're getting worse performance on AMD GPUs with DX12 are still on the old driver.
Gormenghast
Member
1-2% improvement is HUGELY disappointing, tho. It should be 15-20%
Imagine developers working for months to port the engine... and the result is a 2% improvement? It's absurd.
If all that time was simply spent on optimizing better DX11 there could have been a huge boost.
At this point spending resources on DX12 would be simply a waste of money and time if that's the result. Plus negative performance on Nvidia.
It's only available on DX11 and only on Nvidia cards. Should be in the graphics menu under the Ambient Occlusion setting.
Still it seems unfair that Steam users get to break all their shit before MS Store users. Bleeding edge is so fun though..
General Lee
Member
It's in the Ambient Occlusion setting after HBAO+. Only available on DX11.
Like previously quoted, VXAO is an Nvidia GameWorks effect, not a DX12 specific thing.
The benchmark seems to give me better min framerate in Geothermal Valley scene, but using Shadowplay FPS counter it looks like during normal gameplay there was still some performance loss. My guess is you need to be severely hampered by CPU for the current DX12 implementation to be beneficial in this game. So AMD CPUs and slower/non-oc Intel CPUs might see gains, for the rest it's better to stick to DX11.
jim2point0
Banned
ISee
Member
DouglasteR
Member
Typical Nvidia Tech. Twice the price, same product.
KainXVIII
Member
Yeah, same will be with Vulkan i guess.
Wow, so salty before even understanding the situation.
Balmung421
Member
Does DX12 and Gsync not get along?
Insumatposa
Member
How is the new DX12 patch for TROTT performing especially with VXAO? Can someone post some screens for comparison?
shortsFortallPeople
Banned
I lose about 6-7 frames using the same settings on dx12 with a 980.
I guess that's to be expected
I guess that's to be expected
I think UWA doesn't allow vendor specific features, given its theme for unification, so that's understandable that they don't have VXAO there.
Diablohead
Member
windows apps were really not designed to be used for huge games, I think it's silly that microsoft are even trying.
15-20% is probably too much overall to expect, but in any case you shouldn't expect this things to work instantly well. There are usually a lot of growing pains (DX10 especially took a while to get running, and generally was less stable throughout the games, or like the overall move to this generation on consoles). For the full effect developers simply need more time to iterate and start designing for the target platform.
Maxey
Member
I have an Intel i5-4690K 3.50Ghz, 8 GB DDR3 and a Radeon HD7870 2GB GDDR5 and I decided to make a comparative benchmark with the game set to the lowest graphical settings but for some reason DX12 mode caps the game to 60fps even with vsync off, so I'm not sure if I got a proper comparison done.
DX11 results:
DX12 results:
So what's the deal here? DX11 still seems better even with my lower end card.
DX11 results:
DX12 results:
So what's the deal here? DX11 still seems better even with my lower end card.
Maybe it's meant to be run on nvidia cards. Like many pc stuff, sad and unfair but you should be used to it.
Dictator93
Member
Look at your minimums... the framerate is so much more stable in dx12 interestingly.
People in this thread in general have to stop looking only at the averages and maxes.... those do not represent gameplay/frame quality. But the average depression you are seeing is untypical, I imagine it is a compat problem at the moment, your min frames should be higher as they are, but you should not see such a depression.
I'll Repeat.
The minimum frame rates are almost as important as the average frame rate. If you have acceptable averages, the next thing you should check are your minimums as there is no point in having 87 fps on a monitor that doesn't support it.
The results of the original poster are actually pretty good, hovering consistently around 50s. no matter the scene. By contrast the dx11 results are all over the place. This Dx12 implementation is going to take a bit of work, but with some optimization a person is potentially in a much better position.
