... Why is this a thing?!
It's not a thing. Yesterday I launched Doom over 20 times and nothing happened.
... Why is this a thing?!
I don't get it...
I put it on the "Low" preset and am still getting shitty framerates. This is both on Vulkan and OpenGL.
My PC:
![]()
![]()
And my settings I am currently trying, which seem to make almost no difference from Ultra...
Well in that case it might just be the fan. It is blowing downward right now. I can easily swap it without having to reseat the heatsink. I do have one of those upper case fans.
I'll take one when I get home.Yeah you have the fan in a bad position. Also what motherboard do you have so that we know it's mounted right. Mine is mounted where the fan either has to blow to the front of the case or back. Not up or down.
If your blowing the air down you are fighting the fans blowing hot air out and are blowing that hot air back at the processor. Heat rises so if it's situated in that position blow the air out with the fans. Ideally you would be having air from the intake fan blowing towards the heatsink and back out towards a fan blowing out of the case.
Try it with the fan mounted below but even then if your GPU has hot air coming up towards that fan it might still be blowing too hot of air on the heatsink.
post a picture if you can.
I can't remember exactly performance before vulkan. But it never really bothered me. I guess the lowest fps was 40 something.
Tried vulkan yesterday. 90% of the time above 100fps. Couple drops to 90s. Eyegasm.
Then motion sickness kicked in and i had to stop.
Is it "safe" to update my AMD drivers to the new beta? 'Cause Vulkan just crashed the game to me.
Have an R9 390 btw.
This is very good to know, thank you. I will Google that when I get home.There's a long thread on steam about this issue with the GTX 770 (and other 2 GB cards too). You can get back to normal performance by deleting some settingsfolders or reinstalling the drivers, google and you shall find it. It only happens when you fuck with the shadow settings though. Some sort of bug it seems.![]()
Vulkan benchmarks from computerbase.de
![]()
![]()
![]()
https://www.computerbase.de/2016-07/doom-vulkan-benchmarks-amd-nvidia/
Vulkan benchmarks from computerbase.de
![]()
![]()
![]()
https://www.computerbase.de/2016-07/doom-vulkan-benchmarks-amd-nvidia/
That Fury X jump. Fury indeed.
We need dr_rus to appear and spin this numbers.
Why do you need to try to turn this thread into a shit-fest? Jesus Christ, every fucking thread has to have someone basically baiting another user into posting vitriolic shit.
Stop.
Why do you need to try to turn this thread into a shit-fest? Jesus Christ, every fucking thread about AMD, NVIDIA, or game performance has to have someone basically baiting another user into posting vitriolic shit.
Stop.
As a side-note, I tried switching from TSSAA to SMAA+1TX to see if I'd gain any performance. I actually get 3 frames MORE if I use TSSAA.
Fun fact; neither Steam's screenshot mode nor Fraps likes Vulkan at all, so I can't post screenshots to prove it (Hell, Nvidia even broke desktop capture with Nvidia Share/Shadowplay in the most recent version, so I can't even record gameplay as proof), but my performance gains/losses vary on a level-by-level basis. The Foundry sees an 8-10% gain while Vega Central Processing (the most demanding level in the game) sees a 8% reduction in performance.
- CPU: i7 4770K 4.0GHz OC
- GPU: EVGA GeForce GTX 970 SSC
- RAM: Crucial Ballistix Sport 16GB
- OS: Win 10 Pro
There is a simple trick for shadow play.
1. Start Gefore Experience
2. Set the game to borderless window mode.
3. Alt+Tab to your desktop
4. start recording
5. alt+tab back to doom.
Ya see, that's what I NORMALLY do. But due to Nvidia being pillocks, now trying to do that with the latest version simply says "you must be running a supported game in order to record".
This may be that "5 launches per day" limitation that Denuvo has.
My Doom was at 60 FPS on Ultra before Vulkan and now with Vulkan on it's the same. Do I have to enable something in the options for an uncapped framerate?
Which drivers are you using? You must at least have Crimson 16.7.2 to play properly.
You mean 16.7.1?
Anyway, I updated and it's running perfectly, everything on max, 1080p@60 fps
i7 6700k
R9390
8 GB DDR4
No overclocks for the time being.
EDIT: Also don't quite understand what's async. Adaptive Vsync?
You mean 16.7.1?
Anyway, I updated and it's running perfectly, everything on max, 1080p@60 fps
i7 6700k
R9390
8 GB DDR4
No overclocks for the time being.
EDIT: Also don't quite understand what's async. Adaptive Vsync?
Fun fact; neither Steam's screenshot mode nor Fraps likes Vulkan at all, so I can't post screenshots to prove it (Hell, Nvidia even broke desktop capture with Nvidia Share/Shadowplay in the most recent version, so I can't even record gameplay as proof), but my performance gains/losses vary on a level-by-level basis. The Foundry sees an 8-10% gain while Vega Central Processing (the most demanding level in the game) sees a 8% reduction in performance.
- CPU: i7 4770K 4.0GHz OC
- GPU: EVGA GeForce GTX 970 SSC
- RAM: Crucial Ballistix Sport 16GB
- OS: Win 10 Pro
As a side-note, I tried switching from TSSAA to SMAA+1TX to see if I'd gain any performance. I actually get 3 frames MORE if I use TSSAA.
My bad im sorry, but take my word, it will happen.
Vulkan benchmarks from computerbase.de
![]()
![]()
![]()
https://www.computerbase.de/2016-07/doom-vulkan-benchmarks-amd-nvidia/
Never expect a AMD leading in a idtech game, Fury X definitely destory the geforce here, even the hot new 1070.
We need dr_rus to appear and spin this numbers.
Yeah, goes to show how much Async compute helps. As an Nvidia user, I can safely say that the brass at Nvidia HQ are probably eating their hats right now at not including it in hardware.
Yeah, goes to show how much Async compute helps. As an Nvidia user, I can safely say that the brass at Nvidia HQ are probably eating their hats right now at not including it in hardware.
There's nothing to spin. It's a known fact that AMD's OpenGL driver is garbage so this was expected. Or did you think that this is due to that async nonsense? It's not.
Asynchronous Compute. To put it into simple terms, it paces multi GPU threads in such a way as to minimize idle spaces in between workflows.
Ah I see. I'm using TSAA but don't see any async option, is it automatic?Async is Asynchronous Compute, currently only available on AMD cards but you have to enable the TSSAA option to enable it. Seems to be giving some pretty good performance over not having it enabled based on some of the benchmarks I have seen.
There's nothing to spin. It's a known fact that AMD's OpenGL driver is garbage so this was expected. Or did you think that this is due to that async nonsense? It's not.
Yeah, async compute provides rather minimal gains in Doom as well as in all other games where it's actually possible to turn it off:
https://www.youtube.com/watch?v=GlzKPBIjZPo - judging from that video I'd say it's ~+10-15% from async on in Doom on RX480 which is actually pretty good.
The gains Radeon cards are getting in Vulkan renderer comes from how much an improvement this renderer is over AMD's own OpenGL driver. NV don't have that problem with OpenGL so the gains are a lot smaller.
So..fury x > 1070? Is that expected as well?
AMD driver team must been doing wonders then.
It's not just about the relative gains on AMD because of shitty OpenGL drivers though. A Fury X destroying a 980ti, is that how it "should be"?
AMD driver team is truly doing "wonders" keeping their h/w this ineffective behind their DX11/OGL drivers. Vulkan and DX12 renderers remove the slow part of IHV's drivers and thus the performance gains you see isn't because of AMD's driver team, it's because of id's renderer programmers team.
As for Fury X being faster than 1070 and 980Ti - why wouldn't it? Fury X pure specs (flops, bandwidth) are close to 1080 so if a game can push them all out with the help of the new APIs it'll probably perform close to 1080 (unless its 4GB VRAM will become the main limiting factor).