TaintedSquirrel
[H]F Junkie
- Joined
- Aug 5, 2013
- Messages
- 12,689
Dying Light driver would have been nice, especially since AMD took so much bad press for that game.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
... yes?? I mean if you've waited three months what does it matter?
I think "unsupported garbage" is a bit strongly worded. What problems are you having? Very little has been released in the last couple of months after the holidays anyway.
Downsampling wasn't introduced as a major driver feature before NVIDIA added DSR last year. Now both AMD and NVIDIA support it, although NVIDIA's version works better currently in terms of support. So I'm not sure that's the best example of your point.Personally, for myself, I've been frustrated consistently and steadily since I switched over to AMD at the lack of very basic functions I've had since the mid 2000's (Probably earlier! but that's about when I switched seriously to PC gaming) like setting a custom resolution and downsampling.
So, yay! AMD does the bare minimum for all but their flagships to work, and for their flagships, seemingly, they do slightly above the bare minimum required for them to work! I'm really, really frustrated with the general driver support of these things. They basically don't go out of their way to do anything. It FEELS like the budget option. They ARE the budget option, and they FEEL like it. That's just sad.
Downsampling wasn't introduced as a major driver feature before NVIDIA added DSR last year. Now both AMD and NVIDIA support it, although NVIDIA's version works better currently in terms of support. So I'm not sure that's the best example of your point.
I've used NVIDIA and AMD GPUs pretty extensively and the only thing I really like about NVIDIA's drivers over AMD is the ability to force AA in a wider variety of games using NVInspector. Other than that, they are pretty much on par for features.
Radeon Pro does work, but I had better success with a wider variety of games under NVInspector. That said, once DSR and VSR are more broadly supported, it will be kind of a moot point. I can run 3800x1800 on my 290Xs now, which is pretty good.You can also use Radeon Pro for AMD drivers to do everything that NVinspector does for Nvidia cards.
Downsampling wasn't introduced as a major driver feature before NVIDIA added DSR last year. Now both AMD and NVIDIA support it, although NVIDIA's version works better currently in terms of support. So I'm not sure that's the best example of your point.
I've used NVIDIA and AMD GPUs pretty extensively and the only thing I really like about NVIDIA's drivers over AMD is the ability to force AA in a wider variety of games using NVInspector. Other than that, they are pretty much on par for features.
You can also use Radeon Pro for AMD drivers to do everything that NVinspector does for Nvidia cards.
Yeah but there won't be any new features added. And it still doesn't do everything ATT did.it still works fine.
I honestly never considered using custom resolutions and downsampling until maybe a couple of years ago. I can understand why people consider it a big deal now, but I don't think it's anything that was on either company's radar since you could do SSAA just fine. It also wasn't until the last 3-4 years - when consoles really started to hold back PC gaming - that we had enough extra power to downsample games effectively.Actually, you've been able to downsample manually with Nvidia's drivers for ages. Years upon years upon years and make custom resolutions. Again, for years and years and years.
Doing the same two things on AMD requires CRU for custom resolutions (Which also, for whatever reason, breaks HDCP), or freaking HEX EDITING to downsample. I don't even know if the hex editing even works anymore. It was obtuse as hell that that had to even be a thing.
Aside from that (Which I really, honestly, do consider fairly major things), my experience with AMD has been fine enough. Just slow as hell to do anything, and something that should seem like... something ultra basic (CUSTOM RESOLUTIONS) should be there.
YAt least RP still works, and will be updated to stay working. That's better than nothing.
yes, John has stated he will update it if drivers break it.
Personally, for myself, I've been frustrated consistently and steadily since I switched over to AMD at the lack of very basic functions I've had since the mid 2000's (Probably earlier! but that's about when I switched seriously to PC gaming) like setting a custom resolution and downsampling.
Custom resolutions have been possible through CCC for... ever. What are you on about?
Unless there's some magic option I'm not seeing, where? Show me, because I sure haven't found it.
Well, there is an option to create custom resolutions within the specifications of your monitor. IIRC I used it once to lop a pixel off my screen to correct a screen rendering anomaly in some game (Crysis 2?).
Open CCC - Click on My Digital Flat-Panels - Click on HDTV Support. On the right, where it lists resolutions and refresh rates, there is a button labeled "Add". It opens a screen where you can experiment.
Edit: But, yeah, no downsampling.
For me, there's no reason to continue buying AMD cards.http://www.tomshardware.com/reviews/dying-light-benchmark-performance-analysis,4060.html
I guess its over. Even Toms reviews a game and says just get an Nvidia card as it’s cheaper and works better with no mention that I saw of NVidia not playing fair. If Nvidia and its GameWorks is really doing what AMD says then AMD needs to take some f**king action.
http://www.tomshardware.com/reviews/dying-light-benchmark-performance-analysis,4060.html
I guess its over. Even Toms reviews a game and says just get an Nvidia card as its cheaper and works better with no mention that I saw of NVidia not playing fair. If Nvidia and its GameWorks is really doing what AMD says then AMD needs to take some f**king action.
Techspot's game benchmarks are garbage... all of them.
Their numbers are always too high.
http://www.tomshardware.com/reviews/dying-light-benchmark-performance-analysis,4060.html
I guess its over. Even Toms reviews a game and says just get an Nvidia card as its cheaper and works better with no mention that I saw of NVidia not playing fair. If Nvidia and its GameWorks is really doing what AMD says then AMD needs to take some f**king action.
Extra cores beyond 4 don't make any meaningful difference, at least according to Techspot.
You may also want to look at Techspot's own benches, as they paint a very different picture from Tom's, at least when it comes to average FPS. 290X is second only to 980 at every tested resolution, and at 1600p it's basically tied with the 980.
Extra cores beyond 4 don't make any meaningful difference, at least according to Techspot.
You may also want to look at Techspot's own benches, as they paint a very different picture from Tom's, at least when it comes to average FPS. 290X is second only to 980 at every tested resolution, and at 1600p it's basically tied with the 980.
This limited how we could test Dying Light and in the end we benchmarked walking around two levels of the building where the game starts. Interestingly, the frame rates are much lower in-doors anyway, so this worked out well.
There are no quality presets in Dying Light so you must set everything up. For testing we maxed out every setting with the exception of Nvidia HBAO+ to try and keep the results consistant across AMD and Nvidia cards. That said, we did leave 'Nvidia Depth of Field' enabled.
Guru3D said:Our test will be the a level recording in the scene where you first go outside. This way you can mimic the test at home and compare a little. The benchmark can be quick or slow depending on your graphics card, resolution and image quality settings. Typically for a benchmark run there will be a scene rendered where the output of the number of frames rendered over time equals to an average framerate.
HardwarePal said:One of the most demanding areas of the game is when you exit buildings into the open world. That’s where I decided to start out the 60 second run that can be seen in the video below.
You have to compare OC vs OC for the 970/980 and that is where they shine. You guys are likely right that the 290x beats the 970 at stock, but once you OC the 970 should tie/pull slightly ahead. The ref 970 is ~1200 MHz, people OC it to 1500-1600. That's somewhere around a 30% OC.
The reference 980 is 24.x% faster than a custom cooled 290x according to [H]'s OC vs OC review.
My understanding is you can just turn off gameworks features. Although, the only game I actually tracked was FC4 where gameworks worked well on both platforms. Enhanced god ray supposively hit AMD a little harder but they just f' up your gamma anyways. To note, I am not a huge fan of gameworks... Always felt like it should be something being developed by the game engine creators.
I am not totally convinced it's not just AMD's incompetence though. Everyone likes to ignore all of Ubi's games are shit when they launch for everyone. SLi didn't work for a few weeks then nVidia patched it. Apparently AMD doesn't even release drivers for months. If nVidia didn't release drivers for months SLi would still be broken too.
GameWorks is a mandatory library of features that translate the game into usable code for the GPU. It is encrypted. AMD cannot see what is inside it. Thus they cannot write drivers for it. Nvidia writes the hooks that access the AMD drivers. Those hooks are within the encrypted GameWorks library. AMD used to brute force it, but Nvidia is using a different method of encryption now.
So what AMD does now is write a driver and allows developers to enable what features that they wish to. It is up to the developer / Nvidia to turn on CrossfireX, or whatever else they want. Notice that AMD only has problems with Nvidia GameWorks games. There is a damn good reason for this other than "AMD must be incompetent!"
If games like Far Cry 4 are high on your must be played list then I advise you to buy an Nvidia card.
GameWorks is a mandatory library of features that translate the game into usable code for the GPU. It is encrypted. AMD cannot see what is inside it. Thus they cannot write drivers for it. Nvidia writes the hooks that access the AMD drivers. Those hooks are within the encrypted GameWorks library. AMD used to brute force it, but Nvidia is using a different method of encryption now.
So what AMD does now is write a driver and allows developers to enable what features that they wish to. It is up to the developer / Nvidia to turn on CrossfireX, or whatever else they want. Notice that AMD only has problems with Nvidia GameWorks games. There is a damn good reason for this other than "AMD must be incompetent!"
If games like Far Cry 4 are high on your must be played list then I advise you to buy an Nvidia card.
You have to compare OC vs OC for the 970/980 and that is where they shine. You guys are likely right that the 290x beats the 970 at stock, but once you OC the 970 should tie/pull slightly ahead. The ref 970 is ~1200 MHz, people OC it to 1500-1600. That's somewhere around a 30% OC.
The reference 980 is 24.x% faster than a custom cooled 290x according to [H]'s OC vs OC review.
My understanding is you can just turn off gameworks features. Although, the only game I actually tracked was FC4 where gameworks worked well on both platforms. Enhanced god ray supposively hit AMD a little harder but they just f' up your gamma anyways. To note, I am not a huge fan of gameworks... Always felt like it should be something being developed by the game engine creators.
I am not totally convinced it's not just AMD's incompetence though. Everyone likes to ignore all of Ubi's games are shit when they launch for everyone. SLi didn't work for a few weeks then nVidia patched it. Apparently AMD doesn't even release drivers for months. If nVidia didn't release drivers for months SLi would still be broken too.